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: Double BSOD Crash Error


16 Dec 2010   #1

windows 7 x64 home edition
 
 
Double BSOD Crash Error

Hiya,

Just been told to repost this with updated information: I'm having problems with my [COLOR=#0072BC ! important][COLOR=#0072BC ! important]computer[/COLOR][/COLOR]. Inexplicably, my dad tried to log on earlier and upon logon he got BSOD, with the error being cited as IRQL_NOT_LESS_OR_EQUAL. I'm no expert, so I tried to do a system restore, which didn't help at all. Initially, I couldn't even load it up in safe mode without getting BSOD'd, but now it has for some reason begun to work in safe mode. I've been reading around this error on my laptop and it seems to happen when there's a driver inconsistency or you've plugged something in - neither of these have happened.

One time, I got it to work for a short while, but my inet browsers weren't working, and after putting on music for 20 secs or so, I got another BSOD, this time reading SYSTEM_SERVICE_EXCEPTION.

I ran sfc /scannow as admin in cmd but it found no errors, apparently.

I've attached all the data from the minidump folder. I don't know if anyone can use it to help me - if there's something else you need I'll try and get it.



Thanks very much in advance for any help - I'd really prefer not to have to reformat so much appreciated!

Alex


My System SpecsSystem Spec
.

16 Dec 2010   #2

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Hi alx91,
Can you do chkdsk /f in command prompt?
Here's how you do it:

1. Go to Start Menu, type in cmd and hold CTRL+SHIFT+ENTER
2. Type in chkdsk /f and press enter
3. It'll ask you to restart your computer, let the computer restart.
4. When you see something like this:

Don't press any key and let it scan the system.
5. Hopefully, once it's done scanning. It will restart automatically.

Let me know the results.

Probably caused by: Ataport.sys
My System SpecsSystem Spec
16 Dec 2010   #3

Windows 7 Ultimate 32 bit
 
 

Hi, alx and welcome to the forum. I looked at three of your dad's most recent dumps - he has been having BSOD's all along. Two of the three directly blame sptd.sys, a known and notorious cause of BSOD's. Uninstall Daemon Tools or Alcohol or whatever CD virtualization program you have installed. They use this driver. When you have uninstalled the program, use this SPTD uninstaller: DuplexSecure - Downloads. Select uninstall; do NOT select reinstall.

Here is a free alternative CD virtualization program that does not use the sptd.sys driver. Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

The other dump is error code 124, a fatal hardware error code. Read this information on error code 124: [2-Int] Stop 0x124 - what it means and what to try. However, other things can created conflicts and trigger a 124. We will explore those before we test hardware.

Uninstall Trusteer Rapport. This software is a known and documented cause of problems on Win 7. Here is some information on it:
Online Banking Security | Trusteer;

MPECS Inc. Blog: Windows 7 BSODs – RapportPG64.sys is the Culprit
.

Here is another almost guaranteed BSOD maker:
Quote:
Code:
ASACPI.sys Mon Oct 30 22:09:12 2006
The 2006 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
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 8th 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 2006).
I recommend that you uninstall AVG. AVG is a known cause of BSOD's on some Win 7 systems. Use this removal tool: Tool (64 bit). If you have Identity Protection installed, remove it with this tool: Tool. Download and install Microsoft Security Essentials; it will not cause conflicts with Win 7. Make sure Windows Firewall is turned on.

Outdated third party drivers can and do cause conflicts memory corruption and BSOD's. I find three more out of date drivers loaded on the system. These are XP drivers and are not going to work with Win 7. Update these drivers from the links provided.
Quote:
nvm62x64.sys Fri Oct 17 17:01:06 2008 - nVidia Ethernet Networking Driver (nForce chipset driver). http://www.nvidia.com/Download/index.aspx.

scmndisp.sys Wed Jan 17 02:48:03 2007 - Netgear Neutral Wireless Solution. http://kb.netgear.com/app/. If there is not an update for this driver, the adapter is obsolete. Upgrade to an adapter certified compatible with Win 7.

viahduaa.sys Mon Oct 15 23:00:33 2007
- VIA High Definition Audio Function Driver. http://www.via.com.tw/en/support/drivers.jsp. Update this driver.
Follow all of the suggestions above, reboot and let's see how your system does. Post back and let us know. If you get anohter BSOS, upload it and we will go from there and possibly look at hardware.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03058e50
Debug session time: Thu Dec 16 18:57:25.023 2010 (GMT-5)
System Uptime: 0 days 0:00:16.083
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80052fa8f8, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80052fa8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031b66f0 fffff800`030d5a89 : fffffa80`052fa8d0 fffffa80`03d2cb60 00000000`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031b6c10 fffff800`02fb7667 : fffffa80`052fa8d0 fffff800`030305f8 fffffa80`03d2cb60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031b6c40 fffff800`02f1fc45 : fffff800`03092360 fffffa80`052f18d8 fffffa80`052f18d0 fffffa80`03d2cb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031b6c80 fffff800`02e98961 : fffff880`00e3be00 fffff800`02f1fc20 fffffa80`03d2cb60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031b6cb0 fffff800`0312fc06 : 00000000`00000000 fffffa80`03d2cb60 00000000`00000080 fffffa80`03c786f0 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`02e69c26 : fffff880`02f63180 fffffa80`03d2cb60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`037a5540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

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

Debug session time: Thu Dec 16 17:00:33.110 2010 (GMT-5)
System Uptime: 0 days 0:02:10.796
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff80002ea0d29}

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 : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ea0d29, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc0e0
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertQueueApc+1e9
fffff800`02ea0d29 488b5108        mov     rdx,qword ptr [rcx+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffb5b0 -- (.trap 0xfffff88002ffb5b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8003f77ad8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ea0d29 rsp=fffff88002ffb740 rbp=fffff88002fd3180
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiInsertQueueApc+0x1e9:
fffff800`02ea0d29 488b5108        mov     rdx,qword ptr [rcx+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec3ca9 to fffff80002ec4740

STACK_TEXT:  
fffff880`02ffb468 fffff800`02ec3ca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02ffb470 fffff800`02ec2920 : fffffa80`00000002 fffffa80`03fec4a0 fffffa80`07102b80 fffff880`00e25e92 : nt!KiBugCheckDispatch+0x69
fffff880`02ffb5b0 fffff800`02ea0d29 : fffff6fc`40038448 00000000`00007089 00000000`00000001 fffff800`02f780e4 : nt!KiPageFault+0x260
fffff880`02ffb740 fffff800`02ea3fec : fffffa80`03fec4a0 00000000`00000002 00000000`00000000 fffffa80`03f77ad8 : nt!KiInsertQueueApc+0x1e9
fffff880`02ffb770 fffff800`02ec755b : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x80
fffff880`02ffb7d0 fffff880`00e2341a : 00000000`00001000 00000000`00000001 fffffa80`05e82680 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
fffff880`02ffb8b0 fffff880`00e23242 : fffffa80`05e82680 fffff880`00e25b3b fffffa80`07102b80 fffffa80`04b381b0 : ataport!IdeCompleteScsiIrp+0x62
fffff880`02ffb8e0 fffff880`00e1de32 : 00000000`00000000 00000000`00000000 fffffa80`04b27500 fffffa80`04b381b0 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`02ffb910 fffff880`00e267ed : fffffa80`04b261a0 fffffa80`05e82680 00000000`00000000 fffffa80`05e82680 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`02ffba40 fffff880`00e260ec : fffffa80`04b261a0 00000000`00000000 fffffa80`04b261a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02ffbb70 fffff880`010504ce : fffffa80`049c6000 fffffa80`00000000 fffffa80`04b26050 fffffa80`049c6750 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffbc30 fffffa80`049c6000 : fffffa80`00000000 fffffa80`04b26050 fffffa80`049c6750 fffff880`02fd3180 : sptd+0x424ce
fffff880`02ffbc38 fffffa80`00000000 : fffffa80`04b26050 fffffa80`049c6750 fffff880`02fd3180 00000000`00000000 : 0xfffffa80`049c6000
fffff880`02ffbc40 fffffa80`04b26050 : fffffa80`049c6750 fffff880`02fd3180 00000000`00000000 fffff880`02fd7f40 : 0xfffffa80`00000000
fffff880`02ffbc48 fffffa80`049c6750 : fffff880`02fd3180 00000000`00000000 fffff880`02fd7f40 00000000`00000022 : 0xfffffa80`04b26050
fffff880`02ffbc50 fffff880`02fd3180 : 00000000`00000000 fffff880`02fd7f40 00000000`00000022 00000000`00000000 : 0xfffffa80`049c6750
fffff880`02ffbc58 00000000`00000000 : fffff880`02fd7f40 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffff880`02fd3180


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeCompleteScsiIrp+62
fffff880`00e2341a 8bc3            mov     eax,ebx

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ataport!IdeCompleteScsiIrp+62

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc118

FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62

BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62

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

3: kd> lmtsmn
start             end                 module name
fffff880`04f5b000 fffff880`04fa0000   aa7i7x5h aa7i7x5h.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)
fffff880`0116c000 fffff880`011c3000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02d3a000 fffff880`02dc4000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04fb9000 fffff880`04fcf000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`04094000 fffff880`040a9000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`01000000 fffff880`0100b000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`040c6000 fffff880`040ce000   ASACPI   ASACPI.sys   Mon Oct 30 22:09:12 2006 (4546B048)
fffff880`011f6000 fffff880`011ff000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e1a000 fffff880`00e44000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`0480a000 fffff880`04e21000   atikmdag atikmdag.sys Mon Aug 17 23:05:47 2009 (4A8A1A8B)
fffff960`00820000 fffff960`00881000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`03ee5000 fffff880`03f2c000   avgldx64 avgldx64.sys Wed Feb 10 22:52:31 2010 (4B737EFF)
fffff880`03edd000 fffff880`03ee4080   avgmfx64 avgmfx64.sys Wed Feb 17 17:40:14 2010 (4B7C704E)
fffff880`02ca5000 fffff880`02cf5000   avgtdia  avgtdia.sys  Wed Mar 03 12:23:33 2010 (4B8E9B15)
fffff880`05800000 fffff880`058d0000   bcmwlhigh664 bcmwlhigh664.sys Thu Nov 05 19:27:07 2009 (4AF36D5B)
fffff880`015f8000 fffff880`015ff000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03ecc000 fffff880`03edd000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`027cd000 fffff880`027eb000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00690000 fffff960`006b7000   cdd      cdd.dll      unavailable (00000000)
fffff880`00e58000 fffff880`00e82000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cbd000 fffff880`00d7d000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`013cd000 fffff880`013fd000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c5f000 fffff880`00cbd000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01546000 fffff880`015b9000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`04fa9000 fffff880`04fb9000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03fe9000 fffff880`03ff7000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03eae000 fffff880`03ecc000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03e9f000 fffff880`03eae000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`015d4000 fffff880`015ea000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`03fc7000 fffff880`03fe9000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`03e0c000 fffff880`03e15000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`03e00000 fffff880`03e0c000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01200000 fffff880`01213000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`03e15000 fffff880`03e21000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04e21000 fffff880`04f15000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04f15000 fffff880`04f5b000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`00e44000 fffff880`00e58000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00d7d000 fffff880`00dc9000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`015ca000 fffff880`015d4000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01486000 fffff880`014c0000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`017b5000 fffff880`017ff000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`04170000 fffff880`0417d000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02e0b000 fffff800`02e54000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`0414c000 fffff880`04170000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04200000 fffff880`0425c000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`041e1000 fffff880`041fa000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`04800000 fffff880`04808080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`043f0000 fffff880`043fe000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`02705000 fffff880`027cd000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`016af000 fffff880`016b8000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04308000 fffff880`04317000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04000000 fffff880`0400e000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00b9a000 fffff800`00b9d000   kdcom    kdcom.dll    Tue Nov 30 09:40:39 2010 (4CF50CE7)
fffff880`04022000 fffff880`04065000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`0152c000 fffff880`01546000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0408e000 fffff880`04093200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`02672000 fffff880`02687000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`0262e000 fffff880`02651000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c3e000 fffff880`00c4b000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`014c0000 fffff880`014ce000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04317000 fffff880`04326000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0400e000 fffff880`0401b000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00e00000 fffff880`00e1a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02600000 fffff880`02618000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`05261000 fffff880`0528e000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`0528e000 fffff880`052dc000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`052dc000 fffff880`052ff000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`00c22000 fffff880`00c2d000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`011c3000 fffff880`011cd000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`014ce000 fffff880`0152c000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03e94000 fffff880`03e9f000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`0169d000 fffff880`016af000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016c3000 fffff880`017b5000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04ff3000 fffff880`04fff000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`026da000 fffff880`026ed000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`04283000 fffff880`042b2000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04394000 fffff880`043a9000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02c16000 fffff880`02c25000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02cf5000 fffff880`02d3a000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`00c2d000 fffff880`00c3e000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03e88000 fffff880`03e94000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e54000 fffff800`03430000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0122a000 fffff880`013cd000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`00fed000 fffff880`00ff6000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`0417d000 fffff880`041e0d80   nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
fffff880`02687000 fffff880`026da000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`02dcd000 fffff880`02df3000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`040a9000 fffff880`040c6000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`011da000 fffff880`011ef000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f39000 fffff880`00f6c000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`011ef000 fffff880`011f6000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fdd000 fffff880`00fed000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`015b9000 fffff880`015ca000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`052ff000 fffff880`053a5000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`03f8a000 fffff880`03fc7000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c4b000 fffff880`00c5f000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`03e75000 fffff880`03e88000   RapportKE64 RapportKE64.sys Sun Oct 03 17:40:00 2010 (4CA8F830)
fffff880`01213000 fffff880`01225000   RapportPG64 RapportPG64.sys Sun Oct 03 17:40:07 2010 (4CA8F837)
fffff880`04fcf000 fffff880`04ff3000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`042b2000 fffff880`042cd000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`042cd000 fffff880`042ee000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`042ee000 fffff880`04308000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03e24000 fffff880`03e75000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`00ff6000 fffff880`00fff000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`00c10000 fffff880`00c19000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`00c19000 fffff880`00c22000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0144c000 fffff880`01486000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`026ed000 fffff880`02705000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`0168b000 fffff880`01695000   scmndisp scmndisp.sys Wed Jan 17 02:48:03 2007 (45ADD4B3)
fffff880`0113d000 fffff880`0116c000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`053a5000 fffff880`053b0000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`040ce000 fffff880`040da000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02c25000 fffff880`02c42000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01695000 fffff880`0169d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0100e000 fffff880`01134000   sptd     sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`05952000 fffff880`059e8000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`058eb000 fffff880`05952000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`053b0000 fffff880`053dd000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`04326000 fffff880`04327480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`053dd000 fffff880`053ef000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`02c98000 fffff880`02ca5000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02c7a000 fffff880`02c98000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02c5d000 fffff880`02c71000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`03f52000 fffff880`03f8a000   TotRec7  TotRec7.sys  Mon Apr 12 08:15:46 2010 (4BC30EF2)
fffff880`04065000 fffff880`0408e000   TotRec8  TotRec8.sys  Mon Apr 12 08:17:21 2010 (4BC30F51)
fffff960`00530000 fffff960`0053a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03f2c000 fffff880`03f52000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04328000 fffff880`0433a000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`0425c000 fffff880`04279000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`04279000 fffff880`0427af00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`0413b000 fffff880`0414c000   usbehci  usbehci.sys  Sat Oct 24 00:27:33 2009 (4AE28235)
fffff880`0433a000 fffff880`04394000   usbhub   usbhub.sys   Sat Oct 24 00:28:24 2009 (4AE28268)
fffff880`040da000 fffff880`040e5000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`040e5000 fffff880`0413b000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`011cd000 fffff880`011da000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00dc9000 fffff880`00dd7000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`043a9000 fffff880`043f0000   viahduaa viahduaa.sys Mon Oct 15 23:00:33 2007 (47142951)
fffff880`00dd7000 fffff880`00dfc000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00f6c000 fffff880`00f81000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f81000 fffff880`00fdd000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01400000 fffff880`0144c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`058d0000 fffff880`058dd000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`02c00000 fffff880`02c16000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`02c42000 fffff880`02c5d000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`00c00000 fffff880`00c10000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e86000 fffff880`00f2a000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f2a000 fffff880`00f39000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02dc4000 fffff880`02dcd000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000e0000 fffff960`003ef000   win32k   win32k.sys   unavailable (00000000)
fffff880`04fa0000 fffff880`04fa9000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`01134000 fffff880`0113d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`02651000 fffff880`02672000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`015ea000 fffff880`015f8000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`014c0000 fffff880`014cc000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`016b8000 fffff880`016c1000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01200000 fffff880`01213000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
My System SpecsSystem Spec
.


16 Dec 2010   #4

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Quote:
Hi, alx and welcome to the forum. I looked at three of your dad's most recent dumps - he has been having BSOD's all along. Two of the three directly blame sptd.sys, a know and notorious cause of BSOD's. Uninstall Daemon Tools or Alcohol or whatever CD virtualization program you have installed. They use this driver. When you have uninstalled the program, use this SPTD uninstaller: DuplexSecure - Downloads. Select uninstall; do NOT select reinstall.
Knew it would be sptd.sys. I analyzed the report, sptd.sys and ataport.sys were causing the BSOD. Don't know which one to decide.
My System SpecsSystem Spec
16 Dec 2010   #5

Windows 7 Ultimate 32 bit
 
 

Ataport.sys is a Windows system driver and very unlikely to be the real cause. On the other hand, sptd.sys is a well known and documented cause.
My System SpecsSystem Spec
17 Dec 2010   #6

windows 7 x64 home edition
 
 

Hi guys, cheers for the help on this!

Firstly, I ran chkdsk and it came up with no errors, as did memtest and windows 7 upgrade adviser.
Secondly, I removed daemon tools. For some reason it wasn't in the add/remove program list so I deleted it from the program files folder and ran the sptd.sys removal tool, which said there was no record of sptd on the computer, so I guess that worked. I then removed avg and trusteer. None of the problems described in the error 124 post are particularly relevant as I'm not overclocking or anything like that. However, I was still getting sporadic BSODs while trying to complete the rest. I have noticed a correlation with internet usage and BSODing, especially when trying to use Google Chrome. I've had to revert to Firefox which seems to be working ok. I downloaded the motherboard update and installed that, although system information said no update was needed. I had a BSOD after that as well. I've also updated the soundcard - the first time I tried to do this I got a BSOD again, but after reinstalling it seems to be a little more stable. We'll see. I haven't managed to install the nVidia drivers as it says they are up to date. However, Chrome still doesn't work and isn't it a little odd for sound drivers to cause such major problems?

This problem seems bizarre as there is no noticeable pattern to the BSODs, they just seem to happen randomly.

Cheers!

Alex
My System SpecsSystem Spec
17 Dec 2010   #7

windows 7 x64 home edition
 
 

Quick update to this: just tried to reinstall chrome. Upon loading for the first time: BSOD. Also just tried to install Magiciso - after the popup telling me it had installed properly, there was another instant BSOD. It's pretty annoying.
My System SpecsSystem Spec
17 Dec 2010   #8

Windows 7 Ultimate 32 bit
 
 

Upload your latest dumps and we will see what they tell us.
My System SpecsSystem Spec
18 Dec 2010   #9

windows 7 x64 home edition
 
 

I was away over night and when I got back the computer wouldn't even boot up in safe mode. After trying it again and again I managed to get the dumps off it. I've attached them.
My System SpecsSystem Spec
18 Dec 2010   #10

Windows 7 Ultimate 32 bit
 
 

I looked at your four most recent dumps. Each one is a different error code - including 124. This indicates a hardware problem. The fact that you are having trouble booting in the safe mode also indicates a hardware problem. Your uptimes in these dumps are 52.5 seconds, 13.0 seconds, 51.9 seconds, and 1 minute 31.1 seconds. My first thoughts are a faulty power supply unit and/or bad RAM.

You mentioned that you have run Memtest. How many passes did you let it make? You should run it for at least seven passes; this takes 6- 8 hours. Also you should run it from a cold boot after your computer has been off for a while. If you did not run Memtest as described, please run it again. Have you tried removing all but one stick of RAM and seeing how your computer boots and runs?

Do you have or can you borrow another known good power supply to try? Can you test your power supply in another computer?

Unfortunately, your dumps do give us anything specifically. Three of them blame Windows system drivers and the fourth, error code 124, blames hardware. I do see that sptd.sys is still loading in your system. Do a search of your C: drive using Windows Explore for sptd.sys. Rename or delete every occurrence you find. This driver was involved in your crashes.

See if you can update this driver. You can Google this driver and find a lot about how it misbehaves.
Quote:
ASACPI.sys Wed May 13 21:25:17 2009 - Asus ATK0110 ACPI Utility (a known BSOD maker in Windows 7). Also a part of the Asus PCProbe and AISuite Utilities. ASUSTeK Computer Inc.-Support-.
You also still have this out of date driver loading on your system.
Quote:
scmndisp.sys Wed Jan 17 02:48:03 2007 - Netgear Neutral Wireless Solution. Support Home Page. If there is not an update for this driver, the adapter is obsolete. Upgrade to an adapter certified compatible with Win 7.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02259000 PsLoadedModuleList = 0xfffff800`02496e50
Debug session time: Sat Dec 18 10:20:23.635 2010 (GMT-5)
System Uptime: 0 days 0:00:52.509
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 0, fffff800022a5d29}

Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800022a5d29, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800025010e0
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertQueueApc+1e9
fffff800`022a5d29 488b5108        mov     rdx,qword ptr [rcx+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  rstrui.exe

TRAP_FRAME:  fffff88001efb880 -- (.trap 0xfffff88001efb880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800551c898 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800022a5d29 rsp=fffff88001efba10 rbp=fffff88001ecc180
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiInsertQueueApc+0x1e9:
fffff800`022a5d29 488b5108        mov     rdx,qword ptr [rcx+8] ds:2650:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800022c8ca9 to fffff800022c9740

STACK_TEXT:  
fffff880`01efb738 fffff800`022c8ca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`01efb740 fffff800`022c7920 : fffffa80`00000002 fffffa80`0558db60 fffffa80`05430010 fffff880`01159e92 : nt!KiBugCheckDispatch+0x69
fffff880`01efb880 fffff800`022a5d29 : fffffa80`054300e0 00000000`00000200 00000000`00000000 fffff800`0237d0e4 : nt!KiPageFault+0x260
fffff880`01efba10 fffff800`022a8fec : fffffa80`0558db60 00000000`00000002 00000000`00000000 fffffa80`0551c898 : nt!KiInsertQueueApc+0x1e9
fffff880`01efba40 fffff800`022cc55b : 00000000`00000000 00000000`a000000c 00000000`00000000 00000000`00000000 : nt!KeInsertQueueApc+0x80
fffff880`01efbaa0 fffff880`0115741a : 00000000`00000200 00000000`00000001 fffffa80`05432010 00000000`00000000 : nt!IopfCompleteRequest+0xbdb
fffff880`01efbb80 fffff880`01157242 : fffffa80`05432010 fffff880`01159b3b fffffa80`05430010 fffffa80`04a481b0 : ataport!IdeCompleteScsiIrp+0x62
fffff880`01efbbb0 fffff880`01151e32 : 00000000`00000000 00000000`00000000 fffffa80`04a38500 fffffa80`04a481b0 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`01efbbe0 fffff880`0115a7ed : fffffa80`04a371a0 fffffa80`05432010 00000000`00000000 fffffa80`05432010 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`01efbd10 fffff880`0115a0ec : fffffa80`04a371a0 00000000`00000000 fffffa80`04a371a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`01efbe40 fffff800`022d4bfc : fffff880`01ecc180 fffffa80`00000d25 fffffa80`04a37050 fffffa80`04a37118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`01efbf00 fffff800`022cf865 : fffff800`04b7c850 fffffa80`055b1b60 00000000`00000000 fffff880`01159f44 : nt!KiRetireDpcList+0x1bc
fffff880`01efbfb0 fffff800`022cf67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`045e0b30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdeCompleteScsiIrp+62
fffff880`0115741a 8bc3            mov     eax,ebx

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  ataport!IdeCompleteScsiIrp+62

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc118

FAILURE_BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62

BUCKET_ID:  X64_0xA_ataport!IdeCompleteScsiIrp+62

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

Debug session time: Sat Dec 18 09:56:27.136 2010 (GMT-5)
System Uptime: 0 days 0:00:13.010
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005284038, 0, 0}

Probably caused by : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005284038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`01fb96f0 fffff800`02511a89 : fffffa80`05284010 fffffa80`03d22040 00000000`00000008 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`01fb9c10 fffff800`023f3667 : fffffa80`05284010 fffff800`0246c5f8 fffffa80`03d22040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`01fb9c40 fffff800`0235bc45 : fffff800`024ce360 fffffa80`04c16b88 fffffa80`04c16b80 fffffa80`03d22040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`01fb9c80 fffff800`022d4961 : fffff880`00c30e00 fffff800`0235bc20 fffffa80`03d22040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`01fb9cb0 fffff800`0256bc06 : 00000000`00000000 fffffa80`03d22040 00000000`00000080 fffffa80`03d1b890 : nt!ExpWorkerThread+0x111
fffff880`01fb9d40 fffff800`022a5c26 : fffff880`01e5c180 fffffa80`03d22040 fffff880`01e66fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`01fb9d80 00000000`00000000 : fffff880`01fba000 fffff880`01fb4000 fffff880`0259e540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR__UNKNOWN_PRV

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

Debug session time: Sat Dec 18 09:57:06.011 2010 (GMT-5)
System Uptime: 0 days 0:00:51.885
Loading Kernel Symbols
...............................................................
...........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800022cbcd8, fffff88003c1fab0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800022cbcd8, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003c1fab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiTryUnwaitThread+28
fffff800`022cbcd8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0

CONTEXT:  fffff88003c1fab0 -- (.cxr 0xfffff88003c1fab0)
rax=fffff88003c20428 rbx=5f5c415d4120c483 rcx=fffff88001ecc180
rdx=fffff88000e9e719 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800022cbcd8 rsp=fffff88003c20480 rbp=fffff88003c20630
 r8=0000000000000100  r9=0000000000000000 r10=0000000000000002
r11=fffffa80052f14e0 r12=0000000000000000 r13=0000000000000000
r14=fffffa800551e7e0 r15=fffff88001ecc180
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!KiTryUnwaitThread+0x28:
fffff800`022cbcd8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0 ds:002b:5f5c415d`4120c4c3=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800022cbcd8

STACK_TEXT:  
fffff880`03c20480 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x28


FOLLOWUP_IP: 
nt!KiTryUnwaitThread+28
fffff800`022cbcd8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiTryUnwaitThread+28

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff88003c1fab0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiTryUnwaitThread+28

BUCKET_ID:  X64_0x3B_nt!KiTryUnwaitThread+28

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

Debug session time: Sat Dec 18 10:10:18.642 2010 (GMT-5)
System Uptime: 0 days 0:01:37.142
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {70f89, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+35ee )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 0000000000070f89
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880012cdc24 to fffff80002288740

STACK_TEXT:  
fffff880`045bef88 fffff880`012cdc24 : 00000000`00000024 00000000`00070f89 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`045bef90 fffff880`01239aa9 : fffff800`024c0808 fffff6fc`50015928 fffff880`045bf4e0 fffff880`045ae000 : Ntfs!NtfsCommonCleanup+0x35ee
fffff880`045bf3a0 fffff800`02297e5a : fffff880`045bf4e0 fffff800`0227ddff fffff6fc`50015928 00000000`00000000 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`045bf3d0 fffff880`01239662 : fffff880`01239a90 fffff880`045bf4e0 fffff880`045bf800 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`045bf4b0 fffff880`012db244 : fffff880`045bf580 fffff880`045bf580 fffff880`045bf580 00000000`00000000 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`045bf520 fffff880`00d6a23f : fffff880`045bf580 fffffa80`067e0c10 fffffa80`067e0fb0 fffffa80`065e1c20 : Ntfs!NtfsFsdCleanup+0x144
fffff880`045bf790 fffff880`00d686df : fffffa80`04bdd920 00000000`00000000 fffffa80`04a66c00 fffffa80`067e0c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`045bf820 fffff800`0259ea0f : fffffa80`067e0c10 fffffa80`065b2b30 00000000`00000000 fffffa80`0649c770 : fltmgr!FltpDispatch+0xcf
fffff880`045bf880 fffff800`02584a24 : 00000000`00000000 fffff8a0`01575810 fffff8a0`04aa1050 00000000`0000062c : nt!IopCloseFile+0x11f
fffff880`045bf910 fffff800`0259e501 : fffff8a0`01575810 fffff8a0`00000001 fffff8a0`01575810 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`045bf990 fffff800`02546374 : 00000000`00000008 fffff8a0`01575810 fffff8a0`01d6b020 00000000`00000008 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`045bfa20 fffff800`025462f4 : 00000000`00000004 00000000`00000000 fffffa80`065b2b30 fffff800`0252f9e1 : nt!ObpCloseHandleProcedure+0x30
fffff880`045bfa60 fffff800`0254513e : fffff8a0`01c65a01 00000000`00000001 fffffa80`065b2b30 fffffa80`065b2b30 : nt!ExSweepHandleTable+0x74
fffff880`045bfaa0 fffff800`0256dd18 : fffff8a0`01c65a50 00000000`00000000 00000000`00000000 000007ff`fffde000 : nt!ObKillProcess+0x62
fffff880`045bfae0 fffff800`0254585b : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x878
fffff880`045bfba0 fffff800`02287993 : fffffa80`065b2b30 fffff880`00000000 00000000`00283e70 fffffa80`05e3cb60 : nt!NtTerminateProcess+0x25b
fffff880`045bfc20 00000000`773d001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0019fdf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773d001a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsCommonCleanup+35ee
fffff880`012cdc24 49837b4000      cmp     qword ptr [r11+40h],0

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsCommonCleanup+35ee

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonCleanup+35ee

BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonCleanup+35ee

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 Double BSOD Crash Error




Thread Tools



Similar help and support threads for2: Double BSOD Crash Error
Thread Forum
BSOD crash error STOP 0x00000101 BSOD Help and Support
BSOD crash with error 0000007f BSOD Help and Support
Great computing/technology based double double meaning jokes? Chillout Room
error 0x8000000000000002 even no BSOD just crash BSOD Help and Support
Double BSOD Crash Error BSOD Help and Support
BSOD Crash error 1000007e - HELP! BSOD Help and Support

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 10:11 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33