BSOD while playing Dota 2

[avatarv2]

sfc is clean now, and I just installed the video drivers. I'll keep my fingers crossed so that this whole thing is fixed already.
ps: thanks for your help

 

[x BlueRobot]

That's good, the corrupted files have been repaired and the drivers have been updated, leave this thread open for about a week, and then report back any changes or if the problem has been resolved.

 

[avatarv2]

Well, it came back after all, got a bsod while watching a video.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3D[/COLOR], {fffff80000b9bfa0, 0, 0, fffff800030a45f5}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6a6f )

The dump files are not revealing much information, it's best to follow these steps:

Install Windows Updates (Important and Optional):

Start rb: > Type: Windows Update > Check for Updates > Install Updates

Windows Updates provide many stability and security improvements for your operating system.

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:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

 

[avatarv2]

There was one update to install, I'm also running driver verifier as of now. Hope we can grasp what's going on here.
ps: Thanks for your help all along

 

[avatarv2]

This was fast, I got the system to crash playing skyrim, here's the zip as usual

 

[x BlueRobot]

[COLOR="red"]BugCheck C4[/COLOR], {81, fffffa800fd5bdd0, 8a, 0}

*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
Probably caused by : [COLOR="Red"]mcdbus.sys[/COLOR] ( mcdbus+36823 )

4: kd> [COLOR="SeaGreen"]lmvm mcdbus[/COLOR]
start             end                 module name
fffff880`03fa9000 fffff880`03fe5880   mcdbus   T (no symbols)           
    Loaded symbol image file: mcdbus.sys
    Image path: \SystemRoot\system32\DRIVERS\mcdbus.sys
    Image name: mcdbus.sys
    Timestamp:        [COLOR="red"]Tue Feb 24 10:34:07 2009[/COLOR] (49A3CD1F)
    CheckSum:         00041E84
    ImageSize:        0003C880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The dump file indicates that MagicISO SCSI Host Controller driver is causing some problems (Driver Reference Table)

Remove:

Start Menu\Programs\MagicISO

 

[avatarv2]

Just removed it. Should I run Driver Verifier again to see if anything else is amiss?

 

[x BlueRobot]

Disable Driver Verifier for now, and just use your system as you normally would. If any more BSODs occur which do not indicate a exact cause, then we can start running it again.

 

[avatarv2]

Got another bsod just now (again, while playing)

 

[x BlueRobot]

[COLOR="Red"]BugCheck 1E[/COLOR], {0, 0, 0, 0}

Probably caused by : [COLOR="red"]hardware[/COLOR] ( nt!KiKernelCalloutExceptionHandler+e )

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

1: kd> [COLOR="SeaGreen"]!error c000001d[/COLOR]
Error code: (NTSTATUS) [COLOR="Blue"]0xc000001d[/COLOR] (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:

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: Additional Help - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

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:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

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

 

[avatarv2]

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]

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

:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[x BlueRobot]

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]

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]

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

 

[avatarv2]

Well, here's the screen for both my HDD and SSD:
View attachment 258344
I'll start running the tests now

 

[x BlueRobot]

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

 

[avatarv2]

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]

[COLOR="Red"]BugCheck 1E[/COLOR], {[COLOR="SeaGreen"]ffffffffc000001d[/COLOR], fffff80003109064, 0, fffff8800a4c9a00}

Probably caused by : [COLOR="Red"]memory_corruption[/COLOR] ( nt!MiLocateAddress+34 )

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

0: kd> [COLOR="SeaGreen"]!error ffffffffc000001d[/COLOR]
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:

• http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

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:

• http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html

:warn: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:

American Megatrends Inc. P2.20, [COLOR="Red"]12/10/2012[/COLOR]

• How to Update Your BIOS | PCWorld