BSOD - Windows 7 x64 - 0x0000009f

goots

Member
Joined
Mar 18, 2016
Posts
6
Hello All,

I have been getting less BSOD's lateley, but this one seems to be coming up. Bluescreenview tells me it is in the ntoskrnl.exe driver, i have also uploaded the dmp file. Any advice will be greatly appreciated.
 

Attachments

There are some drivers flagged in the dump, but it seems Dell doesn't provide driver updates for Windows 10 for your laptop.
Even though Dell doesn't support Windows 10 for your laptop, it may still be worth it to update drivers and BIOS
The drivers that have been flagged are
  • Nvidia display drivers
  • Intel display drivers
As only display drivers have been flagged, I would make sure to not switch between graphics cards because that sometimes may cause problems.
Product Support | Dell US
Code:
BiosReleaseDate = 08/09/2012

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800d1d7a10, fffff80000b9a3d8, fffffa800d4adb60}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : ACPI.sys

fffff800`00b9a7b8  fffff880`056c5f24Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0x72f24

fffff800`00b9a4f0  fffff880`042c3190Unable to load image nvkflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvkflt.sys
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
 nvkflt+0x3d190


0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff880`0481b000 fffff880`0531a000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#FF0000]Mon Oct 28 22:38:03 2013[/COLOR] (526ED93B)
    CheckSum:         00AD0AFE
    ImageSize:        00AFF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lmvm igdkmd64
Browse full module list
start             end                 module name
fffff880`05653000 fffff880`05b6f1c0   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#FF0000]Fri Feb 22 22:49:20 2013[/COLOR] (5127E7E0)
    CheckSum:         005213ED
    ImageSize:        0051C1C0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lmvm nvkflt
Browse full module list
start             end                 module name
fffff880`04286000 fffff880`042d3000   nvkflt   T (no symbols)           
    Loaded symbol image file: nvkflt.sys
    Image path: nvkflt.sys
    Image name: nvkflt.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR=#FF0000]Mon Oct 28 22:38:39 2013[/COLOR] (526ED95F)
    CheckSum:         0004CEF1
    ImageSize:        0004D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 
We're certainly not going to find much from a minidump.
Most likely is the Nvidia driver.

Code:
//Thread callstack of the thread which called the bugcheck
//Trying to drain the DPC list from queue

0: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff800`00b9a388 fffff800`02f3f920 nt!KeBugCheckEx
01 fffff800`00b9a390 fffff800`02edb2cc nt! ?? ::FNODOBFM::`string'+0x32450 // nt!PopCheckIrpWatchdog
02 fffff800`00b9a430 fffff800`02edb166 nt!KiProcessTimerDpcTable+0x6c
03 fffff800`00b9a4a0 fffff800`02edb04e nt!KiProcessExpiredTimerList+0xc6
04 fffff800`00b9aaf0 fffff800`02edae37 nt!KiTimerExpiration+0x1be
05 fffff800`00b9ab90 fffff800`02ec7d8a nt!KiRetireDpcList+0x277
06 fffff800`00b9ac40 00000000`00000000 nt!KiIdleLoop+0x5a

//Context not saved, can't find out what the DPC actually is

0: kd> dt nt!_KDPC FFFFF80000BA0FB0
   +0x000 Type             : ??
   +0x001 Importance       : ??
   +0x002 Number           : ??
   +0x008 DpcListEntry     : _LIST_ENTRY
   +0x018 DeferredRoutine  : ???? 
   +0x020 DeferredContext  : ???? 
   +0x028 SystemArgument1  : ???? 
   +0x030 SystemArgument2  : ???? 
   +0x038 DpcData          : ???? 
Memory read error fffff80000ba0fe8

//The device object associated with the driver object where the IRP timed out
//ACPI gets the blame, but it's almost certainly the attached Nvidia driver up the stack, when it has been passed down to it

0: kd> !devobj fffffa800c9cee40 f
fffff80003086070: Unable to get value of ObpRootDirectoryObject
Device object (fffffa800c9cee40) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa800c9cee10
 \Driver\ACPI DriverObject fffffa800c9ceab0
Current Irp 00000000 RefCount 0 Type 00000032 Flags 00000000
DevExt fffffa800c9ef3f0 DevObjExt fffffa800c9cef90 
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) fffffa800d724480 \Driver\nvlddmkm
Device queue is not busy.

//Can't display any other IRPs, what they were doing. And who initiated them.

Allocated power irps (PopIrpList - fffff80003085bd0)
Error resolving nt!_LIST_ENTRY...


Irp worker threads (PopIrpThreadList - fffff80003085520)
Error resolving nt!_LIST_ENTRY...


Error resolving nt!_POP_CURRENT_BROADCAST...

As said by axe0, it's most likely your Nvidia driver. No surprise. I'd update it to one late last year, there are lots of problems with the recent ones.
 
Thank you all for the advice. Where would I be able to find the older drivers? I am not too savy with computers. Thanks again!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top