BSoD

[Shini]

i am using windows 7 64bit home premium OEM
i reinstalled my OS today.. after i started getting BSoD
and my hardware is about 5 months old

and i only use this pc for internet browsering..

 

[panais]

i am using windows 7 64bit home premium OEM
i reinstalled my OS today.. after i started getting BSoD
and my hardware is about 5 months old
------------------------------------------------
Hi.
Ur minidumps points to Hdaudbus.sys and ntoskrnl.exe
The Hdaudbus.sys is a HD Audio Drivers error,so please unistall any sound software/driver,clean with ccleaner CCleaner - Optimization and Cleaning - Free Download any remaining fragments.
Install the most updated HD Audio Drivers for ur system.
The ntoskrnl.exe it can be occur for several reasons, thats why you must follow those steps NTOSKRNL.EXE is missing or corrupt.
Error message: "Windows could not start because of a computer disk hardware configuration problem"
--------------------
If you like you can do the above one at the time and wait for results.Better start with HD Audio Drivers.
Advice : uninstall norton av,again clean with ccleaner,for a.v. install and keep MSE http://www.microsoft.com/security/pc-security/mse.aspx

 

[Shini]

il try that thanks!

 

[Shini]

Alright so i tried all of that and it worked for awhile but.. now i have started to get BSoD again..

 

[yowanvista]

Alright so i tried all of that and it worked for awhile but.. now i have started to get BSoD again..

Your old Nvidia Display Driver is blamed, update it
Drivers - Download NVIDIA Drivers

More info on this error
http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html
If updating the driver does not fix it you should test your RAM and GPU
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
http://www.sevenforums.com/tutorials/160729-nvidia-video-card-test-occt.html

nvlddmkm.sys    nvlddmkm.sys+11ef00    fffff880`0f034000     fffff880`0fd6c500    0x00d38500    0x4bb45b23    01/04/2010 12:36:51

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80025b44e0, fffff8800f152f00, 0, 2}

Unable to load image 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
Probably caused by : nvlddmkm.sys ( nvlddmkm+11ef00 )


VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80025b44e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f152f00, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+11ef00
fffff880`0f152f00 803dc90db80000  cmp     byte ptr [nvlddmkm+0xc9fcd0 (fffff880`0fcd3cd0)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`009cc9c8 fffff880`0413d000 : 00000000`00000116 fffffa80`025b44e0 fffff880`0f152f00 00000000`00000000 : nt!KeBugCheckEx
fffff880`009cc9d0 fffff880`0413cd0a : fffff880`0f152f00 fffffa80`025b44e0 fffffa80`046fad50 fffffa80`046ee010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`009cca10 fffff880`0400ff07 : fffffa80`025b44e0 00000000`00000000 fffffa80`046fad50 fffffa80`046ee010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`009cca40 fffff880`04039b75 : 00000000`ffffffff 00000000`0004ae6e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`009ccb20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`0004ae6e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`009ccb50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`046ee010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`009ccbf0 fffff880`04037e7a : 00000000`00000000 fffffa80`0231b010 00000000`00000080 fffffa80`046ee010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`009ccd00 fffff800`02d20bc6 : 00000000`fffffc32 fffffa80`046ec770 fffffa80`021b1040 fffffa80`046ec770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`009ccd40 fffff800`02a5bbc6 : fffff880`009e9180 fffffa80`046ec770 fffff880`009f3f40 fffff880`012402b4 : nt!PspSystemThreadStartup+0x5a
fffff880`009ccd80 00000000`00000000 : fffff880`009cd000 fffff880`009c7000 fffff880`07743b70 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+11ef00
fffff880`0f152f00 803dc90db80000  cmp     byte ptr [nvlddmkm+0xc9fcd0 (fffff880`0fcd3cd0)],0

SYMBOL_NAME:  nvlddmkm+11ef00

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bb45b23

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

 

[panais]

the new bsod

yowanvista is right,the new error nvlddmkm.sys is a nvidia driver error.
-----------------------------------------------
A good idea is...after the uninstallation do a cleanup with the ccleaner,then install the most updated driver for your graphic card.
Please update and the directX.

 

[Shini]

Alright so i did all that and updated driectX hopefully its fixed now! thanks!

 

[panais]

Alright so i did all that and updated driectX hopefully its fixed now! thanks!

Your welcome

 

[Shini]

Damn i am still getting BSoD i guess il just have to take it down to the store and have them deal with it

 

[panais]

Damn i am still getting BSoD i guess il just have to take it down to the store and have them deal with it

Please upload the new minidump file.

 

[Shini]

its weird though.. i ahve done everything that you guys have said.. and it still have not gotten fixed.. i even changed my keyboard/screen.. maybe its some other faulty hardware?

 

[panais]

its weird though.. i ahve done everything that you guys have said.. and it still have not gotten fixed.. i even changed my keyboard/screen.. maybe its some other faulty hardware?

The new bsod caused by kbdclass.sys.
This now is a logitech driver error.
Download the most updated software/driver for ur pc. Logitech
Uninstall any logitech driver you have,again clean any remaining fragments with ccleaner.
Install the new software/driver.

 

[Shini]

Holys*** i think reinstalling my logitech driver actually fixed it thanks!

 

[panais]

Holys*** i think reinstalling my logitech driver actually fixed it thanks!

Glad for the good news!!