Constant system crash related to nvidia? Windows 10 BSOD

[x BlueRobot]

[...]

When you return the system, include a printed copy of this thread to show them what crash experts have found in their system.

Regards. . .

jcgriff2

Definitely agree, especially since the system is only 2 months old as well.

 

[LucidityOfPower]

Could you please post your hardware temperatures when a game is running? It'll be interesting to see if there is a possible overheating issue, especially since we're dealing with a laptop.

In another thread on another site, I showed what nvidia reports. I think you'll want to see this. This is Fur Mark being run for ~3 minutes. And the values are blank, as you can see. I don't know why. They flash back and forth. This issue seems to be a problem even with GPU-Z. It will blink on and off on the sensors.




If I open Nvidia Inspector right this moment as I put in the screenshots, it shows this.

Have you tried the other RAM stick? I understand that you tested it with one, but have you tested it with the other?

Yes, tried both, but I kept them in the same slot that they belonged in.

Could you please zip and post those live kernel reports? They should be within the following directory:

C:\Windows\LiveKernelReports

All I see is empty folders there

Just noticed the following from one the event log entries:

Haha, yeah, but maybe it's "just a driver issue"!

I would pester them to death about this system. From reading your posts, I gather that the trouble did not just start recently, rather it likely started day 1 after you initially booted up (or problems began at that time that ultimately led to the NVIDIA BSODs).

NVIDIA writes some of the finest drivers in the world; we rarely see them in BSODs as compared to ATI video drivers, which are definitely problematic. My estimate of the ratio for BSODs caused by NVIDIA drivers vs. those caused by ATI drivers - 1:100 - meaning that we may find one NVIDIA driver issue (almost always out-dated drivers) vs. 100 ATI driver issues.

The fact that your system is BSOD'ing and naming NVIDIA tells me that there is a hardware problem afoot. I do not believe at all that there are any problems with the current NVIDIA drivers. Your system's problem is more than likely unknown hardware failure.

If you paid by credit card, contact the credit card company and try to have the charge stopped/reversed. Doing so will certainly get AVADirect's attention and force them to deal with you.

You deserve a new system, considering that you likely began to have problems with this system very early on after receiving it.

Just to review - 4 BSODs - Bugchecks -

BugCheck 1C7, {0, ffffb60be5ba0000, a8a65024, 144da0}
Probably caused by : ntkrnlmp.exe ( nt!SmHpBufferProtectEx+10cb04 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 113, {19, 2, 10de, 1f11}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoHandleSurpriseRemoval+167 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {ffffcc0150939000, 2, fffff80421d7fc6f, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+6efc6f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 50, {ffffe50071f3f000, 2, fffff803285afc6f, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+6efc6f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

0x1c7 - store component detected a corruption in its data structures; probable cause "NT" - the Windows Kernel - a default of sorts
0x113 - Microsoft DirectX graphics kernel subsystem has detected a violation
0x50 - invalid memory referenced; illegal page fault

When you return the system, include a printed copy of this thread to show them what crash experts have found in their system.

Regards. . .

jcgriff2

Thank you for the info.

And yes, there were flickers of the system earlier and other issues that seemingly "went away" only to have come back in full force. I'm also surprised. I didn't know that BSODs are that rare for Nvidia. And no, I didn't pay by credit... I had it financed since I was in school and couldn't work full time to save up anything. I'm probably going to buy another computer, but I am not sure I want a Clevo/Pro Star anymore... (plus my wife needs a PC, so I may end up buying one for her and end up temporarily using it while I wait for either a fix or a replacement). (I've also decided to donate to the site as a result of your help. Thank you so much!)

Really appreciate all the help.

Definitely agree, especially since the system is only 2 months old as well.

Well, it's two months old in usage--it sat around for a month and a half because I had another computer. I didn't officially finish classes until end of July, so I wasn't able to use it at all until August.

 

[LucidityOfPower]

Here's an interesting update. I let Victor Vran crash. Then I restarted the computer by pressing the shut down button (power button) and waited for it to shut off completely with the power button method. It then rebooted. Now I can get into the map of Victor Vran (by pressing "F"), but Nvidia Inspector shows an even weirder screen now.



GPU-Z Also is reporting some weird stuff.



HWiNFO64 also shows oddities for the GPU sensors. Running programs under INTEL GPU works, but not under NVIDIA.
One game example:

Another game example:


And this:


After this reboot, also, for some reason with only the browser running I have the CPUs running hard, too, but they appear to be doing nothing??:



This isn't normal, is it? Would a reinstall of Windows fix this problem if it weren't a hardware issue? Just curious to know. And would DDUing the drivers fix the problem? Or not? I ask because I'm in the process of doing an RMA for this laptop. AVADirect looked at the crash dumps and they've agreed to have it sent back for diagnostics and repair. I just don't want to be a fool by not exhausting every alternative, only to have it sent to me and be told that it was a driver problem and that I'm an idiot for not reinstalling the system freshly three more times >_<

 

[Sysnative Windows Update]

The number of fresh installs does not matter. If it doesn't work after a single reinstall, it's a hardware issue. No question about it. The only other thing I would try before sending it back is to lower the laptop temperatures by using a cooling pad/pointing a fan into it or something similar to verify that this isn't a thermal issue.

 

[x BlueRobot]

I agree with @softwaremaniac, this definitely seems to be a hardware issue, especially after you've done a clean install as well. Those temperatures from the first set of screenshots do appear to be quite high, do you own a cooling pad or anything sort of fan which you could place near the laptop air intake vents?

 

[satrow]

Looks like there may be a BIOS/WMI problem, or the sensor(s) on the 'board are rare/unknown; try touching bases with Martin, the author of HWiNFO, at his forum with details, he might be able to pinpoint where the sensor's display 'fault' is: HWiNFO Forum

I'd use 3 column mode - the arrows bottom left on HWiNFO - more detail is always good :)

 

[LucidityOfPower]

The number of fresh installs does not matter. If it doesn't work after a single reinstall, it's a hardware issue. No question about it.

I was just wondering if there's any possibility that there are left-over window files. I saw that even on a fresh install, some stuff was left in my games folder, even though, it seems, all programs for the most part were uninstalled. Idk.

The only other thing I would try before sending it back is to lower the laptop temperatures by using a cooling pad/pointing a fan into it or something similar to verify that this isn't a thermal issue.

I use a cooling pad and the fans do work... most of time unless it hits too high of c. For some reason, there's an issue with fans working as they should, though, with the different profiles. The CPU is not overclocked, but if I use Throttlestop, it'll lower the temps. If I don't use Throttlestop, everything is always sky-rocketing. Despite an increase in temperatures, the fans don't actually go past 2k RPM unless the CPU goes into 80+ territory. I know that the idle temps are quite high and unusual. Normal idle temps when I first got the PC were around ~35c. Right now all I run is a browser right after a restart, and this is what's happening:

I agree with @softwaremaniac, this definitely seems to be a hardware issue, especially after you've done a clean install as well. Those temperatures from the first set of screenshots do appear to be quite high, do you own a cooling pad or anything sort of fan which you could place near the laptop air intake vents?

I do... everything is elevated and the fans are *not* spooling up half of the time. This was a problem from day one. I thought maybe BIOS related. I don't know. I tried requesting one, but the company doesn't want to send anything to anyone apparently (this is Clevo/ProStar mfg themselves). They went through a merger, apparently, and they're really hard to work with now. I'm going to be really mad if they tell me that it was the BIOS and that they managed to fix it by upgrading it (because they really could just send it to me and walk me through it instead of having me pay $100 for shipping of this laptop).

Looks like there may be a BIOS/WMI problem, or the sensor(s) on the 'board are rare/unknown; try touching bases with Martin, the author of HWiNFO, at his forum with details, he might be able to pinpoint where the sensor's display 'fault' is: HWiNFO Forum

I'd use 3 column mode - the arrows bottom left on HWiNFO - more detail is always good :)

Ah, yes, ok. Thanks for telling me about that. You think he, Martin, will be able to know what the issue is? Does this software do any sensor logging or anything to try to find what the fault is other than "it's not reporting anything"?

I don't really understand what's happening, lol X_X

Things were a lot more normal prior to shutting down on a game crash. Maybe I should try restarting again...

Edit: Seems to be better after the restart. It's unusual, however, for the black screen to be shown for so long after the BIOS logo. It didn't always do this, I think. When shutting down, the shutting down shows for a few seconds (screen), then turns black. And stays black for a minute or so before it really shuts down. Is that normal shut down behavior for an SSD? I don't recall seeing such on a non-SSD computer where the screen turns off but the computer is still technically on. I know if I DDU the drivers, it should work again. But is that something I really need to do every time? Obviously not practical. Lastly: CPU temperatures are very random. They jump anywhere from ~10-25 degrees in a split second.

 

[Sysnative Windows Update]

The game could be causing your system to overheat. The laptop has a thin and metal chassis which could impact the heat dissipation. Although, it does have triple fan design.

 

[LucidityOfPower]

The game could be causing your system to overheat. The laptop has a thin and metal chassis which could impact the heat dissipation. Although, it does have triple fan design.

But how can ~12 year old games (from 2008) running on partial resolution overheat the laptop? Is that really possible? Video running in the game (as I mentioned before) would crash at a particular point and cause a BSOD-like shut-down. And Victor Vran crashing immediately after starting up and running to the map by pressing "F" -- well, right now it doesn't do that anymore because the intel GPU runs it instead of the nvidia one since it now doesn't work at all anymore, lol. Can this be a heat-related issue? I did run benchmarks before and had everything logged to a file through GPU-Z when the Nvidia card worked. File shows normal temps under stress, I believe. I'll add the file here so you can see. Fur Mark used to run fine, too with temp never hitting over 72c on the GPU. But now the GPU doesn't exist, so we have this error:





Ah, can't edit thread past 15 mins. Ok. I did see this just now in the reliability center:

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 193
Parameter 1: 810
Parameter 2: 0
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_18362
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.18362.2.0.0.256.48
Locale ID: 1033

Extra information about the problem

Bucket ID: LKD_0x193_DxgkrnlLiveDump:810_dxgkrnl!DxgCreateLiveDumpWithWdLogs_dxgkrnl!DxgCreateLiveDumpWithWdLogs
Server information: 3a75b0bd-e70d-448e-aa71-cccde4cbfbd7

And the same reports of this below in the event viewer:

Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Unknown, type 0
Event Name: LiveKernelEvent

and

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Expanded view:

 

[Sysnative Windows Update]

Yup. The GPU may have been faulty or it could have been damaged by the heat.

 

[LucidityOfPower]

Yup. The GPU may have been faulty or it could have been damaged by the heat.

I see! Well, I don't know. If the BIOS didn't run the fans as it should have and the thing over-heated, that should be covered by warranty, right?

 

[Sysnative Windows Update]

Of course.

 

[satrow]

I saw that even on a fresh install, some stuff was left in my games folder, even though, it seems, all programs for the most part were uninstalled

That's sounds like it's a result of a refresh (over the top) install, rather than a clean install - there may well have been other leftovers that would continue to plague programs that needed reinstalling, maybe still affecting Windows...

You think he, Martin, will be able to know what the issue is? Does this software do any sensor logging or anything to try to find what the fault is other than "it's not reporting anything"?

Spend five minutes reading his replies there, you'll find he knows his stuff (I think his monitoring software is probably updated more frequently than any others), he'll want details - you could include a link to this Topic, as well, he'll likely ask you for specific logs, too. Bottom right side of the clock to enable/disable sensor logging.

 

[LucidityOfPower]

That's sounds like it's a result of a refresh (over the top) install, rather than a clean install - there may well have been other leftovers that would continue to plague programs that needed reinstalling, maybe still affecting Windows...



Spend five minutes reading his replies there, you'll find he knows his stuff (I think his monitoring software is probably updated more frequently than any others), he'll want details - you could include a link to this Topic, as well, he'll likely ask you for specific logs, too. Bottom right side of the clock to enable/disable sensor logging.

Interesting. So, should I attempt to reinstall? I used the media creation tool for that with the option to remove everything. I tried it four or five times. One was through the Windows itself (in the settings) where you can refresh the system by reinstalling and deleting everything. Another time was keeping files but deleting everything. Another was an in-place upgrade. And the last one was with a USB-bootable Windows. Of all times, the only thing that left the games folder was the USB-bootable reinstall. It was in C:\Games folder--the only folder in addition to the Users folder that survived the process. My browser and all other apps were deleted. I will go to his forum and ask him about this. Thanks for the advice.

Edit: I have made a thread on the forums over there. Will see what replies I get.

 

[LucidityOfPower]

Sorry for so many posts. Is there a possible problem with why Windows would tell the CPU to run at turbo boost all the time even with all programs closed? Are drivers responsible for controlling this? Or could it be linked to hardware? I've posted this to the HWiNFO forums as well to ask Martin about the sensor issue to see if there's any relationship.

 

[Sysnative Windows Update]

Windows controls that automatically in the background and increases the frequency as it sees fit. Don't worry about this.

 

[LucidityOfPower]

Windows controls that automatically in the background and increases the frequency as it sees fit. Don't worry about this.

Understood! I was afraid that idling at max frequency for several hours was bad. Thanks for clarifying. So this must be the reason why the idle temps are constantly so high, even in just the BIOS it runs at max frequency with fans. Unfortunately I can't lower the temps in this case then.

 

[Sysnative Windows Update]

I think that we all agree at this point that the unit should be RMA-ed.

 

[LucidityOfPower]

I think that we all agree at this point that the unit should be RMA-ed.

Yes, I agree. I'm just really concerned about having done everything on my part to weed it out as a hardware problem and not a dumb driver conflict from a Windows update/re-installation. I'll be without a PC for about a month, I imagine, once I send it off to them. I will send it off when they give me the green light and I'll reply here to tell you what was wrong exactly. Thank you for all your help!

BTW, Martin's reply was this:

Well, this is not easy to diagnose precisely as such analysis would require dedicated hardware diag tools.
But according to those symptoms (communication with the GPU seems to be failing), everything points to a problem with the NVIDIA GPU. This can be either a driver or hardware fault. Considering that you tried a clean install, different driver versions and the way how those failures appear, I believe this is a hardware failure.
That system is only 2 months old, there's nothing to hesitate - RMA.

 

[LucidityOfPower]

Okay, I know this is really old, but I did say I'd give an update. It took two months for them to fix the problem, with most of the fault going to the manufacturer and to FedEx.

When manufacturer received laptop (because the laptop failed several tests on AVADirect's end), chassis was bent/damaged and the screen was broken. Prior to this, the tests were run on the SSD, the RAM, CPU, GPU, etc. They swapped the components that they could, and it would randomly shut down after 10-15 hours of testing every time. So... back to the shipping: FedEx denied the insurance claim. It was then fixed by AVADirect. After the laptop "fixing" by the manufacturer, it was sent back to AVADirect and they ran some more tests to see if the RMA was satisfied. Turned out that only the cosmetic damage was fixed originally and that the random shut-downs kept recurring. The manufacturer said they ran their own tests, though, and it passed. Not what AVADirect found, though, as I just mentioned. As a result, it had to send be sent back again to the manufacturer who then replaced the motherboard and waited for AVADirect's instructions (that explains why manufacturers aren't in the value-added sector of companies like AVADirect). After the repair, That seemed to do the trick. Not sure what was faulty, but something on the mobo was. Now, today, I received the computer back (they did extensive testing prior to sending it back to me). Over-all, I'm happy with AVADirect. They did good. I even got a couple t-shirts for my superb patience =]

There's a good ending. And if anyone asks if I'd recommend AVADirect, the answer is yes. I've not seen many companies update and take care of their customers as much as they had taken care of me, despite the long waiting time. Certainly was worth it to RMA it. Thanks again, to all, for convincing me to do it.