HP Prodesk 400 G7 SFF BsOD with ntoskrnl

[gavarnos]

Hi I've got a head scratcher for me, bluescreenview can't seem to find the culprit wonder if you guys can help, save me considerable time flattening it and reinstalling everything.

It's a HP Prodesk 400 G7 SFF, i7-10700, 32Gb ram 4TB SSD, 16TB HDD. Been working perfectly fine until I had to remove Adobe CC. I uninstalled using the app in settings then ran the CC removal tool, then the 24H2 update was installed. Since then I get a BSOD and reboot after about 6-7 hours of use. I come back to see the machine on the logon screen which is frustrating, its got things to do unattended. I was getting a visual C++ error connected to CCXProcess which I removed using autoruns but this reboot keeps occurring. Is it to do with 24H2 or Adobe being Adobe leaving rubbish behind?

I've run DISM, sfc, all good, looked at driver verifier, ran Windows memory diagnostic and memtest86 via USB, nada.

Thanks in advance,

Gav

 

[ubuysa]

There have been many more BSODs than just the two dumps that were uploaded. Where are the other dumps? Do you run a garbage cleaner? if so please exclude all dump files.

I can see you said that you had run the Windows memory diagnostic test, but I don't see the results in the System log (which is where they should be). The logs only go back to 6th December in any case, can you increase the size of the log file please? Expand the Windows Logs section, right-click on System, select Properties from the drop-down menu and increase the log size there.

The two dumps do very much look a though bad RAM is the prime candidate, both dumps fail during memory management operations. Since you have two 16GB sticks I suggest you remove one of them and run on just one for a few days, or until you get another BSOD. Then swap sticks and run on just the other stick for a few days, or until you get another BSOD.

If it BSODs on each stick on their own then we will discount RAM and move on.

 

[gavarnos]

I have run the Windows memory diagnostic with no errors. I ran memtest on a long test, 3 passes and it passed. I presume 24H2 wiped the logs from 2 days older but I'll increase the log size. I'll run memtest tonight on an overnight loop.

It's just extremely coincidental this happened during 24H2 and removing Adobe and it's associated detritius when its been working tip top for ages, I don't believe in co-incidences!

However I was going to get a pair of 32's for it anyway I'll get them ordered and get back to you, hopefully with more log files next time.

 

[ubuysa]

If you're going to buy more RAM, and we don't know that RAM is the problem yet, then please pay attention to the following...

• If the new 32GB RAM is in addition to the existing RAM then the new RAM must be exactly the same part number as the existing. Mixing RAM is know to cause problems.
• In any case, I would advise only buying RAM that is on the QVL for your motherboard.

Do please try removing one RAM stick at a time to see whether it only BSODs on one of them.

 

[gavarnos]

Thanks. The pair of identical 32Gb sticks are on order, the usual stock Crucial.

Though strangely enough I noticed I had an error with a particular torrent file in qbittorrent; I have removed the file off the app and so far I havent had single unexpected reboot since Sunday. I have done nothing else to it aside from increasing the log file size, bizarre.

 

[ubuysa]

Well...if it BSODs again run the Sysnative data collection app again and upload the new output file.