Steam BSODing on Download

[BIGNERDSAM LOGGING IN FOR FISH]

System:
Windows 10 Home
Intel i7 6700K
Nvidia GeForce 1060 6GB
32 GB RAM
Steam installed on C Drive (256 GB M.2 SSD)
Game attempted on D Drive (2TB HDD)

Edit: Additional Hardware
EVGA 600B PSU
ASRock Z170M Extreme4 Motherboard

Stopcode: WHEA_UNCORRECTABLE_ERROR

I have been having this issue for a few weeks now with my repair guy, and our last fix didn't help it and I can't find anymore solutions.

It started in mid-August, the game kept crashing on Warframe at seemingly random. At first I've had it crash while I was idling with Twitch or YouTube in the background, then it began crashing on loading screens and such. When I took it to the repair guy he blamed and removed the Overclocking software that came bundled with my system (no big deal). When the crashes continued, he figured it was the game. Later it was happening while attempting to redownload Warframe onto my C Drive and later it would always happen when downloading onto my D Drive.

Eventually in a Hail Mary attempt to fix what the issue might be, we formatted the computer to see if the problem would be fixed with a clean system and brand new drivers.

It was not, this time it Blue Screened when I was trying to redownload Doom 2016.

At this point I'm all out of ideas and from the way we talked about this, so is he. I've been researching Steam bluescreening on downloads like this, but they have all either involved completely different stop codes or Windows 7 instead. I know that it cannot be the age of the system because this computer was built in May 2018, just a few months ago.

Please help, I really hate how much Warframe I'm missing right now, I feel like I've completely missed out on Frame Fighter and now I'm missing out on the Revenant quest!

[meheezen]

with that much RAM, you sure did a RAM test(mdsched or ramtest86) when you got that computer, didin't you?

[BIGNERDSAM LOGGING IN FOR FISH]

I've run the Windows memory diagnostic a few times after the first blue screens. Came up fine.

[meheezen]

good, now load up bluescreenview and find what is throwing that error.

[_I_]

select the xmp profile for your ram in bios

if mixing ram, use highest common speed and lowest common timings
use cpuz spd tab to see the profiles for each dimm
https://www.cpuid.com/softwares/cpu-z.html

[BIGNERDSAM LOGGING IN FOR FISH]

1: I dont have BlueScreenView
2: I'm not mixing RAM, they're both two sticks of 16GB RAM from the same package.

[meheezen]

Escrito originalmente por Sam in "Computer Problems":

1: I dont have BlueScreenView

then download it... its easy to find and use.
or just use windbg[www.tenforums.com]

[OLDMAN🎅]

BlueScreenView v1.55
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.

Download links are on the bottom of this page https://www.nirsoft.net/utils/blue_screen_view.html

[chiefputsilao✖️ping]

psu? antivirus?

[meheezen]

doing a quick google search returned these 2 links i found useful:
https://windowsfish.com/how-to-fix-whea_uncorrectable_error/
http://www.tomshardware.com/answers/id-2039223/whea-uncorrectable-error-bsod-message.html

it seems to be most likely a CPU overclock or the memory controller.
you wont know for sure until you take a look into the windows dump tho, but these 2 links can point you on the right direction.

[Bad 💀 Motha]

Launch Command Prompt (Admin)
Run...

SFC /SCANNOW (just from C drive, to verify OS files)

CHKDSK /F /R (on each drive letter)

[🦊Λℚ𝓤ΛƑΛᗯҜᔕ🦊]

Escrito originalmente por Bad_Motha:

Launch Command Prompt (Admin)
Run...

SFC /SCANNOW (just from C drive, to verify OS files)

CHKDSK /F /R (on each drive letter)

They've already formatted the hard drive and done a complete windows re-install and it's still having issues. Did you even read the first post at all?

Also as to Sam in "Computer Problems": Do you have another video card to try? It sounds like your video card is likely the problem at this point, you've ruled out all possible software issues with the format and windows re-install. So the only thing left it can be is a problem with the hardware.

[Bad 💀 Motha]

Escrito originalmente por Impending Rentacle Tape:

Escrito originalmente por Bad_Motha:

Launch Command Prompt (Admin)
Run...

SFC /SCANNOW (just from C drive, to verify OS files)

CHKDSK /F /R (on each drive letter)

They've already formatted the hard drive and done a complete windows re-install and it's still having issues. Did you even read the first post at all?

Also as to Sam in "Computer Problems": Do you have another video card to try? It sounds like your video card is likely the problem at this point, you've ruled out all possible software issues with the format and windows re-install. So the only thing left it can be is a problem with the hardware.

None of that has any merit though.
None of that fixes these issues if you have say; bad sectors for example.

[chiefputsilao✖️ping]

^windows does not check for bad sectors during installation unless user manually does it.

[rotNdude]

I would also download and run this memory test utility. I've never been comfortable only running the Windows built-in diagnostic.

https://www.memtest86.com/

[Revelene]

Did you go look up the error in Event Viewer? That should be your first course of action.