[SOLVED] BSOD in Win 10

Kanoa

Kanoa

Member
Joined
Feb 11, 2021
Posts
16
Hi
I have tried all in my knowledge (doesn't mean it is much though) and I have run out of ideas.Please help
Win 10 pro 20H2 OS build 19042.746 (64bit) installed month and a half ago
Old system build by myself years ago
Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz 4.40 GHz (long time overclocked, even from win 7 times, never gave me problems)
nVidia GTX 980 (untouched)
Asus P6X58E-d
Power suply came with the case a 1200w PSU pre-installed in an Antech P190
I tried driver veryfier but crashes my PC and have to revert to the previously set system restore point
 
Hi
I have tried all in my knowledge and run out of ideas (it doesn't mean I knwo much though), please help.
  • A brief description of your problem (but you can also include the steps you tried).It only happens when running Prepar3d (a simulator) I have check if anything in the simulator may be causing th eproblem but is a pretty clean installation and Progress monitor, its log files and event viewer do not indicate that is the simulator causing the problem. The sim though runs for a long while before it crashe the computer
  • System Manufacturer? My own build PC
  • Desktop
  • Windows 10 pro, 20H2 OS build 19042.746, 64bit
  • I installed it fresh a month and a half ago and with no problems
  • My system is old and started with win 7
  • CPU: Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz 4.40 GHz
  • RAM slots 1, 3, 5 Corsair CMX6GX3M3A2000C9
  • RAM slots 2, 4, 6 Corsair CMX6GX3M3B2000C9
  • Video Card: nVidia GTX 980
  • MotherBoard - Asus P6X58D-E
  • Power Supply - 1200w in 2600w preinstalled in a Antec P190 case
  • Driver verifier creashed the PC when I enabled it and had to use system restore
  • Security software windows 10 default, defender and firewall
  • Are you using proxy, vpn, ipfilters or similar software? No
  • I'm using virtual CloneDrive
  • Are you currently under/overclocking? Are there overclocking software installed on your system? The PC has been under overclocking since build (although I have upgrade processor and RAM. Is currently overclocked but I tried reducing it substantially (more than half) and also tried a bit more voltage, none of the actions avoid the patern of the problem.
I hope this helps

Cheers
 

Attachments

Merged threads.

When you are asked to follow the BSOD Posting Instructions, there is no need to create a new thread. :-)
 
Hi, understand, but it was just a mess... when I started drafting I tried to log in with Facebook; as it doesn't work, I tried to return to the post, but had gone (I have facebook in a browser container) and i didn't realized it was posted (I asumed that, because I failed logging in, it had just vanished). So sorry, it was unintentional. It was meant to have been like the second one from the beginning:-)
Cheers
 
Last edited:
No problem :-)

In the future, do consider checking that you haven't already posted something.
 
I thought that while I wait I could add a few more things that I tried:

  • Run sfc /scannow many times, on occassions it reported and fixed some corruption in particulaar, always, after a crash. More often than not, it comes clear. The file collection attached was done with the sfc not reporting issues.
  • I have also run the Windows 10 memory test, no problems reported.
  • Windows is fully up to date.
  • The computer runs nicely and smothly all the time, even when I run the simulator is really good, decent frames and smoth, during quite a bit of time.
  • The crash only happens with the simulator, or at least I only have seen it with it. There is jus an add-on related to the sim that crashes ramdomly (but does not cause BSOD). Apart from those two instances, al works fine, nice and smoth.
  • The antivirus installed does not report infections.
  • This level of overclocking has had good performance for some years now, so I would dare to call it stable. However, the latest versions of the sim are pretty demanding and I wonder if that could have an impact, although the fact that I have lowered setting did not make a difference.
  • The Wnidows 10 installation was first a legit update from my legit copy of win 7 pro. But as performance was not brilliant (just performance) I decided to install it fresh last December. Performance of course improved substantially overall. The BSOD with the sim have started a couple of week ago not being able to identify another event that coincide with it.
  • The only event that is close to that time and may, and with a lot of caution I say may, could be related to a warning in Device Manager related to the driver ATK0110 ACPI. I downloaded the one from the internet that I thought was compatible, the warning disapear, but I'm just not sure.

I hope this helps

K
 
Please remove any overclocking for troubleshooting purposes. All the dumps appear to indicate either an issue with your RAM or a buggy driver.

Kanoa said:
I have also run the Windows 10 memory test, no problems reported.
Click to expand...
Please run MemTest86 instead, it's far more reliable than the memory diagnostic test provided by Windows. The instructions are available here - Test RAM with PassMark MemTest86

Kanoa said:
Driver verifier creashed the PC when I enabled it and had to use system restore
Click to expand...
By crashed? Do you mean a BSOD?
 
By crashed? Do you mean a BSOD? Yes, in the process, driver verifier restarts the PC. Well, it never managed, a BSOD happens and only going straight back to a restore point allowed me to recover. Didn't tried again.

I'll follow the other two instructions in a bit and report back
 
Kanoa said:
Yes, in the process, driver verifier restarts the PC. Well, it never managed, a BSOD happens and only going straight back to a restore point allowed me to recover. Didn't tried again.
Click to expand...
I assume that it simply froze then and then couldn't progress any further?
 
x BlueRobot said:
I assume that it simply froze then and then couldn't progress any further?
Click to expand...
It simply shut down the pc to carry out the test and when was going to re-start, the BSOD came up saying there had been a violation and the PC needed repair. I made several attempst to restart but the BSOD persisted so I opted for loading the restore point I made just before running driver verifier.
 
Last edited:
It certainly seems that the issue lies with one of the drivers which loads at boot. Did you ensure that you excluded Microsoft drivers when you ran DV?
 
Just to let you know that I run Memtest with full overclocking (as I wanted to take this opportunity to check a bit on the OC stability) and it passed the test in about 40' with no errors. Unless you instruct me otherwise I will perform the test again, this time without OC (I will remove the OC now anyway, I just wanted to test with it as I haven't doen it in a while). I wanted you to know, as it is my understanding that, if the OC passes the test, it is safe to assume that it would have pass it without OC as well. But if you rather to perform it again (without the OC), happy to go ahead. I'll do this before the driver verifier.
 
It should pass without overclocking too. However, it should be noted, that MemTest86 runs a number of specific tests and actual programs can behave rather differently. I would run DV for now, especially if it found violations when you ran it beforehand. When it crashes again with DV, please ensure that you upload the dump files.
 
x BlueRobot said:
When it crashes again with DV, please ensure that you upload the dump files.
Click to expand...
Could you please assit with this? Last time, when I tried to look for the dump files, I couldn't find them. When you say to upload the dump files you mean to run Synative file collector again or a specific dump file?

Cheers
 
Kanoa said:
When you say to upload the dump files you mean to run Synative file collector again or a specific dump file?
Click to expand...
I would use the file collector tool again, it will gather all the dump files. Just for reference, they'll always be available in the following directory:

Code: 
%systemroot%\Minidump
 
I manged this time to go through the driver verifier, followed the isntructions and reboot. Nothing happened this time, I mean nothing at all, it just went through the normal windows start up process; is that the way it should? (note that I never managed to make it work before, so I don't know what to expect).
or now that I sort of "activate" DF, is there anything you want me to do or log to obtain and post?

Cheers
 
No, let DV run in the background. If it finds any issues, then it will produce a crash (BSOD) which is usually a Stop 0xC9 or Stop 0xC4. To ensure that DV is running correctly, you can always enter the following in Command Prompt:

Code: 
verifier /query

If it is running correctly, then you won't get a message stating that no drivers are being verified.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top