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 (mostly) during gaming


  • Please log in to reply
9 replies to this topic

#1 czeslav87

czeslav87

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:24 AM

Posted 02 April 2016 - 03:19 AM

Hello,

 

I'm having some issues with my PC. There are some random crashes, mostly during gaming. Usualli it freezes, blue screen appears. Last time screen turned red and pc restarted. I've tried to analyse it with furmark, memtest, checked power supply voltage and everything seemed fine.

 

My configuration.

 

Operating System
    Windows 10 Home 64-bit
CPU
    AMD Phenom II X4 955    51 °C
    Deneb 45nm Technology
RAM
    8,00GB Dual-Channel DDR3 @ 766MHz (9-9-9-24)
Motherboard
    MICRO-STAR INTERNATIONAL CO.LTD 870-C45 (MS-7599) (CPU 1)    47 °C
Graphics
    SA300/SA350 (1920x1080@60Hz)
    2048MB ATI AMD Radeon R9 200 Series (MSI)    52 °C
Storage
    111GB KINGSTON SV300S37A120G ATA Device (SSD)    36 °C
    298GB Western Digital WDC WD3200AAKS-00L9A0 ATA Device (SATA)    50 °C
    2794GB Seagate Backup+ Desk SCSI Disk Device (USB (SATA))    53 °C
Optical Drives
    LITE-ON DVDRW LH-20A1L ATA Device
Audio
    Realtek High Definition Audio

 

I'll send some reports in a second.

 

Thank you in advance for help.



BC AdBot (Login to Remove)

 


#2 czeslav87

czeslav87
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:24 AM

Posted 02 April 2016 - 03:21 AM

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 2016-04-02 07:48:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040216-9046-01.dmp
This was probably caused by the following module: cdd.dll (cdd!_report_gsfailure+0x26)
Bugcheck code: 0xF7 (0xFFFFD000239B7970, 0xD69634D551A3, 0xFFFF2969CB2AAE5C, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\cdd.dll
product: MicrosoftŽ WindowsŽ Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 Sat 2016-04-02 07:48:02 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: cdd.dll (cdd!_report_gsfailure+0x26)
Bugcheck code: 0xF7 (0xFFFFD000239B7970, 0xD69634D551A3, 0xFFFF2969CB2AAE5C, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
file path: C:\WINDOWS\system32\cdd.dll
product: MicrosoftŽ WindowsŽ Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 2016-04-01 18:30:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040116-12281-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsCopyReadA+0x217)
Bugcheck code: 0x1A (0x5002, 0xFFFFF79940000000, 0x15393, 0x2005738FFFFFFE)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: System operacyjny MicrosoftŽ WindowsŽ
company: Microsoft Corporation
description: Sterownik systemu plików NT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 2016-04-01 06:46:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040116-11265-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DXGCONTEXT::~DXGCONTEXT+0xE8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8007BEC63FE, 0xFFFFD001DAD45AD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: MicrosoftŽ WindowsŽ Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 2016-03-29 16:45:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032916-9453-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm!PerfSelectionPTStates+0x12)
Bugcheck code: 0xD1 (0xFFFFE021099421B0, 0x2, 0x0, 0xFFFFF80166FD4142)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: MicrosoftŽ WindowsŽ Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 2016-03-25 16:52:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032516-11203-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1 (0x6D647704, 0x0, 0xFFFF, 0xFFFFD00022927CC0)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2016-03-17 22:53:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031716-11343-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8019429F607, 0xFFFFD000230F2A50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2016-01-14 18:34:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\011416-8187-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8018724EEF6, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 2015-12-20 19:00:40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\122015-8781-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x403, 0xFFFFF6800030DE58, 0xD86000003D76E867, 0xFFFEF6800030DE58)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 2015-12-13 10:33:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\121315-7265-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE000776D6030)
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



#3 czeslav87

czeslav87
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:24 AM

Posted 02 April 2016 - 06:06 AM

Little update - removed one ram stick and so far it's good.

 

EDIT: just crashed again. Red screen just after starting a game. Not sure if it's faulty memory problem. Or maybe it's motherboard issue?


Edited by czeslav87, 02 April 2016 - 06:19 AM.


#4 Foldingchair

Foldingchair

  • Members
  • 109 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Netherlands
  • Local time:03:24 AM

Posted 02 April 2016 - 06:45 AM

This may seem a bit obvious, but have you tried using only the other RAM stick? I've experienced weird crashes in the past, even after removing one of the RAM sticks, but when I only used the one I had earlier taken out, everything was fine.


"Peace and blessings be upon you all."


#5 czeslav87

czeslav87
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:24 AM

Posted 02 April 2016 - 09:28 AM

Tried both, tried different slots. Nothing helps :(



#6 czeslav87

czeslav87
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:24 AM

Posted 02 April 2016 - 12:42 PM

I'm running memtest now. Both memory sticks look fine (2 passes so far)



#7 czeslav87

czeslav87
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:24 AM

Posted 02 April 2016 - 04:09 PM

I've just formatted drive, installed windows 7 and got blue screen after couple of minutes. Guess it's hardware related then :/

 

My guess is motherboard or ssd. Any suggestions how to check it?



#8 ScathEnfys

ScathEnfys

    Bleeping Butterfly


  • Members
  • 1,375 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Deep in the Surface Web
  • Local time:10:24 PM

Posted 13 April 2016 - 03:03 PM

Not a whole lot you can do about motherboard testing unless you have a different system with the same socket CPU... as for SSD issues, there are some good tools posted here.
Proud system builder, modder, and watercooler.

GitHub | SoundCloud | Keybase

#9 czeslav87

czeslav87
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:03:24 AM

Posted 13 April 2016 - 03:57 PM

Hey. Thanks for reply. I forgot to update :)

 

I run tests with "Hot CPU tester pro". Each time it crashed after ~10s so i figured it's cpu related issue. Then i realised something i completly forgot about. My motherboard (MICRO-STAR INTERNATIONAL CO.LTD 870-C45 (MS-7599)) had "quick OC" switch which happened to be turned on, which i had no idea. I checked the bios and it was indeed OCed. So after resetting switch it's stable now.

 

Thanks for help



#10 ScathEnfys

ScathEnfys

    Bleeping Butterfly


  • Members
  • 1,375 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Deep in the Surface Web
  • Local time:10:24 PM

Posted 13 April 2016 - 07:55 PM

No problem :) Glad it was fixed so easily :)
Proud system builder, modder, and watercooler.

GitHub | SoundCloud | Keybase




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users