error code 9f when starting laptop after auto shutdown

[JeepRider]

i have my laptop set so after a certain amount of time being idle, it hibernates itself. but whenever it does do this, i start it back up and it says windows has recovered from a serious error. the error code is 9f. if i manually hibernate (close lid or choose hibernate in start menu) it works fine. any ideas? everything is up to date.

 

[Berkey]

i have my laptop set so after a certain amount of time being idle, it hibernates itself. but whenever it does do this, i start it back up and it says windows has recovered from a serious error. the error code is 9f. if i manually hibernate (close lid or choose hibernate in start menu) it works fine. any ideas? everything is up to date.

Welcome to the Forums!

Is this a BSOD (blue screen of death issue)? If so this will be moved and you can follow this link http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html in order to get the info needed to help.

Generally, this sounds like a driver issue from the searches of previous threads, possible bluetooth drivers, but again more info will be needed to be sure

 

[JeepRider]

i have my laptop set so after a certain amount of time being idle, it hibernates itself. but whenever it does do this, i start it back up and it says windows has recovered from a serious error. the error code is 9f. if i manually hibernate (close lid or choose hibernate in start menu) it works fine. any ideas? everything is up to date.

Welcome to the Forums!

Is this a BSOD (blue screen of death issue)? If so this will be moved and you can follow this link http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html in order to get the info needed to help.

Generally, this sounds like a driver issue from the searches of previous threads, possible bluetooth drivers, but again more info will be needed to be sure

im not sure what to call it. i never physically see the BSOD, so im not sure what "category" it would go under. but i checked everything (drivers, ran chkdsk, defrag, disk cleanup) and everything came out good. next time it happens, i will copy and paste the whole error box that pops up on the desktop.

 

[Golden]

Its a 0x9f BSOD by the sounds of it - common with hibernation. Do the following anyway, as the problem will be recorded in the files this tool gathers, and I'll take a look.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

 

[JeepRider]

Its a 0x9f BSOD by the sounds of it - common with hibernation. Do the following anyway, as the problem will be recorded in the files this tool gathers, and I'll take a look.

1. Download the DM Log Collector application to your desktop by clicking the link below

DM Log Collector.exe

2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

heres the .zip ya wanted

and that exe made a UN DELETEABLE file called SFdebugFiles. sying location has changed. i search whole HDD for it and it was not found. how do i get rid of that.

 

[Golden]

Please re-run the application - I need more than just the .dmp files to look at the issue.

 

[JeepRider]

Please re-run the application - I need more than just the .dmp files to look at the issue.

this is all it gave me. also made a file called SFdebugFiles that i cant delete no matter what. how do i get rid of it.

 

[Golden]

I don't know why your system won't record all the files....anyway, this is about all I can do now.

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80036653a0, fffff80000b9c518, fffffa8003411550}

Probably caused by : ACPI.sys

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

0: kd> !irp fffffa8003411550
Irp is active with 8 stacks 7 is current (= 0xfffffa80034117d0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8003e8f050 00000000 fffff80002ecf210-fffffa800285b680 Success Error Cancel pending
	      Unable to load image \SystemRoot\system32\DRIVERS\SMSCir64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SMSCir64.sys
*** ERROR: Module load completed but symbols could not be loaded for SMSCir64.sys
 \Driver\SMSCIRDA	nt!PopSystemIrpCompletion
			Args: 00015500 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800285b680    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm SMSCir64
start             end                 module name
fffff880`043b8000 fffff880`043c1380   SMSCir64 T (no symbols)           
    Loaded symbol image file: SMSCir64.sys
    Image path: \SystemRoot\system32\DRIVERS\SMSCir64.sys
    Image name: [B][COLOR="Red"]SMSCir64.sys[/COLOR][/B]
    Timestamp:        Wed [B][COLOR="red"]Apr 25[/COLOR][/B] 23:04:11 [B][COLOR="red"]2007[/COLOR][/B] (462F58D3)
    CheckSum:         0000C8CA
    ImageSize:        00009380
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The SMSC infra-red device driver is more than 7 years old - it was originally an OEM product (probably XP or Vista) and there are no updates and SMSC is now a defunct company - acquired by Microchip (you can try there for a driver, but I think the chances of success are slim). I recommend uninstalling the device.

 

[JeepRider]

I don't know why your system won't record all the files....anyway, this is about all I can do now.

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80036653a0, fffff80000b9c518, fffffa8003411550}

Probably caused by : ACPI.sys

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

0: kd> !irp fffffa8003411550
Irp is active with 8 stacks 7 is current (= 0xfffffa80034117d0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8003e8f050 00000000 fffff80002ecf210-fffffa800285b680 Success Error Cancel pending
	      Unable to load image \SystemRoot\system32\DRIVERS\SMSCir64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SMSCir64.sys
*** ERROR: Module load completed but symbols could not be loaded for SMSCir64.sys
 \Driver\SMSCIRDA	nt!PopSystemIrpCompletion
			Args: 00015500 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800285b680    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm SMSCir64
start             end                 module name
fffff880`043b8000 fffff880`043c1380   SMSCir64 T (no symbols)           
    Loaded symbol image file: SMSCir64.sys
    Image path: \SystemRoot\system32\DRIVERS\SMSCir64.sys
    Image name: [B][COLOR="Red"]SMSCir64.sys[/COLOR][/B]
    Timestamp:        Wed [B][COLOR="red"]Apr 25[/COLOR][/B] 23:04:11 [B][COLOR="red"]2007[/COLOR][/B] (462F58D3)
    CheckSum:         0000C8CA
    ImageSize:        00009380
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The SMSC infra-red device driver is more than 7 years old - it was originally an OEM product (probably XP or Vista) and there are no updates and SMSC is now a defunct company - acquired by Microchip (you can try there for a driver, but I think the chances of success are slim). I recommend uninstalling the device.

i just want to say this, thats pretty neat how you did that and found an error without being on the computer with the issues. it would make sense that the infrared driver is out of date. this laptop is from 2006 (works perfect when it wants to) this laptop was originally made for Vista but i put 7 on it (you mentioned XP or Vista). so if i turn it off, it might help? GET THIS: believe it or not, i found a driver for this that is 2 years newer (2007 to 2009). maybe it will help.