BSODs when computer is about to shut down. No visible error code.

[Corny]

Recently, I have noticed that I have been getting BSOD errors when shutting down the computer. Right before the computer is about to shut down, the screen fizzes out and the comp restarts. The BSOD does not appear to look like an ordinary one and there is no error code visible.

According to device manager, all of my drivers are installed.

My Specs:

Windows 7 Pro 64 Bit
AMD XFX Radon 6870
4 GB G-Skill Ripjaw 1600 mhz
AMD FX 6100 Processor
Asus Xonar DG Soundcard
Belkin Wireless USB
Corsair TX 650 Watt
Asus M599XEVO

I also have not done any overclocking.
I will also try and get a picture of the blue screen when I next see it occur.

Thanks for any possible help!

 

[Arc]

The BSOD is caused by Belkin USB Wireless Adapter Driver.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002e82e42}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=RTL8192su.sys"]RTL8192su.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=RTL8192su.sys"]RTL8192su.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=RTL8192su.sys"]RTL8192su.sys[/URL] ( RTL8192su+fd34 )

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

And the driver is very old.

fffff880`0a87e000 fffff880`0a941000   RTL8192su T (no symbols)           
    Loaded symbol image file: RTL8192su.sys
    Image path: RTL8192su.sys
[COLOR=Red]    Image name: RTL8192su.sys
    Timestamp:        Thu Jul 08 12:48:33 2010[/COLOR] (4C357BC9)
    CheckSum:         000B0D2E
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download and install Realtek RTL8192SU Wireless LAN 802.11n USB 2.0 Network Adapter Driver for it, from Realtek

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Free up the startup . Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

 

[Corny]

I have first updated the wireless driver from Realtek, then uninstalled Daemon Tools and checked for SPTD with the program from disc tools (the "uninstall" option was grayed out), and finally changed the startup to include only the Kaspersky Internet Security.

During that process, I have gotten another BSOD when I restarted the system after I installed the Realtek driver. This time however, the BSOD appeared to look like a normal one with an error code. I didnt have a pen with me at the time to write it down but the new dump file is here.

 

[Arc]

This BSOD caused by the same driver as mentioned earlier, though it is updated to a comparatively later version. No newer update is available at all?
USB network adapters with with old drivers are always problematic. But before changing the adapter, you may have another try.

Kaspersky sometimes blocks network access and causes BSODs. Just as a test if it is the same going on here or not, uninstall Kaspersky using Kaspersky Removal Tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Now observe the situation. If it still crashes and blames the same driver, you will need to change the dongle to a newer one.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff88001c7fa1b}

*** WARNING: Unable to verify timestamp for [COLOR=Red]RTL8192su.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=Red]RTL8192su.sys[/COLOR]
Probably caused by : [COLOR=Red]RTL8192su.sys[/COLOR] ( RTL8192su+fdf8 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001c7fa1b, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030cc100
GetUlongFromAddress: unable to read from fffff800030cc1c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!ndisOidRequestComplete+9b
fffff880`01c7fa1b 803e05          cmp     byte ptr [rsi],5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800394e790 -- (.trap 0xfffff8800394e790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff880039861e0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001c7fa1b rsp=fffff8800394e920 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=ffffffffffffffef
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
ndis!ndisOidRequestComplete+0x9b:
fffff880`01c7fa1b 803e05          cmp     byte ptr [rsi],5 ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e941a9 to fffff80002e94c00

STACK_TEXT:  
fffff880`0394e648 fffff800`02e941a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0394e650 fffff800`02e92e20 : 00000000`00000001 fffff880`079bb110 fffffa80`03c42840 fffff880`039861e0 : nt!KiBugCheckDispatch+0x69
fffff880`0394e790 fffff880`01c7fa1b : fffff880`0394ea50 00000000`00000001 00000000`00000000 fffffa80`03dcab50 : nt!KiPageFault+0x260
fffff880`0394e920 fffff880`01ccaffe : fffff880`0394ea00 00000000`00000000 fffff880`039861e0 00000000`00000000 : ndis!ndisOidRequestComplete+0x9b
fffff880`0394e9b0 fffff880`01d1771e : fffff880`039861e0 fffff880`01ce0110 00000000`00000000 fffffa80`03dcab50 : ndis!ndisMOidRequestCompleteInternal+0xde
fffff880`0394ea30 fffff880`0a70ddf8 : fffff880`039861e0 00000000`00000001 fffffa80`05ffe000 fffff800`0303a280 : ndis!NdisMOidRequestComplete+0x6e
fffff880`0394ea70 fffff880`039861e0 : 00000000`00000001 fffffa80`05ffe000 fffff800`0303a280 fffffa80`05ffe000 : RTL8192su+0xfdf8
fffff880`0394ea78 00000000`00000001 : fffffa80`05ffe000 fffff800`0303a280 fffffa80`05ffe000 fffff880`0a70dd06 : 0xfffff880`039861e0
fffff880`0394ea80 fffffa80`05ffe000 : fffff800`0303a280 fffffa80`05ffe000 fffff880`0a70dd06 00000000`00000001 : 0x1
fffff880`0394ea88 fffff800`0303a280 : fffffa80`05ffe000 fffff880`0a70dd06 00000000`00000001 00000000`00000000 : 0xfffffa80`05ffe000
fffff880`0394ea90 fffffa80`05ffe000 : fffff880`0a70dd06 00000000`00000001 00000000`00000000 fffffa80`0718c100 : nt!ExWorkerQueue
fffff880`0394ea98 fffff880`0a70dd06 : 00000000`00000001 00000000`00000000 fffffa80`0718c100 fffff880`01d0410c : 0xfffffa80`05ffe000
fffff880`0394eaa0 00000000`00000001 : 00000000`00000000 fffffa80`0718c100 fffff880`01d0410c 00000000`00000001 : RTL8192su+0xfd06
fffff880`0394eaa8 00000000`00000000 : fffffa80`0718c100 fffff880`01d0410c 00000000`00000001 fffffa80`05e518b0 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTL8192su+fdf8
fffff880`0a70ddf8 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  RTL8192su+fdf8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTL8192su

IMAGE_NAME:  RTL8192su.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e434031

FAILURE_BUCKET_ID:  X64_0xD1_RTL8192su+fdf8

BUCKET_ID:  X64_0xD1_RTL8192su+fdf8

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

4: kd> lmvm RTL8192su
start             end                 module name
fffff880`0a6fe000 fffff880`0a7c1000   RTL8192su T (no symbols)           
    Loaded symbol image file: RTL8192su.sys
    Image path: \SystemRoot\system32\DRIVERS\RTL8192su.sys
[COLOR=Red]    Image name: RTL8192su.sys
    Timestamp:        Thu Aug 11 08:06:33 2011[/COLOR] (4E434031)
    CheckSum:         000B620E
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[Corny]

Hm thanks a lot so far on the feedback.

I downloaded a driver off the Belken website itself and I did not get a BSOD last night when I shut off.

I will continue testing this week.

 

[Arc]

Apparently good
Let us know how it worked.