BSoD on system startup

[vbTom]

I've been getting consistent BSoDs when starting my computer. Usually it's described as memory management, but also "bad pool caller" and "reference by pointer". Sometimes no cause is given.

Win7 is 64 bit, came installed with the computer (prebuilt), about 10 months old.

System specs are in my profile. The only hardware change I've made is a new CPU fan.

Any help is appreciated. This is way over my head. If more information is needed, I'll do my best to get it.

 

[writhziden]

A few possibly minor things: I see Gigabyte Easy Saver - mobo power utility driver loaded. I recommend removing the software. I do not see it installed, though, so if it is not in your Uninstall a program list in Start Menu -> Control Panel -> Uninstall a program, then go to C:\Windows\System32\Drivers and rename gdrv.sys to gdrv.sys.bak

I also see USB charging software for Apple devices installed. Please remove the software the same way as the Easy Saver software. AppleCharger.sys is the driver to look for if you cannot uninstall it through conventional methods.


The latest crash indicates hard disk corruption. It is likely due to the previous crashes.

• Run http://www.sevenforums.com/tutorials/433-disk-check.html with Automatically fix file system errors checked. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.

Your previous crashes are rather inconclusive. See if taking care of the above resolves them.

 

[vbTom]

Both programs were not installed, and only the Apple charging driver was appearing, so I made the change. Had to run disk check twice, I'll attach both reports. I'll post again if I get another BSoD in the morning, since it only really happens after the computer's been shut down for a while.

 

[writhziden]

Alright, best of luck.

Cold boot blue screens are usually hardware related, but we'll address that if it happens again.

 

[vbTom]

Well, it's happened again. Was fine for a day and then this morning it decided to act up.

 

[writhziden]

Crashes point to hardware problems or driver conflicts.

• 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.
  
  
• 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
    View attachment 214917
  • 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.

 

[vbTom]

All right, I'll be having a really busy week and I won't have a lot of time to do these tests in a timely manner. I'll post again when I've done everything and hopefully by then found the problem, but until then, thanks for all the help writhziden.

 

[writhziden]

You're welcome. No rush in doing the steps. Whatever pace suites your lifestyle is fine by us. We'll be here when you're able to post back.