Getting a BSOD while idling. New system

Memtest was solid, same as the time before.

I did the driver verifier and it crashed upon restart. Didn't even get into windows. took down the code and restarted in safe mode just in case. Ive attached the minidump and turned off the driver verifier.

Please advise. Thanks

The Verifier enabled crash was caused by your Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver), MBfilt64.sys; recommend updating to the latest driver. Realtek

You may need to disable Verifier before updating the driver.

writhziden said:

The Verifier enabled crash was caused by your Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver), MBfilt64.sys; recommend updating to the latest driver. Realtek

You may need to disable Verifier before updating the driver.

Thanks ok. I will check that out.

Ive already disabled the Verifier. Ill report back.

Still pointing to memory corruption which may still mean a driver. I see AppleCharger installed; it is a driver for increasing the charging speed for an iPod. It can cause crashes due to changing how the USB ports utilize power, so I would recommend removing it to test.

writhziden said:

Still pointing to memory corruption which may still mean a driver. I see AppleCharger installed; it is a driver for increasing the charging speed for an iPod. It can cause crashes due to changing how the USB ports utilize power, so I would recommend removing it to test.

10-4 I will look into it.

I downloaded and played Diablo 3 for a good 4-5 hours yesterday and didn't have any bsods. They are so random!

I will report back after removing the charger

Whats the cause of this one? Got while playing Diablo 3.

I suspect hardware. Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

I think its my USB 3.0 header. I have since unplugged it and it was unplugged the whole weekend with no BSODs.

I plugged it back in today, and it BSOD's pretty fast, within about 10 mins of booting up.

Ive run priem95 for hours on end. Temps are fine. Run intel burn test, temps also fine. Ive run memtest and the windows memory test. Nothing is overclocked.

Since the bsod i have unplugged the 3.0 header connection to my ports on the front and i have not had any problems.

I'll test tomorrow by plugging back in and seeing what happens. whackyyyyyy

You wouldn't be the first to have that problem, actually. USB 3.0 won't start after PC sleeps