Random BSOD - First BSOD after windows format

I see, before I used DDU to remove and reinstall but did not perform the extra steps you provided. I will do so in the coming hour.

I also performs the CMD commands (errors were found before installations but none here) but here are the results

Microsoft Windows [Version 10.0.16299.251](c) 2017 Microsoft Corporation. All rights reserved.

- currently entering safe mode for DDU, will post back shortly
--------------------------------

C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism / online /cleanup-image /restorehealthError: 87DISM doesn't recognize the command-line option "".For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.251[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 348672 file records processed.File verification completed. 6191 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 357 reparse records processed. 444472 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 357 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 47901 data files processed.CHKDSK is verifying Usn Journal... 40822928 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 487805951 KB total disk space. 105374568 KB in 203205 files. 138196 KB in 47902 indexes. 0 KB in bad sectors. 472947 KB in use by the system. 65536 KB occupied by the log file. 381820240 KB available on disk. 4096 bytes in each allocation unit. 121951487 total allocation units on disk. 95455060 allocation units available on disk.C:\WINDOWS\system32>


---- Edit : Upon removal of drivers in safe mode using DDU, I installed directly from website instead of geforce software. The physx box was already checked and i checked the clean install box as well.

Spamming I know, just for purposes of being new to this forum and making sure you catch everything. At this point I have uninstalled and reinstalled the GPU drivers directly from the website instead of through their nvidia software and unchecked the auto restart box from before so something will be generated in the future. I am pretty positive this will happen again soon but at this point software related I suppose it is a waiting game.

zbook said:

When there is a BSOD they are given a number and a name for classification.
PAGE_FAULT_IN_NONPAGED_AREA (50)
This BSOD had the number 50 and the name: PAGE_FAULT_IN_NONPAGED_AREA
So when you see the BSOD window it may have a different name.
Drivers typically end with .sys
So for some BSOD you may only see the bugcheck name and for other BSOD you may see both.

Once you uninstall the Nvidia GPU using DDU and reinstall a new driver this should fix the BSOD.
Sometimes there are problems with the underlying hardware.
Other times there is another driver that caused the crash and another driver was a bystander.
At this time the first step is to replace the GPU driver and then observer the computer for stability.

It kernel 41'd this morning again with no bugcheck codes, all 0's even with that box unchecked it did not generate a memory file.

1) Which source was used for the Nvidia drivers?
2) Make a backup image using Macrium:
Macrium Software | Your Image is Everything
3) Make a brand new restore point
4) Run the beta log collector after the next unexpected reboot or crash and post a zip into the thread
log collector v2-beta08.zip
(extract > open)

I used nvidias website and tools for the drivers after removing all drivers for the 1080 with DDU. They seem to be working fine without any Kernel 41's. At this point I believe it's a faulty 1080, I am still in warranty and it has been a day or so with no kernel 41 just on these intel graphics. I have already issued an RMA with them but am still waiting for a kernel 41.

I will follow your advance here as welll and run the log collector if the kernel 41 occurs again. Please do not close this thread, but I am almost confident it's a faulty gpu, this issue started 2 months after I got it.

As far as the source it was Nvidias website and they aren't the best of course, but they play outlast on medium just fine so I am sure they are correct. :)

Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

edit

zbook said:

Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

Attachment 180712


odd speccy is saying the ram is at 1333mhz but it's 2666 with 4 8 gig sticks, i'm sure it has something to do with the cpu being the gpu..... weird

Please update the progress with the steps in post #15.

Windows driver verifier is a tool that is used to find misbehaving drivers.
It will repetitively produce BSOD until all drivers are fixed or until the tool is turned off.

Before using the tool you will need to make a brand new restore point, backup all files to another drive or to the cloud, and make a backup image.

In order to use the tool you must know how to turn it off:
Review this link for 3 methods using the Windows advanced troubleshooting menu to either turn off or recover from using the tool.

The tool will be used for 48 hours. Once there are no longer any BSOD the tool will be used for an additional 36 hours.

While using the tool the computer may become sluggish or have a very slow boot. If either of these happens the customized test settings can be modified.

Use the settings in this link for the customized test settings:
Driver Verifier | Microsoft Docs

After each BSOD use the windows advanced troubleshooting menu command verifier /reset to return to the desktop. On the desktop run the beta log collector and post a new zip into the thread.