Random BSOD, Hangs and Reboots, Multiple Errors

C4X · 07 Sep 2011

Hello,

I've been trying to find solutions in other threads and online "help" only to find no help at all.
I would rather avoid contacting the Manufacturers if I can help it.

Some of the BSOD Error codes include:
1e, a, 24, 7e and many others.
I've had System Service Exception and Driver IRQ Equal or less (or something similar) and at this point I am at a loss.

--
System Specs:
AMD Phenom II x6 1075t 3.00GHz
4GB DDR3 RAM
nVidia GeForce 450 GTS
800w xilence PSU
Asus M4A87TD EVO Motherboard
Windows 7 x64 Home Premium SP1

- x86 (32-bit) or x64 ?
x64
- the original installed OS on the system?
yes
- an OEM or full retail version?
Full Retail I believe
- What is the age of system (hardware)?
6/7 months old
- What is the age of OS installation (have you re-installed the OS?)
No re-install as of yet, Came with windows 7.

--

I Can several high-demand games one after the other and get a clear day without crashes, then later start my Minecraft server or attempt to watch a video on YouTube and suddenly get a blue screen or random restart.
I also ran Virus Scans with Malwarebytes, Super Anti Spyware and Norton 360 and found Nothing, I did run a Check Disk and It supposedly found Hardware issues, at the least I would like to narrow it down to what It could be.
Since disabling alot of startup Items, I seem to be getting Less blue screens, Hence I'm not sure if its a false positive from the mem-check.

I've attached the Perfmon html and The Windows_nt files in one zip, and the Minidump In another.
I hope I have included everything needed and can get some help before I call the company to return my pc for fixing.

Thank-you.

seth500 · 07 Sep 2011

Most of these are said to be caused by ntkrnlmp.exe which tends to lead me to believe they are hardware related also a dump is pointed towards your usb drivers most likely outdated please update them.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\Windows_NT6_BSOD_jcgriff2\090511-24616-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03064000 PsLoadedModuleList = 0xfffff800`032a9670
Debug session time: Mon Sep  5 14:39:04.367 2011 (UTC - 6:00)
System Uptime: 0 days 1:20:44.209
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 1, fffff880043da017}

Probably caused by : usbehci.sys ( usbehci!EHCI_DecPendingTransfer+53 )

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

5: 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: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880043da017, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003313100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
usbehci!EHCI_DecPendingTransfer+53
fffff880`043da017 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880032af8e0 -- (.trap 0xfffff880032af8e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8006533c48 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043da017 rsp=fffff880032afa70 rbp=fffffa8005dcc6a0
 r8=fffffa8006a004e8  r9=fffff88005569200 r10=00000000ffffffff
r11=fffffa8005dcc6a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
usbehci!EHCI_DecPendingTransfer+0x53:
fffff880`043da017 488908          mov     qword ptr [rax],rcx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030e01e9 to fffff800030e0c40

STACK_TEXT:  
fffff880`032af798 fffff800`030e01e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`032af7a0 fffff800`030dee60 : fffffa80`06740000 fffff880`114fc4a6 fffffa80`04dbdc10 fffffa80`06a004e8 : nt!KiBugCheckDispatch+0x69
fffff880`032af8e0 fffff880`043da017 : fffff880`0397a000 fffff880`00d915fa fffffa80`049e6008 00000000`00000000 : nt!KiPageFault+0x260
fffff880`032afa70 fffff880`043d9480 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`06533ee0 : usbehci!EHCI_DecPendingTransfer+0x53
fffff880`032afaa0 fffff880`043d8b73 : fffffa80`06533c48 fffffa80`05f30900 fffffa80`06533ee0 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x540
fffff880`032afb30 fffff880`043ddd91 : fffffa80`06533c48 00000000`00000000 00000000`00000000 00000000`00000005 : usbehci!EHCI_PollPerAsyEndpoint+0x53
fffff880`032afb70 fffff880`11fa5e8b : 00000000`00000002 fffffa80`05dcb1a0 00000000`00000000 00000000`00000010 : usbehci!EHCI_PollEndpoint+0x41
fffff880`032afbb0 fffff880`11faa9d1 : 00000000`00000010 00000000`00000004 fffffa80`06533a00 fffffa80`05dcb050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`032afbe0 fffff880`11fb6077 : fffffa80`05dcb1a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`032afc40 fffff880`11fa6f89 : fffffa80`05dcb050 00000000`00000000 fffffa80`05dcba02 fffffa80`05dcba18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`032afca0 fffff800`030ec0ac : fffff880`03287180 fffffa80`05dcba18 fffffa80`05dcba30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`032afcd0 fffff800`030d896a : fffff880`03287180 fffff880`03292040 00000000`00000000 fffff880`11fa6db0 : nt!KiRetireDpcList+0x1bc
fffff880`032afd80 00000000`00000000 : fffff880`032b0000 fffff880`032aa000 fffff880`032afd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_DecPendingTransfer+53
fffff880`043da017 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbehci!EHCI_DecPendingTransfer+53

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c00

FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_DecPendingTransfer+53

BUCKET_ID:  X64_0xD1_usbehci!EHCI_DecPendingTransfer+53

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

The main concern is your memory that is most likely the cause of your biggest headache please follow this tutorial for Memtest86+: RAM - Test with Memtest86+
Let us know the results. Thanks

Seth

C4X · 07 Sep 2011

Thanks seth, I'll run the memtest soon.

Please excuse the newbie question, how would I update my USB drivers?

seth500 · 07 Sep 2011

Go here and put the info in the pull down menus knowing via technologies they probably have an all in one driver package that you just install like a program and it will update them.

VIA Drivers Download - VIA Technologies, Inc.

C4X · 07 Sep 2011

I ran the Memtest for 7 passes and It came up with 6 errors (taking nearly 6 hours :O)
If i read it correctly it found:
Two errors on 2nd Pass
One on 4th
three on 5th pass

Is there any way to view any logs it left on my Flashdrive? I was silly and didn't write down the codes or type them up into my laptop.

I will test individual sticks tomorrow as it s very late here.

seth500 · 07 Sep 2011

Actually don't worry about the codes since you had errors that is the first step and your going about it the right way, it's a lengthy process but following the tutorial is essential to ruling out the bad stick or sticks...

C4X · 08 Sep 2011

Thanks, ~~Will I need to run them for seven passes? or just until I receive errors?~~ Found the tutorial page, said 7 passes.

Also, I tried to install those USB drivers and It said It couldn't find the hardware?
Should I try the Asus Website?

seth500 · 08 Sep 2011

Yes try the asus website and see what they have for your mobo. And when you find the bad sticks you'll have to have them replaced..

C4X · 08 Sep 2011

OK so far, Ran tests on sticks one and two in slots one and 3 as they were in dual channel, each stick was clean surprisingly, looks like its my motherboard slot.
I've decided to test them in the other black dual channel slots rather than blue, i'll run the memtest tomorrow or the day after, i have a little work to do and that pc is the only one i can use photoshop on and such on.
Thank's for the help so far, i will post final results when i run the memtest

seth500 · 09 Sep 2011

Sounds good C4X