I see only 1 crash dump where Driver Verifier is enabled. But there the Ntfs.sys system driver was specified as the cause. Are you sure you set up Driver Verifier well (you did not select Microsoft drivers there)? From standard settings I would enable all
and these two additional options (Force pending I / O requests and IRP Logging) can be left enabled.
The random crashes are most likely indicative of a hardware problem.
Other possibilities are compatibility issues and low-level driver problems.
I suggested the test with the video card simply because I saw the nVidia driver in the crash dump (and you had a built in graphics card to test with).
You've ruled out the video card - as the crash occurs with or without the video card.
We presume that you've ruled out the memory - as you mentioned that it passed MemTest
I suspect that you've tested the hard drives (using only the SSD, and then using only the HDD). Is that correct?
I tend to dismiss any software issues (and most compatibility issues) as you stated you did a clean install of Windows on several occasions (with only the Windows Update drivers used at one point) and have updated the BIOS/UEFI.
So, now we can move on to other hardware tests (to help rule out other components)
Should this be a motherboard problem - it may take a while to figure this out.
As you have had the components over 8 months - you'll have to decide when to attempt a return/exchange of components.
More about motherboards at the end of this post........
FWIW - I had, at work, a system with a video problem. The sensor readings were normal.
When I reached inside the case to check connections (after unplugging it), I got a second degree burn from the video card.
Turns out that the sensor was malfunctioning!
The moral of the story is that diagnostics are merely software readings of hardware components - and, as such, they aren't necessarily 100% accurate.
The next steps/tests are:
1) Intel Processor Diagnostic Tool: Download Intel(R) Processor Diagnostic Tool
Disregard if not using an Intel processor
2 OCCT: OCBASE / OCCT
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall
If these hardware tests don't find anything, then you'll have to start troubleshooting by removing parts. Here's a page that describes this: Hardware Stripdown Troubleshooting
Although it's old, it's still relevant in these situations.
Good luck!
Now, about motherboards:
- there are no definitive motherboard diagnostics. The boards have a selling life of about 3 years - so it's not profitable to design a test that will be obsolete when the next series of motherboards come out. It's actually cheaper just to replace the board than to attempt to test it.
- diagnosing a motherboard problem on the forums here is a long process. We ask you to run the tests and also ask you to remove/replace other components to help rule things out. But in the end (if it is a motherboard problem) it usually comes down to the motherboard or CPU (and motherboard failures are much, much more common than CPU failures). Unfortunately, the CPU tests aren't always accurate either - so it.
- diagnosing a motherboard for return is "usually" much more simple. BUT, each reseller/manufacturer has their own process. Most often (again), they ask you to clean install Windows using recovery media or a clean download of Windows before they'll accept it as a return.
- our process here is much more thorough than the reseller/manufacturer because we're concerned with saving money and time. You'd be mighty upset if I told you to buy a new part and it wasn't needed (and, that's why I suggest purchasing from places that will give you your money back if the part isn't needed)
I used the exact settings for Verifier it showed in the link you had originally linked me, restarted, waited for it to crash then ran a log collector upon reboot.
- - - Updated - - -
How long should I run this test for ? I ran the Intel tool for the CPU 3 times and it passed every time. I was reading the OCBase site but I'm not clear on how long to leave it running. Do I just wait for an error to occur or should I stop it at a certain point?
Depends on how long you can pay attention to the system. I’d suggest an hour (minimum). Be sure to keep monitoring the system in case it gets stuck in an error condition. If you can’t stop the test, pull the power cord/press and hold the power button to shut it downto shut it down (
So I ran the default selected test (CPU:OCCT), its been going for a little over an hour now with no issues, going to leave it on til it hits the 2 hour mark, but assuming all goes well (I will update when its done) whats the next step in testing now that both of those tests were passed?
Also I'm no expert on any of this of course but some1 earlier in the thread said that they didn't believe it to be a motherboard issue because of the nature of the different errors I got. They said something about how one of the errors had to relation to the motherboard, but like I said I have no idea I just didn't know if that information would be useful.
Tested for 1 hr 45min here are the results:
Screenshot - d17f411b0ffd6583c869dd512e667968 - Gyazo
Last edited by Auztin; 24 Sep 2019 at 19:47.
When the testing has completed please place the computer in safe mode with Ethernet connection.
Report into the thread whether the computer is stable or unstable ( BSOD or unexpected shutdown / restart).
The longer the time in safe mode the better the testing period.
Overnight test RAM and return to safe mode with networking to test stability /instability.
These were the bugchecks:
3B
1E
139
7E
D1
EF
133
FC
7F
Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better the testing conditions.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 8 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
MemTest86+ - Test RAM
Unfortunately, I'm not able to hook up an ethernet cable because my modem is across the house currently. Of course I could buy a 100ft cable or something, or even try power line adapters, but would staying on wifi be an issue in safe mode? If so, could I just keep the computer offline while testing to see if it is stable in safe mode or is having an ethernet connection required?
Ethernet is not required.
Safe mode can be used with wireless.
The best testing is with safe mode only (no networking or command prompt).
Please change the earlier post for overnight RAM testing.
Run Memtest86 version 8.2 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.
MemTest86 - Official Site of the x86 Memory Testing Tool
Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)
Memtest86 has a feature to produce a text report.
Please post this in addition to the images.
From my previous post:
If these hardware tests don't find anything, then you'll have to start troubleshooting by removing parts. Here's a page that describes this: Hardware Stripdown Troubleshooting
Although it's old, it's still relevant in these situations.
Quote