BSOD 6 times, usually while Idle - ntoskrnl.exe

Entropy42 · 14 Nov 2013

Computer has done this randomly ever since it was built. Sometimes it goes 1 day, sometimes it goes 2 weeks. It is on 24/7, and most of the crashes are while I am not working and it is just idling. Today it crashed while I was typing a post in Chrome.

Used WhoCrashed to find out that 5/6 crashes were ntoskrnl.exe, 1 was rt64win7.sys.
BugCheck names were: memory_management, bad_pool_caller, memory_management, system_service_exception, driver_irql_not_less_or_equal (rt64win7.sys), irql_not_less_or_equal

Have run memcheck and passed all tests with no errors.
After the rt64win7.sys/driver_irql_not_less_or_equal crash the BSOD said it was a tcpip.sys error so I updated my network drivers. Thought that fixed it as I had 15 days of uptime until today's crash.

Now I'm at a loss, hopefully someone can help.

Arc · 14 Nov 2013

Hi Entropy42.

First of all, Update your ATI/AMD display driver to the latest WHQL. It is too old.

Code:

fffff880`07e05000 fffff880`07e5a000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Oct 26 06:51:58 2011 (4EA760B6)
    CheckSum:         0005289A
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

The realtek network driver is not too old; but it is failing (on hardware?).

Code:

BugCheck D1, {8089, 2, 1, fffff88001a839c3}

*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : hardware ( Rt64win7+1ac84 )

Followup: MachineOwner
---------

Update it from Realtek ..... take the Win7 and WinServer 2008 R2 Auto Installation Program (the 4th one in the list).

Also, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

Entropy42 · 14 Nov 2013

Thank you very much for the advice. I've updated the drivers and will run memtest tonight (I did run it overnight in the past with no errors, but it was not a version that required a bootable USB/CD). It could be a while before I know if the problem is fixed, since I recently went 15 days with no crashes.

Entropy42 · 18 Nov 2013

Ran MemTest for the weekend, 19 passes completed, no errors.

Arc · 19 Nov 2013

OK, let us know for any further issue.

Entropy42 · 25 Nov 2013

Computer has blue screened twice since my last post. Apparently updating the drivers did not fix the issue. Updated SF Diag Tool dump attached.

Arc · 25 Nov 2013

It is hardware level failure.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f6be7c, fffff8800a8b1d30, 0}

Probably caused by : hardware ( nt!RtlpCopyAces+39c )

Followup: MachineOwner
---------

Last hardware failure was on rt64win7.sys, the onboard network adapter see post #2.

I would suggest you to RMA the motherboard.

Entropy42 · 18 Feb 2014

Rather than sending in the whole mobo, I disabled the onboard network adapter in the bios and put in a PCI-E network card. Still getting BSODs, but they have a huge range of bugcheck names. KMODE_EXCEPTION_NOT_HANDLED, SYSTEM_SERVICE_EXCEPTION, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, PAGE_FAULT_IN_NONPAGED_AREA.

They almost always occur when I am not even at my computer and it is just sitting idle overnight with the displays off.

Uptime between crashes still ranges from less than a day, to 12 days.

I've attached another zip from the SF Diagnostic Tool.

Arc · 18 Feb 2014

Entropy42 said:

I've attached another zip from the SF Diagnostic Tool.

Sorry?

I thought that the issue is identified, but as you want another check, I will do. Upload the data properly.

Entropy42 · 19 Feb 2014

Yeah, from the crashes I submitted before, you said it was a hardware problem with my onboard NIC, but I disabled that and am still getting the crash, so I was hoping someone could look at the more recent crashes and see what they indicate the problem to be. I updated the previous post with the zip file from the SF tool, is that data uploaded wrong?
Thanks for the help.