Windows 10: 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.[/quote]

:)

 

Issues with Win10 Anniversary update

ranges from games like CSGO or Overwatch to windows based programs like task manager or trying to view settings. Also seems my network connectivity is acting funny. says im connected but sometimes CSGO or Overwatch will say im not and wont connect.

 

Random system crashes

Troubleshooting

EDIT: it can also happen on system boot.

EDIT2: it only happens on certain games. Like I never experienced this in CSGO or Overwatch.

 

Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions

 

Hi please find attached the dmp files, appreciate any help!

Attachment 111798

 

Looks like you have an illegal installation/activation. When you correct this and upload a new DM_Log_collector zip file I'll be happy to look at it and see if I can help.

 

hi i have reinstall, my OS is original, so are everything else.

please see my new dump files

Attachment 111993

 

The dumpfiles have many different bugcheck:
Code: BugCheck 50, {fffff803493e2340, 10, fffff803493e2340, 2} Could not read faulting driver name Probably caused by : memory_corruption BugCheck 1E, {ffffffffc0000005, fffff80102dc8077, 0, ffffffffffffffff} Probably caused by : memory_corruption BugCheck 3B, {c0000005, fffff8019b4850a0, ffffaf01a25f7310, 0} Probably caused by : memory_corruption BugCheck A, {100000000f, 2, 1, fffff802ab8a9fde} Probably caused by : memory_corruption[/quote] But these dumpfiles have 1 thing in common Memory corruption.

You have G skill F4-2400C15-8GVR modules. But according to the dumpfiles they are running at 2133 mhz.
Code: Speed 2133MHz Manufacturer G-Skill Serial Number Asset Tag Number Part Number F4-2400C15-8GVR[/quote] Try to set in your BIOS the modules at the right speed 2400 mhz. and check the settings.
Hopefully this stops the BSOD.
If not i am afraid your memory is faulty.
You can test your memory with:
You can use the free tool "Memtest86+" to stress test the RAM.

How to run "Memtest" - RAM - Test with Memtest86+ - Windows 7 Help Forums
MemTest86+ - Test RAM - Windows 10 Forums
Make sure you are using the latest version 5.01 - Memtest86+ - Advanced Memory Diagnostic Tool

You can stop the test even if a single error is found during the test. Otherwise continue the test for 8-10 passes and post a screenshot with next reply. 8 passes is the recommended bare minimum but more passes will give better result.

 

Yes, it is running as 2133mhz because my motherboard is H170. However it shouldn't be a problem as the board should be able to use the 2400mhz as 2133mhz right?

 

Yes, i overlooked that you had H170 mobo.

 

To rule out defective ram, run memtest86+ for a minimum of 8 passes. Follow these directions.

===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

If that shows no errors I suggest enabling Driver Verrifier and see if that shows us anything:

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.