Windows crashes with errors 7B, 1E, and others

After having some earlier trouble with my CD drive and my new Nvidia 9800GTX conflicting things seemed to be running smoothly. The system was stable literally all day while it was in use. Then, tonight, I suddenly blue screened with a 1E error. The computer restarted and almost immediately crashed again with another 1E. I finally managed to boot up and after a few minutes I crashed again with a 7B error instead. I know this most likely has to do with the new video card. I also heard from a friend that errors like this could be caused by virtual drives conflicting with the card and I do have a virtual drive running, which I disabled now.

I've included a zip folder with all of my crashes from the last two days inside of it. If someone could analyze my last few dumps and tell me how I can fix this, I'd be extremely thankful. I'm running Windows 7 64-bit with an Intel Dual-Core E5400 @ 2.7 GHz, an Asus P5N-D board, 4 GB DDR2 800 RAM, and the aforementioned 9800GTX.

MorsePacific said:

After having some earlier trouble with my CD drive and my new Nvidia 9800GTX conflicting things seemed to be running smoothly. The system was stable literally all day while it was in use. Then, tonight, I suddenly blue screened with a 1E error. The computer restarted and almost immediately crashed again with another 1E. I finally managed to boot up and after a few minutes I crashed again with a 7B error instead. I know this most likely has to do with the new video card. I also heard from a friend that errors like this could be caused by virtual drives conflicting with the card and I do have a virtual drive running, which I disabled now.

I've included a zip folder with all of my crashes from the last two days inside of it. If someone could analyze my last few dumps and tell me how I can fix this, I'd be extremely thankful. I'm running Windows 7 64-bit with an Intel Dual-Core E5400 @ 2.7 GHz, an Asus P5N-D board, 4 GB DDR2 800 RAM, and the aforementioned 9800GTX.

Easy

You have two of the biggest causes of BSOD's installed

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).


2-SPTD.SYS the second biggest cause used by daemon tools and alcohol120

Remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller when you're done:DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview


OR

SlySoft Virtual CloneDrive

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder\052611-27658-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02860000 PsLoadedModuleList = 0xfffff800`02aa5650
Debug session time: Thu May 26 03:58:33.597 2011 (GMT-4)
System Uptime: 0 days 0:09:04.299
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : sptd.sys ( sptd+46ae8 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6454952f0381dcd0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba2858 -- (.exr 0xfffff80000ba2858)
ExceptionAddress: fffff88000e771d2 (Wdf01000!FxRequestBase::CompleteSubmitted+0x000000000000011e)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba2900 -- (.trap 0xfffff80000ba2900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=11b94aa50275ace8 rbx=0000000000000000 rcx=fffffa80057cea90
rdx=fffffa80057cda10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000e771d2 rsp=fffff80000ba2a90 rbp=0000000000000000
 r8=fffffa80057cda00  r9=0000000000000000 r10=fffffa8005674e70
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Wdf01000!FxRequestBase::CompleteSubmitted+0x11e:
fffff880`00e771d2 ff5018          call    qword ptr [rax+18h] ds:aa01:11b94aa5`0275ad00=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800028d76be to fffff800028dfcd0

STACK_TEXT:  
fffff800`00ba1938 fffff800`028d76be : 00000000`00000000 00000000`00000000 fffff800`00ba20b0 fffff800`0290b890 : nt!KeBugCheck
fffff800`00ba1940 fffff800`0290b55d : fffff800`02ae6968 fffff800`02a23cbc fffff800`02860000 fffff800`00ba2858 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1970 fffff800`0290a335 : fffff800`02a27028 fffff800`00ba19e8 fffff800`00ba2858 fffff800`02860000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba19a0 fffff800`0291b3b1 : fffff800`00ba2858 fffff800`00ba20b0 fffff800`00000000 fffffa80`05674e70 : nt!RtlDispatchException+0x415
fffff800`00ba2080 fffff800`028df382 : fffff800`00ba2858 fffffa80`057cda10 fffff800`00ba2900 fffffa80`0580fe40 : nt!KiDispatchException+0x135
fffff800`00ba2720 fffff800`028ddc8a : 00000000`00000000 fffff880`042787a8 00000000`00000018 00000000`c00000bb : nt!KiExceptionDispatch+0xc2
fffff800`00ba2900 fffff880`00e771d2 : 00000000`00000005 00000000`00000004 00000000`00000000 00000000`00000004 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2a90 fffff880`00e4dc9b : fffffa80`0580fe40 fffffa80`0580fe40 fffffa80`0580fe50 fffffa80`04d67c01 : Wdf01000!FxRequestBase::CompleteSubmitted+0x11e
fffff800`00ba2b10 fffff880`00e4ddc4 : fffffa80`03e0e802 00000000`00000000 00000000`00000000 fffff800`0281a7d8 : Wdf01000!FxIoTarget::RequestCompletionRoutine+0x1cb
fffff800`00ba2b80 fffff800`028cc505 : 00000000`00000000 fffffa80`05e39010 00000000`00000005 fffff800`028e2d41 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x3c
fffff800`00ba2bb0 fffff800`028e3091 : fffffa80`04d67e0b 00000000`00000000 00000000`00000000 00000000`000007ff : nt!IopUnloadSafeCompletion+0x55
fffff800`00ba2bf0 fffff880`04213631 : fffffa80`0507c050 fffffa80`057ceb00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3b1
fffff800`00ba2cd0 fffff880`04213b0f : fffffa80`03e0e802 fffffa80`04d67c60 00000000`ffffffff fffffa80`0507ceb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff800`00ba2db0 fffff880`0421166f : fffffa80`0507ceb0 fffffa80`0507c1a0 fffffa80`0507d050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00ba2e10 fffff880`04202f89 : fffffa80`0507c050 00000000`00000000 fffffa80`0507ce02 fffffa80`0507ceb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00ba2e50 fffff880`010b2ae8 : fffffa80`04d98000 fffffa80`0507cec8 fffffa80`0507ce00 fffff800`00ba2ef8 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00ba2e80 fffffa80`04d98000 : fffffa80`0507cec8 fffffa80`0507ce00 fffff800`00ba2ef8 00000000`00000000 : sptd+0x46ae8
fffff800`00ba2e88 fffffa80`0507cec8 : fffffa80`0507ce00 fffff800`00ba2ef8 00000000`00000000 00000000`00000000 : 0xfffffa80`04d98000
fffff800`00ba2e90 fffffa80`0507ce00 : fffff800`00ba2ef8 00000000`00000000 00000000`00000000 00000000`00000022 : 0xfffffa80`0507cec8
fffff800`00ba2e98 fffff800`00ba2ef8 : 00000000`00000000 00000000`00000000 00000000`00000022 00000000`00000000 : 0xfffffa80`0507ce00
fffff800`00ba2ea0 00000000`00000000 : 00000000`00000000 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffff800`00ba2ef8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
sptd+46ae8
fffff880`010b2ae8 ??              ???

SYMBOL_STACK_INDEX:  10

SYMBOL_NAME:  sptd+46ae8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: sptd

IMAGE_NAME:  sptd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7362f8

FAILURE_BUCKET_ID:  X64_0x1E_sptd+46ae8

BUCKET_ID:  X64_0x1E_sptd+46ae8

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

Wow, thank you so much for responding so quickly. I had just about given up for the night. I'll get right on it and see what happens. Thanks so much!

MorsePacific said:

Wow, thank you so much for responding so quickly. I had just about given up for the night. I'll get right on it and see what happens. Thanks so much!

Just stumbled across the thread and the causes were so obvious. Good luck

I followed your instructions and after using the SPTD uninstaller, the system rebooted and crashed again almost immediately with another 1E error. I zipped the new dump up and included it. It seems to be relatively stable now, however.

So this morning everything seemed to be fine but I was eventually greeted by another bluescreen and another and another. The original one was another 7e error. After rebooting I received a 1E, another 1E, an FE, and another 7E. The FE was specifically a BUGCODE_USB_DRIVER and the last named a driver specifically that I wasn't able to copy down. My system is pretty unstable, but I managed to zip up all of this morning's dumps. If someone could analyze my new dumps and help me get to the bottom of this, I'd really appreciate it.

MorsePacific said:

So this morning everything seemed to be fine but I was eventually greeted by another bluescreen and another and another. The original one was another 7e error. After rebooting I received a 1E, another 1E, an FE, and another 7E. The FE was specifically a BUGCODE_USB_DRIVER and the last named a driver specifically that I wasn't able to copy down. My system is pretty unstable, but I managed to zip up all of this morning's dumps. If someone could analyze my new dumps and help me get to the bottom of this, I'd really appreciate it.

The causes are all over the map but all of them point to a possibly commonality. DO you have a USB wifi device?

MorsePacific said:

I absolutely do. It's a Netgear WG111v3 wireless receiver.

Edit: I completely uninstalled the driver from the receiver and installed the most recent one. I haven't had a problem since, but one can never know if it's really solved. I'll keep this updated if I run across anything else. Zigzag, thank you so ridiculously much for all of your help. If you have any other suggestions I wouldn't mind hearing them.

I would update any driver before 07/13/2009 (windows release date) and Im glad you are working

Looks like my problems are back. They're far less frequent but still keep coming. The system seems more stable when I'm actually using it.