New PC build frequently BSODs

Toggle sidebar Toggle sidebar
P

Pyrulen

Commendable
Jun 24, 2016
4
0
1,510
New PC build frequently gets BSOD. Fresh build with new parts and Windows 10 clean install. Crashing after about 1 hour of gaming, then continues to crash within minutes after rebooting. GPU and CPU temps are within normal ranges, around 60 degrees C for both.

Hardware:
CPU Intel i5-6500 @ 3.20 GHz
GPU nVidia GTX 970
PSU EVGA 650 GQ
Mobo Asrock H170 Pro4
aftermarket cooling: Corsair Hydro series H75
RAM 8GB (2x4GB) G.Skill Ripjaws, DDR4 - 2133

The BSODs have several error messages including: CRITICAL_STRUCTURE_CORRUPTION. MEMORY_MANAGEMENT, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and IRQL_NOT_LESS_OR_EQUAL

Using BlueScreenView tends to highlight ntoskrnl.exe as red.

Never really used EventViewer before, but if you guys can tell me what I need to upload to give more info I'd be more than happy to.

-------------------
Edit:
Here's what BlueScreenView gives me for the most recent crash:

Dump File: 062416-3796-01.dmp
Crash time: 6/24/2016 11:54:18 AM
Bug Check String: MEMORY_MANAGEMENT
Bug Check Code: 0x0000001a
Parameter 1: 00000000`00041793
Parameter 2: fffff681`2a692e60
Parameter 3: 00000000`00000101
Parameter 4: 00000000`00000100
Caused by Driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+142780
Processor: x64
Crash Address: ntoskrnl.exe+142780


 
Solution
MeanMachine41
WinRing0_1_2_0 is a known problematic driver and is not a necessary part of windows and can be stopped.
Malware has been known to hide itself inside WinRing.
Run Malwarebyts and use the rootkit revealer just incase you have malware in the hierarchical area.
This is all the info I could find that is understandable: http://www.file.net/process/winring0.sys.html

The guys at the W10 Forum are good at analyzing mini dump files. They can be difficult to decipher but these guys seem to relish in it.
I myself have come to the end of being helpful. I really hope you sort this out and please let me know the outcome.
Sort by date Sort by votes
MeanMachine41

MeanMachine41

Judicious
May 8, 2014
5,195
336
33,390
The ntoskrnl.exe error is usually related to your DIMMs however the complete dump file would need to be analyzed to be 100% sure.
It may be your DIMM compatibility with the MB or poor Primary Timings in Bios.
Try first booting the system with just one DIMM in first slot and try changing them around incase one DIMM is failing.
If one is failing then RMA the full kit.
You can also check you DIMM kit using MemTest86+ from a USB stick. If you don't know how to do this then I can explain further.
Also check your drivers in Device Manager as they may require an update.
If you see any yellow triangles then this can be an issue.
 
Upvote 0 Downvote
P

Pyrulen

Commendable
Jun 24, 2016
4
0
1,510


I've ran Memtest 86 overnight and came back to no errors detected. I'm going to try using one stick, moving it from slot to slot and then trying with the other one.

There are no yellow triangles in device manager, but I'll be running Advanced Driver Updater just incase.

What is the best way to provide the full crash dump?

Edit:
Tried running single Ram sticks in each of the 4 slots on the mobo, and consistently get a BSOD between 1-2 games of Overwatch.
 
Upvote 0 Downvote
MeanMachine41

MeanMachine41

Judicious
May 8, 2014
5,195
336
33,390
Go here for instructions on how to have your mini dump analyzed.
http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html

Also please list the P/N of your DIMMs

Check the System Log in Event Viewer and see if you can identify any drivers or devices that may be the culprit.
If any driver is suspect disable the driver or check with the manufacturer for driver updates.

Check your OS files. Do an "SFC /Scannow" in an elevated command prompt without the quotation marks.
This will test the integrity of W10 OS files for any possible corruption and the system will try to fix them if any found.

Report the results. I'm running out of ideas.

 
Upvote 0 Downvote
P

Pyrulen

Commendable
Jun 24, 2016
4
0
1,510


Did the SFC scan, it found errors and repaired them successfully, but still the crash persists.

P/N of the DIMM: F4-2133C15D-8GRR

Looking in Event Viewer, I'm seeing a consistent warning or error leading up to the crashes, but I am seeing this error often:
The description for Event ID 56 from source Application Popup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ACPI
1

the message resource is present but the message is not found in the string/message table
----

Looking into it further, using BluescreenView's timestamps I notice that right before each crash, the last System information log is the following:

A service was installed in the system.

Service Name: WinRing0_1_2_0
Service File Name: C:\Program Files (x86)\EVGA\PrecisionX 16\WinRing0\WinRing0x64.sys
Service Type: kernel mode driver
Service Start Type: demand start
Service Account:


Used the link you posted to change the dump files to be written as Minidumps. Going to see if I can understand those after generating a few.
 
Upvote 0 Downvote
MeanMachine41

MeanMachine41

Judicious
May 8, 2014
5,195
336
33,390
WinRing0_1_2_0 is a known problematic driver and is not a necessary part of windows and can be stopped.
Malware has been known to hide itself inside WinRing.
Run Malwarebyts and use the rootkit revealer just incase you have malware in the hierarchical area.
This is all the info I could find that is understandable: http://www.file.net/process/winring0.sys.html

The guys at the W10 Forum are good at analyzing mini dump files. They can be difficult to decipher but these guys seem to relish in it.
I myself have come to the end of being helpful. I really hope you sort this out and please let me know the outcome.
 
Upvote 0 Downvote
Solution
P

Pyrulen

Commendable
Jun 24, 2016
4
0
1,510


So after crashing upon switching the settings to generate minidumps, the Windows ran updates that were waiting to install. After the updates, infinite crashing on boot. Had to format and start over at a fresh Windows 10 install.

Going to try again only using windows updates, and gpu driver, see if it's a software issue. If it crashes at this point, it's most likely hardware, so I'll need advice on how to isolate which piece is malfunctioning.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom