GTXZX
New Member
- Joined
- Feb 18, 2017
- Messages
- 2
- Thread Author
-
- #1
Hey guys, I've gotten this BSOD twice so far since upgrading to windows 10.
FAULTY HARDWARE CORRUPTED PAGE
Here's my files, help is appreciated.
Thanks in advance.
My SPECS:
I7-5820k
EVGA X99 Micro
Nvidia GTX 980 Reference GPU
32GB Mushkin DDR4-2400 (4x 8gb)
X2 Mushkin Enhanced Chronos 240GB in RAID 0
Corsair H100i
Corsair RM1000 PSU
FAULTY HARDWARE CORRUPTED PAGE
Here's my files, help is appreciated.
Thanks in advance.
My SPECS:
I7-5820k
EVGA X99 Micro
Nvidia GTX 980 Reference GPU
32GB Mushkin DDR4-2400 (4x 8gb)
X2 Mushkin Enhanced Chronos 240GB in RAID 0
Corsair H100i
Corsair RM1000 PSU
Attachments
Solution
Hi GTX,
to help you best we need to see the dump files created at the point of BSOD.
If non are present then this is usually down to settings which need changing:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.
Other causes for no dump file creation can be no page file or one that's very low.
Problems with the HDD...
to help you best we need to see the dump files created at the point of BSOD.
If non are present then this is usually down to settings which need changing:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.
Other causes for no dump file creation can be no page file or one that's very low.
Problems with the HDD...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Hi GTX,
to help you best we need to see the dump files created at the point of BSOD.
If non are present then this is usually down to settings which need changing:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.
Other causes for no dump file creation can be no page file or one that's very low.
Problems with the HDD can also affect dump file creation.
Please ensure your settings match those shown above and then wait for another bsod event.
to help you best we need to see the dump files created at the point of BSOD.
If non are present then this is usually down to settings which need changing:
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.
Other causes for no dump file creation can be no page file or one that's very low.
Problems with the HDD can also affect dump file creation.
Please ensure your settings match those shown above and then wait for another bsod event.
- Joined
- Jan 28, 2013
- Messages
- 2,419
What windows version were you upgrading FROM to W10?
<<<<BIGBEARJEDI>>>>
<<<<BIGBEARJEDI>>>>
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Excellent, thank you for the update.@kemical Alright, I followed those steps and will wait for another one.
@BIGBEARJEDI From windows 7 ultimate.
Hopefully 'it' the bsod) is simply a driver related issue although until we see the dump file it's hard to say for certain.
Similar threads
- Replies
- 6
- Views
- 5K
- Solved
- Replies
- 1
- Views
- 2K
- Replies
- 3
- Views
- 23K