Various BSOD errors during normal use and sleep

[omegalisk]

Latest Error Message: PAGE_FAULT_IN_NONPAGED_AREA

Hi. I upgraded my computer a few weeks ago with a new motherboard, CPU, RAM, and SSD, and lately I have been having various BSOD errors. They seem to happen at random, and often I will come back to my computer with it having the BSOD error message up (or, before I changed it, the computer restarted saying that it crashed). I have updated my BIOS and reinstalled my drivers (with the exception of the Intel VGA driver which will not install). I have reinstalled Windows several times and updated to SP1 (I had trouble with errors when installing SP1, but those were fixed when I reinstalled Windows).

I have search around for an answer, both on these forums and through Google, but all the solutions to the problem seem to be specific to the computer and the dump, so I decided to make an account and a post. Any information would be useful! Thanks in advance!

 

[koolkat77]

Welcome to SevenForums..

Is the firmware of your SSD up to date?

[FONT="Lucida Console"]*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80002000000, 8, fffff80002000000, 2}

*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys

Could not read faulting driver name
Probably caused by : [COLOR="red"]athurx.sys[/COLOR] ( athurx+9f3bb )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80002000000, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80002000000, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c6100
GetUlongFromAddress: unable to read from fffff800036c61c0
 fffff80002000000 Nonpaged pool

FAULTING_IP: 
+0
fffff800`02000000 ??              ???

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002b638a0 -- (.trap 0xfffff88002b638a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002000000 rsp=fffff88002b63a30 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000f44 r10=fffff80003418000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`02000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000343d8e0 to fffff80003496fc0

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff800`02000000 ??              ???

STACK_TEXT:  
fffff880`02b63738 fffff800`0343d8e0 : 00000000`00000050 fffff800`02000000 00000000`00000008 fffff880`02b638a0 : nt!KeBugCheckEx
fffff880`02b63740 fffff800`034950ee : 00000000`00000008 fffff800`02000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x437f6
fffff880`02b638a0 fffff800`02000000 : fffffa80`40820089 fffff880`038af3bb fffffa80`00000000 fffff880`00004048 : nt!KiPageFault+0x16e
fffff880`02b63a30 fffffa80`40820089 : fffff880`038af3bb fffffa80`00000000 fffff880`00004048 fffff800`00000000 : 0xfffff800`02000000
fffff880`02b63a38 fffff880`038af3bb : fffffa80`00000000 fffff880`00004048 fffff800`00000000 00000000`00000000 : 0xfffffa80`40820089
fffff880`02b63a40 fffffa80`00000000 : fffff880`00004048 fffff800`00000000 00000000`00000000 00000000`00000000 : athurx+0x9f3bb
fffff880`02b63a48 fffff880`00004048 : fffff800`00000000 00000000`00000000 00000000`00000000 fffffa80`08636030 : 0xfffffa80`00000000
fffff880`02b63a50 fffff800`00000000 : 00000000`00000000 00000000`00000000 fffffa80`08636030 fffff880`02b63bdc : 0xfffff880`00004048
fffff880`02b63a58 00000000`00000000 : 00000000`00000000 fffffa80`08636030 fffff880`02b63bdc fffffa80`0667c840 : 0xfffff800`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athurx+9f3bb
fffff880`038af3bb ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  athurx+9f3bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athurx

IMAGE_NAME:  athurx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4daeb071

FAILURE_BUCKET_ID:  X64_0x50_BAD_IP_athurx+9f3bb

BUCKET_ID:  X64_0x50_BAD_IP_athurx+9f3bb

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

1: kd> lmvm athurx
start             end                 module name
fffff880`03810000 fffff880`039ee000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:       [COLOR="Red"] Wed Apr 20 16:07:45 2011 (4DAEB071)[/COLOR]
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4[/FONT]

Perform a clean install of the above Atheros driver.

METHOD:

Click on the Start rb: ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATHEROS & restart the computer. Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper

:ar: Atheros Driver:

If its wireless, match your device from here:

• ATHEROS Wireless drivers for Windows

If its not a wireless, match your device from here:

• ATHEROS Network drivers for Windows

Perform a System File Check:

• Click on the start rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Disk Check on your hard drive for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

If this does not bring stability, test the RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Let us know your results.

 

[omegalisk]

Sorry it took so long to reply; I was waiting to see if I got another BSOD.

Yes, my SSD firmware is current.

I did the two disk checks on both my drives and no errors were found.

I also reinstalled the Atheros driver from the website you linked, but that didn't seem to fix the problem (I am still getting BSOD's, but this time they don't have an error message. I am attaching the latest grab from the diagnostic tool here.

I did a basic memory check (no removing RAM) with memtest before on the new set of RAM and no errors were found, but I'll do the full one you posted just to make sure and edit this post with the results.

 

[koolkat77]

There are no .dmp files after the 26th of last month

 

[omegalisk]

That's odd. The crash screen I got said that it dumped the memory, but it wasn't the normal BSOD (it didn't have an error message and was longer). I just ran the diagnostic tool again and verified that there isn't a dump inside, so I'm not sure how to report the crash.

Also, I ran memtest for 8 passes on all my RAM with no errors found. I'll do the "individual RAM piece" tests tomorrow.

 

[koolkat77]

I will check the files again.

Do let us know the results from memtest.

 

[omegalisk]

Ok, I ran 8 passes on all the RAM and 6 passes on each stick, but it didn't find any errors. I just flashed an updated version of the BIOS; I'll see if that has fixed the blue screens.

 

[koolkat77]

OK, and after that we'll enable driver verifier.

 

[omegalisk]

I just got another "odd" BSOD with that:

1. Didn't have an error message
2. Dumped the memory somewhere but the diagnostic tool doesn't grab it
3. Didn't automatically restart after it dumped the memory (which I have it set to in settings)

It happened during various activities; I had music playing through Youtube, updating Visual Studio, and renaming a shortcut on my HDD. I'll attach what the Diagnostic Tool found, but it doesn't include the memory dump from the last BSOD.

 

[koolkat77]

Do you get BSOD-s in safe mode?

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Hard drive test both short and long with:

• SeaTools for Windows

Also the DOS version of:

• SeaTools for DOS
• SeaTools for DOS tutorial

 

[omegalisk]

I got two more BSOD's, and one of them created a dump file, so I'm attaching that to this post. I'm also attaching the screenshots you requested (the HDD has two screenshots to show all the values at the bottom of the program).

I ran all the tests you posted and none of them gave me any errors.

I'm not sure if it BSOD's in safe mode because it doesn't happen all that often and not in response to anything that I do (it is quite random). I ran the computer in safe mode for a day and no BSOD, but I haven't had one for a few days anyway.

 

[koolkat77]

Unfortunately the last dump is of 9th Jan'13. Configure the system for minidumps again.

PS: Have you reinstalled the OS after making hardware changes? Not sure if I've asked this earlier.

 

[omegalisk]

Does this zip have the correct dump? I just got another BSOD (while logging in) and then went into Safe Mode to grab the dump. I did the reconfiguring after, though.

Yes, I reinstalled Windows to the SSD. I actually had to do it several times, as I couldn't install SP1 because of a general error. I found that the only way to install it was to only install the networking driver onto my computer and then immediately install SP1 (and then install everything else).

 

[Vir Gnarus]

Just so you know OCZ brand SSDs have a very high ROF (rate of failure). Even though tests do not show up problems they often don't because the tests aren't very well structured on testing SSD drives. Keep that in mind as we approach this.

I recommend you remove the SSD drive, install Windows on one of the HDDs, and test stability. If things stabilize, you can return the SSD drive for a replacement. You may have to go through a few before you find a stable OCZ drive - you are paying for pure performance, not reliability. If you want reliability, you're going to need to go with a non-Sandforce controller Samsung, Intel or Crucial drive (Samsung being top-notch).

The crashdumps so far aren't showing a reliable pattern. You can try turning on Driver Verifier and let the system crash some more then send us the resulting crashdumps, as those may prove more reliable. However, if this is certainly been going on shortly after you installed the new hardware, then most likely one of them is bad, in which case these minidumps won't prove worth much in telling us what. Still worth a try.

 

[omegalisk]

I removed the SSD and did a fresh install of Windows to a 24GB partition on my HDD and got another BSOD. The only thing I had installed was Firefox, the core drivers provided by my motherboard's CD, and a few automatic Windows updates. I've attached the zip file.

I also tried installing Ubuntu to that same partition and got a few random system errors, so I don't think it is just Windows that is causing the problem.

Edit: Got another one after several Firefox crashes. I'm attaching a second zip file.

 

[Vir Gnarus]

Yes, it's a hardware issue. We won't be able to ascertain cause from crashdumps. You've already done thorough memory testing so the RAM seems fine. If you haven't already, it's time to test the CPU. Run Prime95 on Torture Test on Large FFT settings for a few hours (make sure CPU cooling is stable since this test produces tons of heat). Follow up with another run on Blend settings instead for a few hours, regardless if something bad happens with the first one.

If Large FFT runs fine for a while but Blend croaks, the CPU is more likely at fault. If it's vice versa, the motherboard is more likely at fault. If both are very bad in state, it could be either or, but more likely CPU. If your system BSOD's during a run, just do the other run and then send us the crashdumps so we can ascertain whether the BSOD was from Prime95 or from something else.

 

[omegalisk]

I ran both Large FFT and Blend. The Large FFT test lasted 2 hours until all cores failed, with the first core failing at ~1 minute. With Blend, the cores took quite a lot longer to fail, with the first core failing at 30+ minutes and the total test lasted >4 hours. I got a BSOD after 4 hours, so I'm attaching the crash dump.

 

[Vir Gnarus]

I'd start with replacing the CPU then, based on those results. It may be that there's some issues with the internal CPU caches that aren't getting hit with Blend settings until much later. Of course, mobo is still potential suspect here, but I'd still go with CPU first.

 

[omegalisk]

I just ran a longer Blend test. 1 core failed after 2 hours and the other three lasted >9 hours (I had to stop it after that).

Is there way to be more sure whether it is the CPU or motherboard? I don't have a spare CPU on hand (my last one was a Core 2 Duo, which doesn't fit), so I would have to go through Intel's warranty service since it's been over 30 days since I bought the hardware from Newegg. It's not much of a hassle to do this, but if it turns out it's the motherboard that is failing, then I would be left without the computer for several weeks while both items were shipped there and back. It's possible, as I can use the university's computers during that time, but it would be nice if I didn't have to.

 

[Vir Gnarus]

Nope. That's the problem with the CPU/Mobo/PSU trio (I call them the Trio of Trouble). All three are involved in nearly every activity on a system and all three share a very close relationship, so if one fails, it'll often show symptoms that makes it appear like any of the other two parts (or any other PC part for that matter). That's why in a hardware diagnostic lab, they will have a motherboard testing kit which is a diagnostic version motherboard that the tech will connect the potentially suspect PSU/CPU onto and run diagnostics. If they come up clean, the original motherboard is the offender. They also have PCI POST cards (punny) that can run diagnostics on a potentially suspect motherboard, but those things are quite old, and I'm not sure how they operate with today's mobos (if they even do). Either way, you're looking at a few hundred to a thousand bucks for the kits. Best to just do it the old fashioned way and swap hardware and cross fingers.