Getting a BSOD while idling. New system

[fondupot]

Hi everyone,

I just built a new system and I have been getting some BSOD's. They go so quick that I am not able to get the exact error number, but I have learned to disable automatic restarts, so if it happens again, I can record it.

But that last one I got gave me these details upon restarting:

Problem signature
Problem Event Name BlueScreen
OS Version 6.1.7601.2.1.0.256.48
Locale ID 1033

Additional information about the problem
BCCode a
BCP1 FFFFFA8C00E43ACA
BCP2 0000000000000002
BCP3 0000000000000000
BCP4 FFFFF80001CEC317
OS Version 6_1_7601
Service Pack 1_0
Product 256_1

I just built this new system. Its a Z77X-UD5H Gigabyte motherboard, Intel i5 3570k ivy bridge processor. I am using a 60gb Corsair Force 3 SSD for my boot drive and a 1TB HDD Western Digital Caviar Black as my Storage drive. I was getting the BSOD's before I even installed the Caviar Black, fyi. Also I am running Windows 7 64 bit Professional with SP1.

Ive run, Memtest and windows memory checker. My RAM is good, it is Corsair Vengeance 4gb x2 (total 8gb).

Ive even run Prime 95 and Intel burn test for several hours each and have been stable, no errors.

I am overclocked, but only slightly to 4.0ghz.

Let me know what else you guys might need. I appreciate the help.

Take care,

Fondupot

 

[zigzag3143]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
Please attach the DMP files to your next post not to post one.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

[/QUOTE]

 

[fondupot]

Ok Ive attached the contents of the windows/minidumps folder. See the attached zip. There are a few .dmp files in there.

I have also reverted back to optimized defualts for my motherboard. Stock voltages, freqs etc.

I just got another blue screen when attempting to transfer files over homegroup from my old PC. The Blue screen error was:

IRQL_NOT_LESS_OR_EQUAL

STOP: 0x00000000A

Any ideas?

Thanks for the help.

 

[fondupot]

And here is the Windows_NT6 and System Health information.

 

[fondupot]

Anyone?

 

[zigzag3143]

And here is the Windows_NT6 and System Health information.

Memory corruption probably caused by your Norton. I would remove and replace it with MSE at least to test,

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

 

[fondupot]

And here is the Windows_NT6 and System Health information.

Memory corruption probably caused by your Norton. I would remove and replace it with MSE at least to test,

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

Ive actually done this today. I decided I didnt want Norton anymore. So I downloaded MSE. lol.....I havent had a BSOD today yet after uninstalling. I will monitor the system and see if it happens again.

Thanks for the help ZigZag.

 

[fondupot]

Been getting more BSODS.....

Here are the minidumps. Got 4 today alone. Yesterday was fine. I no longer have Norton installed.

Please advise.

 

[zigzag3143]

Been getting more BSODS.....

Here are the minidumps. Got 4 today alone. Yesterday was fine. I no longer have Norton installed.

Please advise.

Still memory corruption lets try these.


These crashes were caused by memory corruptionprobably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise.
Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[fondupot]

Ok, thanks. I have run Memtest before and it showed no errors. I will do the driver verifier. Unfortunatley, I am going out of town on business today thru Friday. Then have a wedding to attend on Saturday. So I might not be able to troubleshoot until Sunday. I will post back with my results.

 

[fondupot]

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

 

[writhziden]

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.

 

[fondupot]

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.

 

[fondupot]

Installed the latest audio driver....

still got a random bsod. minidump attached.

 

[writhziden]

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.

 

[fondupot]

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

 

[fondupot]

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

 

[writhziden]

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 http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html 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. :warn: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.

 

[fondupot]

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

 

[writhziden]

You wouldn't be the first to have that problem, actually. http://www.sevenforums.com/hardware-devices/225435-usb-3-0-wont-start-after-pc-sleeps.html