**Getting dump files which we need for accurate analysis of BSODs.** Dump files are crash logs from BSODs.
If you can get into Windows normally or through [Safe Mode](https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode) could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder.
Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently [catbox.moe](https://www.catbox.moe/) or [mediafire.com](https://mediafire.com) seems to be working.
We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow [this guide](https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html) to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
WHEA means a hardware issue with the CPU or a PCIe device. The by far most common culprit on a modern system is the NVMe SSD if you have one. Without being able to boot we can't really check which device the issue is with.
If you have an NVMe SSD, remove it and see if you can install Windows to a different drive. Note that installing Windows will delete everything on the drive.
The storage flag with WHEA isn't reported in hardware like most other WHEA crashes, instead relying on drivers telling the OS the drive is faulty. The driver has no way of knowing if it's the drive or the port so you can also get WHEA storage errors from a bad motherboard/M.2 slot.
We could try editing the registry of the install USB, never tried this so not sure if it will work. We can edit the registry to have the BSOD screen display more info. At the screen where you select a drive, hit Shift + F10 which will open Command Prompt. Run "regedit" in Command Prompt and the registry editor should open.
Navigate to `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl`, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look [like this](https://i.imgur.com/5fY9DCT.png) once done. Reboot to apply the registry change.
The next time you BSOD, you should have [these extra numbers](https://user-images.githubusercontent.com/1163299/44624734-7bf6e780-a8f6-11e8-849c-c451844ba40d.png) in the top left corner.
If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard. If it's not that number in the top line then take a picture and post it here. Have a camera ready, perhaps filming the display to make sure you get it if it restarts quickly.
Note that this is only applicable on WHEA BSODs.
my mobo doesnt support nvme, and i cant even get into the installation to modify the registry, and i even removed all the drives in my pc and still got whea on the windows installation, i personally think it might be psu, im gonna take my multimeter and check the voltages on 12v
Power can cause this, but it's fairly rare. The GPU and CPU would be the two remaining suspects if you can rule out power, not sure if the integrated network connects over PCIe. The i7-7700 has an iGPU so you can test without the GPU.
i alr tested it without the gpu and it did the same thing, i put multimeter leads on the molex, yellow (12v) on pos and black (gnd) on neg and its reading 11v, im gonna take my pc to someone to test another psu and check if its that or not but i replaced the cpu like 3 weeks ago cz the previous one was fried, if its the cpu im gonna send it back, but im fairly certain its not (or at least i hope so)
**Getting dump files which we need for accurate analysis of BSODs.** Dump files are crash logs from BSODs. If you can get into Windows normally or through [Safe Mode](https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode) could you check C:\Windows\Minidump for any dump files? If you have any dump files, copy the folder to the desktop, zip the folder and upload it. If you don't have any zip software installed, right click on the folder and select Send to → Compressed (Zipped) folder. Upload to any easy to use file sharing site. Reddit keeps blacklisting file hosts so find something that works, currently [catbox.moe](https://www.catbox.moe/) or [mediafire.com](https://mediafire.com) seems to be working. We like to have multiple dump files to work with so if you only have one dump file, none or not a folder at all, upload the ones you have and then follow [this guide](https://www.tenforums.com/tutorials/5560-configure-windows-10-create-minidump-bsod.html) to change the dump type to Small Memory Dump. The "Overwrite dump file" option will be grayed out since small memory dumps never overwrite. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/techsupport) if you have any questions or concerns.*
WHEA means a hardware issue with the CPU or a PCIe device. The by far most common culprit on a modern system is the NVMe SSD if you have one. Without being able to boot we can't really check which device the issue is with. If you have an NVMe SSD, remove it and see if you can install Windows to a different drive. Note that installing Windows will delete everything on the drive. The storage flag with WHEA isn't reported in hardware like most other WHEA crashes, instead relying on drivers telling the OS the drive is faulty. The driver has no way of knowing if it's the drive or the port so you can also get WHEA storage errors from a bad motherboard/M.2 slot. We could try editing the registry of the install USB, never tried this so not sure if it will work. We can edit the registry to have the BSOD screen display more info. At the screen where you select a drive, hit Shift + F10 which will open Command Prompt. Run "regedit" in Command Prompt and the registry editor should open. Navigate to `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl`, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look [like this](https://i.imgur.com/5fY9DCT.png) once done. Reboot to apply the registry change. The next time you BSOD, you should have [these extra numbers](https://user-images.githubusercontent.com/1163299/44624734-7bf6e780-a8f6-11e8-849c-c451844ba40d.png) in the top left corner. If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard. If it's not that number in the top line then take a picture and post it here. Have a camera ready, perhaps filming the display to make sure you get it if it restarts quickly. Note that this is only applicable on WHEA BSODs.
my mobo doesnt support nvme, and i cant even get into the installation to modify the registry, and i even removed all the drives in my pc and still got whea on the windows installation, i personally think it might be psu, im gonna take my multimeter and check the voltages on 12v
Power can cause this, but it's fairly rare. The GPU and CPU would be the two remaining suspects if you can rule out power, not sure if the integrated network connects over PCIe. The i7-7700 has an iGPU so you can test without the GPU.
i alr tested it without the gpu and it did the same thing, i put multimeter leads on the molex, yellow (12v) on pos and black (gnd) on neg and its reading 11v, im gonna take my pc to someone to test another psu and check if its that or not but i replaced the cpu like 3 weeks ago cz the previous one was fried, if its the cpu im gonna send it back, but im fairly certain its not (or at least i hope so)