New
#1
BSOD during CSGo / Overwatch with windows 10.
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?
Code:======================================== Windows version: Windows 10 , 10.0, build: 10586 Windows dir: C:\Windows Hardware: ASUSTeK COMPUTER INC., H170 PRO GAMING CPU: GenuineIntel Intel(R) Core(TM) 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.
Last edited by Brink; 28 Nov 2016 at 20:06. Reason: code box