Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD after shutdown, error 0x00000d1, shutdown not complete

25 Jan 2013   #11
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Johny, your crash dump makes me a bit . It's strange, and its rare.
Code:
Unable to load image rspCrash32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rspCrash32.sys
*** ERROR: Module load completed but symbols could not be loaded for rspCrash32.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {0, 0, 189dbc49, 3c2a58ed}

Probably caused by : rspCrash32.sys ( rspCrash32+10b2 )

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

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

MANUALLY_INITIATED_CRASH1 (deaddead)
The user manually initiated this crash dump.
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 189dbc49
Arg4: 3c2a58ed

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xDEADDEAD

PROCESS_NAME:  WhoCrashedEx.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9c5480b2 to 83d2ae98

STACK_TEXT:  
aef82ad0 9c5480b2 deaddead 00000000 00000000 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
aef82aec 84a2ead1 00000000 0012f508 00000018 rspCrash32+0x10b2
aef82b38 84a44641 9cf10c28 0012f508 00000018 fltmgr!FltpFilterMessage+0x9d
aef82b6c 84a44a69 8b4dc300 00000000 0012f508 fltmgr!FltpMsgDeviceControl+0xa9
aef82bb0 84a2d339 8b3b0148 a0ea6f68 8b2c2898 fltmgr!FltpMsgDispatch+0x91
aef82bdc 83f7e6c3 8b3b0148 a0ea6f68 8b4dc398 fltmgr!FltpDispatch+0x33
aef82c00 83c82be0 00000000 a0ea6f68 8b3b0148 nt!IovCallDriver+0x258
aef82c14 83e77b29 8b4dc398 a0ea6f68 a0ea6fd8 nt!IofCallDriver+0x1b
aef82c34 83e7acfb 8b3b0148 8b4dc398 00000000 nt!IopSynchronousServiceTail+0x1f8
aef82cd0 83ec163b 8b3b0148 a0ea6f68 00000000 nt!IopXxxControlFile+0x6aa
aef82d04 83c898fa 000001cc 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
aef82d04 77147094 000001cc 00000000 00000000 nt!KiFastCallEntry+0x12a
0012f490 00000000 00000000 00000000 00000000 0x77147094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rspCrash32+10b2
9c5480b2 6a04            push    4

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  rspCrash32+10b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rspCrash32

IMAGE_NAME:  rspCrash32.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50976853

FAILURE_BUCKET_ID:  0xDEADDEAD_rspCrash32+10b2

BUCKET_ID:  0xDEADDEAD_rspCrash32+10b2 

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

0: kd> lmvm rspCrash32
start    end        module name
9c547000 9c54e000   rspCrash32 T (no symbols)           
    Loaded symbol image file: rspCrash32.sys
    Image path: rspCrash32.sys
    Image name: rspCrash32.sys
    Timestamp:        Mon Nov 05 12:48:43 2012 (50976853)
    CheckSum:         000041EC
    ImageSize:        00007000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
So, it says that it is manually initiated. It may not be a fact, coz only the trolls do it, and you are not a troll It may be something happened, may be something played there beyond your knowledge.

This bugcheck code 0xDEADDEAD is some results of a registry manipulation, some registries of keyboard/mouse usage. TuneUp may cause it, as it mess up with the registries upto a great extent, and sometimes it comes to be beyond repair. Uninstall TuneUp Utilities. Run SFC /SCANNOW Command - System File Checker

It is expected that SFC will recover those errors of registry. If not, we need to take some different ways.

At the same time, rspCrash32.sys indicates to WhoCrashed. So better you uninstall it, too.

Let us know the results.


My System SpecsSystem Spec
.
25 Jan 2013   #12
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

The DEADDEAD bugcheck means that a driver (in this case, rspCrash32.sys) called KeBugCheckEx and forced a crash to occur. I don't know why a program that informs you of system crashes will actually force a crash itself, but I advise along with Arc to remove WhoCrashed. The TuneUp Utilities are also a no-no. Remove them.
My System SpecsSystem Spec
28 Jan 2013   #13
Jhony Smith

Microsoft Windows 7 Ultimate 32-bit 7601 Multiprocessor Free Service Pack 1
 
 

Quote   Quote: Originally Posted by Arc View Post
Yes, it is TuneUp utilities

Most of us SF members believe that it is not tune up but tune down; but that is a different story. Uninstall it for the time being (the best option is to not use it at all; windows 7 does not need any of those programs, and they are not enough efficient to deal with windows 7's file and registry structure. It is good for XP).

I hope you will be able to upload a crash dump after uninstalling it.
I finally manage to get some minidump...didnt know what to select...so i compressed them all, try to get last one might be 2 that were caused by seem programs intentionally.
please heeelp
My System SpecsSystem Spec
.

28 Jan 2013   #14
Jhony Smith

Microsoft Windows 7 Ultimate 32-bit 7601 Multiprocessor Free Service Pack 1
 
 

Quote   Quote: Originally Posted by Vir Gnarus View Post
The DEADDEAD bugcheck means that a driver (in this case, rspCrash32.sys) called KeBugCheckEx and forced a crash to occur. I don't know why a program that informs you of system crashes will actually force a crash itself, but I advise along with Arc to remove WhoCrashed. The TuneUp Utilities are also a no-no. Remove them.
Told you, some crashes were intentionally to see if its possible to write some minidumps...
the last minidump that I attched earlier said this...(i will atach a file .txt from windbg)
Please translate what he sais
My System SpecsSystem Spec
28 Jan 2013   #15
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {cff30023, ff, 8, cff30023} DRIVER_IRQL_NOT_LESS_OR_EQUAL

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )

Followup: MachineOwner
---------
Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
29 Jan 2013   #16
Jhony Smith

Microsoft Windows 7 Ultimate 32-bit 7601 Multiprocessor Free Service Pack 1
 
 

Got 2 minidumps Hope it helps !
My System SpecsSystem Spec
29 Jan 2013   #17
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It indicates to Motorola SM56 voice modem driver.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, 94e942cc, 94956ed8, 0}

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

Followup: MachineOwner
---------
And that is really old.
Code:
94e8c000 94fa0000   smserial T (no symbols)           
    Loaded symbol image file: smserial.sys
    Image path: \SystemRoot\system32\DRIVERS\smserial.sys
    Image name: smserial.sys
    Timestamp:        Fri Sep 26 13:53:38 2008 (48DC9C0A)
    CheckSum:         0010D5AE
    ImageSize:        00114000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Try to update it from Motorola Mobility - Motorola Solutions - India
My System SpecsSystem Spec
30 Jan 2013   #18
Vir Gnarus

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

The Motorola driver one may be a false positive because Force Pending I/O Requests check on Driver Verifier was enabled. Please do not have that option checked. The driver is very old, though, as it predates Windows 7. Please find an update as Arc mentioned, or remove it altogether.

The other DV crashdump showed behavior I cannot interpret with just the minidump. However, I'm concerned that if DV didn't catch a 3rd-party driver immediately in its tracks, then we may very well be dealing with hardware failure. I recommend doing a battery of hardware tests as follows:

RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Blend; overnight (9+ hours)
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones or Long Generic.

All of these are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the latest version of UBCD due to a bug. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. If you can get the system to crash during high load logging, that's even better. Be careful with Prime95, as it will generate high heat for your CPU. Make sure your CPU cooling is stable before letting it run for an extended period of time.
My System SpecsSystem Spec
03 Feb 2013   #19
Jhony Smith

Microsoft Windows 7 Ultimate 32-bit 7601 Multiprocessor Free Service Pack 1
 
 

Sorry it took a while for me to get back, the error is still on, so ill try that...I am assuming that the error might come from CPU, 'cause its always hot, and the cooler sounds like an rocket engine...Am I risking a CPU failure ? with or without the tests ?
My System SpecsSystem Spec
04 Feb 2013   #20
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

If it is a hit CPU, first dismantle the system and make it sure that the thermal paste still exists. If not, apply Arctic Silver.

Then stress test the CPU.
Hardware - Stress Test With Prime95
My System SpecsSystem Spec
Reply

 BSOD after shutdown, error 0x00000d1, shutdown not complete




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Complete Computer Shutdown Attempting Target Disk Mode
I have an Asus k55A laptop which originally came with Windows 8. I installed Windows 7 Ultimate x64 in a separate partition as well as upgraded the original OS to 8.1 (like anything they do is going to make Windows 8 better). I mainly run Windows 7. Recently, I obtained a Mac iBook G4. This...
Performance & Maintenance
BSOD as computer shutdown, turns on after shutdown
I have shutdown correctly, but I get BSOD and then it shutdowns, but then it turns on again.
BSOD Help and Support
Complete and unexpected System shutdown
Hello, Iv'e been working on this for a few days now and cant seem to come to any definite diagnosis so I really hope someone here can help! For the last 2/3 months I have sometimes noticed (but never seen first hand) that if I left my computer on for a few hours that sometimes Id come back and...
BSOD Help and Support
No BSOD but Complete shutdown and restart uTorrent issue Maybe?
I thought the original problem was related to uTorrent, however it just happened again without uTorrent running. There is no traditional BSOD, just black screen as the PC reboots. I get the "Start in safe mode option" I had my RAM set to XMP but disabled that and set it back to Manual before...
BSOD Help and Support
BSOD on Shutdown - Error 0x50
I built a custom desktop last week (specs are in profile). I've had 3 BSODs in the last 10 days. (The 4th one was caused when I tried to use DriverVerifier) The most recent one happened after trying to shut down Windows. BlueScreenView shows them as Bug Check Code 0x50 PAGE_FAULT_IN_NONPAGED_AREA....
BSOD Help and Support
annoying usb net drop no complete shutdown error
hello, my name is chris. i have recently upgraded my machine. Windows 7 Home Premium x64 (inc Service pack 1) Asus Crosshair IV Formula AMD Phenom II 1100T x6 Corsair Vengeance 4x 4gb 1600mhz XFX Radeon HD6870 2x WD 20EARS 2TB Sata drives
General Discussion


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 17:20.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App