[10ProV1709b16299 x64] Random system restarts - only when gaming, no minidump created

Dyonas

Member
Joined
Apr 12, 2018
Posts
18
Hi,

OK this is going to be long so please bear with me as I've asked for help on at least three other forums with no luck yet and I have a lot of information to include. The best tl;dr version I can offer is that my system restarts while playing some games, some of the time, from a few minutes to a few hours and leaves no evidence / minidump behind that it happened.

I bought a laptop in October 2017 from a Quanta rebadger (CyberPower PC UK) and from early on it crashed playing Fallout 4. I decided it was a Bethesda game being a Bethesda game or a mod. Unfotunately it kept happening but only with Fallout 4 so I linked it to mod issues. I totally reinstalled Fallout 4 and it behaved fine even with more mods than I originally had. Problem solved? No. While playing Subnautica one night I hadn't saved (painful) and the same crash issue meant a lot of lost progress. The screen showed the image frozen as the audio played fine for a few more seconds then became equally stuck before the laptop restarted itself.

I could go on but suffice to say that this has now happened on at least eight games I own to varying degrees even if some crash it more often. Each crash is the same as above and will start with the video locking before the audio gets stuck and loops then it restarts. Despite me checking every setting three or more times and making sure I even had a 21GB pagefile (16GB RAM in the machine) it *never* creates a dumpfile when these restarts happen. It's as if Windows is oblivious to it. I had to use WhoCrashed where I discovered something I didn't know about, Live Kernel Reports, to find a supposed cause. I also took the opportunity to force a crash with the program which did indeed create a minidump so something about the issue stops them being created. The only reason I'm sure this is a BSOD issue is that when I disabled BSOD restarts the system will instead just hang when the problem occurs until I manually power it down.

Things I've tried so far:
Reseating the RAM
Testing both RAM sticks, individually, in each RAM slot
Ran memTest 86 with no errors
Three separate drives (SSD, m.2 SSD, hybrid SATA HDD) with clean Windows installs, Steam, and one game only on them
Installed *only* Windows, Steam and one game that crashes it most often with no peripherals attached
Monitored temps carefully with GPU never going above 70C
At least three separate nVidia driver versions from the one Windows installs to the current one on nVidia's site
Probably other things that I'm forgetting now and will add later

To make this issue more problematic to troubleshoot I've used Oculus Rift with it for many hours and not yet had a single instance of this crash / restart issue. I can also run a stress test benchmark (FurMark) for hours without a single issue and I will add that it has only ever happened while gaming. Yet the moment I play one of these games I feel like I'm playing a game of Russian Roulette where it's only a matter of time before it restarts. It can't be heat related because as I mentioned it can happen literally as I land at the title screen which is less than four minutes or go for hours without an issue.

The games that it has crashed on so far are Fallout 4, Subnautica, Destiny 2, TERA, WWE 2K18, Deux Ex: Mankind Divided, Borderlands 2, and Deep Rock Galactic. These can play fine for minutes to hours at a time with no issue so I don't always see it with all these games but WWE 2K18 I can almost guarantee a crash within 5 minutes. Even that, though, can play for a few hours (rarely) without crashing. I'll also add that each time I've formatted and reinstalled Windows the games seem to run without issues until after a reboot. The last clean install I tried was Wednesday / yesterday and it was fine. I shut the system down because I had to go out but when I came back I checked and within 10 minutes it restarted. I've also made it crash again just now so I have a comparison Live Kernel dump.

I have been in contact with the retailer trying to find a cause but after three days of troubleshooting and doing things I still had nothing. Only when I sent the Live Kernel dumps did they collect the laptop to check it out. Unfortunately, after 2 1/2 weeks they found zero issues and in the return note it mentions they ran FurMark for 140 hours with no problem. If that's all they did then I can see why they found no issues even after I linked them to a video of the crash happening. The result of them finding no issue is that they can't send it to the manufacturer for repair as it will be returned to them as no fault found.

If you made it this far I will say thank you for that alone. If you can help me pinpoint the cause and give me something to hurl at the retailer to make them fix this issue I would be eternally grateful. I'm attaching all information requested in the BSOD posting as well as a GPU-Z image, CPU-Z file, and the two Live Kernel crash dumps.

All I want is a working laptop and right now all I have is an expensive paperweight. I can play these games on an older system with a GT740m without any issue although at a much lower detail and with varying degrees of slowdown. Please help me if you can.
 

Attachments

Re: Random system restarts - only when gaming, no minidump created

There's a newer driver/software installer available for your wifi adapter which can be found here. There is also an update for your Ethernet driver which can be found here (10.025). I don't see anything to suggest they are the problem but I'd recommend updating them anyway.

I've been unable to find a product support page for the computer. Do you know of one?
 
Re: Random system restarts - only when gaming, no minidump created

There's a newer driver/software installer available for your wifi adapter which can be found here. There is also an update for your Ethernet driver which can be found here (10.025). I don't see anything to suggest they are the problem but I'd recommend updating them anyway.

I've been unable to find a product support page for the computer. Do you know of one?

The laptop is no longer listed on the supplier's (CyberPower PC UK) website but this is almost identical in terms of specifications. The only differences are in terms of storage and GPU where my system has a GTX1070 8GB.

Customise Vector II 15 VR 400 Gaming Laptop Gaming PC

Are you looking for something specific? If so I might be able to provide it.
 
Re: Random system restarts - only when gaming, no minidump created

I wanted to check to see if it was running the latest motherboard BIOS. The information in the msinfo32 output shows:

BIOS Version/Date INVALID QP113, 22/02/2017

which is both kind of old and looks a little strange as far as the INVALID text. Are you using the wifi or the Ethernet while gaming? I'm not sure if you already have but if not, please try making the changes on this page, rebooting, and then using the settings that made your system hang rather than reboot. When it hangs again see if you can generate a manual crash dump by holding the right CTRL key and then tapping ScrLck twice (assuming the laptop has a ScrLck key). Hopefully that will generate a manual crash dump and we might be able to see what's going on if it's a complete, automatic, or active dump.
 
Re: Random system restarts - only when gaming, no minidump created

It doesn't have a Scroll Lock key so while I wait for you to confirm I'm going to attach a USB keyboard and see if that will be enough. From the article you linked it wants me to create a new DWORD I assume with a value of 1.

I've looked around and can only find a few bits of information on it.

Quanta NL5A
- Geekbench Browser


Is the same system and shows the same information. I don't have much faith in the support at CyberPower but they did say it was the latest BIOS available. I remember thinking it's very, very limited when I first looked at it. The only real options available are to alter boot device & order, switch between Legacy and UEFI mode and a few others like Virtualisation. There isn't even an option to enable or disable the i7's integrated GPU but I don't know if that's normal or not.
 
Re: Random system restarts - only when gaming, no minidump created

Well I just got one but it's 870MB. I'm trying to get a Kernel one now. I have it zipped to 132MB and can host it unless there's another option.
 
Re: Random system restarts - only when gaming, no minidump created

Using the method mentioned I got a dumpfile for automatic and kernel assuming it worked but even compressed they're totalling around 260MB. I had to be quite quick triggering it as soon as I saw the video freeze. If I waited longer then no dumpfile was created.

I've uploaded the two dumpfiles after zipping them together. Available at this link.
 
Re: Random system restarts - only when gaming, no minidump created

I will have a look and at the dumps and let you know whether or not I find anything helpful. It's a late here but I should have time tomorrow.
 
Re: Random system restarts - only when gaming, no minidump created

tsddd.dll in my system has got creation date 29 Sep 2017, while in yours is 24 May 2013.
Maybe sfc /scannow could correct it...

From my system: description Framebuffer Display Driver, size 15.0kB (15 360 byte), version 10.0.16299.15, previous name framebuf.dll.
 
Last edited:
Re: Random system restarts - only when gaming, no minidump created

Using the method mentioned I got a dumpfile for automatic and kernel assuming it worked but even compressed they're totalling around 260MB. I had to be quite quick triggering it as soon as I saw the video freeze. If I waited longer then no dumpfile was created.

I've uploaded the two dumpfiles after zipping them together. Available at this link.

The dump files only show 1 core doing any interesting work, it's the core running the game, and it seems to just be shutting down the game. The other cores are idle or processing the crash dump so I don't think we're capturing the system while it's actually frozen. You did uncheck the Automatically restart option in Startup and Recovery, correct? If so, it gets to a point where the system is so frozen it won't respond to the manual crash key combination?

This won't necessarily work but on many laptops the built-in keyboard is actually a PS/2 keyboard. If you can get manual dump file generation working using the built-in keyboard you have a much better chance of capturing the dump file when the system is frozen. PS/2 keyboards have an interrupt level that takes precedence over almost anything. However, since your keyboard doesn't have a ScrLck key you'd need to use the alternative instructions at the bottom of the page I linked to remap a different key (the Home key for example). The instructions are a bit cryptic but is it something you can try?
 
Re: Random system restarts - only when gaming, no minidump created

tsddd.dll in my system has got creation date 29 Sep 2017, while in yours is 24 May 2013.
Maybe sfc /scannow could correct it...

From my system: description Framebuffer Display Driver, size 15.0kB (15 360 byte), version 10.0.16299.15, previous name framebuf.dll.

I will take a look at that. Perhaps keep in mind this is a basic install system so things like that may just be normal for how it is currently but I appreciate you pointing it out regardless.
 
Re: Random system restarts - only when gaming, no minidump created

The dump files only show 1 core doing any interesting work, it's the core running the game, and it seems to just be shutting down the game. The other cores are idle or processing the crash dump so I don't think we're capturing the system while it's actually frozen. You did uncheck the Automatically restart option in Startup and Recovery, correct? If so, it gets to a point where the system is so frozen it won't respond to the manual crash key combination?

This won't necessarily work but on many laptops the built-in keyboard is actually a PS/2 keyboard. If you can get manual dump file generation working using the built-in keyboard you have a much better chance of capturing the dump file when the system is frozen. PS/2 keyboards have an interrupt level that takes precedence over almost anything. However, since your keyboard doesn't have a ScrLck key you'd need to use the alternative instructions at the bottom of the page I linked to remap a different key (the Home key for example). The instructions are a bit cryptic but is it something you can try?

Yes I unchecked automatic restart but I also found that while using the USB keyboard if I waited too long after the first sign (video freezing) then it gave no dumpfile. I will look at changing the key combination, I didn't get much chance to look at that as it was a painful day overall trying to find something I can use to throw at the retailer and say "LOOK AT THIS AND THEN ACCEPT YOUR FAULT" or, as much as I doubt it's a problem of my doing, hold my hand up and then fix what is wrong.

This video shows what happens and sometimes the audio plays for longer than other times before the inevitable loop. It should be at the right time but if not it's just after 3m 47s.
YouTube
 
Re: Random system restarts - only when gaming, no minidump created

tsddd.dll in my system has got creation date 29 Sep 2017, while in yours is 24 May 2013.
Maybe sfc /scannow could correct it...

From my system: description Framebuffer Display Driver, size 15.0kB (15 360 byte), version 10.0.16299.15, previous name framebuf.dll.

Searched for the file and it shows two entries. One is in \Windows\System32 and the other is in \Windows\WinSxS but both have creation dates of 29th September 2017.
 
Re: Random system restarts - only when gaming, no minidump created

This won't necessarily work but on many laptops the built-in keyboard is actually a PS/2 keyboard. If you can get manual dump file generation working using the built-in keyboard you have a much better chance of capturing the dump file when the system is frozen. PS/2 keyboards have an interrupt level that takes precedence over almost anything. However, since your keyboard doesn't have a ScrLck key you'd need to use the alternative instructions at the bottom of the page I linked to remap a different key (the Home key for example). The instructions are a bit cryptic but is it something you can try?

I'm struggling with how to find the right value for keys. I can use Space or Home easily if you have any idea how to set that. The laptop is a bit of a mess as it's a US keyboard layout but was sold in the UK and has UK language settings so I don't know if that makes a difference.
 
I don't know why I didn't think to upload these, perhaps I didn't think they'd be much use but at this point I don't see what I have to lose. Each crash has always triggered the LiveKernel Watchdog to create a dumpfile and I have no idea if it'll help at all but I'll include all crashes from the Windows install onwards on the laptop.

Watchdog
 
Since you have live dumps it may not be necessary to try and get a crash dump. Since you can also generate manual crash dumps I think your settings are fine which suggests sanity checks are failing during the crash dump file creation process. Windows performs some tests to make sure what was dumped from memory to the pagefile after a crash matches the dump which gets generated after the system reboots and if the test fails the dump file isn't generated.

The most recent dumps are still showing the older versions of the network adapter drivers. Have you tried installing them and the drivers aren't getting updated or do you not want to install them? It's quite possible for a misbehaving driver to interfere with unrelated hardware drivers so I'd recommend updating if possible.

The documentation for live kernel dump 0x141 is here. The automated analysis is pointing the finger at nvlddmkm.sys. I know you've tried several versions of the Nvidia drivers. The nvlddmkm.sys in the latest live minidump has a timestamp of Wed Apr 12 12:51:53 2017 but I can't tell which driver version it is from the dump. If you're going to try an older Nvidia driver I'd recommend version 388.71 as it seemed to be the most stable prior to the Spectre/Meltdown update debacle. Since your BIOS predates the Spectre/Meltdown update I would expect that to be as good or better than any other driver and BIOS pairing.

Is there any hardware you're using that the retailer didn't have while doing their testing?
 
Since you have live dumps it may not be necessary to try and get a crash dump. Since you can also generate manual crash dumps I think your settings are fine which suggests sanity checks are failing during the crash dump file creation process. Windows performs some tests to make sure what was dumped from memory to the pagefile after a crash matches the dump which gets generated after the system reboots and if the test fails the dump file isn't generated.

<snip>

Is there any hardware you're using that the retailer didn't have while doing their testing?

Apologies, I haven't updated the network adapter drivers. I will update them but based on past experience with a fully patched and updated system I don't believe it will have any effect. The nVidia driver are 381.78 so I will also update those. I have been in contact with nVidia who stated,

"Since the graphic card is always drawing to your screen, Windows will often report the graphics card or its drivers as the problematic device after a system error. In most cases, the problem is caused by another device or component in your system such as the motherboard, system memory, power supply, Bus errors or hard drive.

The issue occurs when the Timeout Detection and Recovery (TDR) feature available in Windows OS, detects that the graphics card (GPU) has not responded within a predetermined period of time and reinitializes it with the Windows Display Driver Model (WDDM) to prevent the need to reboot"

I don't know how true that is but they did escalate it to their L2 support group and I'm waiting for them to contact me. As far as hardware goes I made sure to discount all possible hardware issues and I've been testing it without any external devices attached. I will also add that BitLocker is not enabled and it isn't a G-Sync screen. I'll update the drivers and see what happens.
 
The response from Nvidia is likely true and consistent with what I've experienced myself. It doesn't eliminate the videocard as the problem, though. If the system is only creating a live dump I wouldn't expect it to automatically reboot. As Nvidia wrote, it should only reinitialize the videocard and allow the system to at least recover to your desktop; assuming the videocard successfully reinitialized.

I'm not certain of this but I suspect reinitializing the videocard likely puts games in an unreliable state if the games are running when it happens. I don't think there are many games that are expecting the videocard to be reinitialized and are therefore unlikely to have been programmed to recover from it. I think a game would likely crash but not necessarily.

Please do try the system after updating the drivers and let us know if the problem continues. If any new live dumps are generated it might be useful to have a look so please make them available. I'd be curious to know what Nvidia has to say if they get back to you.
 
I updated everything and sat running the game that crashes most. It went for over 4 hours with the game running but without a system crash. The game itself actually crashed for the first time ever and I dared let myself hope it was fixed. Restarted and within 10 minutes it hung with the following corrupted display showing. I've attached both the latest Live Kernel dump and the dump from the game crashing in case it shows anything possibly related. It isn't the most stable game in general though so I almost forgot to include it.

Corrupt.jpg

It's the most bizarre issue I've ever had and is almost like it performs fine for a while but then decides it's going to act up. I've never really paid attention to it but I'm wondering if there is a link between the issues and how long the system has been running. If it's a fresh boot it feels like it will work fine for a while and only after I've cycled through loading game, quitting and then reloading that it has this. I would like to be sure on that but I'm also sure it has happened very soon after freshly booting.

I want to thank you both for trying to help me with this. I can't tell you how crazy it's been driving me having the retailer just tell me how they ran benchmark stress tests and saw no issues which I quite believe. Never have I seen a system that could do stress tests fine but not games.
 

Attachments

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

Back
Top