BSOD Win 7 Pro 0x0000000A on 3 HP Machines

[pcts]

Hi there

We are getting intermittent BSOD's on 2 HP desktops and 1 HP laptop (Desktops are 3-4 years old, the laptop is 6 months old). We get the same 0A stop message (IRQL_NOT_LESS_OR_EQUAL).

Happens - 3 times a week on one of the desktops (no real pattern on times of day)
Happens - every 2-3 weeks on the laptop - (no real pattern - could be different days)

There was no C:\Windows\Minidmp folder on any of these computers and we had the MiniDmp settings set as per your article on this forum. We then manually created a Minidmp folder and still no dmp file saved to it or anywhere else on the machine when it bluescreened. Regardless of whether we enabled the Automatic restart setting or disabled it - the PC would not restart and would stay stuck on the bluescreen.

Attached is a photo of the bluescreen.

One of the desktops gives a black screen when driver verifier is enabled and PC rebooted.
Laptop works fine with Driver verifier.

We have found no way to replicate the bluescreen.

Any help/advice you can give us is greatly appreciated.

Thanks and Kind Regards
PCTS

 

[pcts]

Hi there

Just as I post this my colleague has found a possible hotfix that we will try to see if it will resolve the issue. We will update this post over the coming week or so once we test it. https://support.microsoft.com/en-us/kb/979444

We appreciate any other advice users have if they have encountered this in the past.

If anyone has any tips on how to get the bluescreen minidmps to create that would be very helpful also. Maybe its just for this bluescreen. I might try and force a different bluescreen to see if we get any dmp files.

Thanks
PCTS

 

[Laith]

Hiya and welcome to SevenForums!rb:
Please follow the Blue Screen of Death (BSOD) Posting Instructions

 

[pcts]

Hi all

We have tested the hotfix above but no versions of it are applicable to this Windows 7 SP1 computer. :-( I think the hotfix comes included as part of Windows 7 SP1.

As we can't get the memory dumps working - I ran a Microsoft Windows Memory Dump configuration tool which changed some of the settings back and restarted the machine. Auto restart is now enabled, kernel dump is selected and path %systemroot%\MEMORY.DMP. Before this we had auto restart off and small memory dump enables and path %systemroot%\Minidump and no dmp files were created.

We will revert back if this has helped create any dmp files.

@Laith - I have attached the dm log collector logs at the current state.

Thanks
PCTS

 

[Laith]

Please follow these steps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[pcts]

Hi there

Thanks we had followed those before but I have ran the reg file for the small memory dump and restarted the machine.
Will keep you posted.

Thanks and Kind Regards
PCTS

 

[Laith]

Okay.

 

[pcts]

Hi there

The W7PRo desktop PC bluescreened again last night but there was no logs. The bluescreen says "initialising disk for crash dump..." at the bottom and then no more lines. So it appears the root cause of the bluescreen is also stopping the disk from taking a log. What might cause this I wonder?

This is the same issue we are seeing on the other Windows 7 Pro laptop. Both are AMD CPU and AMD Graphics albeit different AMD models.

We forced a bluescreen earlier as a test on the desktop (stopping the crss.exe process) and it bluescreened and did capture a log so we know the memory dump config is correct.

Could it be a memory leak over time? We have replaced the HDD and RAM in this machine also but no joy.

On the laptop and desktop when we ran driver verifier - and enabled everything but Low Resource simulation and enabled all non microsoft drivers as per your article it freezes to a black screen after the starting windows logo disappears. We don't know if the cause of the black screen is related to the cause of the blue screen but we can't replicate a bluescreen. It only happens over time.

On the laptop so far - when we untick the I/O verification and IRP Logging and Force pending I/O which are all dependent on each other it seems - we don't get a black screen and Windows loads fine. Not sure why this is yet?

Thanks and Kind regards
PCTS

 

[Laith]

Hmm, run SeaTools(DO NOT RUN FOR SSDS) http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[pcts]

Hi there again

Ok we figured out the black screen on driver verifier - with webroot ticked it black screens on login - it must not like the I/o verification or forced I/0 request.

Still no joy on replicating bluescreen. Webroot was only installed recently but the machines have been bluescreening with the same issue before it was installed so that rules out Webroot being the issue.

Is there any way to replicate a memory leak or is it possible to monitor and identify if memory is leaking?

Thanks
PCTS

 

[Laith]

Well you can run MemTest86+ and see if the memory is failing.

Run MemTest86+, It must be MemTest86+. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[pcts]

Hi there

We have replaced the memory with brand new RAM and its still causing an issue.

Trying to see if there is a way to spot a memory leak before it happens?

Let me know if you think of anything else.

Thanks
PCTS

 

[Laith]

I think this guide will help you out. https://msdn.microsoft.com/en-us/library/ms859415.aspx