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.

 

[nobspls]

I've had terrible experiences with quality control of ryzen motherboards. Doesn't matter if it is Asus, AsRock, Gigabyte, MSI, etc. Worked with 6 boards in the past 12 months, 3 of them failed in all sorts of terrible ways. I of them was DOA, another one would random BSOD after 3 months, and another one would random BSOD afte 6 months. Pain the butt, to swap out the motherboards, but it a good motherboard fixed all the BSOD issue. I re-installed, clean install, etc. Fooled me into thinking those fixed the problems a few times to prove that the self-delusion powers are strong as ever. But within a week the BSOD problems are back. 3 out of six boards are bad, all from different makes. 50% failure rate, real crappy quality control out there.

 

[stdragon]

I've had terrible experiences with quality control of ryzen motherboards. Doesn't matter if it is Asus, AsRock, Gigabyte, MSI, etc. Worked with 6 boards in the past 12 months, 3 of them failed in all sorts of terrible ways. I of them was DOA, another one would random BSOD after 3 months, and another one would random BSOD afte 6 months. Pain the butt, to swap out the motherboards, but it a good motherboard fixed all the BSOD issue. I re-installed, clean install, etc. Fooled me into thinking those fixed the problems a few times to prove that the self-delusion powers are strong as ever. But within a week the BSOD problems are back. 3 out of six boards are bad, all from different makes. 50% failure rate, real crappy quality control out there.

Very interesting! MB assembly is no different than that of Intel MB from a design and manufacturing process. I'm wondering if perhaps the real problem is the chipset dies themselves not undergoing proper QA/QC.

 

[thedude79]

Alright, so I decided to try swapping a hardware component to see if that would fix the issues I was having. I decided to swap the motherboard for one from the same brand. I then wiped the drives and re-installed windows. I needed to contact customer support to activate the windows again on the pc.

I Haven't had the chance to do any BSOD testing, but I thought i'd manually initiate a crash to see if the motherboard was the issue with my windows installation problems.

I've uploaded the kernel dump to a google drive. I'll post again once I do some more troubleshooting, and install the latest video drivers for the system to utilize.

here's a link to the drive with the kernel dump.
https://drive.google.com/file/d/18-wJ9i2YfrykIvjXdz0nHtolBFfqCpju/view?usp=sharing

Alright I did some more game playing and I got yet another bluescreen. I zipped the file and uploaded it here's a link.
https://drive.google.com/file/d/1oJVCDe1eESQftfxALWAArKJh8mTOMRLG/view?usp=sharing

Given that swapping the motherboard didn't fix the issue, I'm probably going to swap out the graphics card next...

 

[johnbl]

after your new install, the debugger still thinks the kernel has been modified.
some data is not being saved in the memory dump for some reason.
most of the windows files can not be checked to see if they are valid for some reason.
here is the build string:Built by: 17134.1.amd64fre.rs4_release.180410-1804

I would make a new install ISO maybe a current windows insider build directly from Microsoft.
it could also be some issue in how the memory dump is being made (the fact that info is not there)
the modified files, could be a pirate version of windows, or maybe a special version for a localized market? don't know why it would have been changed. just that the debugger can not check most of the files.



the first part is what your version has, the second part is what windows thinks the version should have:




: kd> !chkimg -lo 50 -db !nt88061db0=00000000000000e2
0: kd> !chkimg -lo 50 -db !nt
4 errors : !nt (fffff80086064789-fffff80086064791)
fffff80086064780 00 00 00 00 00 00 00 00 50 *d9 *da 85 00 f8 ff ff ........P.......
fffff80086064790 *a0 *d9 da 85 00 f8 ff ff f0 7f 45 00 00 00 00 00 ..........E.....
0: kd> u fffff80086064780
nt!msrpc_NULL_THUNK_DATA:
fffff800`86064780 0000 add byte ptr [rax],al
fffff800`86064782 0000 add byte ptr [rax],al
fffff800`86064784 0000 add byte ptr [rax],al
fffff800`86064786 0000 add byte ptr [rax],al
nt!_guard_check_icall_fptr:
fffff800`86064788 50 push rax
fffff800`86064789 d9da fstp1 st(2)
fffff800`8606478b 8500 test dword ptr [rax],eax
fffff800`8606478d f8 clc
0: kd> u fffff80086064790
nt!_guard_dispatch_icall_fptr:
fffff800`86064790 a0d9da8500f8fffff0 mov al,byte ptr [F0FFFFF80085DAD9h]
fffff800`86064799 7f45 jg nt!_IMPORT_DESCRIPTOR_PSHED+0xc (fffff800`860647e0)
fffff800`8606479b 0000 add byte ptr [rax],al
fffff800`8606479d 0000 add byte ptr [rax],al
fffff800`8606479f 0000 add byte ptr [rax],al
fffff800`860647a1 0000 add byte ptr [rax],al
fffff800`860647a3 00ba804500d8 add byte ptr [rdx-27FFBA80h],bh
fffff800`860647a9 7645 jbe nt!_IMPORT_DESCRIPTOR_BOOTVID+0x8 (fffff800`860647f0)

0: kd> !chkimg -f !nt
Warning: Any detected errors will be fixed to what we expect!
4 errors (fixed): !nt (fffff80086064789-fffff80086064791)
0: kd> u fffff80086064780
nt!msrpc_NULL_THUNK_DATA:
fffff800`86064780 0000 add byte ptr [rax],al
fffff800`86064782 0000 add byte ptr [rax],al
fffff800`86064784 0000 add byte ptr [rax],al
fffff800`86064786 0000 add byte ptr [rax],al
nt!_guard_check_icall_fptr:
fffff800`86064788 50 push rax
fffff800`86064789 8cd6 mov esi,ss
fffff800`8606478b 8500 test dword ptr [rax],eax
fffff800`8606478d f8 clc
0: kd> u fffff80086064790
nt!_guard_dispatch_icall_fptr:
fffff800`86064790 50 push rax
fffff800`86064791 16 ???
fffff800`86064792 da8500f8ffff fiadd dword ptr [rbp-800h]
nt!_IMPORT_DESCRIPTOR_ext-ms-win-ntos-werkernel-l1-1-0:
fffff800`86064798 f07f45 lock jg nt!_IMPORT_DESCRIPTOR_PSHED+0xc (fffff800`860647e0)
fffff800`8606479b 0000 add byte ptr [rax],al
fffff800`8606479d 0000 add byte ptr [rax],al
fffff800`8606479f 0000 add byte ptr [rax],al
fffff800`860647a1 0000 add byte ptr [rax],al

 

[stdragon]

most of the windows files can not be checked to see if they are valid for some reason.

Isn't that as a result from ASLR as dumped from RAM? If so, that's a security feature.

 

[johnbl]

it is not an Address space layout randomization problem, the actual code has been modified
since it was a guard function call that was modifed i was thinking it could be an exploit
using this method:
https://www.blackhat.com/docs/us-15/materials/us-15-Zhang-Bypass-Control-Flow-Guard-Comprehensively-wp.pdf

maybe put your code into the VGA Boot Driverr, then use the modifed the guard function to tranfer the control to the VGA Boot Driver to get it to run.


!chkimg -f !nt
command in the debugger takes the memory dump image and corrects the errors in the image
so you dump the code before as it exists in the memory dump, then do the fix and dump the code from the fixed image in the memory dump. Then look at the changes.



lock instruction prefix removed from the call to
platform-specific hardware error driver (PSHED)

other changes also
call to Windows Error Reporting Kernel Driver
has been removed.

most of the windows files can not be checked to see if they are valid for some reason.

Isn't that as a result from ASLR as dumped from RAM? If so, that's a security feature.

 

[thedude79]

it is not an Address space layout randomization problem, the actual code has been modified
since it was a guard function call that was modifed i was thinking it could be an exploit
using this method:
https://www.blackhat.com/docs/us-15/materials/us-15-Zhang-Bypass-Control-Flow-Guard-Comprehensively-wp.pdf

maybe put your code into the VGA Boot Driverr, then use the modifed the guard function to tranfer the control to the VGA Boot Driver to get it to run.


!chkimg -f !nt
command in the debugger takes the memory dump image and corrects the errors in the image
so you dump the code before as it exists in the memory dump, then do the fix and dump the code from the fixed image in the memory dump. Then look at the changes.



lock instruction prefix removed from the call to
platform-specific hardware error driver (PSHED)

other changes also
call to Windows Error Reporting Kernel Driver
has been removed.

most of the windows files can not be checked to see if they are valid for some reason.

Isn't that as a result from ASLR as dumped from RAM? If so, that's a security feature.

Hello,

Sorry, it took me so long to reply. I've swapped the gpu and I still get bluescreens. So you're saying i should make a new ISO file from windows and then perform another clean install file from windows?

 

[johnbl]

you might join the windows insider program, then download a more current build.
Make a new ISO, try running the default drivers and see how the system works.
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced
I run preview builds but sometimes i change to slow updates to delay getting some builds.

it is not an Address space layout randomization problem, the actual code has been modified
since it was a guard function call that was modifed i was thinking it could be an exploit
using this method:
https://www.blackhat.com/docs/us-15/materials/us-15-Zhang-Bypass-Control-Flow-Guard-Comprehensively-wp.pdf

maybe put your code into the VGA Boot Driverr, then use the modifed the guard function to tranfer the control to the VGA Boot Driver to get it to run.


!chkimg -f !nt
command in the debugger takes the memory dump image and corrects the errors in the image
so you dump the code before as it exists in the memory dump, then do the fix and dump the code from the fixed image in the memory dump. Then look at the changes.



lock instruction prefix removed from the call to
platform-specific hardware error driver (PSHED)

other changes also
call to Windows Error Reporting Kernel Driver
has been removed.

most of the windows files can not be checked to see if they are valid for some reason.

Isn't that as a result from ASLR as dumped from RAM? If so, that's a security feature.

Hello,

Sorry, it took me so long to reply. I've swapped the gpu and I still get bluescreens. So you're saying i should make a new ISO file from windows and then perform another clean install file from windows?

 

[jonathan1683]

Try reinstalling windows and do not update it. download some older nvidia drivers and see if it will run stable. I had issues with some of the windows updates where I couldn't use the most current vesion of windows. If that still doesnt work. What else is left? I would just sell the hardware on ebay and get an intel setup.