BSOD...several messages

dustinbrimer · 31 Oct 2010

I've been getting BSOD's for the last week or so...almost every time I reboot. 7 tries to do repairs prior to full boot up, but always says its unable to find anything wrong. At that time, it'll make it all the way into windows - both in safe mode or standard. The BSOD messages I've received are always different. The ones that have remained up long enough for me to jot down have been:

Bugcode_usb_driver
system_service_exception
memory_management
irq_not_less_or_equal (most recent).

I've seen some mention that their blue screen issues start after making the machine sleep...I did do that for the first time ever somewhat recently, so maybe that's part of it? I ran memtestx86+ and it stated "windows resource protection found corrupt files but was unable to fix some of them." I've attached the log file from that as well as my mini dump from the most recent BSOD display.

To my knowledge all my drivers are up to date. However, on my devices manager, it lists a Multimedia controller & Multimedia Video Controller as not having drivers installed...can't track them down for my mobo either.

I've had 7 installed for the greater part of a year now with no problems until recently. I have 4 GB ram, a 2.13GHz core 2 duo cpu. Overall, the rig is probably a few years old by now. I'm running 7 Ultimate x64 retail and it was installed clean.

I'm definitely stumped at this point. Any help you guys can throw my way would be greatly appreciated.

Thanks in advance,

Dustin

zigzag3143 · 31 Oct 2010

dustinbrimer said:

I've been getting BSOD's for the last week or so...almost every time I reboot. 7 tries to do repairs prior to full boot up, but always says its unable to find anything wrong. At that time, it'll make it all the way into windows - both in safe mode or standard. The BSOD messages I've received are always different. The ones that have remained up long enough for me to jot down have been:

Bugcode_usb_driver
system_service_exception
memory_management
irq_not_less_or_equal (most recent).

I've seen some mention that their blue screen issues start after making the machine sleep...I did do that for the first time ever somewhat recently, so maybe that's part of it? I ran memtestx86+ and it stated "windows resource protection found corrupt files but was unable to fix some of them." I've attached the log file from that as well as my mini dump from the most recent BSOD display.

To my knowledge all my drivers are up to date. However, on my devices manager, it lists a Multimedia controller & Multimedia Video Controller as not having drivers installed...can't track them down for my mobo either.

I've had 7 installed for the greater part of a year now with no problems until recently. I have 4 GB ram, a 2.13GHz core 2 duo cpu. Overall, the rig is probably a few years old by now. I'm running 7 Ultimate x64 retail and it was installed clean.

I'm definitely stumped at this point. Any help you guys can throw my way would be greatly appreciated.

Thanks in advance,

Dustin

Dustin

First remove stpd.sys (daemon tools/alcohol)

Please 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
[/quote]
You can use MagicDisc as an alternative.

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

Second Update drivers

Code:

adfs.SYS        fffff880`05a23000    fffff880`05a3b000    0x00018000    0x48640195    6/26/2008 16:52:37                        
a1s6ow8j.SYS        fffff880`0491f000    fffff880`04963000    0x00044000    0x49c4fe40    3/21/2009 10:48:32                        
sptd.sys        fffff880`0107c000    fffff880`011b0000    0x00134000    0x49c63097    3/22/2009 08:35:35                        
spldr.sys        fffff880`0169b000    fffff880`016a3000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
spsys.sys        fffff880`07600000    fffff880`07671000    0x00071000    0x4a085e7a    5/11/2009 13:20:58                        
GEARAspiWDM.sys        fffff880`04b95000    fffff880`04ba2000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`00e00000    fffff880`00e0b000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

These were 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 Stop 0x124 - what it means and what to try

Thanks

Ken

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\Windows_NT6_BSOD_jcgriff2\103110-33867-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Sun Oct 31 14:48:46.929 2010 (GMT-4)
System Uptime: 0 days 0:02:03.098
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffd8000f07dfa4, 2, 1, fffff80002f30210}

Probably caused by : hardware ( nt!EtwTraceReadyThread+d0 )

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

1: 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: ffffd8000f07dfa4, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002f30210, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af0e0
 ffffd8000f07dfa4 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!EtwTraceReadyThread+d0
fffff800`02f30210 00448954        add     byte ptr [rcx+rcx*4+54h],al

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  dwm.exe

TRAP_FRAME:  fffff88002f22d60 -- (.trap 0xfffff88002f22d60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8005d80b60 rbx=0000000000000000 rcx=fffff80003019310
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f30210 rsp=fffff88002f22ef8 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000064 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!EtwTraceReadyThread+0xd0:
fffff800`02f30210 00448954        add     byte ptr [rcx+rcx*4+54h],al ds:0001:ffffd800`0f07dfa4=??
Resetting default scope

MISALIGNED_IP: 
nt!EtwTraceReadyThread+d0
fffff800`02f30210 00448954        add     byte ptr [rcx+rcx*4+54h],al

LAST_CONTROL_TRANSFER:  from fffff80002e76ca9 to fffff80002e77740

STACK_TEXT:  
fffff880`02f22c18 fffff800`02e76ca9 : 00000000`0000000a ffffd800`0f07dfa4 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f22c20 fffff800`02e75920 : 00000000`00000001 fffff880`009e7180 00000000`00000064 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f22d60 fffff800`02f30210 : fffff800`02e82bfc fffff880`009e7180 fffffa80`00001e8f 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f22ef8 00000598`00000000 : 00000598`00000000 00000598`00000000 00000598`00000000 00000598`00000000 : nt!EtwTraceReadyThread+0xd0
fffff880`02f22f48 00000598`00000000 : 00000598`00000000 00000598`00000000 00000598`00000000 80000000`00000001 : 0x598`00000000
fffff880`02f22f50 00000598`00000000 : 00000598`00000000 00000598`00000000 80000000`00000001 00000000`00000002 : 0x598`00000000
fffff880`02f22f58 00000598`00000000 : 00000598`00000000 80000000`00000001 00000000`00000002 00000000`003a83f0 : 0x598`00000000
fffff880`02f22f60 00000598`00000000 : 80000000`00000001 00000000`00000002 00000000`003a83f0 00000000`00000001 : 0x598`00000000
fffff880`02f22f68 80000000`00000001 : 00000000`00000002 00000000`003a83f0 00000000`00000001 00000000`00479900 : 0x598`00000000
fffff880`02f22f70 00000000`00000002 : 00000000`003a83f0 00000000`00000001 00000000`00479900 00000000`00000000 : 0x80000000`00000001
fffff880`02f22f78 00000000`003a83f0 : 00000000`00000001 00000000`00479900 00000000`00000000 fffff880`02befca0 : 0x2
fffff880`02f22f80 00000000`00000001 : 00000000`00479900 00000000`00000000 fffff880`02befca0 fffff880`009e7180 : 0x3a83f0
fffff880`02f22f88 00000000`00479900 : 00000000`00000000 fffff880`02befca0 fffff880`009e7180 fffff800`02e7d865 : 0x1
fffff880`02f22f90 00000000`00000000 : fffff880`02befca0 fffff880`009e7180 fffff800`02e7d865 00000598`00000000 : 0x479900


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!EtwTraceReadyThread+d0
fffff800`02f30210 00448954        add     byte ptr [rcx+rcx*4+54h],al

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!EtwTraceReadyThread+d0

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

dustinbrimer · 31 Oct 2010

Ken,

I deleted the emulation software and that seems to have cleared it up so far. I've rebooted several times now with no snags whatsoever. I'm going to go through the thread you linked about Stop 0x124 messages now and see if there's any other loose ends to look for.

Thanks so much for your quick reply!

Dustin

zigzag3143 · 31 Oct 2010

dustinbrimer said:

Ken,

I deleted the emulation software and that seems to have cleared it up so far. I've rebooted several times now with no snags whatsoever. I'm going to go through the thread you linked about Stop 0x124 messages now and see if there's any other loose ends to look for.

Thanks so much for your quick reply!

Dustin

My pleasure glad to hear it is helping

Ken J

dustinbrimer · 01 Nov 2010

Well, that was short lived success. I got one more bsod while reading about stop errors (ironically). This one read "page fault in nonpaged area." I shut it off for the night in disgust. When I went to turn it on this afternoon, I couldn't get a display to come up...monitor just stays in standby. I've turned it on/off...switched to the 2nd dvi out on the video card, still nothing.

Ken, if you're reading this...you mentioned that the generic stop error generally correlates to a piece of hardware in distress. Is it possible that it was the video card and that it just finally died last night? The pain of this situation now is that I only have the one pci x16 slot on this mobo to move the vid card around on...nor do I have another pci x16 vid card to swap out...

Does anybody have an idea/opinion of what the best move would be to make at this point? I'm just hesitant to drop 100-300 bucks on a new video card to find thats not the issue either.

Thanks again,

Dustin