Solved BSOD While watching video on Amazon.com error 0x0000003b

[kmeck22]

Okay, so I disabled the Realtek audio driver in device manager. Should I run driver verifier with that now disabled?

 

[Arc]

Not right now. If there is any need later, we have to take that way again.

 

[kmeck22]

Okay. I will run Skyrim again tonight and see what happens.

 

[kmeck22]

One more question before I test again... Were all three of those BSODs caused by that realtek driver when using driver verifier??

 

[Arc]

Only one of the three crash dumps were executable (completely recorded). So it is not possible to answer this question correctly, unfortunately.

 

[kmeck22]

Would it hurt if I ran driver verifier again and produced more BSODs to give you more results?

 

[Arc]

Would it hurt if I ran driver verifier again and produced more BSODs to give you more results?

Driver verifier puts a stress on the overall system. If it is not a must, better to not use it.

 

[kmeck22]

So I haven't received a BSOD yet. I don't know if this is solved or not. Would it be okay to run driver verifier while playing Skyrim to see if this problem has been finally solved?

 

[Arc]

If it is not broken, dont fix it

If there is any further issue, troubleshooting will be done again.

 

[kmeck22]

So I was playing skyrim again and I needed to charge up my xbox pc controller. I plugged it into one of my usb 3.0 slots and everything froze and then I got another bluescreen. With all these issues, something really tells me this has to be a motherboard issue... First the storage drive disappears, then the realtek driver needs to be disabled, now the usb 3.0 slot throws out another BSOD. It just doesn't seem to be one thing making this happen. Attached is the SF diagnostic results and the two most recent bluescreens. Apparently one happened on 2/25/2014. I can't remember if that was one that I sent you already or not. Let me know if you need anything else.

 

[Arc]

Have another chance before blaming the motherboard? As you said, there is all the possibilities. But let us have one more try?

The crash dump indicates to Intel USB3.

BugCheck 7A, {fffff6fc400164c0, ffffffffc000000e, 40f68e860, fffff88002c98000}

*** WARNING: Unable to verify timestamp for iusb3hub.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3hub.sys
[COLOR=Red]Probably caused by : iusb3hub.sys[/COLOR] ( iusb3hub+46ffc )

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

If there is any available update in MSI's site, you may install it.

And, form your well written reply, one more thing came out which does not reflect in the crash dump at all. XBox 360 wireless receiver. Your installed version is:

fffff880`013ea000 fffff880`013fc100   xusb21     (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
[COLOR=Red]    Image name: xusb21.sys[/COLOR]
[COLOR=Red]    Timestamp:        Fri Aug 14 03:40:17 2009 (4A848F49)[/COLOR]
    CheckSum:         0001398B
    ImageSize:        00012100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

See what is said by Driver Reference Table about this version:

Driver Description: XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012)

Minimize this possibility by updating the driver from Software Downloads | Microsoft Hardware.

If still all is the same, and the versatile BSODs continue to occur in the similar fashion, replace the motherboard.

 

[kmeck22]

Thanks for getting back to me so quickly! Out of curiosity, What did the BSOD show from 2/25/2014?

 

[kmeck22]

And as for updating both of the drivers suggested... They are both updated to the most current driver version. I cannot update them anymore :/.

 

[Arc]

Thanks for getting back to me so quickly! Out of curiosity, What did the BSOD show from 2/25/2014?

Now you are seriously annoying me. I hope I quoted the results.

And as for updating both of the drivers suggested... They are both updated to the most current driver version. I cannot update them anymore :/.

I stop here.

 

[kmeck22]

First off, the xbox driver IS up to date. The driver I have is from 2009 and version 2.1.0.1349. The driver they are offering as the most up to date driver on Microsoft's website, is from 2009 and IS version 2.1.0.1349. So I don't see how I misunderstood you. Second off, I was just asking questions. The BSOD from 2/25/14 was something totally different than the BSOD from last night. I was just curious as to what you could determine from that one as well. People come to you for help. I was not badgering you or getting impatient with you. I tried to show my appreciation around every turn. You do not need to be like that. I appreciate your help thus far, and I will take it from here. I did not mean to be an annoyance. I will not turn to this site anymore.