3 BSOD in a row; New SSD, RAM and Video Card

[Bizarro181]

I recently (last weekend) replaced my RAM, OS HDD and Video Card. Today is the first time I've experienced any problems but I've had three BSOD in a row. The first two were while watching videos in VLC and the third was while trying to post here. Attached is my system info from the sevenforums tool for the first 2 BSOD problems.

 

[x BlueRobot]

[COLOR=Red]BugCheck 24[/COLOR], {1904fb, fffff8800bf13ed8, fffff8800bf13730, fffff800038a1915}

Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerFileObjectContext+a5 )

Usual causes:  Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

2: kd> [COLOR=SeaGreen].trap fffff8800bf13f80;knL[/COLOR]
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=88fffa80105a8da8 rbx=0000000000000000 rcx=fffffa80508ba4b8
rdx=fffffa800abade70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800038a1915 rsp=fffff8800bf14110 rbp=0000000000000000
 r8=0000000000000000  r9=fffffa801fe53ac0 r10=fffffa800ab98b90
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!FsRtlLookupPerFileObjectContext+0xa5:
fffff800`038a1915 48395810        cmp     qword ptr [rax+10h],rbx ds:88fffa80`105a8db8=????????????????
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 fffff880`0bf14110 fffff880`012eab1f [COLOR=Red]nt!FsRtlLookupPerFileObjectContext[/COLOR]+0xa5
01 fffff880`0bf14150 fffff880`012e8852 fltmgr!FltpGetStartingCallbackNode+0x3f
02 fffff880`0bf141e0 fffff800`038a06a3 fltmgr!FltpPreFsFilterOperation+0xa2
03 fffff880`0bf14270 fffff800`03b56fe4 nt!FsFilterPerformCallbacks+0xd3
04 fffff880`0bf142d0 fffff800`038c2427 nt!FsRtlAcquireFileForCcFlushEx+0xd0
05 fffff880`0bf14570 fffff800`038c19bc nt!MmFlushSection+0x1c3
06 fffff880`0bf14630 fffff880`014dd654 nt!CcFlushCache+0x7bc
07 fffff880`0bf14730 fffff880`014d34cd Ntfs!NtfsFlushUserStream+0xb4
08 fffff880`0bf147b0 fffff880`014dbf48 Ntfs!NtfsFlushVolume+0x2ad
09 fffff880`0bf148e0 fffff880`014dc63c Ntfs!NtfsCommonFlushBuffers+0x444
0a fffff880`0bf149c0 fffff880`012e9bcf Ntfs!NtfsFsdFlushBuffers+0x104
0b fffff880`0bf14a30 fffff880`012e86df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
0c fffff880`0bf14ac0 fffff800`03b8ba9b fltmgr!FltpDispatch+0xcf
0d fffff880`0bf14b20 fffff800`03b20781 nt!IopSynchronousServiceTail+0xfb
0e fffff880`0bf14b90 fffff800`0387fe13 nt!NtFlushBuffersFile+0x171
0f fffff880`0bf14c20 00000000`77c0176a nt!KiSystemServiceCopyEnd+0x13
10 00000000`0191f548 00000000`00000000 0x77c0176a

The last instruction which was called, and where the interrupt handler broke in to save the context of the thread, and then produce a bugcheck was FsRtlLookupPerFileObjectContext, which is used by filter drivers to receive the context of a previous file object; a file object can refer to an actual file or physical hard disk. The IRQL level is fine here, so no functions were being called at the incorrect IRQL level.

2: kd> [COLOR=SeaGreen]!irql[/COLOR]
Debugger saved IRQL for processor 0x2 -- 1 (APC_LEVEL)

For crashes involving filter drivers, it is usually related to anti-virus programs or programs which perform interaction with FSD drivers.

From another bugcheck (Stop 0x1E):

0: kd> [COLOR=SeaGreen]lmvm sptd[/COLOR]
start             end                 module name
fffff880`0108b000 fffff880`011fe000   sptd     T (no symbols)           
    Loaded symbol image file: sptd.sys
    Image path: sptd.sys
    Image name: sptd.sys
    Timestamp:       [COLOR=Red] Sat Mar 03 16:45:52 2012[/COLOR] (4F524AC0)
    CheckSum:         0008CE54
    ImageSize:        00173000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Daemon Tools uses a driver called sptd.sys, which is known to cause BSODs with Windows 7. It is recommend you remove this program, and use Windows own in-built features or ImgBurn.

Reduce the number of programs at startup, to avoid any driver or program conflicts:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

 

[Bizarro181]

Hey BlueRobot,

Thanks. I uninstalled daemon tools as per your suggestion and used the SPTD installer to fully uninstall SPTD. I am confused as to if there is any action I should take with regards the first bugcheck. Currently I don't have an antivirus installed. I'm just running Windows Defender (Which is now having errors starting since the SPTD and Daemon tools uninstall...related?) and Microsoft Security Essentials.

Thanks
-Rob

 

[Layback Bear]

If you have installed Microsoft Security Essential for your anti virus it should of turned off the built in Defender.

Go to Start Orb and type in Defender and then tick on it. I should indicate it is turned off.
Have you completed all Windows Updates? This should be done.

 

[Bizarro181]

If you have installed Microsoft Security Essential for your anti virus it should of turned off the built in Defender.

Go to Start Orb and type in Defender and then tick on it. I should indicate it is turned off.
Have you completed all Windows Updates? This should be done.

Ah, okay. It is turned off. For some reason it autostarted at my last reboot.

-Thanks

 

[x BlueRobot]

Any more problems?

 

[Bizarro181]

Any more problems?

Hey, thanks for following up. Thinks looked to be going fine for a while but today I got another bluescreen, all the goods attached. I wasnt doing anything out of the ordinary, just web browsing and boom.

Anyway, I asked a friend and he seems to think that it's because I havent manually set the voltage and timing for my new RAM, but I've read that "Auto" settings are fine and the voltage and timing just effects the performance. Anyway, thanks.

Edit: mere moments after posting this I got another blue screen while shutting down my computer that said SYSTEM SERVICE EXCEPTION 0x0000003b

Another edit: Since my friend insisted, my RAM in now running at the recommended timings, voltage and frequency. So if that was indeed the problem, hopefully it wont be anymore

 

[x BlueRobot]

Okay, hopefully your system will remain stable, but I'll look at the dump file for your nonetheless.

 

[x BlueRobot]

[COLOR=Red]BugCheck 1A[/COLOR], {[COLOR=Blue]5002[/COLOR], fffff70001080000, 3970, b003971fffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2902c )

6: kd> [COLOR=SeaGreen]!stack[/COLOR]
Call Stack : [COLOR=Red]8 frames[/COLOR]
## Stack-Pointer    Return-Address   Call-Site       
00 fffff88009eee798 fffff800038efd34 nt!KeBugCheckEx+0 
01 fffff88009eee7a0 fffff80003897ece nt!MiCompleteProtoPteFault+49e44 (perf)
[COLOR=Blue]02[/COLOR] fffff88009eee830 fffff800038a5d05 [COLOR=Red]nt!MiResolveDemandZeroFault+93e [/COLOR]
[COLOR=Blue]03[/COLOR] fffff88009eee920 fffff800038a44f3 [COLOR=Red]nt!MiResolveProtoPteFault+4f5[/COLOR] 
04 fffff88009eee9b0 fffff80003894179 nt!MiDispatchFault+1c3 
05 fffff88009eeeac0 fffff80003885cae nt!MmAccessFault+359 <-- Demand Zero Fault?
06 fffff88009eeec20 000000006ec382ed nt!KiPageFault+16e

The subtype error of this bugcheck is not publicly documented by Microsoft, but looking at the call stack, I see regular maintenance going on. The most interesting frames are 2 and 3. Prototype PTES and PTEs are the same, apart from Prototype PTEs add a additional layer to address translation. So, from what has happened, a demand zero Prototype PTE was accessed, and then the Access Fault handler was executed to resolve this fault, by writing a page with 0's.

Do you have the latest WHQL version of your nVidia graphics card driver installed?

 

[Bizarro181]

Hey BlueRobot,

My nVidia drivers are current. I just ran the update check now and they are from 9/19/2013 and listed as 327.23 WHQL on the nividia site.

Thanks
-Rob

 

[x BlueRobot]

Okay, that's good to know, my next suggestion would be:

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[Bizarro181]

Hey BlueRobot

Thanks, I'll have to run that overnight or maybe tomorrow then...in the meantime I got another bluescreen (sigh) again...just using chrome and notepad++. Dump and all attached.

Thanks a TON
-Rob

Edit: just got another after posting this "uncorrectable hardware error"

 

[Bizarro181]

My computer was only running for about 30 minutes before I got a bluescreen do I need to continue running it?

Everything attached.

-Rob

 

[ICIT2LOL]

Just my two cents worth mate and I might be way out but have yo checked out the PSU try this

http://www.sevenforums.com/tutorials/86648-psu-jump-start.html

for a reference
Power Supply 101: A Reference Of Specifications - Power Supplies as you will see there is a +/- 5% variance that can make all the difference so 11.4v is way too low and 12.6v way too high.

Plus remember correct bolts do not mean correct current (amps - in turn watts)

Suppose you have tried reseating everything too??

 

[Bizarro181]

Just my two cents worth mate and I might be way out but have yo checked out the PSU try this

http://www.sevenforums.com/tutorials/86648-psu-jump-start.html

for a reference
Power Supply 101: A Reference Of Specifications - Power Supplies as you will see there is a +/- 5% variance that can make all the difference so 11.4v is way too low and 12.6v way too high.

Plus remember correct bolts do not mean correct current (amps - in turn watts)

Suppose you have tried reseating everything too??

Hey, Thanks for the suggestion. Although I'm not totally sure what I would be looking for or what jumping the power supply accomplishes (unless its in that article you linked which, admittedly, I only skimmed). That my be outside of my comfort level. Would using a tester like http://www.soarland.com/shared/images/product/SLPT100_Power_Supply_Tester.jpg that work just the same?

I'll definitely go though and check all my connections though. I haven't cracked my case open at all since these problems started happening.

Thanks
-Rob

 

[x BlueRobot]

Stop running Driver Verifier, it seems you've had a few Stop 0x124's, which usually indicate some form of hardware failure.

[COLOR="Red"]BugCheck 124[/COLOR], {[COLOR="Blue"]0[/COLOR],[COLOR="SeaGreen"] fffffa800e301028[/COLOR], ba000000, 400405}

Probably caused by : GenuineIntel

3: kd> [COLOR="SeaGreen"]!errrec fffffa800e301028[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa800e301028
-------------------------------------------------------------------------------
Record Id     : 01cec3bd9df63264
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/8/2013 0:41:03 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR="Red"]Micro-Architectural Error[/COLOR]
Flags         : 0x00
CPU Version   : 0x00000000000106a4
Processor ID  : 0x0000000000000003

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

Local APIC Id : 0x0000000000000003
CPU Id        : a4 06 01 00 00 08 10 03 - bd e3 98 00 ff fb eb bf
                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  @ fffffa800e301240

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

Error         : [COLOR="Red"]Internal unclassified (Proc 3 Bank 5)[/COLOR]
  Status      : 0xba00000000400405

Please run the Small FFT's, Large FFT's and the Blend Test for a few hours each. Do not let the temperature exceed around 80*C.

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

Enable "Round off checking" before the test (see first post below tutorial).

 

[Bizarro181]

Hey Bluerobot,

All 3 tests bluescreened almost right away. Dumps and fun stuff attached.

Thanks
-Rob

 

[ICIT2LOL]

Just my two cents worth mate and I might be way out but have yo checked out the PSU try this

http://www.sevenforums.com/tutorials/86648-psu-jump-start.html

for a reference
Power Supply 101: A Reference Of Specifications - Power Supplies as you will see there is a +/- 5% variance that can make all the difference so 11.4v is way too low and 12.6v way too high.

Plus remember correct bolts do not mean correct current (amps - in turn watts)

Suppose you have tried reseating everything too??

Hey, Thanks for the suggestion. Although I'm not totally sure what I would be looking for or what jumping the power supply accomplishes (unless its in that article you linked which, admittedly, I only skimmed). That my be outside of my comfort level. Would using a tester like http://www.soarland.com/shared/images/product/SLPT100_Power_Supply_Tester.jpg that work just the same?

I'll definitely go though and check all my connections though. I haven't cracked my case open at all since these problems started happening.

Thanks
-Rob

Well Rob all you need to do is take out the 24 pin put the clip into that green lead socket and any black ground socket that will start the PSU you then just test the volts on all the leads with a multimeter. Another thing you can try is a resistance test with the meter between the black lead sockets on the 24 pin and one of the motherboard fixing screws. The other pin to check is number 8 the grey one and as I said it is critical to the machine starting or resetting itself it has to be between 11.4 and 12.6 volts either side of those and it could either keep resetting the timer chip or damage the motherboard.
That device is ok but I I don't place a lot of confidence in them they can be very good and well made ones and some pretty ordinary when you want to know exact volts.
If you are worried about shocks mate the only shock you will get is if you are daft enough to put your tongue on the 12v rails lines or muck about inside that PSU which you will not have to go near. You are in no danger so do not worry about that if you follow what I said.
If you are able look at this http://www.sevenforums.com/vip/257690-psu-how-test.html#post2130086
Now as for reading the whole article I know it is long but the page 2 and 12 and 13 at least.

 

[x BlueRobot]

[COLOR=Red]BugCheck 124[/COLOR], {[COLOR=Blue]0[/COLOR], [COLOR=SeaGreen]fffffa800f3c7028[/COLOR], b2000000, 4008f}

Probably caused by : GenuineIntel

7: kd> [COLOR=SeaGreen]!errrec fffffa800f3c7028[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa800f3c7028
-------------------------------------------------------------------------------
Record Id     : 01cec3db1fc77ac8
Severity      : Fatal (1)
Length        : 873
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/8/2013 4:20:52 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Memory
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f3c70a8
Section       @ fffffa800f3c7180
Offset        : 344
Length        : 73
Flags         : 0x00000001 Primary
Severity      : Fatal


===============================================================================
Section 1     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f3c70f0
Section       @ fffffa800f3c71c9
Offset        : 417
Length        : 192
Flags         : 0x00000000
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Unknown error
Flags         : 0x00
CPU Version   : 0x00000000000106a4
Processor ID  : 0x0000000000000007

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800f3c7138
Section       @ fffffa800f3c7289
Offset        : 609
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]Unknown (Proc 7 Bank 8)[/COLOR]
  Status      : 0xb20000000004008f

7: kd> [COLOR=SeaGreen]!sysinfo cpuspeed[/COLOR]
CPUID:        "Intel(R) Core(TM) i7 CPU         940  @ 2.93GHz"
MaxSpeed:     2930
CurrentSpeed: [COLOR=Red]2940[/COLOR]

Are you overclocking at all? If so, please stop and revert back to the default settings within the BIOS.

7: kd> [COLOR=SeaGreen]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.5, DMIVersion 37, Size=2999]
BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 0202   
BiosReleaseDate = [COLOR=Red]12/04/2008[/COLOR]
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To Be Filled By O.E.M.
SystemVersion = System Version
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = [COLOR=Red]P6T[/COLOR]
BaseBoardVersion = Rev 1.xx

Your BIOS seems to be very outdated, have you checked for any BIOS updates from your motherboard support page? Remember to find the BIOS version for the exact version of your motherboard (including revision number), otherwise you could irreversibility corrupt your BIOS. Make sure the computer isn't turned off or interrupted when updating the BIOS.

I would also recommend testing the PSU. You may be able to get the voltage readings from the BIOS; post the 3.3V, 5V and 12V rail readings.

 

[Bizarro181]

Hey BlueRobot,

No overclocking here. The only thing I've done in the bios is set the timing, frequency and voltage for my RAM.

BIOS Readings for Power below

CPU - 1.264v
3.3v - 3.296v
5v - 5.09v
12v - 12.081v

I also checked my power supply with a power supply checker and got all the LEDs lit up and a beep...which is apparently a good sign.

A friend recommended that I check my new memory I bought so I ran memtest overnight and found a bad stick. Right now I'm running with my old memory so we'll see how that goes.

Wow, yeah...my BIOS is out of data. I'll try to update my bios tonight if everything seems stable enough, I'm worried about a BSOD in the middle of a BIOS update and frying everything.

Thanks!
-Rob

Edit: Just flashed the BIOS with no issue and everything seems better...No Blue screens yet