BSOD randomly BCCode 1e

[Omnibox]

Hi, my computer is BSODing every once in a while and I get the BCCode 1e. But I don't know what to do...

Specs:

Os - Windows 7 Home Premium 64bit OEM (I installed it, but it said OEM on the box)
CPU - Intel i5 2500k (not overclocked)
Hard drive for OS - Corsair Force GT 60 GB
Hard Drive - 2TB Seagate Barracuda Green 5900rpm
Graphic card - Asus HD 6950 DirectCUII
RAM - Corsair 4GB (2x2048MB) CL9 1333Mhz XMS3
Motherboard - MSI P67a-GD55

 

[writhziden]

It is difficult to find patterns with only one .dmp file, and yours was inconclusive. If you are using CCleaner to clean your disks, it is probably deleting your .dmps. Please refrain from using CCleaner for the duration of our troubleshooting.

Update the following driver:
DB3G.sys, your Diamondback USB Optical Mouse Driver. It is very old and may be causing problems on your system. If you cannot find an up to date driver for it, consider replacing it with a modern mouse that is compatible with Windows 7.

 

[Omnibox]

Thanks for the reply! Sorry I didn't know it removed them... The driver I have for my diamondback right now is the latest from Razer This. If this is the faulty driver I will be very happy as I can just buy a new mouse and fix it...

 

[writhziden]

We may have to wait for more crashes to be sure it is the mouse that is causing the problem. Upload any new crash reports if you have more crashes.

 

[Omnibox]

So, I bluescreened again... I'll upload the dumpfile. I got the same Bccode: 1e. And I thought the bluescreens had stopped.

 

[writhziden]

What security software are you running on your system? I see ZoneAlarm installed, and possibly Kaspersky, but Kaspersky does not show up in your running programs, your startup programs, or your program groups.

 

[Omnibox]

I have ZoneAlarm Anti Virus and Firewall, but I have never installed Kaspersky.

I had AVG at one point but since ZoneAlarm has Antivirus as well I removed it.

 

[writhziden]

Ah, the ZoneAlarm antivirus uses the same engine as Kaspersky. That explains that.

Make sure your Arctosa.sys driver is up to date, which is your Razer Arctosa Keyboard Driver. Yours is from 2009 and could possibly cause problems.


Since your crash reports continue to be inconclusive, let's press the issue a bit:

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