Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

PC Crashes During Gaming


  • Please log in to reply
3 replies to this topic

#1 zapper375

zapper375

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 14 October 2014 - 05:57 PM

My PC just shuts off during gaming, or rarely displays the Blue Screen for about 3 seconds before shutting off. It does this when playing high end games such as World of war craft and such. I'm leaning towards the video card is whats causing the problem, but im not sure.

EDIT: I was having this problem on my old computer, so i got a new one hoping it would fix the problem. the only thing i transferred from the old computer was the video card.

Here are specs: 

http://speccy.piriform.com/results/CBcbhe2rQJqIgLMGfilvE5T

 

And here is my crash report:

 System Information (local)


computer name: NICK-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: p6774y, Hewlett-Packard, FOXCONN, 2AB1 
CPU: AuthenticAMD AMD Phenom™ II X4 840T Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 6439538688 total





Crash Dump Analysis


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 10/14/2014 10:44:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101414-17113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006B68038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 10/14/2014 10:09:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101414-17768-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA80061E48F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 10/14/2014 10:00:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101414-17830-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006B598F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 10/14/2014 9:47:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101414-27019-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006AD68F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Mon 10/6/2014 6:26:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100614-18813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A63CC) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006C35038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 9/30/2014 9:06:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-18907-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC4283) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000194283, 0xFFFFF8800535D060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Tue 9/30/2014 9:06:30 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x863) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000194283, 0xFFFFF8800535D060, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Sun 8/24/2014 8:21:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082414-17565-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA800753F078, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sun 8/24/2014 1:50:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082414-22464-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960001BB630) 
Bugcheck code: 0x50 (0xFFFFF8800724291D, 0x1, 0xFFFFF960001BB630, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Fri 8/22/2014 8:53:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082214-18158-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) 
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8006BE0078, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





Conclusion


32 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 


Edited by zapper375, 14 October 2014 - 09:26 PM.


BC AdBot (Login to Remove)

 


#2 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,239 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:04:55 PM

Posted 14 October 2014 - 06:11 PM

this is normally a heat error... please regard this in depth post

 

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-bug-check-0x124-wheauncorrectableerror/f15eab92-1bae-4d7a-af83-6ff4f885f22d?tab=question&status=AllReplies#tabs


Edited by TsVk!, 14 October 2014 - 06:16 PM.


#3 zapper375

zapper375
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 14 October 2014 - 09:24 PM

heat error huh? Thats weird cause i just got this pc... could it be that the video card i over heating? cause ive had it for awhile.

 



#4 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,239 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:04:55 PM

Posted 14 October 2014 - 09:52 PM

Not really sure mate... follow the troubleshooting in the post I linked. It should lead you to the answer.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users