BSOD Randomly, error 0x3b, but varies sometimes.

[Ezwazwaz]

Specs:
CPU:AMD 6300
GPU:2X GTX 660 SLI
RAM: DDR3 16GB (2X8
PSU:RM750
DISK:1TB Western Digital
SSD:125GB Samsung
MOBO:990FXA-UD3 (Gigabyte)

I updated my BIOS and the BSOD's seemed to stop, but after a month or so it started happening again.

Ran Memtest, no errors.

 

[axe0]

Hi Ezwazwaz,

Welcome to the 7forums.

Please uninstall Gigabyte software, it is known for causing bluescreens.

Please update your Realtek network drivers
Driver Reference Table - Rt64win7.sys

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
View attachment 380686

Realtek driver

fffff880`14355f48  fffff880`0431fab1Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x2ab1
4: kd> lmvmRt64win7
start             end                 module name
fffff880`04400000 fffff880`0448d000   Rt64win7   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR="Red"]Tue Aug 23 15:55:41 2011[/COLOR] (4E53B15D)
    CheckSum:         00097338
    ImageSize:        0008D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Nvidia driver

fffff880`143563d8  fffff880`11214834Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1e7834
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`1102d000 fffff880`11c37000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        [COLOR="Red"]Wed Dec 16 15:13:02 2015[/COLOR] (5671716E)
    CheckSum:         00BD14EC
    ImageSize:        00C0A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Ezwazwaz]

Still BSOD, but it's happening more frequently. I did all that except i don't believe the realtek drivers installed properly.

Thank you for your help.

 

[cluberti]

This is a stop 0x50, and it appears it had a problem reading the MFT record off of a disk attached to the system (NTFS being a kernel driver, a page fault during NTFS routines will bugcheck the box):

// The fault that started the problem:
1: kd> .bugcheck
Bugcheck code 00000050
Arguments fffff6fc`400626d8 00000000`00000000 fffff800`030f6cbf 00000000`00000009

1: kd> .trap 0xfffff8800b534960
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800cd4aed0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff98001c22800 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033dbb37 rsp=fffff8800b534af0 rbp=0000000000000000
 r8=000000000000000f  r9=0000000000362800 r10=0000000000000800
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!CcMapData+0x117:
fffff800`033dbb37 0fb602          movzx   eax,byte ptr [rdx] ds:fffff980`01c22800=??

1: kd> k
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 fffff880`0b534af0 fffff880`012f8382 nt!CcMapData+0x117
01 fffff880`0b534bb0 00000000`00000000 Ntfs!NtfsReadMftRecord+0xb2

// The full stack showing the resulting bugcheck:
1: kd> !thread
GetPointerFromAddress: unable to read from fffff80003319000
THREAD fffffa800fd8c360  Cid 0510.0530  Teb: 000007fffffd3000 Win32Thread: fffff900c1ae0010 RUNNING on processor 1
IRP List:
    Unable to read nt!_IRP @ fffffa8010fb9750
Not impersonating
GetUlongFromAddress: unable to read from fffff80003257bf0
Owning Process            fffffa800fd36060       Image:         spoolsv.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      1519         
Context Switch Count      248            IdealProcessor: 1                 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000ff50d240
Stack Init fffff8800b535c70 Current fffff8800b533dc0
Base fffff8800b536000 Limit fffff8800b52d000 Call 0
Priority 10 BasePriority 8 UnusualBoost 1 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0b533bf8 fffff800`03157ea0 : 00000000`00000050 fffff6fc`400626d8 00000000`00000000 fffff880`0b533d60 : nt!KeBugCheckEx
fffff880`0b533c00 fffff800`030d9d2e : 00000000`00000000 fffff6fc`400626d8 fffffa80`00000000 fffffa80`0e8a2a20 : nt! ?? ::FNODOBFM::`string'+0x4149d
fffff880`0b533d60 fffff800`030f6cbf : fffff880`0b534150 fffff880`0151e1cf fffffa80`0fd8c360 fffff880`009ea180 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0b533d60)
fffff880`0b533ef0 fffff880`01253a41 : fffffa80`0e8a2a20 fffff800`0000c4db 00000000`00000001 00000000`00001000 : nt!MmMapLockedPagesSpecifyCache+0x2c4
fffff880`0b533fc0 fffff880`0125f703 : fffff880`0b534410 fffffa80`0e76a970 fffffa80`10fb9750 fffff980`02988601 : Ntfs!NtfsVerifyAndRevertUsaBlock+0x81
fffff880`0b5340b0 fffff880`01258ec8 : fffff880`0b534410 fffffa80`10fb9750 00000000`00000000 fffffa80`0fd8c360 : Ntfs!NtfsNonCachedIo+0x8a1
fffff880`0b534270 fffff880`01259398 : fffff880`0b534410 fffffa80`10fb9750 fffff880`0b534501 fffffa80`111ee801 : Ntfs!NtfsCommonRead+0x18df
fffff880`0b5343e0 fffff880`01002bcf : fffffa80`10fb9aa8 fffffa80`10fb9750 fffffa80`111ee880 00000000`00000000 : Ntfs!NtfsFsdRead+0x1b8
fffff880`0b5345f0 fffff880`010016df : fffffa80`0e766880 fffffa80`0e766880 fffffa80`0e766800 fffffa80`10fb9750 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0b534680 fffff800`03103689 : fffffa80`10fb9750 fffffa80`0e8a29b0 fffff880`0b534700 fffff880`009ea180 : fltmgr!FltpDispatch+0xcf
fffff880`0b5346e0 fffff800`03103109 : fffffa80`0e650400 fffffa80`0e650400 fffffa80`0e8a29b0 fffffa80`0e650008 : nt!IoPageRead+0x2a9
fffff880`0b534770 fffff800`030e99c9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`03b45000 : nt!MiIssueHardFault+0x255
fffff880`0b534800 fffff800`030d9d2e : 00000000`00000000 fffff980`01c22800 fffff8a0`0034c000 00000000`0000000e : nt!MmAccessFault+0x1399
fffff880`0b534960 fffff800`033dbb37 : 00000004`00000001 00000000`00362800 fffff880`0b534bb8 fffff880`0b534bb0 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0b534960)
fffff880`0b534af0 fffff880`012f8382 : fffff880`0001d800 fffffa80`0cd4aed0 00000000`00000001 fffffa80`0000000e : nt!CcMapData+0x117
fffff880`0b534bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsReadMftRecord+0xb2

// Can't enumerate devices, IRP is not present in dump either:
1: kd> !devnode 0 1
Error reading value of IopRootDeviceNode (0xfffff800032e5db0)

While this dump is probably an issue with a disk (you might want to chkdsk the volumes attached to the machine), it's also probably not likely related to your 0x3B crashes either.