Windows 7: BSOD while playing Dota 2

**x BlueRobot** · 01 Mar 2013

Code:

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )

Code:

Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Code:

1: kd> !error c000001d
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

The kernel detected a illegal or unknown processor instruction, this may be reason why it is pointing to a hardware issue, I would follow these steps:

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

Driver Verifier - Enable and Disable

Additional Help - Using Driver Verifier to identify issues with Drivers

We seem to be picking up quite a few problematic drivers from this, so there may be other programs or drivers which are causing the bugchecks.

We can stress test the CPU for any problems also:

Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

avatarv2 · 03 Mar 2013

I stress tested my CPU with no errors for 2 hours, and verifier hasn't crashed since I started it two days ago (I have tried running various games and watching videos, as long as normal use).
I find this pretty weird sice I was pretty sure the problem was on the driver side.
Should I keep running verifier just to be sure?

VistaKing · 03 Mar 2013

How about you run a memtest . I didn't see any results for that

RAM - Test with Memtest86+

**x BlueRobot** · 04 Mar 2013

If Driver Verifier hasn't detected any errors since of it's initial activation two days ago, then you may disable Driver Verifier and begin testing the RAM for any issues.

avatarv2 · 07 Mar 2013

Memtest didn't find any errors (did 7 passes).
Also, I havent had any BSOD's in the last 2 days.
I haven't changed anything meaningful, though, which makes me wonder if the issue just solved itself

**x BlueRobot** · 07 Mar 2013

Run some hard-drive diagnostics and follow these steps:

Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

Post a screenshot of Crystal Disk Info summary:

Screenshots and Files - Upload and Post in Seven Forums

Quote: Originally Posted by writhziden

If you have an SSD, make sure the following are up to date:

SSD firmware
BIOS Version
Chipset Drivers
Hard disk controller drivers/SATA drivers
If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

Disk Check

Use this command with Disk Check:

Code:

chkdsk C: /f /r

avatarv2 · 07 Mar 2013

Well, here's the screen for both my HDD and SSD:

I'll start running the tests now

**x BlueRobot** · 08 Mar 2013

The S.M.A.R.T results seem to be fine, which is a good sign.

avatarv2 · 16 Mar 2013

I couldnt find a test for my SSD from its manufacturer, but I did test my seagate HDD with no errors found. Also Diskcheck returned no errors either.
This past days the bsod's seemed to have dissappeared, but I got one yesterday and another one today.
Here's the info, as usual:

**x BlueRobot** · 16 Mar 2013

Code:

BugCheck 1E, {ffffffffc000001d, fffff80003109064, 0, fffff8800a4c9a00}

Probably caused by : memory_corruption ( nt!MiLocateAddress+34 )

Code:

Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Code:

0: kd> !error ffffffffc000001d
Error code: (NTSTATUS) 0xc000001d (3221225501) - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

-->Test CPU:

Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

The results should be found under the location, where you installed Prime95, the file will be named results.txt.

-->Graphics Card:

NVIDIA/AMD Video Card - Test with OCCT

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.

Use the following program to monitor your hardware temperatures during the stress test:

CPUID HWMonitor

-->Update BIOS:

Code:

American Megatrends Inc. P2.20, 12/10/2012

How to Update Your BIOS | PCWorld

Windows 7: BSOD while playing Dota 2

BSOD while playing Dota 2 problems?