BSOD after shutdown, error 0x00000d1, shutdown not complete

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.

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

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

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

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

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

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