New PC build has lots of BSOD's

[thedude79]

Hello, I recently built a new gaming rig and i'm having a lot of trouble with system stability. The system seems to run fine for normal web browsing activities, but once i start gaming on it, there's a chance for some random bluescreen error to pop up.

OS Name Microsoft Windows 10 Home
Version 10.0.17134 Build 17134
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-G3M0DMS
System Type x64-based PC
System SKU SKU
Processor AMD Ryzen 7 2700X Eight-Core Processor, 3700 Mhz, 8 Core(s), 16 Logical
BIOS Version/Date American Megatrends Inc. 0804, 2018-07-09
SMBIOS Version 3.1
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
It's running a Crosshair hero VII (wi-fi)
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.17134.285"
User Name DESKTOP-G3M0DMS\Michael
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 15.9 GB
Available Physical Memory 11.2 GB
Total Virtual Memory 18.3 GB
Available Virtual Memory 10.9 GB
Page File Space 2.38 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

I'm running an xc 2080 from EVGA, it's not overclocked or anything.
i've got 16gb of g skill ripjaws ddr4 it's supposed to clock to 3200mhz but i found the system is a bit more stable with 2933mhz, though this could just be my own bias.
All of the parts are brand new and not used. The system has a 500gb samsung evo 860 for it's boot drive and a 1tb samsuing 860 evo for it's second hard drive for game storage.

The computer has been throwing blue screen errors at me pretty much from day one, i've tried clean installing the nvidia drivers, running the default bios settings, flashing the bios. Generally speaking the BSOD's come when i'm gaming, ARK really seems to blue screen a lot but the witcher 3 and skyrim SE have also had bluescreen happen during gaming. I'm at my witts end with how to repair this pc.

Another thing the system does is randomly shut off. This usually seems to happen when i'm stress testing it or gaming, the system will just power off completely, and the only way to get the power button to function again is to flip the power supply's switch on and then off. I'm not sure whether or not the motherboard or some component is causing the issue. All of the fans the system has seem to be running smoothly and the 850 watt power supply is more than enough considering the fact i'm not overclocking the cpu or graphics card.


so the first system failure had the following information
Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: ab
Parameter 1: 2
Parameter 2: 2e0
Parameter 3: 0
Parameter 4: 17
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

followed by this bluescreen
Problem signature
Problem Event Name: BlueScreen
Code: 4e
Parameter 1: 99
Parameter 2: 3ade7b
Parameter 3: 2
Parameter 4: a0003a0003ade7a
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

following this it had another couple of bluescreens
Problem signature
Problem Event Name: BlueScreen
Code: 19
Parameter 1: 20
Parameter 2: ffffc58c9c2f5000
Parameter 3: ffffc58c9c2f5730
Parameter 4: 5730100
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0x19_20_nt!EtwpEnumerateAddressSpace

and then this blue screen
Problem signature
Problem Event Name: BlueScreen
Code: c2
Parameter 1: 7
Parameter 2: 666e6477
Parameter 3: 4050004
Parameter 4: ffffcc0371dfd160
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0xc2_7_wdnf_nvlddmkm!CMemoryAllocator::freeMemoryWithTag

which was then followed by this blue screen
Problem signature
Problem Event Name: BlueScreen
Code: 119
Parameter 1: 10000
Parameter 2: ffff958aef468000
Parameter 3: ffff958af41c3ac0
Parameter 4: 0
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0x119_10000_UNKNOWN_dxgmms2!VidSchiSetFlipDevice

then after another couple of days i got this blue screen
Problem signature
Problem Event Name: BlueScreen
Code: c2
Parameter 1: 4
Parameter 2: 51bb36a3
Parameter 3: 681a4d27
Parameter 4: ffffb206fdac53b8
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0xc2_4_dxgmms2!operator_delete

followed by this one
Problem signature
Problem Event Name: BlueScreen
Code: 19
Parameter 1: 20
Parameter 2: ffffbd043faa6e20
Parameter 3: ffffbd043faa6e90
Parameter 4: 407042b
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0x19_20_nt!MiRemoveSecureEntry

followed by
Problem signature
Problem Event Name: BlueScreen
Code: c2
Parameter 1: 7
Parameter 2: 4d52564e
Parameter 3: 4050004
Parameter 4: ffff8506af875730
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0xc2_7_NVRM_nvlddmkm!CMemoryAllocator::freeMemoryWithTag

this was then followed by
Problem signature
Problem Event Name: BlueScreen
Code: 139
Parameter 1: 1d
Parameter 2: ffff8c07d19870d0
Parameter 3: ffff8c07d1987028
Parameter 4: 0
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0x139_1d_INVALID_BALANCED_TREE_nt!RtlAvlRemoveNode

this issue was then followed by
Problem signature
Problem Event Name: BlueScreen
Code: c2
Parameter 1: 7
Parameter 2: 4d52564e
Parameter 3: 50005
Parameter 4: ffffd38363745e30
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: CORRUPT_MODULELIST_0xc2_7

another bluescreen followed
Problem signature
Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000005
Parameter 2: fffff803b08224d8
Parameter 3: ffff9b8f58b7fab0
Parameter 4: 0
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0x3B_nt!MiRemoveSharedCommitNode

with this one following
Problem signature
Problem Event Name: BlueScreen
Code: c2
Parameter 1: 4
Parameter 2: ffffac05
Parameter 3: a8b50280
Parameter 4: ffffac05a78859c0
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 4105

Extra information about the problem
Bucket ID: 0xc2_4_nvlddmkm!CMemoryAllocator::freeMemoryWithTag

Today the computer didn't bluescreen but it shut down randomly and required me to flip the power button switch to turn it on. I don't really know what to make of these blue screens as multiple components are pointed at. I was wondering if the GPU's vram could be at fault for the errors because i ran a prime 95 memory and cpu test for about 20 hours consecutively and the system didn't bluescreen or freeze at all during that time period. Let me know if i can provide any other information, i'll be watching this thread fairly frequently, and i'd appreciate any help i could get with the issues. Thank you in advance.

 

[thedude79]

FYI, if you've got a UPS, disconnect the PSU from it and instead plug directly to the wall. Some high efficient PSUs really hate synthetic sine wave generation that most consumer UPS put out. True sine wave is the way to go

I don't have it plugged into a UPS, would running a benchmark like heaven be something that consumes a lot of power?

 

[stdragon]

Yes, benchmarking, game playing, stress testing (like Prime95) will pull lots of current from the PSU. Ideally if you can, run Prime95 at the same time as FurMark to put maximum load in both CPU and GPU

 

[thedude79]

Yes, benchmarking, game playing, stress testing (like Prime95) will pull lots of current from the PSU. Ideally if you can, run Prime95 at the same time as FurMark to put maximum load in both CPU and GPU

Alright, i'm running prime95 and furmark at the same time, is there a way to get furmark to run its test on loop without needing to restart it manually?

 

[stdragon]

http://www.tomshardware.com/answers/id-3440780/software-good-stress-testing-constant-loop.html

 

[thedude79]

http://www.tomshardware.com/answers/id-3440780/software-good-stress-testing-constant-loop.html

So, interesting update, I was running prime95 and furmark, for a few hours consistently no issues, but then i decided i was going to go to sleep so i wanted to max my fan speeds to make sure my system didn't overheat, and when i cranked the cpu fancurve to 100% the system shut itself down automatically. I'm thinking that this means the issue is most likely caused by the motherboard then? I was using asus' aisuite to tune the fan curves.

The cpu fain is a corsair h100i pro, i'm not sure hot to categorize it in the program because the fan and pump are both plugged into the cpu fan slot, via a 3 pin connector. Nonetheless playing with the fan curves seemed to shut off the computer. I'm going to run more tests tonight with furmark and prime95 but i'm thinking it's probably a faulty motherboard.

I know furmark only got the gpu up to 77 degrees max, i'm not 100% sure what the cpu got up to, but i haven't really seen prime 95 or a anything get it past 80 degrees.

 

[thedude79]

So, I left the tests running overnight, and it seems like both furmark and prime95 stopped around 3:30 so 1.5 hours after i started them with the fans running at full tilt, and it powered off in the way that required me to flip the power bars switch to power off the motherboard, completely, before turning it back on in order to get the computer to turn on again. I'm still not sure which component is to blame.

 

[stdragon]

It's either your graphics card, PSU, or MB.

At this point it's process of elimination. If you have a way of borrowing a spare PSU or another card of similar wattage (can be a few generation back, doesn't matter, you just want to replicate the current load).

 

[thedude79]

It's either your graphics card, PSU, or MB.

At this point it's process of elimination. If you have a way of borrowing a spare PSU or another card of similar wattage (can be a few generation back, doesn't matter, you just want to replicate the current load).

So in the event I can't really borrow components or test out other similar parts. What's the best course of action should i swap components that are on warranty/ still eligible for return?

 

[stdragon]

If you must reach out to a vendor first given your limited options at this point, call ASUS. Hear what they have to say as this could be a known issue with their MB.

 

[thedude79]

If you must reach out to a vendor first given your limited options at this point, call ASUS. Hear what they have to say as this could be a known issue with their MB.

Hey so I've got an update, the system bluescreened again, and the bios keeps on freezing on me now when I try to boot it again, would this indicate that it is a motherboard problem for sure? It only seems to freeze if i leave the input (corsair k95) keyboard alone for a little bit. then it won't respond to either the keyboard or mouse. If i'm fast though, i can get it to boot to windows.

 

[thedude79]

Also, I have one of the minidump files from the most recent BSOD.

here's a link to the file itself
https://drive.google.com/file/d/1W5VNIdYGnnL_7mhjfaZoVMpT5WVpTsHY/view?usp=sharing

 

[johnbl]

bugcheck was in the gpu driver, It freed the same memory location twice.
this could be a timing related but so you would want to remove the asus gpu tweak utility,
I would fix the various old drivers and questionable drivers since they can change the timing of gpu streaming
you will also need to check the bios date of your installed bios. basically if it has been update past april of 2012 you could not run the old usb driver. Windows 10 will have various issues with mixing old bios, old usb driver with the new generic drivers that it provides. these hook driver are not allowed now and will cause a issues.
(assuming you even want the driver and it is not part of some malware)

I was unable to read bios info (means the the windows interface does not match, likely a old bios version)

normally, this bugcheck would just be a bug in the gpu driver, but you can not tell since you have a gpu tweak driver installed. you would update the gpu driver and gpu sound support driver.

to actually debug this problem I would need a kernel memory dump.
(i would do a malwarebytes scan to make sure you don't have malware running on your GPU card)
some unnamed driver was calling into the gpu driver. (maybe it was the asus tweak driver, not sure)



strange that you windows antilmalware driver seems to be running out of the wrong directory:
\SystemRoot\system32\drivers\wd\WdFilter.sys Tue Jan 3 05:38:17 1995 (2F095349)

unexpected driver:
NetFilter SDK TDI Hook Driver
\SystemRoot\system32\drivers\netfilter2.sys Sat Sep 17 17:52:38 2016
driver update: http://netfiltersdk.com/download.html

unexpected driver:
FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package
\SystemRoot\System32\drivers\FNETURPX.SYS Wed May 30 20:00:47 2012

outdated network driver:
Intel Pro/1000 Network Adapter driver
\SystemRoot\system32\DRIVERS\e1r65x64.sys Sat Jul 30 00:56:48 2016
https://downloadcenter.intel.com/

old driver:
ASUS hardware monitoring software related
(you should update from the motherboard vendors utilities)
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 2 19:47:59 2010
overclock driver

asus gpu tweak utility ( i would remove since the bugcheck is in the GPU code)
\C:\WINDOWS\system32\drivers\IOMap64.sys Fri Apr 28 03:02:15 2017

Also, I have one of the minidump files from the most recent BSOD.

here's a link to the file itself
https://drive.google.com/file/d/1W5VNIdYGnnL_7mhjfaZoVMpT5WVpTsHY/view?usp=sharing

 

[thedude79]

bugcheck was in the gpu driver, It freed the same memory location twice.
this could be a timing related but so you would want to remove the asus gpu tweak utility,
I would fix the various old drivers and questionable drivers since they can change the timing of gpu streaming
you will also need to check the bios date of your installed bios. basically if it has been update past april of 2012 you could not run the old usb driver. Windows 10 will have various issues with mixing old bios, old usb driver with the new generic drivers that it provides. these hook driver are not allowed now and will cause a issues.
(assuming you even want the driver and it is not part of some malware)

I was unable to read bios info (means the the windows interface does not match, likely a old bios version)

normally, this bugcheck would just be a bug in the gpu driver, but you can not tell since you have a gpu tweak driver installed. you would update the gpu driver and gpu sound support driver.

to actually debug this problem I would need a kernel memory dump.
(i would do a malwarebytes scan to make sure you don't have malware running on your GPU card)
some unnamed driver was calling into the gpu driver. (maybe it was the asus tweak driver, not sure)



strange that you windows antilmalware driver seems to be running out of the wrong directory:
\SystemRoot\system32\drivers\wd\WdFilter.sys Tue Jan 3 05:38:17 1995 (2F095349)

unexpected driver:
NetFilter SDK TDI Hook Driver
\SystemRoot\system32\drivers\netfilter2.sys Sat Sep 17 17:52:38 2016
driver update: http://netfiltersdk.com/download.html

unexpected driver:
FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package
\SystemRoot\System32\drivers\FNETURPX.SYS Wed May 30 20:00:47 2012

outdated network driver:
Intel Pro/1000 Network Adapter driver
\SystemRoot\system32\DRIVERS\e1r65x64.sys Sat Jul 30 00:56:48 2016
https://downloadcenter.intel.com/

old driver:
ASUS hardware monitoring software related
(you should update from the motherboard vendors utilities)
\SystemRoot\SysWow64\drivers\AsUpIO.sys Mon Aug 2 19:47:59 2010
overclock driver

asus gpu tweak utility ( i would remove since the bugcheck is in the GPU code)
\C:\WINDOWS\system32\drivers\IOMap64.sys Fri Apr 28 03:02:15 2017

Also, I have one of the minidump files from the most recent BSOD.

here's a link to the file itself
https://drive.google.com/file/d/1W5VNIdYGnnL_7mhjfaZoVMpT5WVpTsHY/view?usp=sharing

Okay, I'll get on changing these issues, do you think just doing a clean install of windows would be more effective? Also it bluescreened on my again. Here's a link to another drive with minidump files.

I changed the system specs so it'll give full dumps. I'll upload one of these files once I get my next bluescreen.

I was doing some digging in my windows drive, and i found some watchdog .dmp files that look like they might correspond with all of the other BSOD's i've been having. I'm currently uploading them to a google drive in a folder, one of the dumps is just shy of 900mb, i'm not sure if this is how big of a dmp file you're looking for but i hope it helps. Also thank you so much for all of the help.


https://drive.google.com/file/d/104E3HN-Q6PSy_EX8H4VVVwbdrrv8RbTj/view?usp=sharing

 

[stdragon]

Definitely try a clean install on another drive and test. You can format/install on another, but you risk loss of data if you haven't properly backed it up; be it individual files or a disk image. Either way up to you.

 

[thedude79]

Here's a link to the google drive folder with all of the .dmp files on the system i could find

https://drive.google.com/drive/folders/1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN?usp=sharing

 

[johnbl]

UcmCxUcsiNvppc.sys Mon Sep 10 14:52:15 2018
I would check for a update for this driver.
guess it is NVIDIA USB Type-C Port Policy Controller

or see if you can disable it. It would explain your problems if it had a bug.
also check nvidia firmware update tool


-------------

you have a bunch of live kernel memory dumps, most likely from the windows live automated debugging trying to report why your system is messed up. (windows error reporting)

the first one is from the usb 3 subsystem
basically the usb 3 controller indicated it completed a transfer but driver did not know what was transferred.
so it would be a bug. either it processed the same packet twice or processed some other drivers request. (means the other driver will get a timeout)
I it does not have the dump info to see what you have connected to your usb 3. ports. you have the generic Microsoft usb 3 drivers. these drivers assume your bios is dated after about april of 2013.
I could not read your bios date so you should check and update your bios if you can. Otherwise, you need to use the USB 3 drivers that are on the motherboard vendors website.

you could also take off the device from the usb 3. port and put it on the usb 2 port. (if you can figure out what device it is)
you can use this tool to look at the ports and see what is connected:
https://www.uwe-sieber.de/usbtreeview_e.html

if you provide a kernel dump it will contain the USB subsystem info and internal error logs. if your bios is old then the error logs will not be decoded by the debugger.


you also have a lot of window live debug sessions trying to figure out why you video stopped responding driver had a pooltag of 202b

I would need a kernel memory dump to figure anything out about this problem.
you could also search for the pool tag, but it is likely to just be the nvidia driver.

Here's a link to the google drive folder with all of the .dmp files on the system i could find

https://drive.google.com/drive/folders/1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN?usp=sharing

 

[thedude79]

UcmCxUcsiNvppc.sys Mon Sep 10 14:52:15 2018
I would check for a update for this driver.
guess it is NVIDIA USB Type-C Port Policy Controller

or see if you can disable it. It would explain your problems if it had a bug.
also check nvidia firmware update tool


-------------

you have a bunch of live kernel memory dumps, most likely from the windows live automated debugging trying to report why your system is messed up. (windows error reporting)

the first one is from the usb 3 subsystem
basically the usb 3 controller indicated it completed a transfer but driver did not know what was transferred.
so it would be a bug. either it processed the same packet twice or processed some other drivers request. (means the other driver will get a timeout)
I it does not have the dump info to see what you have connected to your usb 3. ports. you have the generic Microsoft usb 3 drivers. these drivers assume your bios is dated after about april of 2013.
I could not read your bios date so you should check and update your bios if you can. Otherwise, you need to use the USB 3 drivers that are on the motherboard vendors website.

you could also take off the device from the usb 3. port and put it on the usb 2 port. (if you can figure out what device it is)
you can use this tool to look at the ports and see what is connected:
https://www.uwe-sieber.de/usbtreeview_e.html

if you provide a kernel dump it will contain the USB subsystem info and internal error logs. if your bios is old then the error logs will not be decoded by the debugger.


you also have a lot of window live debug sessions trying to figure out why you video stopped responding driver had a pooltag of 202b

I would need a kernel memory dump to figure anything out about this problem.
you could also search for the pool tag, but it is likely to just be the nvidia driver.

Here's a link to the google drive folder with all of the .dmp files on the system i could find

https://drive.google.com/drive/folders/1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN?usp=sharing

Hey, I don't actually have anything plugged into the usb c port on the graphics card, could this still be the issue?

Interesting, i've got a corsair k95, and scimtar plugged in along with the adapter for my lg monitor, a 2 tb WD portable hard drive and an adapter for xbox 360 controllers plugged in would any of these devices cause that type of an issue?

Also, where do i find kernel dumps? I tried searching in the windows folder for a .dmp file and I don't think it turned up any other files, is there a way to access these?

 

[johnbl]

maybe there is a way to disable the port in windows device manager.
if the controller responds to a packet that it should not, then the device that should get it will not.

google how to set windows to make a kernel memory dump. it is a setting and the default file is different.
it is saved as c:\windows\memory.dmp

UcmCxUcsiNvppc.sys Mon Sep 10 14:52:15 2018
I would check for a update for this driver.
guess it is NVIDIA USB Type-C Port Policy Controller

or see if you can disable it. It would explain your problems if it had a bug.
also check nvidia firmware update tool


-------------

you have a bunch of live kernel memory dumps, most likely from the windows live automated debugging trying to report why your system is messed up. (windows error reporting)

the first one is from the usb 3 subsystem
basically the usb 3 controller indicated it completed a transfer but driver did not know what was transferred.
so it would be a bug. either it processed the same packet twice or processed some other drivers request. (means the other driver will get a timeout)
I it does not have the dump info to see what you have connected to your usb 3. ports. you have the generic Microsoft usb 3 drivers. these drivers assume your bios is dated after about april of 2013.
I could not read your bios date so you should check and update your bios if you can. Otherwise, you need to use the USB 3 drivers that are on the motherboard vendors website.

you could also take off the device from the usb 3. port and put it on the usb 2 port. (if you can figure out what device it is)
you can use this tool to look at the ports and see what is connected:
https://www.uwe-sieber.de/usbtreeview_e.html

if you provide a kernel dump it will contain the USB subsystem info and internal error logs. if your bios is old then the error logs will not be decoded by the debugger.


you also have a lot of window live debug sessions trying to figure out why you video stopped responding driver had a pooltag of 202b

I would need a kernel memory dump to figure anything out about this problem.
you could also search for the pool tag, but it is likely to just be the nvidia driver.

Here's a link to the google drive folder with all of the .dmp files on the system i could find

https://drive.google.com/drive/folders/1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN?usp=sharing

Hey, I don't actually have anything plugged into the usb c port on the graphics card, could this still be the issue?

Interesting, i've got a corsair k95, and scimtar plugged in along with the adapter for my lg monitor, a 2 tb WD portable hard drive and an adapter for xbox 360 controllers plugged in would any of these devices cause that type of an issue?

Also, where do i find kernel dumps? I tried searching in the windows folder for a .dmp file and I don't think it turned up any other files, is there a way to access these?

 

[thedude79]

maybe there is a way to disable the port in windows device manager.
if the controller responds to a packet that it should not, then the device that should get it will not.

google how to set windows to make a kernel memory dump. it is a setting and the default file is different.
it is saved as c:\windows\memory.dmp

UcmCxUcsiNvppc.sys Mon Sep 10 14:52:15 2018
I would check for a update for this driver.
guess it is NVIDIA USB Type-C Port Policy Controller

or see if you can disable it. It would explain your problems if it had a bug.
also check nvidia firmware update tool


-------------

you have a bunch of live kernel memory dumps, most likely from the windows live automated debugging trying to report why your system is messed up. (windows error reporting)

the first one is from the usb 3 subsystem
basically the usb 3 controller indicated it completed a transfer but driver did not know what was transferred.
so it would be a bug. either it processed the same packet twice or processed some other drivers request. (means the other driver will get a timeout)
I it does not have the dump info to see what you have connected to your usb 3. ports. you have the generic Microsoft usb 3 drivers. these drivers assume your bios is dated after about april of 2013.
I could not read your bios date so you should check and update your bios if you can. Otherwise, you need to use the USB 3 drivers that are on the motherboard vendors website.

you could also take off the device from the usb 3. port and put it on the usb 2 port. (if you can figure out what device it is)
you can use this tool to look at the ports and see what is connected:
https://www.uwe-sieber.de/usbtreeview_e.html

if you provide a kernel dump it will contain the USB subsystem info and internal error logs. if your bios is old then the error logs will not be decoded by the debugger.


you also have a lot of window live debug sessions trying to figure out why you video stopped responding driver had a pooltag of 202b

I would need a kernel memory dump to figure anything out about this problem.
you could also search for the pool tag, but it is likely to just be the nvidia driver.

Here's a link to the google drive folder with all of the .dmp files on the system i could find

https://drive.google.com/drive/folders/1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN?usp=sharing

Hey, I don't actually have anything plugged into the usb c port on the graphics card, could this still be the issue?

Interesting, i've got a corsair k95, and scimtar plugged in along with the adapter for my lg monitor, a 2 tb WD portable hard drive and an adapter for xbox 360 controllers plugged in would any of these devices cause that type of an issue?

Also, where do i find kernel dumps? I tried searching in the windows folder for a .dmp file and I don't think it turned up any other files, is there a way to access these?

Hello,

I just got another bluescreen while the system was set to create kernel dumps. The bluescreen code is different than the usual code, but I hope this can point towards the solution.

Here's a link to the folder that i have the dump file in https://drive.google.com/open?id=1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN

 

[johnbl]

you might try to search the drivers to find the pooltag that was shown in the memory dump.
to do this you would start cmd.exe as an admin then run
findstr.exe /s /m /l 202b *.sys
if it finds the tag inside of a driver it will name the driver file name.
(it could be a bogus pooltag, some old drivers did not specify pooltags, they tend to corrupt data in memory because of this)
--------------
files not shared for public access. can not download them.

maybe there is a way to disable the port in windows device manager.
if the controller responds to a packet that it should not, then the device that should get it will not.

google how to set windows to make a kernel memory dump. it is a setting and the default file is different.
it is saved as c:\windows\memory.dmp

UcmCxUcsiNvppc.sys Mon Sep 10 14:52:15 2018
I would check for a update for this driver.
guess it is NVIDIA USB Type-C Port Policy Controller

or see if you can disable it. It would explain your problems if it had a bug.
also check nvidia firmware update tool


-------------

you have a bunch of live kernel memory dumps, most likely from the windows live automated debugging trying to report why your system is messed up. (windows error reporting)

the first one is from the usb 3 subsystem
basically the usb 3 controller indicated it completed a transfer but driver did not know what was transferred.
so it would be a bug. either it processed the same packet twice or processed some other drivers request. (means the other driver will get a timeout)
I it does not have the dump info to see what you have connected to your usb 3. ports. you have the generic Microsoft usb 3 drivers. these drivers assume your bios is dated after about april of 2013.
I could not read your bios date so you should check and update your bios if you can. Otherwise, you need to use the USB 3 drivers that are on the motherboard vendors website.

you could also take off the device from the usb 3. port and put it on the usb 2 port. (if you can figure out what device it is)
you can use this tool to look at the ports and see what is connected:
https://www.uwe-sieber.de/usbtreeview_e.html

if you provide a kernel dump it will contain the USB subsystem info and internal error logs. if your bios is old then the error logs will not be decoded by the debugger.


you also have a lot of window live debug sessions trying to figure out why you video stopped responding driver had a pooltag of 202b

I would need a kernel memory dump to figure anything out about this problem.
you could also search for the pool tag, but it is likely to just be the nvidia driver.

Here's a link to the google drive folder with all of the .dmp files on the system i could find

https://drive.google.com/drive/folders/1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN?usp=sharing

Hey, I don't actually have anything plugged into the usb c port on the graphics card, could this still be the issue?

Interesting, i've got a corsair k95, and scimtar plugged in along with the adapter for my lg monitor, a 2 tb WD portable hard drive and an adapter for xbox 360 controllers plugged in would any of these devices cause that type of an issue?

Also, where do i find kernel dumps? I tried searching in the windows folder for a .dmp file and I don't think it turned up any other files, is there a way to access these?

Hello,

I just got another bluescreen while the system was set to create kernel dumps. The bluescreen code is different than the usual code, but I hope this can point towards the solution.

Here's a link to the folder that i have the dump file in https://drive.google.com/open?id=1K6ECwakBZj8epp8k_QbdS2DSdwrsPGVN

 

[stdragon]

Are you sure you're chasing the right rabbit here? The problem might not be the OS as the cause, rather you're seeing the BSODs as symptomatic of a hardware based issue.

I mean, I freely admit I could be wrong. But rather then burn all that time and energy debugging dump files, at least rule out the problem via installing Windows 10 (trial) on another drive and booting from that. You can make all the changes you want and not worry about messing with what otherwise could be a perfectly fine OS with drivers installed.

When troubleshooting, you want to "divide and conquer". That is to say, you need to isolate the scope of the problem to where it is and isn't occurring. Only then can you have a workable path forward to resolving the issue; be it reinstalling the OS with new drivers, or replacing the MB.

 

[thedude79]

Are you sure you're chasing the right rabbit here? The problem might not be the OS as the cause, rather you're seeing the BSODs as symptomatic of a hardware based issue.

I mean, I freely admit I could be wrong. But rather then burn all that time and energy debugging dump files, at least rule out the problem via installing Windows 10 (trial) on another drive and booting from that. You can make all the changes you want and not worry about messing with what otherwise could be a perfectly fine OS with drivers installed.

When troubleshooting, you want to "divide and conquer". That is to say, you need to isolate the scope of the problem to where it is and isn't occurring. Only then can you have a workable path forward to resolving the issue; be it reinstalling the OS with new drivers, or replacing the MB.

I just did a clean windows install on the current disc. And i got yet another bluescreen. I read online that the Crosshair VII has compatability issues with corsair link and icue. After I removed my monitoring systems, and such it seems like i got stability or at least i'm not getting the random shut downs anymore. But I had yet another bluescreen today which windows is saying was because of a hardware issue.

Asus released a new bios for the motherboard so i'm going to flash the motherboard again to update the bios once more. The update was released on the second.

Here's a link to the dump file. I'll switch the system to recording kernel dumps, it seemed to be running smoothly, so I didn't do this yet. https://drive.google.com/open?id=1oRw6y8aZdKhxtrII7FP8SAINrbeOMKYZ

 

[johnbl]

- looks like a hacked windows build,
- window user kernel files look modified
- bios interface messed up
- windows defender updates not being completed

bugcheck 0x133 would require a kernel memory dump to debug

--------------------

Are you sure you're chasing the right rabbit here? The problem might not be the OS as the cause, rather you're seeing the BSODs as symptomatic of a hardware based issue.

I mean, I freely admit I could be wrong. But rather then burn all that time and energy debugging dump files, at least rule out the problem via installing Windows 10 (trial) on another drive and booting from that. You can make all the changes you want and not worry about messing with what otherwise could be a perfectly fine OS with drivers installed.

When troubleshooting, you want to "divide and conquer". That is to say, you need to isolate the scope of the problem to where it is and isn't occurring. Only then can you have a workable path forward to resolving the issue; be it reinstalling the OS with new drivers, or replacing the MB.

I just did a clean windows install on the current disc. And i got yet another bluescreen. I read online that the Crosshair VII has compatability issues with corsair link and icue. After I removed my monitoring systems, and such it seems like i got stability or at least i'm not getting the random shut downs anymore. But I had yet another bluescreen today which windows is saying was because of a hardware issue.

Asus released a new bios for the motherboard so i'm going to flash the motherboard again to update the bios once more. The update was released on the second.

Here's a link to the dump file. I'll switch the system to recording kernel dumps, it seemed to be running smoothly, so I didn't do this yet. https://drive.google.com/open?id=1oRw6y8aZdKhxtrII7FP8SAINrbeOMKYZ

 

[stdragon]

- looks like a hacked windows build,
- window user kernel files look modified
- bios interface messed up
- windows defender updates not being completed

bugcheck 0x133 would require a kernel memory dump to debug

@thedude79 - Is this true? Are you using a hacked build of Windows??

If so, than what johnbl said is most likely the culprit. Meaning, go and install a legitimate copy and test again. NEVER trust a hacked OS!!!

https://www.microsoft.com/en-us/software-download/windows10

 

[smorizio]

make sure the bios is updated on the mb. with amd and ryzen there been a lot of bug fixes.. your running an old version of windows 10. make a new windows iso from microsoft and install a clean windows 10 image and then install the newest amd chipset drivers for your mb from amd.