Solved BSOD mainly playing TF2 and Dota 2, multiple error codes

[faebu4]

Good day,

I hope the text-wall below doesn't scare you too much, but I wrote down all the things I thought could be helpful.

Let me explain the problem further: I get BSODs seemingly random, with all kinds of error codes and .sys files (as far as I could see on the bluescreens). It startet roughly about when I picked up Team Fortress 2 again. Maybe it's something else, but when it began I was so sure that it was TF2 causing it, that I didn't investigate other causes back then. Surprisingly (for me), it went on even when I wasn't playing, causing BSOD whenever it wants (Youtube in Firefox, while booting...).
In addition to the BSOD I can give you the following scenario that happens whenever it bluescreens: The PC automatically tries to reboot after the dump files have been collected (by the way, not all files get collected. I have multiple BSODs without logs, because it got stuck while collection dump files. After 1+ hour I forced it to shut down by holding down the start button). The PC tries to reboot 2 times without success (it doesn't get to the BIOS screen) and with the third attempt it just idles somewhere - I don't get any video signals nor am I able to enter BIOS, because my (USB) keyboard isn't active. I can tell because it's a wireless one and the receiver has a little LED when the keyboard is ready to use. I have tried none the less by constatnly pressing F2 to enter BIOS (which gives a 'beep' when successful), but nothing happened. The screen goes to standby because of no signal after a couple of minutes and all that's happening is a short HDD-noise every second or so, as if they were in some kind of loop.
I now have enabled 'Boot Beep', which gave me 4 beeps per failed bootattempt today when I got another bluescreen. I looked it up and it means 'System timer failure', whatever that is.
What I have done so far:

• Video Card driver: uninstalled, reinstalled, tried an old one, updated
• RAM: memtestx86+: one RAM stick after the other, both slots, 8 passes (~4h) each
• Prime95: After more than 1 hour, the temperature was still at a comfortable 48°C
• EVGA OC Scanner: tested for possible overheating, GPU temperature was stable at 68°C; 90-100% load
• PSU: Ran EVGA and Prime95, as well as all case fans on high, checked voltages with SpeedFan, looked ok to me.

Now I'm a bit sad that I didn't get my self-built PC to work. Whatever tests/things/screenshots you want me to do, count me in.

PS: I found a very reliable way to provoke a BSOD: Playing Dota 2 for a couple of minutes. Just in case you want even more dump files .

 

[koolkat77]

Welcome to the Forum faebu4,

Please remove Norton for testing purpose.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability
compared to other antivirus or internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes: Removes malware including viruses, spyware, worms and trojans, plus it protects your computer
• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

RTCore64.sys Mon Mar 11 11:32:06 2013 (513D6C56)
RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
Driver Reference Table - RTCore64.sys

Uninstall Riva Tuner, it is known to cause BSOD's.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue Jul 22 20:28:23.202 2014 (UTC + 6:00)
System Uptime: 0 days 0:01:13.046
BugCheck 50, {fffff90049a03cd4, 1, fffff960000d8d55, 5}
Probably caused by : win32k.sys ( win32k!DC::bSetDefaultRegion+5 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  flux.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue Jul 22 20:26:15.377 2014 (UTC + 6:00)
System Uptime: 0 days 0:09:51.093
BugCheck 1000007E, {ffffffffc0000005, fffff8800f40d7db, fffff880025f0ab8, fffff880025f0310}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+18b )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Jul 21 23:31:53.039 2014 (UTC + 6:00)
System Uptime: 0 days 0:36:23.883
BugCheck 1A, {41201, fffff68000163bb0, 848000000b659867, fffffa800a706bb0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon Jul 21 21:55:18.221 2014 (UTC + 6:00)
System Uptime: 0 days 3:16:44.065
BugCheck 3B, {c0000005, fffff9600008f7f5, fffff88009d7bf40, 0}
Probably caused by : win32k.sys ( win32k!InternalBuildHwndList+39 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun Jul 20 20:45:20.557 2014 (UTC + 6:00)
System Uptime: 0 days 0:23:29.400
BugCheck 1000007E, {ffffffffc0000005, fffff80002ccb25b, fffff880039327c8, fffff88003932020}
Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+a0 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Sun Jul 20 19:40:06.351 2014 (UTC + 6:00)
System Uptime: 0 days 1:45:59.195
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

 

[faebu4]

Hello again,

first of all, thanks for the reply. After I ran Malewarebytes (no result), CHKDSK on my drives (no result) and Scannow on my boot drive (no result), I had an idea what could cause the problem.
Solution: I moved the RAM sticks from the first priority slots (A2 and B2) to the next best option, A1 and B1 RAM slots. I'm running it for 3 days without any problems now, so it seems like the motherboard or the processor had something agains me using the first priority RAM slots.
Anyway, thanks for the help, it's been much appreciated.

 

[koolkat77]

Glad you got it sorted