USB devices BSOD failed boot

[HardCelery]

My USB devices are causing crashes and failed boots until removed, thought it was a single device but it seems to be a problem with most if not all of them. EVGA X58 Micro SLI mobo. Computer will run fine and then crash suddenly and not boot until powered on with the devices removed. These devices and system worked fine before a cmos clear...Also my hdmi output no longer works either. GTX 480
Could one bad driver cause issues across multiple devices? I did get a wireless usb adapter when this started happening

 

[Alec Mowat]

Upload the DPM file from windows/minidump and I can take a look.

 

[HardCelery]

Upload the DPM file from windows/minidump and I can take a look.

https://www.dropbox.com/s/3l5df4gl1t1pewg/MEMORY.DMP?dl=0

 

[Alec Mowat]

300 MB? That's huge?

 

[Alec Mowat]

Looks like bad RAM




SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003d98d45, The address that the exception occurred at
Arg3: fffff88004d426a8, Exception Record Address
Arg4: fffff88004d41f00, Context Record Address

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


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

FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79
fffff880`03d98d45 ff90a8000000 call qword ptr [rax+0A8h]

EXCEPTION_RECORD: fffff88004d426a8 -- (.exr 0xfffff88004d426a8)
ExceptionAddress: fffff88003d98d45 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000079)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000a8
Attempt to read from address 00000000000000a8

CONTEXT: fffff88004d41f00 -- (.cxr 0xfffff88004d41f00)
rax=0000000000000000 rbx=fffff8a0010ff130 rcx=fffffa800c700000
rdx=fffffa800c808e00 rsi=fffffa800c700000 rdi=fffffa800c700000
rip=fffff88003d98d45 rsp=fffff88004d428e0 rbp=fffffa800c80d038
r8=fffffa800c803200 r9=0000000000000000 r10=0000000000000000
r11=0000000000000001 r12=fffffa800c808e00 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x79:
fffff880`03d98d45 ff90a8000000 call qword ptr [rax+0A8h] ds:002b:00000000`000000a8=????????????????
Resetting default scope

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000000a8

READ_ADDRESS: 00000000000000a8

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79
fffff880`03d98d45 ff90a8000000 call qword ptr [rax+0A8h]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: CODE_CORRUPTION

LAST_CONTROL_TRANSFER: from fffff88003d95ed3 to fffff88003d98d45

STACK_TEXT:
fffff880`04d428e0 fffff880`03d95ed3 : 00000000`00000000 fffffa80`0c755010 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x79
fffff880`04d42910 fffff880`03db065d : 00000000`00000000 fffff8a0`0101bd80 fffffa80`00000000 fffffa80`0c8032e0 : dxgmms1!VIDMM_GLOBAL:😛repareDmaBuffer+0x43f
fffff880`04d42ae0 fffff880`03db0398 : fffff800`00b96080 fffff880`03dafd00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04d42cd0 fffff880`03dafe96 : 00000000`00000000 fffffa80`0c801660 00000000`00000080 fffffa80`0c5c6410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04d42d00 fffff800`03570cce : 00000000`028d487a fffffa80`0c2a5b60 fffffa80`0a344040 fffffa80`0c2a5b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04d42d40 fffff800`032c4fe6 : fffff800`03445e80 fffffa80`0c2a5b60 fffff800`03453cc0 fffff880`01257384 : nt!PspSystemThreadStartup+0x5a
fffff880`04d42d80 00000000`00000000 : fffff880`04d43000 fffff880`04d3d000 fffff880`04d42680 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -db !dxgmms1
536 errors : !dxgmms1 (fffff88003d95042-fffff88003daaf7a)
fffff88003d95040 01 00 *ff 4c 89 7c 24 50 4c 8b *ff 24 40 4c 89 44 ...L.|$PL..$@L.D
fffff88003d95050 24 48 *ff 8b 44 24 60 48 89 44 *ff 70 44 3b ef 0f $H..D$`H.D.pD;..
fffff88003d95060 83 f6 *ff 00 00 45 8b 1f 44 89 *ff 24 6c 44 3b db .....E..D..$lD;.
fffff88003d95070 75 1c *ff 01 a6 8c 1b 00 00 49 *ff 18 33 c9 48 89 u........I..3.H.
...
fffff88003d95280 48 18 *ff 8b cd 48 89 48 20 48 *ff 78 28 8b 4c 24 H....H.H H.x(.L$
fffff88003d95290 68 48 *ff 48 30 48 89 58 38 48 *ff d0 41 8b cc ff hH.H0H.X8H..A...
fffff88003d952a0 15 33 *ff ff ff c7 84 24 08 01 *ff 00 13 ea ff ff .3.....$........
fffff88003d952b0 bf 13 *ff 1e c0 89 7c 24 34 4c *ff 44 24 48 e9 37 ......|$4L.D$H.7
...
fffff88003d954c0 ff ff *ff 89 70 18 4c 89 78 20 *ff 8f 38 01 00 00 ....p.L.x ..8...
fffff88003d954d0 48 89 *ff 28 48 89 58 30 48 89 *ff 38 48 8b d0 41 H..(H.X0H..8H..A
fffff88003d954e0 8b cc ff 15 f0 3e ff ff c7 84 *ff 08 01 00 00 85 .....>..........
fffff88003d954f0 e9 ff ff bf 11 01 1e c0 89 7c *ff 34 4c 8b 44 24 .........|.4L.D$
...
fffff88003d95940 28 04 *ff 25 48 8b 86 88 00 00 *ff 48 8b 08 48 8b (..%H......H..H.
fffff88003d95950 41 18 *ff 09 1c 24 0f ae e8 48 *ff 86 98 00 00 00 A....$...H......
fffff88003d95960 75 07 *ff 01 a6 a8 1b 00 00 48 *ff 05 48 37 ff ff u........H..H7..
fffff88003d95970 f6 40 *ff 04 74 25 48 8b 8e 88 *ff 00 00 48 8b 46 .@..t%H......H.F
...
fffff88003d95a00 4c 24 *ff 49 63 c5 44 3b eb 76 *ff 48 8d 04 40 4c L$.Ic.D;.v.H..@L
fffff88003d95a10 8d 4c *ff f0 44 8b 94 24 18 01 *ff 00 49 83 e8 08 .L..D..$....I...
fffff88003d95a20 4c 89 *ff 24 40 49 39 18 74 37 *ff 8b d2 f7 da 49 L..$@I9.t7.....I
fffff88003d95a30 8b 08 *ff c2 f0 0f c1 41 18 45 *ff 21 74 19 48 8b .......A.E.!t.H.
...
fffff88003d95c40 cf 4d *ff c6 48 8b d5 48 8b cf *ff dd 84 00 00 33 .M..H..H.......3
fffff88003d95c50 d2 48 *ff cf e8 57 3a 00 00 45 *ff c0 49 8b d6 48 .H...W:..E..I..H
fffff88003d95c60 8b cf *ff c1 85 00 00 45 33 d2 *ff 8b 0d c7 77 ff .......E3.....w.
fffff88003d95c70 ff 49 *ff ca 0f 84 be 00 00 00 *ff 8b 84 24 10 02 .I...........$..
...
fffff88003d98340 db 45 *ff d2 41 8b f8 48 8b d9 *ff 85 c9 74 03 45 .E..A..H.....t.E
fffff88003d98350 21 11 *ff 81 34 0c 00 00 f7 d0 *ff c2 74 04 32 c0 !...4.......t.2.
fffff88003d98360 eb 46 *ff d2 74 34 45 33 c0 f6 *ff 01 74 21 48 8b .F..t4E3....t!H.
fffff88003d98370 83 38 *ff 00 00 4a 8b 0c 00 8b *ff 30 23 c7 3b f8 .8...J.....0#.;.
...
fffff88003d984c0 0f ff ff 48 89 78 18 48 89 78 *ff 48 8b d0 8b ce ...H.x.H.x.H....
fffff88003d984d0 ff 15 *ff 0f ff ff c7 84 24 b8 *ff 00 00 36 dc ff ........$....6..
fffff88003d984e0 ff 33 *ff e9 3f 05 00 00 49 8b *ff 49 3b c7 74 67 .3..?...I..I;.tg
fffff88003d984f0 48 8d *ff c8 48 39 4b 08 74 0a *ff 8b 00 49 3b c7 H...H9K.t....I;.
...
fffff88003d98580 0e ff ff 4c 8b e8 48 89 44 24 *ff 48 3b c7 75 42 ...L..H.D$.H;.uB
fffff88003d98590 f0 01 *ff ed 4e ff ff c7 84 24 *ff 00 00 00 fd 23 ....N....$.....#
fffff88003d985a0 00 00 *ff 73 8e 8b ce ff 15 33 *ff ff ff 48 89 78 ...s.....3...H.x
fffff88003d985b0 18 48 *ff 78 20 48 8b d0 8b ce ff 15 18 0e ff ff .H.x H..........
...
fffff88003d98700 49 63 *ff 48 89 4b 28 48 89 7b *ff 48 89 7b 38 48 Ic.H.K(H.{.H.{8H
fffff88003d98710 8b d3 *ff ce ff 15 be 0c ff ff *ff 84 24 b8 00 00 ............$...
fffff88003d98720 00 bc *ff ff ff 33 d2 49 8b cd ff 15 78 0c ff ff .....3.I....x...
fffff88003d98730 33 c0 *ff f0 02 00 00 41 39 bc *ff 18 01 00 00 0f 3......A9.......
...
fffff88003d98880 78 18 *ff 89 78 20 48 8b d0 8b *ff ff 15 47 0b ff x...x H......G..
fffff88003d98890 ff c7 *ff 24 b8 00 00 00 5c db ff ff 33 d2 49 8b ...$....\...3.I.
fffff88003d988a0 cd ff *ff 01 0b ff ff 33 c0 e9 *ff 01 00 00 49 8b .......3......I.
fffff88003d988b0 c6 48 *ff 00 f0 ff ff 4c 3b f0 *ff 29 49 8b 44 24 .H.....L;..)I.D$
...
fffff88003d98ac0 49 01 *ff 4c 89 77 18 e9 a3 00 *ff 00 0f ba 65 00 I..L.w........e.
fffff88003d98ad0 1d 73 *ff 45 3b c6 0f 84 93 00 *ff 00 ff 15 1e 06 .s.E;...........
fffff88003d98ae0 ff ff *ff 8b 57 10 48 8b c8 ff *ff 09 06 ff ff eb ....W.H.........
fffff88003d98af0 7e f6 *ff 00 08 75 78 f6 45 00 *ff 75 06 f6 45 00 ~....ux.E..u..E.
...
fffff88003d98c40 89 54 *ff 40 48 8b 57 50 c7 44 *ff 38 01 00 00 00 .T.@H.WP.D.8....
fffff88003d98c50 4c 89 *ff 24 30 4c 89 74 24 28 *ff 89 74 24 20 e8 L..$0L.t$(..t$ .
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

STACK_COMMAND: .cxr 0xfffff88004d41f00 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID: X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

0: kd> lmvm memory_corruption
start end module name
0: kd> .exr 0xfffff88004d426a8
ExceptionAddress: fffff88003d98d45 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000079)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000a8
Attempt to read from address 00000000000000a8

 

[HardCelery]

Looks like bad RAM

Why would RAM only crash my system with usb devices though? It's running fine now but if I tried to reboot I would have to unplug everything to boot windows and the replug it in and reinstall drivers. I've already ran mem checks.

 

[Alec Mowat]

Run a memory test overnight; http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Reset your BIOS back to factory and disable any overclocking, if you are overclocking.

Could be related to power draw as well, causing your memory to fail. You can't do much to troubleshoot your PSU, other than replacing it.

What's your full system specs, including PSU?

 

[Alec Mowat]

Looks like bad RAM

Why would RAM only crash my system with usb devices though? It's running fine now but if I tried to reboot I would have to unplug everything to boot windows and the replug it in and reinstall drivers. I've already ran mem checks.

If I knew "why", I'd just post a quick fix and be done with it 😛

Bad memory can cause a lot of different issues. but it could also indicate a motherboard, PSU or CPU problem. The BSOD dump file isn't necessarily accurate.

But I would do a good 12 - 24 hour RAM test and really confirm that isn't the issue. Even try running Prime95 for awhile and see if it fails. If you don't find any errors, I'd look at the motherboard or PSU next.

 

[HardCelery]

Looks like bad RAM

Why would RAM only crash my system with usb devices though? It's running fine now but if I tried to reboot I would have to unplug everything to boot windows and the replug it in and reinstall drivers. I've already ran mem checks.

If I knew "why", I'd just post a quick fix and be done with it 😛

Bad memory can cause a lot of different issues. but it could also indicate a motherboard, PSU or CPU problem. The BSOD dump file isn't necessarily accurate.

But I would do a good 12 - 24 hour RAM test and really confirm that isn't the issue. Even try running Prime95 for awhile and see if it fails. If you don't find any errors, I'd look at the motherboard or PSU next.

Just don't feel like it's my ram, or my psu, seems to be a issue with my drivers corrupting for some reason, if I insert my windows disc with devices in and run a startup repair it'll boot fine afterwards. Not overclocked anymore, until I solve this.
Running 12gbs of G skill PI
Two GTX 480's in SLI
1200W Thermaltake PSU (Can't think of the model at the moment)
I'm thinking maybe the wireless usb adapter somehow screwed things up, just not sure how to fix it if that's so

 

[Alec Mowat]

Try from CMD
"SFC /Scannow"
That should repair any Windows errors

If it started recently, try Windows restore.

The Windows Debug tool is giving those messages though, it's not something I made up.
The DMP file was also 300 MB, which is huge.

 

[HardCelery]

Try from CMD
"SFC /Scannow"
That should repair any Windows errors

If it started recently, try Windows restore.

The Windows Debug tool is giving those messages though, it's not something I made up.
The DMP file was also 300 MB, which is huge.

I believe you, just seems if I had problems with ram I'd be crashing all the time, not because I use USB wireless adapter or some other attachment.
Why would a .dmp file be so huge to begin with? Would there be old errors? If so maybe I should clear my .dmp and make the issue happen again?(I don't really know anything about them.)
Thanks for all the help by the way.
Just booted fine with only my keyboard, mouse, and wireless headset.

 

[HardCelery]

And the wireless headset just caused a BSOD and had to be removed to boot, will do memtest tonight

 

[Alec Mowat]

Try from CMD
"SFC /Scannow"
That should repair any Windows errors

If it started recently, try Windows restore.

The Windows Debug tool is giving those messages though, it's not something I made up.
The DMP file was also 300 MB, which is huge.

I believe you, just seems if I had problems with ram I'd be crashing all the time, not because I use USB wireless adapter or some other attachment.
Why would a .dmp file be so huge to begin with? Would there be old errors? If so maybe I should clear my .dmp and make the issue happen again?(I don't really know anything about them.)
Thanks for all the help by the way.
Just booted fine with only my keyboard, mouse, and wireless headset.

It's either configured to do a full dump, or (which I believe) that RAM was bad and caused a loop while creating it. Check your mindump directory and see what else is there.

Are you using USB hubs, or the USB ports on the back of the motherboard?

 

[HardCelery]

I'm using the ports on my motherboard.
Memtest gave me no errors after 12 hours.

 

[Alec Mowat]

I'm using the ports on my motherboard.
Memtest gave me no errors after 12 hours.

http://www.evga.com/support/download/
Check the site for BIOS or driver/firmware updates for your motherboard. Make sure your Windows is up to date as well