BSOD playing Dota2 and skyrim

quartz · 27 May 2014

what is double fault can you explain it on simpliest form?
how can i avoid the double fault?

quartz · 27 May 2014

thanks

Thedoctor44 · 27 May 2014

Well to put it simply a double fault occurs when an exception has occurred, the CPU uses a program called an exception handler which catches the exception and fixes the problem which is why you don't get BSODs all the time as there are lots of exceptions happening now as you read this.
Anyway, an exception can then occur whilst the exception handler is trying to work on the previous exception.

You can also get a triple fault which can occur when the exception an exception occurs whilst the CPU is trying to use the double fault handler which doesn't actually fix the double fault but rather collect the information ready to bugcheck the system.

A double fault can be caused by software or hardware, mostly faulty RAM or an overheating CPU.
In this case it looks like the Realtek driver has caused the double fault but we shall see if changing the driver (assuming you have done so) will fix the issue.

quartz · 27 May 2014

i got another bsod -_-

please take a look

Thedoctor44 · 28 May 2014

Code:

BugCheck 1A, {41287, 30, 0, 0}

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

I need a Kernel Memory Dump, the first parameter indicates that an internal memory management structure has been corrupted, the only way to analyse it is with a Kernel Memory Dump.

quartz · 28 May 2014

i got another bsod this is happen when im shutting down my laptop

i will try to upload the kernel memory dump for the mean time can you take a look at this dump files

thanks

Thedoctor44 · 28 May 2014

I will need that Kernel Memory Dump.

The second to latest dump file which is a memory management bugcheck is useless without a Kernel Memory Dump.

Code:

BugCheck 1A, {41287, 30, 0, 0}

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

The first parameter indicates Internal Memory Management structures has been corrupted and the only way to analyse it is with a Kernel Memory Dump.

I can't find anything in the latest dump file that pinpoints to a specific.
An access violation isn't surprising.

Code:

2: kd> .exr 0xfffff880037df568
ExceptionAddress: fffff8800fde6f1d (dxgmms1!VIDMM_SEGMENT::PurgeContent+0x000000000000003d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

The pointer being used is referring to an invalid address...

I can't see that much besides a bunch of DirectX routines.

Code:

2: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff880`037df7a0 fffff880`0fdd371f dxgmms1!VIDMM_SEGMENT::PurgeContent+0x3d
01 fffff880`037df800 fffff880`0fdd34d7 dxgmms1!VIDMM_GLOBAL::ProcessSystemCommand+0xc7
02 fffff880`037df890 fffff880`0fded3ad dxgmms1!VidMmiProcessSystemCommand+0x47
03 fffff880`037df8c0 fffff880`0fdec538 dxgmms1!VidSchiSubmitSystemCommand+0x39
04 fffff880`037df8f0 fffff880`0fdbe786 dxgmms1!VidSchiSubmitQueueCommand+0x74
05 fffff880`037df920 fffff880`0fdeeaa3 dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
06 fffff880`037df9b0 fffff880`0fdd35dd dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
07 fffff880`037dfa20 fffff880`0fdb55c6 dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
08 fffff880`037dfa90 fffff880`0fcf17a1 dxgmms1!VidMmPurgeAllSegments+0xe2
09 fffff880`037dfb00 fffff880`0fced2d7 dxgkrnl!DXGADAPTER::PurgeSegments+0x95
0a fffff880`037dfb30 fffff880`0fce510e dxgkrnl!DXGADAPTER::AcquireCoreSync+0x11b
0b fffff880`037dfb70 fffff880`0fd4fd4d dxgkrnl!DxgkAcquireAdapterCoreSync+0x56
0c fffff880`037dfba0 fffff800`0312873a dxgkrnl!DpiPowerArbiterThread+0x575
0d fffff880`037dfc00 fffff800`02e7d8e6 nt!PspSystemThreadStartup+0x5a
0e fffff880`037dfc40 00000000`00000000 nt!KiStartSystemThread+0x16

On this occasion, due to your computer being a laptop uninstall your display driver and let windows update install it for you.

quartz · 29 May 2014

i got 3 bsod on 1hour -_- this is

i will uninstall my display driver

please take a look again

Thedoctor44 · 29 May 2014

Your USB 3.0 driver is still getting flagged, it still dates back to 2013, there is a newer version...

Remove you display driver and all Nvidia software with it, then let Windows Update install the driver for you and see how that works out.

Do you have any devices installed in the USB 3.0 slots?

quartz · 29 May 2014

my usb 3.0 is the latest version its 1.0.10.255 as you linked its the same but the date is not

i dont know where is usb 3.0 slot but im using usb mouse