Double BSOD

[Phalanx13]

Ok i was playing flash games when i BSOD the i reboot to try and get the minidumps BSOD on the desktop before everything is finished loading. The when i try to turn it on next the fans are going full speed but other than that no computer activity. I finally got it booted and am now using a friends computer to upload the report.
​

 

[zigzag3143]

Ok i was playing flash games when i BSOD the i reboot to try and get the minidumps BSOD on the desktop before everything is finished loading. The when i try to turn it on next the fans are going full speed but other than that no computer activity. I finally got it booted and am now using a friends computer to upload the report.
​

Several problems.


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


Also your avast is known to cause BSOD's on some systems. Suggest replacing it with Microsoft security essentials

http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/

 

[Phalanx13]

Alright i have done as you have suggested hopefully i will get no more BSOD. Thank you for your time and help.

 

[zigzag3143]

Alright i have done as you have suggested hopefully i will get no more BSOD. Thank you for your time and help.

Let us know if you have problems.

 

[Phalanx13]

Alright i have run into some new problems sadly. I was loading up League of Legends i blue screened didnt catch the stop code. I reboot blue screen i think the code was 0x0000000D1 im pretty sure.

 

[zigzag3143]

Alright i have run into some new problems sadly. I was loading up League of Legends i blue screened didnt catch the stop code. I reboot blue screen i think the code was 0x0000000D1 im pretty sure.

caused by hardware

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\052911-22152-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 Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03058650
Debug session time: Sun May 29 15:51:44.599 2011 (GMT-4)
System Uptime: 0 days 0:04:08.910
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e974ba, fffff8800544a7f0, 0}

Probably caused by : hardware ( nt!KeWaitForMultipleObjects+282 )

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

0: 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: fffff80002e974ba, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800544a7f0, 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!KeWaitForMultipleObjects+282
fffff800`02e974ba 0200            add     al,byte ptr [rax]

CONTEXT:  fffff8800544a7f0 -- (.cxr 0xfffff8800544a7f0)
rax=0000000000000000 rbx=fffffa80038bcc68 rcx=0000000000000000
rdx=00000000000007ff rsi=fffffa80038bc900 rdi=fffffa80038bcb60
rip=fffff80002e974ba rsp=fffff8800544b1d0 rbp=0000000000000002
 r8=fffffa8003d4cbb8  r9=0000000000000000 r10=fffffffffffffffe
r11=0000000000000000 r12=0000000000000002 r13=fffff8800544b520
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KeWaitForMultipleObjects+0x282:
fffff800`02e974ba 0200            add     al,byte ptr [rax] ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!KeWaitForMultipleObjects+282
fffff800`02e974ba 0200            add     al,byte ptr [rax]

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e974ba

STACK_TEXT:  
fffff880`0544b1d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForMultipleObjects+0x282


FOLLOWUP_IP: 
nt!KeWaitForMultipleObjects+282
fffff800`02e974ba 0200            add     al,byte ptr [rax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KeWaitForMultipleObjects+282

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800544a7f0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

0: kd> lmvm hardware
start             end                 module name