- Joined
- Aug 28, 2007
- Messages
- 36,164
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd00104d6a6e0, ffffd00104d6a638, 0}
*** WARNING: Unable to verify timestamp for bwcW8x64.sys
*** ERROR: Module load completed but symbols could not be loaded for bwcW8x64.sys
Probably caused by : bwcW8x64.sys ( bwcW8x64+4fda )
Followup: MachineOwnerthe above Bugcheck 139 means corruption has been detected in a critical data structure and two drivers were mentioned. As your aware most of the dumps point to this driver:
bwcW8x64.sys Fri Jan 22 22:07:20 2016: Killer Bandwidth Control Filter Driver please update:
Link Removed
or
Support For Z170A GAMING M3 | MSI Global | Motherboard - The world leader in motherboard design
I know from personal experience that when removing or installing a Killer driver then you need to disable any Anti-virus that you have running otherwise the driver may not install properly.
Please remove the current gpu driver using the display driver uninstaller. This will remove any corruption caused by former gpu driver installs and leave the system ready for a new gpu driver (or the same one again if it's the latest)
Open an admin command prompt and type:
sfc /scannow
Press enter and await results.
Post any new dump files.
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #22
Update:
I had my friend removal all Killer/Rivet software and manually install Just the network driver.
While using Driver Verifier he got a couple blue screens pointing to just nvlddmkm.sys, so we then ran DDU and then got the latest Nvidia drivers and installed only the graphics/HDAudio/PhysX drivers.
He made it through a game of Overwatch with no crashes, but it was largely unplayable due the jittering/clunky-ness from running driver verifier. Before uninstalling-reinstalling the display drivers he would get crashes/restarts in under 30 seconds.
Since windows didn't BSOD/Restart for the duration of a full game, we will have the computer run normally for a while and see what happens. Hopefully nothing out of the ordinary!
I had my friend removal all Killer/Rivet software and manually install Just the network driver.
While using Driver Verifier he got a couple blue screens pointing to just nvlddmkm.sys, so we then ran DDU and then got the latest Nvidia drivers and installed only the graphics/HDAudio/PhysX drivers.
He made it through a game of Overwatch with no crashes, but it was largely unplayable due the jittering/clunky-ness from running driver verifier. Before uninstalling-reinstalling the display drivers he would get crashes/restarts in under 30 seconds.
Since windows didn't BSOD/Restart for the duration of a full game, we will have the computer run normally for a while and see what happens. Hopefully nothing out of the ordinary!
- Joined
- Aug 28, 2007
- Messages
- 36,164
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #24
Well that hope was short lived!
My friend played a game for an hour or so and then browsed the web for a bit before leaving to run some errands. He left the computer idle for a few hours and there was no BSODs during any of that activity.
However, when he returned he tried to fire up Overwatch and it crashed to windows within 15 seconds and moments later windows threw a BSOD. DMP file below.
I couldn't find any consistent information on dxgmms1.sys but it seems to be part of DirectX from what I can dig up. Since we ARE using the most recent drivers I find it difficult to believe they are the cause.
Since I was suspicious of the integrity of his system files, I had him run System File Checker(sfc) and the results read:
That can't be good! I have attached cbs.log as 7zip file because it's 9mb normally and these forums wont let me upload it as-is.
EDIT:
digging through the CBS file I found a couple points of interest;
2016-08-06 23:20:28, Info CSI 0000052e [SR] Could not reproject corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\Microsoft.NET\Framework64\v2.0.50727"\[l:34{17}]"System.Design.dll"; source file in store is also corrupted
2016-08-06 23:20:38, Info CSI 0000055f [SR] Could not reproject corrupted file [ml:520{260},l:128{64}]"\??\C:\Windows\Microsoft.NET\Framework64\v4.0.30319\NativeImages"\[l:36{18}]"system.core.ni.dll"; source file in store is also corrupted
My friend played a game for an hour or so and then browsed the web for a bit before leaving to run some errands. He left the computer idle for a few hours and there was no BSODs during any of that activity.
However, when he returned he tried to fire up Overwatch and it crashed to windows within 15 seconds and moments later windows threw a BSOD. DMP file below.
Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\PC\Downloads\080616-5140-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.18378.amd64fre.winblue_ltsb.160611-0600
Machine Name:
Kernel base = 0xfffff802`70a0e000 PsLoadedModuleList = 0xfffff802`70ce1630
Debug session time: Sat Aug 6 23:05:08.885 2016 (UTC - 4:00)
System Uptime: 0 days 7:04:40.224
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd001d921f3e0, ffffd001d921f338, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+1a895 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd001d921f3e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd001d921f338, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 9600.18378.amd64fre.winblue_ltsb.160611-0600
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7978
SYSTEM_SKU: Default string
SYSTEM_VERSION: 2.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: A.60
BIOS_DATE: 05/16/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: Z170A GAMING M3 (MS-7978)
BASEBOARD_VERSION: 2.0
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffd001d921f3e0
BUGCHECK_P3: ffffd001d921f338
BUGCHECK_P4: 0
TRAP_FRAME: ffffd001d921f3e0 -- (.trap 0xffffd001d921f3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe001c2a0a2f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffc000bd2e3878 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8003e5db515 rsp=ffffd001d921f570 rbp=0000000000000000
r8=000000000000000b r9=000000000000000b r10=fffff78000000008
r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x1a895:
fffff800`3e5db515 cd29 int 29h
Resetting default scope
EXCEPTION_RECORD: ffffd001d921f338 -- (.exr 0xffffd001d921f338)
ExceptionAddress: fffff8003e5db515 (dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x000000000001a895)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY
CPU_COUNT: 8
CPU_MHZ: fa8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: Overwatch.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE_STR: c0000409
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_SESSION_HOST: COREREACTOR
ANALYSIS_SESSION_TIME: 08-06-2016 23:17:13.0616
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff80270b67de9 to fffff80270b5c2a0
STACK_TEXT:
ffffd001`d921f0b8 fffff802`70b67de9 : 00000000`00000139 00000000`00000003 ffffd001`d921f3e0 ffffd001`d921f338 : nt!KeBugCheckEx
ffffd001`d921f0c0 fffff802`70b68110 : ffffd001`d921f3e0 ffffd001`d921f289 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd001`d921f200 fffff802`70b67334 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiFastFailDispatch+0xd0
ffffd001`d921f3e0 fffff800`3e5db515 : ffffe001`c2a0a320 fffff800`00000000 ffffe001`bbfd7000 ffffe001`c2910000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd001`d921f570 fffff800`3e5c0c32 : ffffc000`be2e93e0 fffff800`00000000 ffffe001`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x1a895
ffffd001`d921f6f0 fffff800`3e4630f2 : ffffc000`be0a98d0 ffffd001`d921f8c0 ffffc000`be3448b0 00000000`00000002 : dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x52
ffffd001`d921f730 fffff800`3e45d452 : ffffc000`be2e93e0 00000000`00000000 ffffc000`00000000 ffffc000`be0a98d0 : dxgkrnl!DXGDEVICE:estroyAllocations+0x172
ffffd001`d921f830 fffff802`70b67ab3 : ffffe001`c1a98880 00000000`00000000 ffffe001`bcbbf401 00000078`00000000 : dxgkrnl!DxgkPresent+0x682
ffffd001`d921fa00 00007ffe`300d173a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000078`1e24e3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`300d173a
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 3988fb283b99614e9758437a32f5e2c62bada263
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 02b50e937fa59ec0298772d9017dcd03ef496666
THREAD_SHA1_HASH_MOD: 05c6c0f2a208b89951c23c5d66f594e30627c075
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+1a895
fffff800`3e5db515 cd29 int 29h
FAULT_INSTR_CODE: 44cc29cd
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+1a895
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54505506
IMAGE_VERSION: 6.3.9600.17415
BUCKET_ID_FUNC_OFFSET: 1a895
FAILURE_BUCKET_ID: 0x139_3_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation
BUCKET_ID: 0x139_3_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation
PRIMARY_PROBLEM_CLASS: 0x139_3_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation
TARGET_TIME: 2016-08-07T03:05:08.000Z
OSBUILD: 9600
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 8.1
OSEDITION: Windows 8.1 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-06-11 11:45:59
BUILDDATESTAMP_STR: 160611-0600
BUILDLAB_STR: winblue_ltsb
BUILDOSVER_STR: 6.3.9600.18378.amd64fre.winblue_ltsb.160611-0600
ANALYSIS_SESSION_ELAPSED_TIME: 2b6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_dxgmms1!vidmm_global::closeoneallocation
FAILURE_ID_HASH: {b88b4adf-cd8b-03a6-aa30-49ad86850731}
I couldn't find any consistent information on dxgmms1.sys but it seems to be part of DirectX from what I can dig up. Since we ARE using the most recent drivers I find it difficult to believe they are the cause.
Since I was suspicious of the integrity of his system files, I had him run System File Checker(sfc) and the results read:
That can't be good! I have attached cbs.log as 7zip file because it's 9mb normally and these forums wont let me upload it as-is.
EDIT:
digging through the CBS file I found a couple points of interest;
2016-08-06 23:20:28, Info CSI 0000052e [SR] Could not reproject corrupted file [ml:520{260},l:102{51}]"\??\C:\Windows\Microsoft.NET\Framework64\v2.0.50727"\[l:34{17}]"System.Design.dll"; source file in store is also corrupted
2016-08-06 23:20:38, Info CSI 0000055f [SR] Could not reproject corrupted file [ml:520{260},l:128{64}]"\??\C:\Windows\Microsoft.NET\Framework64\v4.0.30319\NativeImages"\[l:36{18}]"system.core.ni.dll"; source file in store is also corrupted
- Joined
- Aug 28, 2007
- Messages
- 36,164
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd001d921f3e0, ffffd001d921f338, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+1a895 )
Followup: MachineOwnerbefore i forget to ask once again can you please post the make and model of the PSU.
The above dump file means a critical data structure has become corrupted. When the operating system was first installed was it a clean install off a disk/USB or something else?
See if DISM will run after running the sfc, this will attempt to repair any corruption. Open an admin command prompt. Type:
sfc /scannow
press enter and await results
In the same command prompt and after the above scan has finished type:
dism /online /cleanup-image /restorehealth
Press enter and await results (longer this time).
If the first scan found files it could not repair but the second scan is successful, run the first scan again using the same command prompt box and this time it should repair the files found.
Check the event viewer for anything suspicious, sorry i can't be more specific but basically your looking for anything out of the ordinary.
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #26
- Joined
- Aug 28, 2007
- Messages
- 36,164
Thank you, I also assume he did a clean install onto a clean HDD?
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #28
Its an SSD (Samsung Pro 850 512GB). I assume it was clean. Initially he had windows 10 on but had more severe problems. So he booted from the windows 8.1 disk and presumeably formatted the drive since he had to re-copy his personal files back after installing windows 8.1.
Okay, so I just had him rerun "sfc /scannow" There were problems it couldn't fix.
Immediately following that, I had him run "dism /online /cleanup-image /restorehealth". We received the following message:
With that being done, we once again ran: "sfc /scannow". This time we got the following message.
So I assume that's what we want. He's gonna be busy for a while today so we'll have to wait till he gets a chance to stress it in some games to see if this had any effect on the crashing.
Okay, so I just had him rerun "sfc /scannow" There were problems it couldn't fix.
Immediately following that, I had him run "dism /online /cleanup-image /restorehealth". We received the following message:
With that being done, we once again ran: "sfc /scannow". This time we got the following message.
So I assume that's what we want. He's gonna be busy for a while today so we'll have to wait till he gets a chance to stress it in some games to see if this had any effect on the crashing.
- Joined
- Aug 28, 2007
- Messages
- 36,164
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #30
Welp, there was a BSOD today but it was on boot and didn't reoccur upon restart. DMP attached
I am hoping this was a fluke but I somehow doubt it given the history of events!
EDIT:
Additional notes are that late last night games and other 3D programs kept crashing to desktop very quickly. No error logs
I am hoping this was a fluke but I somehow doubt it given the history of events!
EDIT:
Additional notes are that late last night games and other 3D programs kept crashing to desktop very quickly. No error logs
- Joined
- Aug 28, 2007
- Messages
- 36,164
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffc000e28e7d80, 0, fffff8036996836f, 2}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+5f )
Followup: MachineOwneras this bsod keeps recurring you'll have to basically test everything although after rereading the thread I notice no memtest6 scan was ever run after it was suggested at the beginning'
Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link below you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
You must test for at least 12 hours unless it becomes obvious there is a problem straight away.
Memtest86+ - Advanced Memory Diagnostic Tool
Stress test the gpu using furmark:
FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
Monitor system temperatures and run for around an hour unless it bsod's of course.
As a SSD is being used is it fully updating firmware wise and is the controllers set to AHCI?
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #32
Unless memtest6 is different from memtest86, yes it was done;
We actually used furmark initially when my friend's computer was first built to find out the first GPU was DOA. We couldn't even start the test without it crashing on my friend's computer, so we tested the GPU in 2 known good computers of mine. The first GPU crashed less than 20 seconds in on both good computers. So we RMA'd it and the 2nd GPU(same model/make and same driver version at the time) ran flawlessly for 90ish minutes on both good computers.
I suppose we can try running it for an hour in his computer. If it fails or BSODs maybe we'll get some more hints.
As the for the SSD: we updated the firmware before we assembled his computer because of the rumors and end user reviews warning that certain older firmware versions are known to randomly brick samsung 850 drives. I think he is in AHCI mode but I am not entirely sure. I'll have him check and get back with you.
- Joined
- Aug 28, 2007
- Messages
- 36,164
It's entirely up to you but it may help.
The other thing you could try is underclocking the gpu. Basically reduce the core and memory speed by a few MHz each time, if the bsod still occurs then drop the speed again. You may find you have to reduce the core and memory by around 100MHz but every card is different so you'll just have to see.
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #34
- Joined
- Aug 28, 2007
- Messages
- 36,164
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #36
Update: Furmark ran fine for an hour without any changes. It was running just as smoothly at the end as it did in the beginning. No more BSODs since the last DMP I posted. Occasionally some games will run fine for a few hours but then they abruptly start crashing to desktop with no logs. A quick restart of windows remedies this.
We'll see what the rest of the week holds.
We'll see what the rest of the week holds.
- Joined
- Aug 28, 2007
- Messages
- 36,164
Ok welI I hope that the coming week goes well and if any bsod's occur please post the dump files and we'll take a look..
Nubkakes
Member
- Joined
- Jul 25, 2016
- Messages
- 21
- Thread Author
- #38
Well I suppose it was too much to hope for a clear week! 3 more dumps attached.
The first one seems to indicate a DX file, the 2nd one occurred while he was playing World of Warcraft so I figured it might be related, but then Third one occurred when he got up and left his computer alone for a while and I am not seeing anything correlating the 3rd BSOD dmp to the first two.
I am starting to think it maybe the motherboard at this point.
The first one seems to indicate a DX file, the 2nd one occurred while he was playing World of Warcraft so I figured it might be related, but then Third one occurred when he got up and left his computer alone for a while and I am not seeing anything correlating the 3rd BSOD dmp to the first two.
I am starting to think it maybe the motherboard at this point.
- Joined
- Aug 28, 2007
- Messages
- 36,164
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6c80010ee58, 0, fffff8009e3298da, 2}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MmDeleteKernelStack+5a )
Followup: MachineOwnerI reread the whole thread to try and get a handle on this issue. The only result to come from all the testing is your Memtest86 result:
The Passmark web page has this to say regarding the above issue:
PassMark MemTest86 - Memory Diagnostic Tool - Troublingshooting Memory Errors
Do you have any RAM you could lend your friend? Just to see if the issue still occurs after changing the sticks over?
Similar threads
