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 during crysis


29 May 2011   #1

7 ultimate 64bit
 
 
bsod during crysis

for some reason i get a bsod when playing crysis and i dont know why cuz i can do anything else on my pc just fine search the web, watch videos (both player or streamed), download things, chat, and so on at the same time. once i play a high end game like crysis it will slow down then screen shows a glitch then bsod then restarts the pc and here is what i get when i get back to my desktop I have included the mini dump files too so anyone can decipher it:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007C01028
BCP3: 00000000B4692000
BCP4: 00000000BC000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052911-30529-01.dmp
C:\Users\kris\AppData\Local\Temp\WER-55364-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


My System SpecsSystem Spec
.

29 May 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by darksidekei View Post
for some reason i get a bsod when playing crysis and i dont know why cuz i can do anything else on my pc just fine search the web, watch videos (both player or streamed), download things, chat, and so on at the same time. once i play a high end game like crysis it will slow down then screen shows a glitch then bsod then restarts the pc and here is what i get when i get back to my desktop I have included the mini dump files too so anyone can decipher it:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8007C01028
BCP3: 00000000B4692000
BCP4: 00000000BC000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\052911-30529-01.dmp
C:\Users\kris\AppData\Local\Temp\WER-55364-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
These were caused by hardware

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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

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 0x124 - what it means and what to try


Please run driver verifier to find out which driver is at fault.

Quote:
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
My System SpecsSystem Spec
29 May 2011   #3

7 ultimate 64bit
 
 

is there a way to find out which hardware is causing the issue or a program to check my drivers that doesnt require u to pay... i think my drivers r up to date...asus drivers for my mobo were last updated in 2010 on their site..
My System SpecsSystem Spec
.


29 May 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by darksidekei View Post
is there a way to find out which hardware is causing the issue or a program to check my drivers that doesnt require u to pay... i think my drivers r up to date...asus drivers for my mobo were last updated in 2010 on their site..

did you do the things suggested here

Stop 0x124 - what it means and what to try
My System SpecsSystem Spec
30 May 2011   #5

7 ultimate 64bit
 
 

I did a fresh installation with a few bsod moments but so far this is the latest windows issue i recieved and this is the latest minidump..i havent even installed crysis yet so it has to be a hardware issue..i need to figure out which is it so far i did a memory scan b4 i did the reinstall and i did 7 checks and seems that the rams r fine..so it can be either video card amd 6core chip or motherboard or the power supply..those r all i have in there other than 2 hdd 1tb..



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002C9A0F3
BCP3: FFFFF8800C7B5FD0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\053011-29640-01.dmp
C:\Users\Kris\AppData\Local\Temp\WER-38017-0.sysdata.xml
My System SpecsSystem Spec
30 May 2011   #6

7 ultimate 64bit
 
 

can a monitor cause a bsod? if it mentions hardware? cuz i have a iz3d monitor and i have it with the video card since it has 2 dvi ports in the video card..
My System SpecsSystem Spec
01 Jun 2011   #7

7 ultimate 64bit
 
 

think i fixed the issue i opened my pc up cleaned the dust unplugged the power to the video and plugged them back in and then switched the ram chips around and seem to fix the problem...i was able to play the game and finally finish it lol now im onto crysis warhead and then crysis 2 (on ps3 tho lol) crysis is probably the most error filled game known to man...lol thanks for the help tho appreciate it
My System SpecsSystem Spec
02 Jun 2011   #8

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by darksidekei View Post
think i fixed the issue i opened my pc up cleaned the dust unplugged the power to the video and plugged them back in and then switched the ram chips around and seem to fix the problem...i was able to play the game and finally finish it lol now im onto crysis warhead and then crysis 2 (on ps3 tho lol) crysis is probably the most error filled game known to man...lol thanks for the help tho appreciate it
My pleasure and keep us posted if you need help
My System SpecsSystem Spec
02 Jun 2011   #9

7 ultimate 64bit
 
 
guess i spoke to soon...lol

this happened during crysis warhead now...i was able to play for a bit tho b4 it did it...like half hour i think think u can figure out what the code is to this one? heres the latest minidump file is it hardware again?


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800834D028
BCP3: 00000000B6722000
BCP4: 00000000D6000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\060211-25677-01.dmp
C:\Users\Kris\AppData\Local\Temp\WER-33711-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
My System SpecsSystem Spec
02 Jun 2011   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by darksidekei View Post
this happened during crysis warhead now...i was able to play for a bit tho b4 it did it...like half hour i think think u can figure out what the code is to this one? heres the latest minidump file is it hardware again?


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800834D028
BCP3: 00000000B6722000
BCP4: 00000000D6000135
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\060211-25677-01.dmp
C:\Users\Kris\AppData\Local\Temp\WER-33711-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Its still hardware with crysis the active thread. I suggest this

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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

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 0x124 - what it means and what to try


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\060211-25677-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e48650
Debug session time: Thu Jun  2 06:20:26.971 2011 (GMT-4)
System Uptime: 0 days 22:04:33.361
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800834d028, b6722000, d6000135}

Probably caused by : hardware

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800834d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6722000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000d6000135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Crysis.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fddb08 fffff800`031fea3b : 00000000`00000124 00000000`00000000 fffffa80`0834d028 00000000`b6722000 : nt!KeBugCheckEx
fffff880`02fddb10 fffff800`02d90563 : 00000000`00000001 fffffa80`08405c50 00000000`00000000 fffffa80`08405ca0 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddb50 fffff800`031fe700 : 00000000`00000728 fffffa80`08405c50 fffff880`02fddeb0 00000000`35408900 : nt!WheaReportHwError+0x263
fffff880`02fddbb0 fffff800`031fe052 : fffffa80`08405c50 fffff880`02fddeb0 fffffa80`08405c50 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddd00 fffff800`031f1e8f : 00000000`35408980 00000000`00000001 fffff880`02fddf30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddd40 fffff800`02c815ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddd70 fffff800`02c81453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fddeb0 00000000`3510a27d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0058d0e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3510a27d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 bsod during crysis




Thread Tools



Similar help and support threads for2: bsod during crysis
Thread Forum
Solved BSOD during Crysis 3 BSOD Help and Support
BSOD while downloading Crysis 3 BSOD Help and Support
BSOD on Crysis (3 times), and 1 during web browsing BSOD Help and Support
BSOD Running Crysis (dxgmms1.sys) BSOD Help and Support
BSOD playing Crysis Windows 7 x64 BSOD Help and Support
Solved BSOD while playing crysis BSOD Help and Support
BSOD in Crysis 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 07:19 PM.
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