BSOD ERROR - PC Rebooting

ragazzid · 01 Mar 2013

Hi Guys, recently I started to face some problems to use my computer, Looking at the logs I saw some hard-disk erros so I bought a new HD to replaced the existing one but now I'm getting BSOD error.

I think I had a problem with the HD and now I have a new problem, the new HD works perfectly in another computer (using the same SATA cable)

See the dump files attached.

Can someone help me?

Ps. this is the last error I got when the computer restarted:

Signature of the problem:
Name of the problem event: BlueScreen
SO Version: 6.1.7600.2.0.0.256.48
Identity and location: 1046

Info about the problem
BCCode: 116
BCP1: 84DF3008
BCP2: 900429B0
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that can help with the problem
C:\Windows\Minidump\030113-12604-01.dmp
C:\Users\DDDDD\AppData\Local\Temp\WER-20841-0.sysdata.xml

Arc · 01 Mar 2013

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {849fd008, 900269b0, 0, c}

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

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

Code:

90015000 90512000   igdkmd32 T (no symbols)           
    Loaded symbol image file: igdkmd32.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
    Image name: igdkmd32.sys
    Timestamp:        Wed May 06 23:43:40 2009 (4A01D354)
    CheckSum:         0048DF97
    ImageSize:        004FD000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

So it is caused by an old intel graphics driver. Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.

Install Service pack 1.

Code:

Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

Try to update the BIOS.

Code:

BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 080015 
BiosReleaseDate = 02/05/2010

Let us know the results.

Dsprague · 01 Mar 2013

Hello Ragazzid and welcome to the forums, I took a look through your files and it appears that all of your problems are being caused by your display drivers:

Code:

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {84c48510, 9003a9b0, 0, 2} *** WARNING: Unable to verify timestamp for igdkmd32.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys Probably caused by : igdkmd32.sys ( igdkmd32+119b0 ) Followup: MachineOwner ---------

Driver Reference Table - igdkmd32.sys

upon closer inspection the driver is very old:

Code:

kd> lmvm igdkmd32 start end module name 90029000 90526000 igdkmd32 T (no symbols) Loaded symbol image file: igdkmd32.sys Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys Image name: igdkmd32.sys Timestamp: Wed May 06 14:13:40 2009 (4A01D354) CheckSum: 0048DF97 ImageSize: 004FD000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

please update the driver from here: Intel Download Center

Arc beat me to it

ragazzid · 01 Mar 2013

WHOA all u said makes all sense, I'm going to do what you said me to do and I'll let you know about the results, thank yoU!

Arc · 01 Mar 2013

@Dsprague,

Anyway, we analyzed the similar, mate :) You do the next, OK? :)

ragazzid · 20 Mar 2013

Folks, Thank you so much, it worked!

Thank you all for the help.

By the way, would you mind give me some info in how did you found those errors? I mean... did you used a particular program or just looked using the notepad?

Arc · 21 Mar 2013

You are welcome, mate :)
You will get all the answers to all your questions here: Debugging A BSOD - My way