BSODs when idle, when switching audio output, and random others

[Blundertusk]

Well, I've finally hit the brick wall with this latest barrage of crashes and BSODs. When I wake up or return from anything over a half hour or so, my computer is almost always attempting to reboot from a crash, quite unsuccessfully. When I switch from speakers to headphones, there's a very strong chance I'll BSOD within minutes. And, just for fun, I'll get a random crash from time to time when browsing the ol' internet or something similarly mundane. The BSOD from idle doesn't show a code, but the audio BSOD seemed to direct me to a driver conflict. I'm no expert, by any means, so I thought I'd see what you guys thought.

I friend built this rig for me, and it was working fine up until I had to replace the last hard-drive. Now, it has a mind of it's own. I tried updating all my drivers after reading another thread about a similar issue. I also tried deleting and re-downloading a few drivers that seemed to be giving people with similar issues some grief. So far, nothing is sticking.

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

 

[Blundertusk]

Thanks for the quick help.

I just had a couple more crashes, but I'm not seeing anything new in the new zip file, or the minidump folder. I included it for the sake of being thorough, and the fact that I really don't know why nothing is being saved.

 

[Arc]

I just had a couple more crashes, but I'm not seeing anything new in the new zip file, or the minidump folder.

You are right, dumps were not saved.

Can you take a camera snap of the next BSOD screen and let us see it? Asking for it, because we need a starting point to begin the troubleshooting, and the onscreen codes will give us at least some idea.

 

[Blundertusk]

Holy beans, I finally caught one in the minidump. I'm also including a couple screenshots from earlier crashes.

 

[Arc]

The recorded dump is a stop 0xA.

The snaps are showing 0x1E and 0x7E. So all they are different bugchecks, and blaming different things. It is a strong indication that something odd is going on there.

If you dont connect the FreeAgent GoFlex Drive (Drive F), does it BSOD in the same way? Remove the drive and let the computer run without it .... see how it goes.

Also, for the versatility of the bugchecks, test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. A camera snap of the memtest86+ screen before closing the program would be nice.
________________________________________________________

BugCheck A, {200, 2, 1, fffff80002e93a15}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_DecIoRequestCount+31 )

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

 

[Blundertusk]

I'm laughably broke, and will go buy a USB drive when I have the resources. Hopefully next Friday. Meanwhile, maybe you can glean something from the most recent barrage of mindumps. The crashing in games has increased, and the crashing outside games is far and very few between.

 

[Arc]

Reply to post #6 first .... then we will go for any further troubleshooting depending on the result.