Memory_Management BSOD on Clean boot, VERY specific circumstances

philc43 said:

PxHlpa64.sys is related DVD burning software. The driver on your system has a date of 24/04/2012, I suspect it has been added by software you have loaded but I may be wrong. Might be worth removing it anyway.

What is the best way to find out what is using this file, I haven't knowingly installed any CD\DVD software. I just use Windows to write DVDs.

Here is a list of possible software I found from an old post on the SevenForums:

RecordNow!
ESSSONIC
Sonic RecordNow!/Sonic_PrimoSDK
Dell Media Experience
Pioneer RecordNow DX
Sonic MyDVD/RecordNow!/RecordNow DX/MyDVD Plus/PrimoSDK
Microsoft Plus! Digital Media/Digital Image Suite
Corel Photo Album
HP RecordNow/DigitalMedia Archive
IBM RecordNow!
Roxio Easy Media Creator/RecordNow Copy/Drag-to-Disc/Creator Basic v/Media Manager/CinePlayer
Adobe Photoshop Lightroom
Yahoo! Music Jukebox or Roxio
Napster Burn Engine
1CLICK DivxToDVD
OLYMPUS muvee theaterPack

Nope, none of them.

OK, well lets not get too distracted by it. Are you still running Driver Verifier? I would suggest you turn it off and continue testing without it. See the warning in the following tutorial:

https://www.tenforums.com/tutorials/5...dows-10-a.html

philc43 said:

OK, well lets not get too distracted by it. Are you still running Driver Verifier? I would suggest you turn it off and continue testing without it. See the warning in the following tutorial:

https://www.tenforums.com/tutorials/5...dows-10-a.html

Yes, I disabled DV. As the BSOD was on startup I had to disable it in order to get back into Windows. It's disabled now.

When I disable PxHlpa64.sys I receive an error in device Manage on my DVD-Writer saying "A driver (service) for this device has been disabled. An alternative driver may be providing this functionality. (Code 32)".

The puzzling thing is that this ONLY happens if I have two sticks of RAM in, yet I can't find any errors on the slots or the sticks, and there is no instability when the PC is running.

If I switch the PC off at the mains for a couple of hours after a clean shutdown everything is OK.

It "seems" to only happen if the PC has been switched off for a long period of time (Usually overnight). Which is why I thought that it might be the Paging file, yet I still had the BSOD if I disabled it.

Could this be caused by a piece of software or a service trying to update itself, or performing some kind of action when it determines that it's been in active for some time?

Quite a few of the BSOD dumps point to memory corruption or errors and so I would like to concentrate on that aspect. It sounds like you can run with one stick at a time with no problem. As soon as you run with two you have the errors. Which slots are the two memory modules using? Numbering the slots from 1 to 4 with 1 being nearest to your CPU fan, they should be in slots 2 and 4.

This is the output from Autoruns64, with everything that loads on startup.Attachment 88418

philc43 said:

Quite a few of the BSOD dumps point to memory corruption or errors and so I would like to concentrate on that aspect. It sounds like you can run with one stick at a time with no problem. As soon as you run with two you have the errors. Which slots are the two memory modules using? Numbering the slots from 1 to 4 with 1 being nearest to your CPU fan, they should be in slots 2 and 4.

I started with them in slots 2 and 4 (Slot 1 is blocked by the CPU fan, it's totally inaccessible). This was the configuration from the factory.

I then tried both sticks together in various combinations until I had exhausted all available combinations of sticks in all three available slots and it BSOD each time regardless of the combination.

I've tried all three remaining slots with stick 1 individually and everything was OK. I then tried all three slots with stick 2 on its own, and everything was OK.

I tried Memtest with each stick individually, and with both sticks in. It didn't find any errors.

The weird thing is that this only happens after a clean shutdown.

Thanks for your explanations. Can I ask you to do some more testing of the Shutdown process?

Please have a look at the following tutorial and concentrate on options 8 and 9 which give you various ways of shutting down the computer.
Shut Down Computer in Windows 10

Can you determine if there is any type of shutdown which does not trigger the problem? For example compare shutdown /p with shutdown /s and with shutdown /s /f /t 0