Repeated BSOD's on laptop upgraded from Vista

SteveAltman · 21 Dec 2013

Hi,

I'm having repeated BSOD's on my laptop Fujitsu T5010. It's like tlyhat they're caused by driver conflicts; when I bought the machine (2008) it had Vista OS and I Windows 7 upgrade disk but I didn't upgrade until recently. I had several problems installing Windows 7 Service Pack 1 but more importantly, several features of the laptop stopped working (auto rotation of the screen, tablet buttons, etc.). It's a very common problem for this machine's owners and in trying to solve (unsuccessfully) those issues I probably installed drivers that were not compatible.

I set up verifier with the settings suggested here. The machine crashed immediately upon boot. I've attached some .dmp files.

When I try to use the downloaded SF Diagnostic Tool Windows immediately throws a "stopped working" exception. I am running it as administrator.

Thanks for any help.

Arc · 22 Dec 2013

Hi SteveAltman.

Upload the list of all the third party drivers Using NirSoft DriverView :

Download and execute Driverview
View > Hide Microsoft Drivers
Edit > Select all
File > Save Selected Items
In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
Zip the .txt file and upload it.

upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

These will help us to have a deeper look at the situation.

___________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, c2e61980, e3142ae0, c2e48af8}

Probably caused by : ACPI.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: c2e61980, Physical Device Object of the stack
Arg3: e3142ae0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: c2e48af8, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce788e0

MODULE_NAME: ACPI

FAULTING_MODULE: c88c9000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
e3142a94 e30e2377 0000009f 00000003 c2e61980 nt!KeBugCheckEx+0x1e
e3142b00 e30e23f0 e3142bac 00000000 e314f380 nt!PopCheckIrpWatchdog+0x1f5
e3142b38 e30944d9 e315d6e0 00000000 92079a04 nt!PopCheckForIdleness+0x73
e3142b7c e309447d e3145d20 e3142ca8 00000002 nt!KiProcessTimerDpcTable+0x50
e3142c68 e309433a e3145d20 e3142ca8 00000000 nt!KiProcessExpiredTimerList+0x101
e3142cdc e30924ce 0050da58 c77afd48 e314f380 nt!KiTimerExpiration+0x25c
e3142d20 e30922f8 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
e3142d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_3_tpm_IMAGE_ACPI.sys

BUCKET_ID:  0x9F_3_tpm_IMAGE_ACPI.sys

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

0: kd> !irp c2e48af8
Irp is active with 7 stacks 6 is current (= 0xc2e48c1c)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     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
 [ 16, 0]   0  0 c2e61980 00000000 00000000-00000000    
           \Driver\ACPI
            Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 c409b440 00000000 00000000-00000000    pending
           \Driver\TPM
            Args: 00041100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-c772d0e8    

            Args: 00000000 00000000 00000000 00000000
0: kd> !devobj c409b440
Device object (c409b440) is for:
 InfoMask field not found for _OBJECT_HEADER at c409b428
 \Driver\TPM DriverObject c40cf368
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00002004
DevExt c40d1f98 DevObjExt c409b518 
ExtensionFlags (0x00000800)  DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedTo (Lower) c2e61980 \Driver\ACPI
Device queue is not busy.

SteveAltman · 22 Dec 2013

Hi,

Thanks for your response.I've attached those files. I don't know if the msinfo file is any good; when I try to open it I get an error that it is corrupt. Did it three times. Same error.

Arc · 22 Dec 2013

It appears that you have performed an upgrade, which left lots of stuff old, and that is causing the issue.

If you perform a Clean Install with a Upgrade Windows 7 Version, hopefully the situation will be better.