Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playing games at first, then all the time. Multiple errors.


20 May 2013   #1

Windows 7 64 bit
 
 
BSOD playing games at first, then all the time. Multiple errors.

Hello everyone! I'm having problems with my computer with the following specs:

P8Z68-V/GEN3 MOBO
OCZ 120GB Agility 3 SSD
i5 3550 3.3GHz
OCZ ModXStream Pro 700W
Corsair ram 2x4GB
HD 6950 HIS Iceqx 2GB

Initially, it was working beautifully, as in all games were on ultra max settings and no issues at all!

But now it just crashes all the time! It usually crashes in games, some other times just randomly in the middle of watching netflix or just browsing facebook. I don't know what to do. I have tried to isolate the issue, but I just can't. Different ram, with/without graphics card., clean windows install, fans everywhere, etc. nothing does the trick.

I only have a HDMI connection, so even though I can sometimes see a flicker of a blue screen, I can never see what it says before it resets... I am attaching the grab all files. I have been like this since before Christmas, and it is so frustrating. Thank you for taking the time to read this!

Thank you very much!


My System SpecsSystem Spec
.

21 May 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Tip   Tip
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy

Basic checks: Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

1. Hardware - Stress Test With Prime95 - Test your Hardware for Stability and Heat Problems with Prime95
2. CPU - Stress Test Using IntelBurnTest - Test your CPU Stability with IntelBurnTest
3. Video Card - Stress Test with Furmark - Stress Test a Video Card with Furmark
4. Monitor temperature of the system during the tests - Speccy - System Information - Free Download

Summary of the dumps:
Code:
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 20 21:00:08.889 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:31.263
BugCheck 1E, {ffffffffc0000005, fffff80002c4bf94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 20 19:26:42.349 2013 (UTC + 6:00)
System Uptime: 0 days 1:49:15.723
BugCheck 1E, {ffffffffc0000005, fffff80002c95f94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 20 14:53:59.365 2013 (UTC + 6:00)
System Uptime: 0 days 1:27:22.349
BugCheck 3B, {c0000005, fffff960000bfb56, fffff88002b35cf0, 0}
Probably caused by : hardware ( win32k!EngMulDiv+295a )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Photoshop.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun May 19 17:55:00.042 2013 (UTC + 6:00)
System Uptime: 0 days 5:19:10.255
BugCheck 1E, {ffffffffc0000005, fffff80002ca1f94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun May 19 04:08:00.091 2013 (UTC + 6:00)
System Uptime: 0 days 0:07:07.464
BugCheck 1E, {ffffffffc0000005, fffff80002c9bf94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat May 18 21:21:47.360 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:48.344
BugCheck 1E, {ffffffffc0000005, fffff80002ca1f94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat May 18 18:25:41.809 2013 (UTC + 6:00)
System Uptime: 0 days 1:31:17.793
BugCheck 1E, {ffffffffc0000005, fffff80002c61f94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat May 18 14:34:41.573 2013 (UTC + 6:00)
System Uptime: 0 days 0:26:48.557
BugCheck 1E, {ffffffffc0000005, fffff80002c9ff94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat May 18 13:41:26.904 2013 (UTC + 6:00)
System Uptime: 0 days 0:26:28.888
BugCheck 1E, {ffffffffc0000005, fffff80002cabf94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri May 17 03:00:35.682 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:04.056
BugCheck 3B, {c0000005, fffff88004954f82, fffff88005a71b60, 0}
Probably caused by : atikmdag.sys ( atikmdag+76f82 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu May 16 03:58:19.270 2013 (UTC + 6:00)
System Uptime: 0 days 0:08:55.644
BugCheck 1E, {ffffffffc0000005, fffff80002c9bf94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu May 16 03:49:05.407 2013 (UTC + 6:00)
System Uptime: 0 days 0:56:37.391
BugCheck 1E, {ffffffffc0000005, fffff80002c44f94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue May 14 01:39:26.461 2013 (UTC + 6:00)
System Uptime: 0 days 5:12:22.835
BugCheck 7F, {8, 80050033, 406f8, fffff80002f47a4f}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  MsMpEng.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 13 19:58:07.359 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:31.732
BugCheck 1A, {41287, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 13 13:29:59.016 2013 (UTC + 6:00)
System Uptime: 0 days 0:13:32.389
BugCheck 1E, {ffffffffc0000005, fffff80002c5ff94, 1, 0}
Probably caused by : hardware ( nt!NtYieldExecution+24 )
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  Steam.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 13 05:09:32.020 2013 (UTC + 6:00)
System Uptime: 0 days 0:58:52.394
BugCheck 50, {ffffd400372676c5, 1, fffff80002d0df76, 7}
Probably caused by : memory_corruption ( nt!MiLocateAddress+56 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  MsMpEng.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 13 02:51:49.565 2013 (UTC + 6:00)
System Uptime: 0 days 0:02:09.938
BugCheck 124, {0, fffffa8007a2c028, be000000, 800400}
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  mscorsvw.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 13 01:54:23.100 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:51.474
BugCheck 1A, {41287, 4b000006, 0, 0}
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+454f5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  TrustedInstall
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 13 01:45:57.528 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:18.902
BugCheck 1A, {41287, 1f, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+454f5 )
BUGCHECK_STR:  0x1a_41287
PROCESS_NAME:  TrustedInstall
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Mon May 13 01:38:47.277 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:54.261
BugCheck 124, {0, fffffa8007854028, be000000, 800400}
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  mscorsvw.exe
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
My System SpecsSystem Spec
21 May 2013   #3

microsoft window7 Ultimate x64
 
 

Enzoro

-It is likely a driver associated with that game i think the bsods being caused by your drivers

-To resolve the bsods being caused by your drivers, you can either try updating them or simply disabling the device. Try updating first, if that doesnt help, try disabling.
-Click Start , and type "device manager" (without quotes) into the search field.
-Click Device Manager from the results list.
-In the Device Manager window that opens, double-click IEEE 1394 Bus host controllers .
-Select the 1394 Controller.
-Right click on it and select Update Driver software.

hopefully it will help you....
My System SpecsSystem Spec
.


21 May 2013   #4

Windows 7 64 bit
 
 

First of all, thank you very much for taking the time to read and reply to my problems.

Alright, so I started doing all the tests suggested by koolkat77:

SFC Scannow went fine, and chkdsk went fine. I was going to continue when suddendly my computer froze in a way that I hadn't seen beforeSee image below) It does this like 5 minutes in every time unless on safe mode...this doesn't allow me to run a lot of diagnostics inside w indows, but I'll carry on with what I can outside of it.

I tried to open speccy (on safe mode) and it gave me an error within graphics (cannot initialise SPC dll)

britny: I can't see IEEE 1394 Bus host controllers within device manager I opened all categories an I just don't see it. I find Universal serial bus controllers. Is that the same?

Thanks again! you are amazing.


My System SpecsSystem Spec
21 May 2013   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

SPC.dll is the library file used by Speccy, have done some searching, and it seems to be commonly related to third-party firewalls or certain anti-virus programs blocking access. Have you tried reinstalling the program?

So far, it seems to be pointing to a graphics card issue, therefore I would start with Furmark. win32k.sys is part of the Windows API relates to graphics-based support and functions etc.

More Help (Furmark) - FurMark
My System SpecsSystem Spec
21 May 2013   #6
Microsoft MVP

Windows 7 Ultimate X64 SP1
 
 

Hi EnzoRo. You may not have IEEE 1394 on your motherboard, or the drivers were never installed, it's a fading tech brought out by Apple. https://en.wikipedia.org/wiki/IEEE_1394 Universal Serial Bus is USB, where we connect most any peripheral these days.

Now for you screen issue, your shot looks to me that the graphics card is bad or it is overheating. Make sure its fan runs and is not clogged with dust in its cooling fins, which may be under a cover.
You could remove the card and reinstall it to confirm its fully seated and the auxiliary power is fully connected.

Try running Furmark in Safe Mode, not sure if it will. You should have more options than HDMI, I have the same board and it has DVI and VGA. If you don't have the on-chip GPU (IGPU) enabled, enable it and connect the monitor that way and try your games, although they may or may not run, the HD2500 GPU is a bit weak for that.
My System SpecsSystem Spec
21 May 2013   #7

Windows 7 64 bit
 
 

It looks like furmark won't run on safe mode, so I'll uninstall all graphics card drivers and reinstall and see what happens in normal mode with furmark.
My System SpecsSystem Spec
21 May 2013   #8
Microsoft MVP

Windows 7 Ultimate SP1 X64 (Windows 10, 8.1, Linux Mint, Windows XP and others in VM)
 
 

EnzoRo, I agree with Britton30, it appears to be a graphics problem. The error code you mentioned is a general hardware fault, meaning that some piece of hardware has failed, the driver made it fail or the bios settings are wrong. Try going into bios and look atthe hardware monitor and tell us what the +12V, +5V and the +3.3V readings are. While there, look in advanced options and see what your sata controller is set to, by default it should be set to AHCI, but remember what the current setting is. Set bios to optimized defaults (F5), set the sata controller to what it is right now, set your ram timings, frequency and voltage to manufacturers settings. In boot options set you CD/DVD player to 1st boot device and the Hard drive to 2nd boot device, save and exit. If you are overclocking anything, stop and set everything to default values. If you do not have monitoring programs, monitor your CPU and GPU temps. I'm sure your GPU came with a monitoring program or you could use MSI Afterburner. You can also use Core Temp to monitor your CPU temps.
My System SpecsSystem Spec
21 May 2013   #9

Windows 7 64 bit
 
 

Ok, so it was running for a while, like 5 minutes, everything seemed fine, and then all of a sudden it crashed the same way as it crashed earlier.

Just don't have a clue! Temperature was on 72░ most of the time during the test. But then again, it has crashed before without anything taxing, so I don;t think it was the test that made it crash.

My System SpecsSystem Spec
21 May 2013   #10
Microsoft MVP

Windows 7 Ultimate SP1 X64 (Windows 10, 8.1, Linux Mint, Windows XP and others in VM)
 
 

When you run Furmark, make sure and keep watch on your GPU temps. Furmark will cause your GPU to heat up quite rapidly. If temps go too high, stop Furmark.
My System SpecsSystem Spec
Reply

 BSOD playing games at first, then all the time. Multiple errors.




Thread Tools



Similar help and support threads for2: BSOD playing games at first, then all the time. Multiple errors.
Thread Forum
BSOD playing games, multiple errors BSOD Help and Support
Solved BSOD errors when watching videos and playing games. BSOD Help and Support
BSOD playing 3D games (The Witcher 2, FFXIV beta, SC5) various errors BSOD Help and Support
Solved Frequent BSOD, nearly always when playing games, varying errors BSOD Help and Support
Solved BSOD playing multiple games, errors down below BSOD Help and Support
Various BSOD errors playing games such as Bioshock 2/Deus Ex HR BSOD Help and Support
BSoD's playing games, and randomly on Idle, Multiple errors BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 08:20 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33