Random BSOD on new build

[keslrc]

Hi I just built a new computer for a friend but the BSOD keeps crashing his computer (mostly during games).

Attached are the zipped system reports and memory dumps hopefully it helps. I have already gone to both amd and biostar to get the latest drivers but it still hasn't helped.

Specs
CPU INTEL|CORE I5 3550
MB BIOSTAR|TZ77B Z77 LGA1155
MEM 4Gx2|CORSAIR CMZ8GX3M2A1600C9
HD 500G|WD SATAIII WD5000AAKX
GF XFX|FX-785A-CDFC HD7850 2G
PSU ROSEWILL | HIVE-750 750W
Windows 7 64 bit OEM

Thanks in advance for your time and let me know if there is anything else I can help you with.

 

[writhziden]

Your crash reports were incomplete. The system logs do indicate a 0x124 hardware crash BugCheck code.


If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   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 your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• 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).
  
  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.

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.

 

[keslrc]

I have already checked all my temps and they are all fine, and I haven't overclocked anything yet. I ran the memory tests last night and they came up with no errors. Now I am trying prime95 stress test and Ill let you know how that goes. I reformated the computer so all the new dumps I received yesterday are gone but Ill continue to use it today and see if I get any new BSOD and report any dumps that take place. Thanks for you help so far.

 

[writhziden]

You're welcome.

Please let us know what temperatures you see under idle and what you see during stress. CPU, GPU, and motherboard/system temperatures are the most important. Sorry to question you saying the temps are fine, but we have had a number of users who thought their temperatures were fine when they were using misinformation they had read online.

 

[keslrc]

Here are my temps the cpu sits at about 40 c idle and 55 c under load while the gpu ranges from 40 - 75 c

the Memtest86+ came back with no errors after 14 passes and so did the windows memory tests and the Prime95.exe said all the tests were passed as well. After I reformatted I haven't had any bsod but all I have been doing is running these tests and downloading games but I was able to leave it on over night while downloading and it never got the bsod. Ill see if it starts to happen when I start playing games but hopefully its fixed now.

 

[writhziden]

Those temperatures are definitely within the limits, as you said. Everything definitely sounds clean, and you did the troubleshooting steps well. Nice work.

Let us know in a few days how the system is responding after you had a chance to do more of your normal routine.

 

[keslrc]

Well today while installing Star Wars the old republic I got the BSOD twice I've included the memory dumps and when I loaded when I loaded windows back up I got this error not sure if it means anything.

the instruction at 0x76ee7659 referenced memory at 0x00728298. the memory could not be read

 

[writhziden]

BIOS64	fffff880`04927000	fffff880`0492f000	Sat Jun 07 18:12:00 2003 (3ee27f50)	00006027		BIOS64.sys

The above driver is from 2003 and badly in need of updating. This is probably aBIOSTAR I/O driver file: BIOSTAR :: Download


Crashes are pointing to memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• 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.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

You also had some graphics card related crashes. That could indicate the graphics card and/or the DirectX installation. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

• If you are overclocking any hardware, please stop.
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.

Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

1. Download the drivers you want for your display card(s)
2. Click Start Menu
3. Click Control Panel
4. Click Uninstall a program
5. For NVIDIA:
   • Uninstall the NVIDIA Graphics Driver (this should uninstall all NVIDIA software and drivers)
   • Restart your computer
   • Make sure NVIDIA 3D Vision Driver, NVIDIA 3D Vision Video Player, NVIDIA HD Audio Driver, and NVIDIA PhysX System Software are not still listed under Uninstall a program through Control Panel
   • If any remain of the above, uninstall one at a time
   • If asked to restart after uninstalling any of the above, do so, and continue uninstalling any remaining NVIDIA items until all are removed
6. For AMD:
   • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
   • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers (this applies to onboard graphics, as well):
     1. Click Start Menu
     2. Right Click My Computer/Computer
     3. Click Manage
     4. Click Device Manager from the list on the left
     5. Expand Display adapters
     6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
        
        Alternatively:
        1. Login as an adminstrative user
        2. Click Start Menu
        3. Click Control Panel
        4. Click Hardware and Sound
        5. Click Device Manager (the last link under Devices and Printers)
        6. Expand Display adapters
        7. Do the following for each adapter (in case you have multiple display cards)
           • Right click the adapter
           • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
           • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
7. Restart your computer after uninstalling drivers for all display cards
8. Install the driver you selected for the display cards once Windows starts

Remember to try multiple versions of the graphics drivers, download them fresh, and install the freshly downloaded drivers.

 

[keslrc]

I did the driver verifier and restarted windows and got a BSOD almost instantly so here is the dump files.

 

[keslrc]

I tried uninstalling and re installing my graphics drivers and encountered several more more bsod and after downloading and trying to install the newest ones I encountered and error and AMD gave me an error report which I have attached. These BSOD are encountering much more often after I did the driver verifier.

 

[writhziden]

Before re-installing any drivers, it is a good idea to disable Verifier. It will generate false positives since it is trying to verify the drivers being re-installed. First, disable Verifier, and then re-install your graphics drivers again. Then re-enable Verifier and wait for more crashes.

 

[keslrc]

Ok sorry for the delay but I was away from my the computer for most of last week so I haven't had time to try fix it.

Here are a few updates though. I was beginning to think this was a hardware issue so I borrowed my brother's computer which I had just built for him. It has the same motherboard only a different cpu, he only has an i3 instead of i5, I swapped the motherboards and cpus (I didn't feel like unmounting and remounting the cpu heatsinks) and now my brothers computer would get the BOSD even before loading windows so I of assumed it was the motherboard since I have already tried swapping out the ram as well. I ordered the new motherboard and installed it did a fresh install of windows installed all drivers but then I got the BOSD again. I hadn't setup the computer for mini numbers yet so I don't think I have those crash reports but I quickly set it up after that and got another BOSD while trying to installing some windows updates. I've swapped out the ram, the motherboard, used the graphics card in another computer and it worked fine. I tried using a different hard-drive but it I can't seem to install windows on it because every time it tries to expand finals I get an error message that says "Windows installation encountered an error verify that the installation sources are accessible" once I even got the BOSD before I got that error. and I just installed windows on this hard drive on another computer. I am completely clueless, if its not the motherboard, not the ram, hard drive or graphics card that means it could only be the psu or cpu. Can psu even cause a problem like this and I have never really heard of a bad cpu isn't that like a 1/100,000 chance. I was beginning to think they this was a hardware issue because I got the BOSD once while installing windows and once before drivers where even installed.

I have attached a few more dump finals.

 

[writhziden]

Security Software: ??? Make sure to install security software. I recommend either of these:

• Microsoft Security Essentials - Free Antivirus for Windows coupled with Malwarebytes. Do not start the free trial of Malwarebytes. Just use the standalone version, update it, and scan your computer once a week with Malwarebytes and with Microsoft Security Essentials.
  
  
• http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627

After installing your security software, update it, and then run full scans today with each program. Report back the results of the scans.


The following driver needs to be updated or the software removed:

BIOS64.sys Sat Jun 7 18:12:00 [B][COLOR="Red"]2003[/COLOR][/B] (3EE27F50)

BIOS64.sys; This is probably aBIOSTAR I/O driver file


Let's check your RAM settings and compatibility:

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

And yes, a CPU failure is rare, but not unheard of. I'd say it is more like 1/1000 chance. Your crashes point to memory, so it could be the memory controller at fault. It could also be that driver I keep mentioning that is really old.

 

[keslrc]

I am a little confused about this motherboard driver, not sure which one I need to update because when I to the motherboard's driver page I don't see anything similar to it. Another question I have is why do they such an old driver on one of their newest motherboards? I am uploading my screenshots and getting ready to scan using the two programs you told about. I let you know what the results say.

 

[writhziden]

You should set up your RAM to run with a command rate of 2/2T.

For the BIOSTAR driver, the date shown in another log is 8/8/2011. It may just be that BIOSTAR has a bad timestamp on that particular driver. A cursory Google search shows that driver a lot having the 2003 timestamp and none of the gurus have been able to get a more up to date driver or determine what that driver does, so I'll leave it be for now.

See if the RAM adjustment provides more stability. Almost all crashes point to memory issues.


If the RAM adjustment does not provide more stability, see if removing a RAM module does. Run with one module at a time in one slot at a time. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.

Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.

As you add and remove hardware, 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.


Also, have you disabled Verifier since the last time you posted? If not, you should disable it prior to testing the RAM: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:

verifier /reset​

-> Restart your computer.

 

[keslrc]

I ran the scans and both came up with 0 problems how would I change the command rate to 2/2T? Thanks for you help so far.

 

[writhziden]

There should be a setting in the BIOS. You will have to set your RAM timings/frequency settings to manual instead of auto. The first four timings should remain 9-9-9-24 and the command rate set to 2/2T

 

[keslrc]

I managed to figure it out and switch it to 2/2t and it seemed to work fine for about a day but then I got the bsod again. I am still in the process of trying each piece of ram in each slot now but so far nothing has worked I am still getting the BSOD. Any other ideas. Thanks again

 

[writhziden]

I just noticed you did not upload an image for each slot in the SPD tab for CPU-Z. Please do so to make sure the two modules are compatible.