Multiple BSODs, primarily concerning ntoskrnl.exe

[chartedlife]

Hello, I have had a slew of BSOD problems within the past year or so, they seem to come and go for the most part. I have tried a ton of things to pinpoint the problem but have not really be able to tell what exactly is causing the issue.

The BSODs will happen at random for the most part, sometimes during a game, others while doing nothing at all. To make matters worse a lot of times things will crash randomly, especially games, but sometimes even chrome tabs will just crash unexpectedly, these crashes tend to happen more often then a full on BSOD. My computer worked perfectly for the longest time after I built it but after a few initial BSODs it started to be quite unstable.

Things I have tried:
- Updating Drivers
- Re seating RAM (multiple times)
- Running on individual RAM sticks
- Memtest for 8 passes, 12 hours, no errors
- chdsk
- I have reinstalled windows once and seemed to make the errors less prevalent, but didn't cure it
- sfc /scannow says I have errors but cannot fix them, I am unsure how I go about this
- I do not run overclocked
- and some other irrelevant things

I tried running verifier but I couldn't get windows to boot properly, after showing the splash screen it would just go straight to a black screen and just hang there, didn't BSOD or crash, just froze there.

maybe you guys can provide some help

Thanks in advance!

 

[chartedlife]

any help?

 

[Dsprague]

Hello chartedlife, had a look through your files and I have the following trouble shooting steps for you to try:

Please update the following drivers:

SteelBus64.sys it can be updated here SteelSeries - Downloads

SAlpham64.sys also updatable from SteelSeries - Downloads

One of the earlier BSODs you had was a 0x124 which indicates a hardware error:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005198028, b4002000, 24000135}

Probably caused by : AuthenticAMD

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

inspecting the dump closer we see that it detected a problem when trying to read from the L1 cache on the processor:

kd> !errrec fffffa8005198028
===============================================================================
Common Platform Error Record @ fffffa8005198028
-------------------------------------------------------------------------------
Record Id     : 01cd533722e99327
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/26/2012 1:31:34 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80051980a8
Section       @ fffffa8005198180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Read
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100fa0
Processor ID  : 0x0000000000000001
Instr Pointer : 0x0x0000000077587b93

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80051980f0
Section       @ fffffa8005198240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000001
CPU Id        : a0 0f 10 00 00 08 06 01 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8005198240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8005198138
Section       @ fffffa80051982c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]DCACHEL1_DRD_ERR[/COLOR] (Proc 1 Bank 0)
  Status      : 0xb400200024000135
  Address     : 0x000000010da607b0
  Misc.       : 0x0000000000000000

now for this error please run prime95:

Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

 

[chartedlife]

I had updated the SS drivers about a day before posting so the driver was probably outdated in most of the dumps except for the newer ones that happened a few hours before posting, regardless I uninstalled SS engine and made sure to delete the .sys files and then reinstalled it to be perfectly sure.

I also ran Prime for 5 hours today without errors, I will probably run it for another 4-5 tomorrow as well, it didn't BSOD throughout the tests. However, I didn't expect it to as it seems to only BSOD about two times right next to each other and then be fine for the rest of the day, and it had already BSODed a few times today.

Will update tomorrow if the SS update helped.

 

[Dsprague]

Thanks for the Update.

 

[chartedlife]

Edit: nevermind it did decide to BSOD today during a Starcraft II match, win32k.sys PAGE_FAULT_IN_NONPAGED_AREA, I have attached the minidump file. I really hope I can get this crap sorted out.

 

[Dsprague]

Please run Furmark to test your graphics card:
FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature" (BurnIn test in newer versions).
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

let us know what the max temperature gets to, and if it has any errors.

 

[chartedlife]

As an update I decided to try memtesting the DIMM that I had previously deemed as "bad" by itself rather than with my other DIMM, it came up with 512 or so errors after about 9 hours, so I have taken it out to test stability, I will report back within in a few days if I have anymore BSODs. So as it seems it is definitely worthwhile to test individual sticks.

Thanks for the help so far

 

[Dsprague]

Fair enough let us know how things turn out.

 

[chartedlife]

So it seems I might still have issues, I started a blend test with prime95 at around midnight, at about 4am it BSODed and about 30 minutes before that it threw an error on prime itself.

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected (on an 869k test)

I have also included the dumpfile for the BSOD

 

[chartedlife]

I BSODed yet again playing Starcraft II today, another SYSTEM_SERVICE_EXCEPTION, any help on this? I have attached the dumpfile yet again.

Edit: I ran furmark and the temp maxed out at 75 degrees celcius, it didn't seem to have any trouble.

 

[Dsprague]

The stop code you are getting is the 3B:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff8000306db28, fffff88008a8aeb0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpWaitForResource+58 )

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

The ususal causes for this type of BSOD are:

System service, Device driver, graphics driver, memory

on that note please do these two things:

First please uninstall any Asus utilities that you may have installed as it seems that you have a driver known to cause BSods installed on your system that is part of many Asus utilities:

fffff880`043c9000 fffff880`043d1000   ASACPI   ASACPI.sys  
    Symbol file: ASACPI.sys
    Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys
    Timestamp:        Sun Mar 27 22:30:36 2005 (42476C4C)
    CheckSum:         00003C77
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table - ASACPI.sys

Also please run memtest86+ to check for problems with your ram, run it for at least 8 passes (do this overnight it can take a long time):
RAM - Test with Memtest86+

 

[chartedlife]

The only thing Asus I have installed is the general chipset for my motherboard, I have disabled that specific driver by renaming it to ASACPI.bak, hopefully this shouldn't cause any issues correct?

I will run another memtest on the DIMM that I am running on now tonight, will report with any more BSODs and memtest results when they are available.

 

[Dsprague]

I look forward to your results.

 

[chartedlife]

So after a couple weeks of stability testing, (still no memtest other than a 2 pass with no errors), my system seems to be a lot more stable but still BSODed three times during those two weeks.

I have included the dump files and will be doing a memtest soon enough.

 

[Dsprague]

I am honestly stumped, the new Dump files don't point to anything in particular, I am going to see if I can get other eyes on this.

 

[Dsprague]

OK thanks ot the advice of another BSOD analyst Please enable driver Verifier and allow it to crash your computer then post the new files here after the crash:

Driver Verifier - Enable and Disable

Tip: If you can not not normally into windows after enabling driver verifier please enter safe mode by pressing F8 before the windows logo appears during boot.

 

[Dsprague]

So it seems I might still have issues, I started a blend test with prime95 at around midnight, at about 4am it BSODed and about 30 minutes before that it threw an error on prime itself.

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected (on an 869k test)

I have also included the dumpfile for the BSOD

Not sure how I missed this post, but this result from Prime95 indicates hardware failure, it seems you alreaddy addressed the bad stick of ram that you had, however prime95has also pointed out a hardware level error.

 

[chartedlife]

Would that error be associated with ram due to being a blend test? I have ran many tests with small FFT's and it never threw an error.

I guess I will have to run memtest to be sure, I can try verifier afterwards if there are no errors.

 

[Dsprague]

It may have, in which case we are looking at either the failure of a ram module, or a ram slot on the mother board.