Random BSOD ntkrnlpa.exe and sometimes win32k.sys

[centaur78]

put it in dropbox or other similar services and post a link here

 

[JamesLens]

Zip file compressed it to 1MB, so it's fine. A bit late, not thinking straight. Uploaded

 

[JamesLens]

This morning BSOD'd twice before even getting into windows. Is there any hint as to what may be causing this?

Thanks

 

[centaur78]

James

could you post the files in this folder "C:\Windows\LiveKernelReports\WATCHDOG"... It also has dmp files...

 

[JamesLens]

Uploaded.

Thanks

 

[centaur78]

It look like the nvidia display driver not responding in the timely fashion and cause of the crashes on the 10 dumps you posted....... these dmps were all from 25th ..... the day you also stress tested the system using furmark and other cpu stress tools....

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

Use !analyze -v to get detailed debugging information.

BugCheck 117, {a068c510, ac75eed8, 0, 0}

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

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: a068c510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: ac75eed8, The pointer into responsible device driver module (e.g owner tag).
Arg3: 00000000, The secondary driver specific bucketing key.
Arg4: 00000000, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP:
nvlddmkm+13eed8
ac75eed8 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
a3c03b30 ad1955b8 00000000 ac75eed8 9eaac788 dxgkrnl!TdrUpdateDbgReport+0x68
a3c03b9c ad19497e 00000000 00000001 a068c510 dxgkrnl!TdrCollectDbgInfoStage1+0x715
a3c03bbc a9f6f92c 00000000 00000102 9eaac788 dxgkrnl!TdrIsRecoveryRequired+0xfe
a3c03c34 a9f99944 fffffcfb 0000076d 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
a3c03c5c a9f9a065 00000006 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
a3c03c98 a9f768f0 a3c03c90 e2e8b539 9eaac788 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
a3c03d28 a9f9b3c9 9eaac788 e2e8b539 9eaac788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
a3c03d3c a9f9b485 9eaac788 00000000 a05c7b48 dxgmms1!VidSchiRun_PriorityTable+0xf
a3c03d50 e305d056 9eaac788 86e7dbba 00000000 dxgmms1!VidSchiWorkerThread+0x7f
a3c03d90 e2f051a9 a9f9b406 9eaac788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+13eed8
ac75eed8 ?? ???

SYMBOL_NAME: nvlddmkm+13eed8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4fb2071b

FAILURE_BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

BUCKET_ID: 0x117_IMAGE_nvlddmkm.sys

Followup: MachineOwner

Here is what you need to do .....

1. Completely uninstall this full nvidia suite and drivers and reinstall it again.....

2. Since we have not done system files checker .... do that as well

ie; type sfc /scannow at the command prompt

3. You did mention you cleaned the CPU fans .... have you done the same for the Graphics as well ????


try these and let me know how it goes....

 

[JamesLens]

Ok so I just did a complete uninstall of the drivers using driver fusion (both NVidia display and chipboard ones) and installed the new ones over.

Then I used the system files checker, and it said that it found some corrupt files but some could not be fixed, full log attached.

Finally I took the video card out and cleaned the fan (seemed pretty clean) and put it back in. Then when I loaded the computer, it crashed again before getting into windows and then went in. Not sure how it will react now. Crash log attached as well.

There were also some zip files in the folder where the system file checker log was, do you need that?

Thanks

 

[JamesLens]

Crashed about half a dozen times yesterday, so still the same issue.

 

[centaur78]

Crashed about half a dozen times yesterday, so still the same issue.

James the crash you upped yesterday was referring to the display driver as in the stack below

STACK_TEXT:
a3cf29f4 e2e5c468 00000001 ff90a17f 00000000 nt!MmAccessFault+0x106
a3cf29f4 add48195 00000001 ff90a17f 00000000 nt!KiTrap0E+0xdc
a3cf2a8c add3f48d a3cf2aa4 ff90a17f a3cf2b84 win32k!vGetDeviceCaps+0x18
a3cf2a9c add3aa5a ffb8f748 a3cf2c2c 00000000 win32k!GreUpdateSharedDevCaps+0x1a
a3cf2b84 add3915a 00000000 00000000 00000000 win32k!DrvInternalChangeDisplaySettings+0xe62
a3cf2ca0 add2adbd 00000000 00000000 00000000 win32k!DrvChangeDisplaySettings+0x3ae
a3cf2cf8 add16094 ffbbd6d0 00000040 00000000 win32k!InitVideo+0x60
a3cf2d18 add23857 0031f5bc a3cf2d34 e2e5927a win32k!UserInitialize+0x115
a3cf2d24 e2e5927a 00000040 00000044 0031f5d8 win32k!NtUserInitialize+0x9f
a3cf2d24 770d7094 00000040 00000044 0031f5d8 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0031f5d8 00000000 00000000 00000000 00000000 0x770d7094

So the first thing we need to do is the remove the graphics card from the slot and then put the monitor cable to the onboard graphics ...

Try to see if it bsod even after doing this....

 

[JamesLens]

Unfortunately, I don't have any onboard graphics. I do have another video card I could try, though it would use the same nVidia driver pack as the other card.

 

[JamesLens]

Never mind that card is burned out

 

[centaur78]

Sorry ... my bad... forgot to check the model before advising ...

Ok since you have only one card... have you tried putting it at different slots...ie; if its placed in the PCIEX16_1.. then try placing them in PCIEX16_2...if that fails.... put it in PCIEx16_3

 

[centaur78]

James

You nvidia Chipset drivers last update as per ASUS is dated to 2007... but if you check the nforce SLi chipset drivers @ nvidia site... the have one dated 2011...

I would suggest you update the chipset version from here after you did the above..

 

[JamesLens]

Have already done that. There is however a pesky Silicon Image controller driver that refuses to update to the latest 2009 version whatever I try to do; the driver files just stay at the 2007 version. Also switched the video card to another PCI bridge, still the same issue. There's only 2 of them as far as I see.

Edit: I stand corrected, there is a 3rd one, I'll give it a go.