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

Multiple BSOD during CSGo / Overwatch with windows 10.


  • Please log in to reply
1 reply to this topic

#1 bentianjl

bentianjl

  • Members
  • 1 posts
  • OFFLINE
  •  

Posted 28 November 2016 - 08:46 PM

Hi Guys,

so sorry to trouble! In need of desperate help!

i have installed a fresh copy of windows 10 v1511 and all the latest drivers, i faced several frustrating random BSOD issues during gaming! argh!

I have the minidump logs below for the BSOD. never have i faced such issues back when i have winxp and win7.

i checked online, reinstall windows, graphics card driver all to no avail!!.. sigh... anyone can help pls?

 

========================================


Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., H170 PRO GAMING
CPU: GenuineIntel Intel® Core™ i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17110478848 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11/30/2016 12:00:42 AM your computer crashed
crash dump file: C:\Windows\Minidump\112916-4062-01.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. 
Google query: CUSTOM_ERROR



On Tue 11/29/2016 2:04:05 AM your computer crashed
crash dump file: C:\Windows\Minidump\112916-42046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970) 
Bugcheck code: 0xC4 (0x13A, 0xFFFFCF820F676F50, 0xFFFDE0002EE4E0E0, 0xFFFFCF820F676010)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. 
The driver has called ExFreePool and Driver Verifier detects an error in one of the internal values that is used to track pool usage. 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 Tue 11/29/2016 2:04:05 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2!VidMmInterface+0x36327) 
Bugcheck code: 0xC4 (0x13A, 0xFFFFCF820F676F50, 0xFFFDE0002EE4E0E0, 0xFFFFCF820F676010)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. 
The driver has called ExFreePool and Driver Verifier detects an error in one of the internal values that is used to track pool usage. 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 11/29/2016 12:00:43 AM your computer crashed
crash dump file: C:\Windows\Minidump\112916-3859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801351BD157, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Mon 11/28/2016 11:59:37 PM your computer crashed
crash dump file: C:\Windows\Minidump\112916-4250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970) 
Bugcheck code: 0x3B (0x80000003, 0xFFFFF801CA6AB55E, 0xFFFFD000DD69AC50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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.
 

 



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:16 PM

Posted 29 November 2016 - 05:52 AM

Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)   http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities.  
.ZIP is the type file that can be uploaded to the forums.

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users