Constant system crash related to nvidia? Windows 10 BSOD

LucidityOfPower · Sep 15, 2019

Hello.

I don't know where to turn to, so I'm going to turn here in hopes of having some help because I don't know what my options are anymore because these crashes are unpredictable (to some extent).

I tried:
reinstalling windows (many times with different settings)
reinstalling nvidia drivers with DDU (tried this about 7-8 times in safe-mode)
running mem/ram tests (three times)
running disk checks (twice)
doing sfc scans (at least 9-10 times)
running graphics benchmarks such as Fur Mark (probably 6-7 times)
changing/increasing TDR values for graphics controls in registry (doesn't seem to do anything)

All tests come back with GOOD results--no issues reported. I just don't know what the cause is. Could it be that nvidia can't get a driver that works? Or is it a windows issue? I don't have any idea on how to fix this. Maybe someone can help...

I can say that prior to Windows 10 1903 update, everything was fine. But after updating it from what the OEM gave me, nothing seems to work and reinstalling Windows doesn't help.

Here's what's interesting. Games seem to do the trick best (I originally found out that I couldn't do 3D modeling work, and I wondered if it would extend to games--it does). There's one particular game, though, that will cause a crash instantly if I go to the "map" to browse where I want to actually go. All I have to do is press "F" at the map and it will hang up and the computer will crash. Another game, for example, used to crash at the same cut scene every time. After reinstalling drivers and installing intel mangement engine (whatever that is, since I read that it can help), I can get past the cut scene now. Even so, it will still crash unpredictably somewhere else after some time of running around. Even weirder: I can restart the game while the video is in the process of a crash and it will load the map fine (until the PC force-reboots itself as a result of the previous crash--this usually takes about a minute, or enough time for me to reload everything). But the error has evolved from an nvidia error (dxdiag or the nvlddmkm.sys to ntoskrnl or something)... idk what's going on. Even if I try to run anything with intel graphics instead (selecting it from menu when right-clicking), the nvidia kernel stuff crashes anyway, it appears. Basically, it doesn't make sense if the hardware is being switched. Unless the issue lies with something else.

· OS - Windows 10, 8.1, 8, 7, Vista ?
WIN 10

· x86 (32-bit) or x64 (64-bit)?
64 bit

· What was the originally installed OS on the system?
I guess version 1803.

· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
I'm not sure? It comes custom-built and I asked them to install Windows on it.

· Age of system (hardware)
~2 months

· Age of OS installation - have you re-installed the OS?
Literally just reformatted and reinstalled everything about a week ago.

· CPU
8750h

· Video Card
2060 mobile

· System Manufacturer
Clevo/Pro Star

· Exact model number (if laptop, check label on the bottom)
P970ED

· Laptop or Desktop?
Laptop

And here's what WhoCrashed shows, just as a preview to show what has been happening (with sysnativefilecollection zip attached below):

On Sun 9/15/2019 3:04:09 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091519-10500-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80421D7FC6F)
Bugcheck code: 0x50 (0xFFFFCC0150939000, 0x2, 0xFFFFF80421D7FC6F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvcvi.inf_amd64_11bdd2121036771e\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 436.30
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 436.30
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 436.30 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA

On Sun 9/15/2019 3:04:09 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80421D7FC6F)
Bugcheck code: 0x50 (0xFFFFCC0150939000, 0x2, 0xFFFFF80421D7FC6F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvcvi.inf_amd64_11bdd2121036771e\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 436.30
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 436.30
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 436.30 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA

On Sat 9/14/2019 12:49:00 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091419-8359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C10A0)
Bugcheck code: 0x1C7 (0x0, 0xFFFFB60BE5BA0000, 0xA8A65024, 0x144DA0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sat 9/14/2019 3:29:35 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091419-8593-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x41A0)
Bugcheck code: 0x113 (0x19, 0x2, 0x10DE, 0x1F11)
Error: VIDEO_DXGKRNL_FATAL_ERROR
file path: C:\WINDOWS\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the dxg kernel has detected a violation.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Fri 9/13/2019 5:44:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\091319-8437-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF803285AFC6F)
Bugcheck code: 0x50 (0xFFFFE50071F3F000, 0x2, 0xFFFFF803285AFC6F, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvcvi.inf_amd64_11bdd2121036771e\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 436.30
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 436.30
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 436.30 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA

I want to say that I will appreciate any help in advance! I'm utterly flabbergasted, so if anyone can point me in the direction of fixing this, I thank you very much! I just hope it's not a hardware issue for something so new

x BlueRobot · Sep 15, 2019

LucidityOfPower said:
I can say that prior to Windows 10 1903 update, everything was fine. But after updating it from what the OEM gave me, nothing seems to work and reinstalling Windows doesn't help.

Are you referring to a driver update delivered through Windows Update? Or something else?

From the Stop 0x50 dump:

Code:

2: kd> k
 # Child-SP          RetAddr           Call Site
00 ffff8108`39d29de8 fffff803`0e5e3463 nt!KeBugCheckEx
01 ffff8108`39d29df0 fffff803`0e4730bf nt!MiSystemFault+0x1d6733
02 ffff8108`39d29ef0 fffff803`0e5cf120 nt!MmAccessFault+0x34f
03 ffff8108`39d2a090 fffff803`285afc6f [HI]nt!KiPageFault+0x360[/HI] << We crash here!
04 ffff8108`39d2a220 ffffbe8f`77e79b78 [HI]nvlddmkm+0x6efc6f[/HI] << Illegal page fault caused here
05 ffff8108`39d2a228 00000000`00001c43 0xffffbe8f`77e79b78
06 ffff8108`39d2a230 ffff6b28`c2e3db69 0x1c43
07 ffff8108`39d2a238 ffffbe8f`77e6c000 0xffff6b28`c2e3db69
08 ffff8108`39d2a240 00000000`00000007 0xffffbe8f`77e6c000
09 ffff8108`39d2a248 fffff803`2887429d 0x7
0a ffff8108`39d2a250 00000000`00000003 nvlddmkm+0x9b429d
0b ffff8108`39d2a258 00000000`00000000 0x3

Code:

2: kd> !pte ffffe50071f3f000
                                           VA ffffe50071f3f000
PXE at FFFFA9D4EA753E50    PPE at FFFFA9D4EA7CA008    PDE at FFFFA9D4F9401C78    PTE at FFFFA9F28038F9F8
contains 0A000000067C0863  contains 0A000000067C1863  contains 1A000001437F8863  contains 0000000000000000
pfn 67c0      ---DA--KWEV  pfn 67c1      ---DA--KWEV  pfn 1437f8    ---DA--KWEV [HI] not valid[/HI]

Since there is no corresponding physical page mapped, then we cause a page fault, however, the address provided is either completely invalid or within a non-pageable section of memory.

Code:

2: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff803`27ec0000 fffff803`29479000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvcvi.inf_amd64_11bdd2121036771e\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:       [HI] Thu Sep  5 20:44:22 2019[/HI] (5D716596)
    CheckSum:         0155B6AC
    ImageSize:        015B9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Your graphics card driver appears to be very new, I would certainly consider rolling back a few versions to see if it provides any system stability.

There is also a Stop 0x113, which is directly related to the Windows video sub-system crashing, unfortunately the bugcheck parameters aren't well documented at all.

Here's the call stack from it:

Code:

8: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffff485`f5dea2d8 fffff803`79ac41a0 nt!KeBugCheckEx
01 fffff485`f5dea2e0 fffff803`799e32a7 watchdog!WdLogEvent5_WdCriticalError+0xe0
02 fffff485`f5dea320 fffff803`798ba519 dxgkrnl!DpiFdoHandleSurpriseRemoval+0x167 << Likely couldn't handle a PnP IRP for some reason?
03 fffff485`f5dea360 fffff803`7981617a dxgkrnl!DpiFdoDispatchPnp+0xb9
04 fffff485`f5dea410 fffff803`80f99991 dxgkrnl!DpiDispatchPnp+0xea
05 fffff485`f5dea530 ffffa105`a9ce5000 [HI]nvlddmkm+0xd9991[/HI]
06 fffff485`f5dea538 00000000`00000000 0xffffa105`a9ce5000

The first frame just saves the processor context and raises an error which causes the system to produce the dump file.

Code:

8: kd> .frame /r 1
01 fffff485`f5dea2e0 fffff803`799e32a7 watchdog!WdLogEvent5_WdCriticalError+0xe0
rax=0000000000001f11 rbx=0000000000000001 rcx=[HI]0000000000000113[/HI]
rdx=[HI]0000000000000019[/HI] rsi=0000000000000000 rdi=ffffa105a11f3070
rip=fffff80379ac41a0 rsp=fffff485f5dea2e0 rbp=ffffa10596edd9a0
 r8=0000000000000002  r9=00000000000010de r10=fffff80363bc10a0
r11=fffff485f5dea2b0 r12=ffffa105a8db8030 r13=ffffa10596930001
r14=00000000c00000bb r15=ffffa105a8db8030
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040282

Code:

8: kd> u
watchdog!WdLogEvent5_WdCriticalError+0xe0:
fffff803`79ac41a0 cc              int     3 << breakpoint trap?
fffff803`79ac41a1 cc              int     3
fffff803`79ac41a2 cc              int     3
fffff803`79ac41a3 cc              int     3
fffff803`79ac41a4 cc              int     3
fffff803`79ac41a5 cc              int     3
fffff803`79ac41a6 cc              int     3
fffff803`79ac41a7 cc              int     3

However, looking at the call stack again, I'm starting to lean towards either memory issues or a driver issue. The surprise removal call refers to the following IRP - IRP_MN_SURPRISE_REMOVAL - Windows drivers

I understand that you have tested your RAM, but could you please test it again using these instructions? Test RAM with PassMark MemTest86

jcgriff2 · Sep 15, 2019

LucidityOfPower said:
It comes custom-built and I asked them to install Windows on it.

· Age of system (hardware)
~2 months

Have you contacted the system manufacturer about this?

As I'm sure you are aware, a 2 month old, brand new system should not BSOD.

Regards. . .

jcgriff2

LucidityOfPower · Sep 15, 2019

x BlueRobot said:

Are you referring to a driver update delivered through Windows Update? Or something else?

From the Stop 0x50 dump:

Code:

2: kd> k
# Child-SP          RetAddr           Call Site
00 ffff8108`39d29de8 fffff803`0e5e3463 nt!KeBugCheckEx
01 ffff8108`39d29df0 fffff803`0e4730bf nt!MiSystemFault+0x1d6733
02 ffff8108`39d29ef0 fffff803`0e5cf120 nt!MmAccessFault+0x34f
03 ffff8108`39d2a090 fffff803`285afc6f [HI]nt!KiPageFault+0x360[/HI] << We crash here!
04 ffff8108`39d2a220 ffffbe8f`77e79b78 [HI]nvlddmkm+0x6efc6f[/HI] << Illegal page fault caused here
05 ffff8108`39d2a228 00000000`00001c43 0xffffbe8f`77e79b78
06 ffff8108`39d2a230 ffff6b28`c2e3db69 0x1c43
07 ffff8108`39d2a238 ffffbe8f`77e6c000 0xffff6b28`c2e3db69
08 ffff8108`39d2a240 00000000`00000007 0xffffbe8f`77e6c000
09 ffff8108`39d2a248 fffff803`2887429d 0x7
0a ffff8108`39d2a250 00000000`00000003 nvlddmkm+0x9b429d
0b ffff8108`39d2a258 00000000`00000000 0x3

Code:

2: kd> !pte ffffe50071f3f000
                                           VA ffffe50071f3f000
PXE at FFFFA9D4EA753E50    PPE at FFFFA9D4EA7CA008    PDE at FFFFA9D4F9401C78    PTE at FFFFA9F28038F9F8
contains 0A000000067C0863  contains 0A000000067C1863  contains 1A000001437F8863  contains 0000000000000000
pfn 67c0      ---DA--KWEV  pfn 67c1      ---DA--KWEV  pfn 1437f8    ---DA--KWEV [HI] not valid[/HI]

Since there is no corresponding physical page mapped, then we cause a page fault, however, the address provided is either completely invalid or within a non-pageable section of memory.

Code:

2: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff803`27ec0000 fffff803`29479000   nvlddmkm T (no symbols)       
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvcvi.inf_amd64_11bdd2121036771e\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:       [HI] Thu Sep  5 20:44:22 2019[/HI] (5D716596)
    CheckSum:         0155B6AC
    ImageSize:        015B9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Your graphics card driver appears to be very new, I would certainly consider rolling back a few versions to see if it provides any system stability.

There is also a Stop 0x113, which is directly related to the Windows video sub-system crashing, unfortunately the bugcheck parameters aren't well documented at all.

Here's the call stack from it:

Code:

8: kd> knL
# Child-SP          RetAddr           Call Site
00 fffff485`f5dea2d8 fffff803`79ac41a0 nt!KeBugCheckEx
01 fffff485`f5dea2e0 fffff803`799e32a7 watchdog!WdLogEvent5_WdCriticalError+0xe0
02 fffff485`f5dea320 fffff803`798ba519 dxgkrnl!DpiFdoHandleSurpriseRemoval+0x167 << Likely couldn't handle a PnP IRP for some reason?
03 fffff485`f5dea360 fffff803`7981617a dxgkrnl!DpiFdoDispatchPnp+0xb9
04 fffff485`f5dea410 fffff803`80f99991 dxgkrnl!DpiDispatchPnp+0xea
05 fffff485`f5dea530 ffffa105`a9ce5000 [HI]nvlddmkm+0xd9991[/HI]
06 fffff485`f5dea538 00000000`00000000 0xffffa105`a9ce5000

The first frame just saves the processor context and raises an error which causes the system to produce the dump file.

Code:

8: kd> .frame /r 1
01 fffff485`f5dea2e0 fffff803`799e32a7 watchdog!WdLogEvent5_WdCriticalError+0xe0
rax=0000000000001f11 rbx=0000000000000001 rcx=[HI]0000000000000113[/HI]
rdx=[HI]0000000000000019[/HI] rsi=0000000000000000 rdi=ffffa105a11f3070
rip=fffff80379ac41a0 rsp=fffff485f5dea2e0 rbp=ffffa10596edd9a0
r8=0000000000000002  r9=00000000000010de r10=fffff80363bc10a0
r11=fffff485f5dea2b0 r12=ffffa105a8db8030 r13=ffffa10596930001
r14=00000000c00000bb r15=ffffa105a8db8030
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040282

Code:

8: kd> u
watchdog!WdLogEvent5_WdCriticalError+0xe0:
fffff803`79ac41a0 cc              int     3 << breakpoint trap?
fffff803`79ac41a1 cc              int     3
fffff803`79ac41a2 cc              int     3
fffff803`79ac41a3 cc              int     3
fffff803`79ac41a4 cc              int     3
fffff803`79ac41a5 cc              int     3
fffff803`79ac41a6 cc              int     3
fffff803`79ac41a7 cc              int     3

However, looking at the call stack again, I'm starting to lean towards either memory issues or a driver issue. The surprise removal call refers to the following IRP - IRP_MN_SURPRISE_REMOVAL - Windows drivers

I understand that you have tested your RAM, but could you please test it again using these instructions? Test RAM with PassMark MemTest86

I'm not sure if it is a driver update or not. I think it is a windows problem though. Maybe I should switch to Linux...? Oh and I'd get irql bsods with my mouse, but those went away over time. Now I never get them. But before I used to get them every 15 minutes.

I'm running it now. It is on pass 2 of 4 (since memtest no longer allows pass change unless you buy it...). So far no errors. It has been running for 3 hours and I imagine will continue to run for another 3 or 4 based on how slow it is.

Maybe try a different memory test after? HCI memtest perhaps? It is a lot less expensive than memtest86's license.

jcgriff2 said:
Have you contacted the system manufacturer about this?

As I'm sure you are aware, a 2 month old, brand new system should not BSOD.

Regards. . .

jcgriff2

I have and they all refuse for me to send it to them because they said that it was quality tested prior to being sent out (this is AVADirect). Also, when requesting an update to the BIOS, they sent an email to mfg and the mfg never replied. It was three weeks later that I asked about it and they said they had a merger recently and they're not as responsive. And they want me to go through software stuff, insisting on reinstalling windows over and over, to figure out what the cause is because they said that it isn't a hardware problem. I also may have avoided my warranty because I had the touch pad replaced (did it myself) instead of having sent it in to them to do it (wasn't reasonable to do this because it cost over 200 dollars and several weeks of time... I have no other computer to use as a replacement). Maybe I should attempt to sell the computer instead? Windows, during updates, would have its driver verified put the computer into boot loops because of BSODs in attempt to update to 1903 from 1803. Sucks... I'm considering to just buy a different computer all together at this point if there's no other way. Maybe someone can salvage this laptop...

Sysnative Windows Update · Sep 15, 2019

Hi!

If you wish, we can attempt to fix the update issue.

LucidityOfPower · Sep 15, 2019

softwaremaniac said:
Hi!

If you wish, we can attempt to fix the update issue.

And how do you propose that will fix the issue? I dont know what is the underlying cause. That really frustrates me because i thought I'm pretty good with Windows machines but it seems that I'm not really good enough to understand this. I just feel pissed that I spent 2k on a machine that is so unstable. Certainly can (probably) sell it for half the price, right? Lol.

Would you like me to open the game that crashes and get the memdump that is triggered? Maybe that will bring more insight? It is an easy and guaranteed crash. Doesn't even matter if I try to start it with Intel GPU. That, too, btw, crashed A LOT in the past. Now it seems to have moved to the nvidia card for crashing...

I just dont want to reinstall windows for the 10th time now. Please dont make me go through that again. The assembler of this PC that custom built it told me something on the lines of "oh, you did an in place upgrade? And you did another reinstall with the option to keep all settings? But did you reformat and reinstall with everything deleted?" ... as though that'll fix it. Nope. Sadly doesn't.

Anyway, I thank you all for the effort in trying to help me pin down the exact cause of the issue. Otherwise I'm stuck with an overpowered web browser laptop.

Sysnative Windows Update · Sep 15, 2019

I am also inclined to believe that it is hardware, but I meant to say that this procedure would allow us to prove to the manufacturer that it is in fact hardware at fault and not software.

Is this the only game that crashes?

LucidityOfPower · Sep 15, 2019

softwaremaniac said:
I am also inclined to believe that it is hardware, but I meant to say that this procedure would allow us to prove to the manufacturer that it is in fact hardware at fault and not software.

Is this the only game that crashes?

Nope. It seems all 3d programs end up crashing at some point, but some take longer than others. What i mean by this is that i cannot trigger this problem at will. I only know one program (that game) where it will crash every time at will. The odd thing is that this map did not cause crashes in the past. Instead, the crash moved from a random time in that program to the map itself. Sometimes it can be mitigated (not sure what does mitigate it; I tried a lot of different things of installing and uninstalling stuff). Sometimes not. Vampyr, for example, would run just fine for a certain time. At some point, an hour, or two, or even three in, it would crash. Then no crash for a couple days of playing it for 2 or 3 hours. Super random.

I'd also love to prove that it is a hardware problem. If you can at least help me do that, I'll gladly send it back and pay the absurd shipping costs just to get even half of what I paid.

The sequence that crashed the laptop was in Call of Juarez Bound in Blood. When you start a new game, it would crash at the part where after the gun the camera zooms into the character. That was every time. Now it no longer happens. The way I fixed it was this: DDU the drivers, reinstalled them, installed Intel management engine right after. Problem gone. But now it will crash randomly after some time, but not at the sequence. If it is a hardware issue, or even a driver issue, why the inconsistency? Should I Fur Mark it for a whole day? Idk if that would make any difference. Such an elusive problem that doesn't want to get identified.

I forgot to mention that I tried rolling back to a graphics driver from January of this year. Issue still occurs.

Sysnative Windows Update · Sep 15, 2019

Let's prepare your system for the upgrade:

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

LucidityOfPower · Sep 15, 2019

softwaremaniac said:
Let's prepare your system for the upgrade:

SFC Scan

Click on the Start button and in the search box, type Command Prompt

When you see Command Prompt on the list, right-click on it and select Run as administrator

When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Upgrade? To what? I already have all stuff upgraded to all latest windows updates. Is there another upgrade I could do? I will try anything. And some stuff windows tries to update like realtek drivers actually makes the 3.5mm jack not work at all. I had to roll that back or there is crackling and video lagging behind audio if I use other Microsoft-provided drivers than the mfg-provided ones.

Shall I stop the memtest? It is still running (using my phone to type this out). Or wait for it to finish? Please advise on next step. 32gb of ram sure takes a long time to go (I expect another two hours to three hours or so for it to finish pass 3 and 4) through all the passes.

Sysnative Windows Update · Sep 15, 2019

Wait for it to finish.

By upgrade I meant your OS version to the latest 1903 version.

LucidityOfPower · Sep 15, 2019

softwaremaniac said:
Wait for it to finish.

By upgrade I meant your OS version to the latest 1903 version.

Ok, I will wait for that.

Oh. I don't know if that's possible since the support at the laptop building place had me do a complete system reinstall with latest media creation tool in hopes of fixing it, saying that I "need to reinstall directly to 1903 instead of upgrading"... It worked. For a while. Then it didn't after a couple days and started crashing again.

And is 4 passes enough? Should I buy the other memory tester and run 8 passes or more instead? I just dont want to dish out 50 or more bucks for a pro version to test memory.

Sysnative Windows Update · Sep 15, 2019

Then it's 100% hardware issue if a clean install didn't help.

LucidityOfPower · Sep 15, 2019

softwaremaniac said:
Then it's 100% hardware issue if a clean install didn't help.

Ok. Any way to prove that then? Or no? I'll have to call them then and see if anything can be done... or this laptop is going for the recycling bin. I'll take out the ram and HDD and off to garbage it goes.

Sysnative Windows Update · Sep 15, 2019

You have proved it by reinstalling the OS. If a clean installation with nothing but the required drivers crashes, it's a hardware issue. Try using only a single stick of RAM and using it like that. Alternate slots.

After the test is done of course. Don't throw it away!

LucidityOfPower · Sep 15, 2019

softwaremaniac said:
You have proved it by reinstalling the OS. If a clean installation with nothing but the required drivers crashes, it's a hardware issue. Try using only a single stick of RAM and using it like that. Alternate slots.

After the test is done of course. Don't throw it away!

Ok. I'll try your suggestion of exchanging the ram slots. Then I'll try single slot of ram. If that doesn't work, I'm going to see if they'll take it back or I'll find other ways to get rid of it. The thing is useless. I got it for making 3d models but it can't even do that without crashing. I'm ready to give up on it then. Unlike a desktop, not much can be salvaged.

LucidityOfPower · Sep 16, 2019

Well, here's the memtest result. Nothing unusual. Took a friking 6 hours to finish! I'm going to try to deal with the ram sticks now by trying to swap slots and then try individually to see if there's "too much ram" or something.

LucidityOfPower · Sep 16, 2019

All right, so... no BSOD, no memory dumps. Here's what happens when I let the game, where I press "F" to access the map, crash on its own by waiting on it crash itself. The fans shoot through the roof when it happens until the computer goes into a "shutting down..." screen and then, 2 seconds later, shuts down.

Are any of these events hardware related? It'd be of great help for you to tell me before I RMA or throw away the laptop.

And then we get this followed by livekernelevent. Only event viewer shows something. This is the order of events:

And I have switched the spots of RAM. I will try to use only one ram stick this time.

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

Problem signature:
P1: 141
P2: ffffd587e2f1f010
P3: fffff8059d476b34
P4: 0
P5: 1638
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190916-0045.dmp
\\?\C:\WINDOWS\TEMP\WER-2967328-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5672.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5673.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5672.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5682.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_f0ee1a2b4f2a40a669843726c1e0d1f6660437_00000000_cab_39fcfec9-cf0f-4e68-a1cc-ed1d87a99fba

Analysis symbol:
Rechecking for solution: 0
Report Id: 39fcfec9-cf0f-4e68-a1cc-ed1d87a99fba
Report Status: 4
Hashed bucket:
Cab Guid: 0

Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Unknown, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 37ff5ecf-8bed-4ef8-8e9e-cd413460fd67

Problem signature:
P1: 141
P2: ffffd587e2f1f010
P3: fffff8059d476b34
P4: 0
P5: 1638
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190916-0045.dmp
\\?\C:\WINDOWS\TEMP\WER-2967328-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5672.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5673.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5672.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5682.tmp.txt
\\?\C:\Windows\Temp\WERA32B.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_f0ee1a2b4f2a40a669843726c1e0d1f6660437_00000000_cab_39fcfec9-cf0f-4e68-a1cc-ed1d87a99fba

Analysis symbol:
Rechecking for solution: 0
Report Id: 39fcfec9-cf0f-4e68-a1cc-ed1d87a99fba
Report Status: 2147483648
Hashed bucket:
Cab Guid: 0

Faulting application name: VictorVran.exe, version: 2.7.0.0, time stamp: 0x5c52e923
Faulting module name: d3d11.dll, version: 10.0.18362.329, time stamp: 0x2f9cf98c
Exception code: 0xc0000005
Fault offset: 0x0011b626
Faulting process id: 0x1638
Faulting application start time: 0x01d56c49870c7b65
Faulting application path: C:\Games\Victor Vran\VictorVran.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report Id: e1d727a7-260c-40ec-bf34-948fb47745f7
Faulting package full name:
Faulting package-relative application ID:

Version=1
EventType=LiveKernelEvent
EventTime=132130827345135003
ReportType=4
Consent=1
UploadTime=132130827345983066
ReportStatus=2147483648
ReportIdentifier=39fcfec9-cf0f-4e68-a1cc-ed1d87a99fba
Wow64Host=34404
NsAppName=LiveKernelEvent
OriginalFilename=WerFault.exe
AppSessionGuid=00000000-0000-0000-0000-000000000000
BootId=37
IsFatal=4294967295
EtwNonCollectReason=4
Response.BucketId=LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Unknown
Response.type=4
Response.CabId=37ff5ecf-8bed-4ef8-8e9e-cd413460fd67
Sig[0].Name=Code
Sig[0].Value=141
Sig[1].Name=Parameter 1
Sig[1].Value=ffffd587e2f1f010
Sig[2].Name=Parameter 2
Sig[2].Value=fffff8059d476b34
Sig[3].Name=Parameter 3
Sig[3].Value=0
Sig[4].Name=Parameter 4
Sig[4].Value=1638
Sig[5].Name=OS version
Sig[5].Value=10_0_18362
Sig[6].Name=Service Pack
Sig[6].Value=0_0
Sig[7].Name=Product
Sig[7].Value=256_1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18362.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=BLOB
State[1].Value=CHKSUM=E8058DF9CF1D7A1DE2F3BF8BE54BA516;BID=OCATAG;ID=37ff5ecf-8bed-4ef8-8e9e-cd413460fd67;SUB=9//15//2019 9:45:38 PM;SECDATA=9//15//2019 9:45:56 PM;BUID=LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Unknown;FLHASH=1be05842-7bec-2c7f-1714-19f7bdc11590;AutoFLID=4c25e5b8-cdd4-c4c7-cbaf-6425764bfb45;DREQBY=AutoKernelModeCollection
State[2].Key=TpToken
State[2].Value=3.23e6be9e99420c9ce12e49277384cf5e.01d574253e6d6759.meta={oclientingesttime,2019-09-16t04:45:37.6961111z};meta={reportid,39fcfec9cf0f4e68a1cced1d87a99fba}
State[3].Key=TpTokenExp
State[3].Value=132139467387266905
State[4].Key=TpOcaBucket
State[4].Value=LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Unknown
State[5].Key=PayloadType
State[5].Value=secondary
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18362
OsInfo[3].Key=ubr
OsInfo[3].Value=356
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=16162
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.356.18362.0-11.0.145
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32571
OsInfo[19].Key=svolsz
OsInfo[19].Value=464
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.356.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=27002d90-94fa-4369-aad6-48425ae78b1f
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
File[0].CabName=WATCHDOG-20190916-0045.dmp
File[0].Path=WATCHDOG-20190916-0045.dmp
File[0].Flags=34406402
File[0].Type=2
File[0].Original.Path=\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190916-0045.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-2967328-0.sysdata.xml
File[1].Flags=34406402
File[1].Type=5
File[1].Original.Path=\\?\C:\WINDOWS\TEMP\WER-2967328-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WER5672.tmp.WERInternalMetadata.xml
File[2].Flags=34406402
File[2].Type=5
File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5672.tmp.WERInternalMetadata.xml
File[3].CabName=WERInternalRequest.xml
File[3].Path=WER5673.tmp.xml
File[3].Flags=34406402
File[3].Type=5
File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5673.tmp.xml
File[4].CabName=memory.csv
File[4].Path=WER5672.tmp.csv
File[4].Flags=34406402
File[4].Type=5
File[4].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5672.tmp.csv
File[5].CabName=sysinfo.txt
File[5].Path=WER5682.tmp.txt
File[5].Flags=34406402
File[5].Type=5
File[5].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5682.tmp.txt
File[6].CabName=WERDataCollectionStatus.txt
File[6].Path=WERA32B.tmp.WERDataCollectionStatus.txt
File[6].Flags=851971
File[6].Type=5
File[6].Original.Path=\\?\C:\Windows\Temp\WERA32B.tmp.WERDataCollectionStatus.txt
File[7].CabName=Report.zip
File[7].Path=Report.zip
File[7].Flags=65536
File[7].Type=11
File[7].Original.Path=\\?\C:\WINDOWS\system32\Report.zip
Ns[0].Name=stopcode
Ns[0].Value=00000141
Ns[1].Name=p1
Ns[1].Value=FFFFD587E2F1F010
Ns[2].Name=p2
Ns[2].Value=FFFFF8059D476B34
Ns[3].Name=p3
Ns[3].Value=0000000000000000
Ns[4].Name=p4
Ns[4].Value=0000000000001638
FriendlyEventName=Hardware error
ConsentKey=LiveKernelEvent
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
ReportDescription=A problem with your hardware caused Windows to stop working correctly.
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=1300635257

Fault bucket 1939007068149179263, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: VictorVran.exe
P2: 2.7.0.0
P3: 5c52e923
P4: d3d11.dll
P5: 10.0.18362.329
P6: 2f9cf98c
P7: c0000005
P8: 0011b626
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC316.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC4FB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC53B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC53B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC55B.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_VictorVran.exe_9a993e332accb110dac08c87a1851711c6730dc_66edb7cf_4a111875-850d-455f-8a2b-d2f7d4e97edb

Analysis symbol:
Rechecking for solution: 0
Report Id: e1d727a7-260c-40ec-bf34-948fb47745f7
Report Status: 268435456
Hashed bucket: ce2f265f0c071c928ae8bca7ba00e37f
Cab Guid: 0

Version=1
EventType=APPCRASH
EventTime=132130827623356848
ReportType=2
Consent=1
UploadTime=132130827629309163
ReportStatus=268435456
ReportIdentifier=4a111875-850d-455f-8a2b-d2f7d4e97edb
IntegratorReportIdentifier=e1d727a7-260c-40ec-bf34-948fb47745f7
Wow64Host=34404
Wow64Guest=332
NsAppName=VictorVran.exe
OriginalFilename=VictorVran.exe
AppSessionGuid=00001638-0003-0025-657b-0c87496cd501
TargetAppId=W:0006e86aaae16469ef30464be5881ac8b70b00000000!0000094933f345624c8a0f6f0abcadf481932ee2e24c!VictorVran.exe
TargetAppVer=2019//01//31:12:25:07!0!VictorVran.exe
BootId=4294967295
ServiceSplit=1966014464
TargetAsId=506
EtwNonCollectReason=4
Response.BucketId=ce2f265f0c071c928ae8bca7ba00e37f
Response.BucketTable=1
Response.LegacyBucketId=1939007068149179263
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=VictorVran.exe
Sig[1].Name=Application Version
Sig[1].Value=2.7.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5c52e923
Sig[3].Name=Fault Module Name
Sig[3].Value=d3d11.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.18362.329
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=2f9cf98c
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0011b626
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18362.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=1818
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=1818ebce2edbb639657436fec77f05d8
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=f6d4
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=f6d4b46c1d7cd3252aa8cde95671ca42
UI[2]=C:\Games\Victor Vran\VictorVran.exe
LoadedModule[0]=C:\Games\Victor Vran\VictorVran.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\SYSTEM32\apphelp.dll
LoadedModule[5]=C:\WINDOWS\System32\USER32.dll
LoadedModule[6]=C:\WINDOWS\System32\win32u.dll
LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[9]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[10]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[11]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[12]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[13]=C:\WINDOWS\System32\combase.dll
LoadedModule[14]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[15]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[16]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[17]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[18]=C:\WINDOWS\System32\sechost.dll
LoadedModule[19]=C:\WINDOWS\System32\shcore.dll
LoadedModule[20]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[21]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[22]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[23]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[24]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[25]=C:\WINDOWS\System32\profapi.dll
LoadedModule[26]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[27]=C:\WINDOWS\System32\UMPDC.dll
LoadedModule[28]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[29]=C:\WINDOWS\System32\cryptsp.dll
LoadedModule[30]=C:\WINDOWS\System32\ole32.dll
LoadedModule[31]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[32]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[34]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[36]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.18362.356_none_71d539095ae5ad3b\COMCTL32.dll
LoadedModule[37]=C:\WINDOWS\System32\IMM32.dll
LoadedModule[38]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[39]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[40]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[41]=C:\WINDOWS\SYSTEM32\X3DAudio1_7.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\faultrep.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\dbghelp.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\dbgcore.DLL
LoadedModule[45]=C:\Games\Victor Vran\Galaxy.dll
LoadedModule[46]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[48]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[49]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[51]=C:\WINDOWS\System32\NSI.dll
LoadedModule[52]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[53]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[54]=C:\WINDOWS\system32\wshbth.dll
LoadedModule[55]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[56]=C:\Windows\System32\rasadhlp.dll
LoadedModule[57]=C:\WINDOWS\SYSTEM32\secur32.dll
LoadedModule[58]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[59]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[61]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[62]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[63]=C:\WINDOWS\System32\WINTRUST.DLL
LoadedModule[64]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[65]=C:\WINDOWS\System32\DriverStore\FileRepository\nvcvi.inf_amd64_11bdd2121036771e\nvldumd.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[67]=C:\WINDOWS\System32\DriverStore\FileRepository\nvcvi.inf_amd64_11bdd2121036771e\nvwgf2um.dll
LoadedModule[68]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[69]=C:\WINDOWS\SYSTEM32\winmmbase.dll
LoadedModule[70]=C:\WINDOWS\SYSTEM32\cryptdll.dll
LoadedModule[71]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[73]=C:\WINDOWS\SYSTEM32\ColorAdapterClient.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\icm32.dll
LoadedModule[75]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[76]=C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9915c06ba61501b1\igd10iumd32.dll
LoadedModule[77]=C:\WINDOWS\SYSTEM32\ncrypt.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\NTASN1.dll
LoadedModule[79]=C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9915c06ba61501b1\igdgmm32.dll
LoadedModule[80]=C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9915c06ba61501b1\igc32.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\xinput9_1_0.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\XInput1_4.dll
LoadedModule[83]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[84]=C:\WINDOWS\SYSTEM32\inputhost.dll
LoadedModule[85]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll
LoadedModule[86]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[88]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[89]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[90]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[91]=C:\WINDOWS\System32\XAudio2_7.dll
LoadedModule[92]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[93]=C:\WINDOWS\SYSTEM32\resourcepolicyclient.dll
LoadedModule[94]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[95]=C:\Windows\System32\Windows.UI.dll
LoadedModule[96]=C:\Windows\System32\TextInputFramework.dll
LoadedModule[97]=C:\WINDOWS\SYSTEM32\avrt.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18362
OsInfo[3].Key=ubr
OsInfo[3].Value=356
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=16162
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.356.18362.0-11.0.145
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32571
OsInfo[19].Key=svolsz
OsInfo[19].Value=464
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.356.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=27002d90-94fa-4369-aad6-48425ae78b1f
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=VictorVran
AppPath=C:\Games\Victor Vran\VictorVran.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=01DDA8BF5F7ED5AA3D342864AC20B817
MetadataHash=1949916516

EDIT: Tried to swap RAM sticks. Kept only one. Still same problem. Instant crash with this game in particular (Victor Vran). Probably not RAM, then...? Maybe GPU memory is messed up?

x BlueRobot · Sep 16, 2019

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.

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

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

Code:

C:\Windows\LiveKernelReports

I believe that HWInfo64 provides thermal information - Free Download HWiNFO Sofware | Installer & Portable for Windows, DOS

Otherwise, you could try using Speccy instead - Download Speccy | Find your computer specs, free!

Just noticed the following from one the event log entries:

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

jcgriff2 · Sep 16, 2019

jcgriff2 said:
Have you contacted the system manufacturer about this?

As I'm sure you are aware, a 2 month old, brand new system should not BSOD.

LucidityOfPower said:
I have and they all refuse for me to send it to them because they said that it was quality tested prior to being sent out (this is AVADirect).

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 -

Code:

[font=lucida console]
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 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

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

Constant system crash related to nvidia? Windows 10 BSOD

Contributor

Attachments

Administrator

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Contributor

Inactive

Contributor

Inactive

Contributor

Inactive

Contributor

Inactive

Contributor

Inactive

Contributor

Inactive

Contributor

Contributor

Attachments

Contributor

Administrator

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)