Blue screen and overclock accusations

Just found the "how to post bsod thread"
I will fix that asap

Hello.
Recently my pc started taking trips to the good old blue screen but only when playing games for a good 20min or so. I can browse and do everything else just fine

At the blue screen it says something about "dumping physical memory" and then shuts down. At restart It says "overclock has failed... something something(can remember the specific text)" though I did not overclock . Afterwards my pc will start up just fine.

Thanks in advande
Best regards
Sandro :)

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1030

Additional information about the problem:
BCCode: 135
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88008CA3BE0
BCP3: FFFFF8800534A224
BCP4: FFFFF8A0026EE0F0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050112-26656-01.dmp
C:\Users\Sandro\AppData\Local\Temp\WER-66500-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

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.

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.

I'm not overclocking. I said that in the post (:
I can use of the pc just fine. The problem only occurs when I'm gaming as far as I know
Oh cruel world :/

The dmp files should be attached. (If I did it right)

sandrogiusio said:

I'm not overclocking. I said that in the post (:
I can use of the pc just fine. The problem only occurs when I'm gaming as far as I know
Oh cruel world :/

The dmp files should be attached. (If I did it right)

It did say "if"

Virtually all of these were Related to sbapifs.sys Sunbelt CounterSpy AP Driver.. I would remove it at least to test.

There was also some involvement Related to SbFw.sys Solo-1 Sunbelt Personal Firewall driver.. I would remove them both

Now these files are related to the shutdown :/


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1030

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 0000000000144ADC
BCP3: 0000000000000002
BCP4: 00000000000531DB
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050412-48593-01.dmp
C:\Users\Sandro\AppData\Local\Temp\WER-111750-0.sysdata.xml

And now this :/
I should try figuring out how to read the dmp files myself.
I have never encountered any problems what so ever before these :/

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1030

Additional information about the problem:
BCCode: a
BCP1: FFFFFA80C071D1F0
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002AA9A4F
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050412-42656-01.dmp
C:\Users\Sandro\AppData\Local\Temp\WER-76437-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

Did you replace the Sunbelt software with antivirus software? Recommend Microsoft Security Essentials - Free Antivirus for Windows if you have not yet added antivirus software. Also, if you have been unprotected for some time, please update the software and run a full scan. You may also want to run a full scan with Malwarebytes : Free anti-malware, anti-virus and spyware removal download. Download Malwarebytes, install it, update it, do not start the trial version, and then run a full scan of your system.


Both crashes point to memory problems or driver issues.

• 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.
  
  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
    Attachment 210237
  • 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 System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  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.