Jump to content

My Dell Inspiron 15z has this problem where it had a BSOD. The error is Faulty Hardware Corrupted Page. I was using roblox studio the clicked on colors. The computer has gone to sleep an hour before and I was doing some programming. My dad said I clicked on something I was not supposed to. I just went on to roblox.com and Google and YouTube. Anyone know what to say so I can reassure him that it was not my fault.

print "Hello World"

 

Link to comment
https://linustechtips.com/topic/642808-faulty-error-corrupted-page/
Share on other sites

Link to post
Share on other sites

BSOD is associated with hardware, not software.... there you go

CPU: Intel Core i7-5820K | Motherboard: AsRock X99 Extreme4 | Graphics Card: Gigabyte GTX 1080 G1 Gaming | RAM: 16GB G.Skill Ripjaws4 2133MHz | Storage: 1 x Samsung 860 EVO 1TB | 1 x WD Green 2TB | 1 x WD Blue 500GB | PSU: Corsair RM750x | Case: Phanteks Enthoo Pro (White) | Cooling: Arctic Freezer i32

 

Mice: Logitech G Pro X Superlight (main), Logitech G Pro Wireless, Razer Viper Ultimate, Zowie S1 Divina Blue, Zowie FK1-B Divina Blue, Logitech G Pro (3366 sensor), Glorious Model O, Razer Viper Mini, Logitech G305, Logitech G502, Logitech G402

Link to post
Share on other sites

3 minutes ago, manikyath said:

it is also related to software falsely reporting hardware problems.

But not with web browsing... That was my point....

CPU: Intel Core i7-5820K | Motherboard: AsRock X99 Extreme4 | Graphics Card: Gigabyte GTX 1080 G1 Gaming | RAM: 16GB G.Skill Ripjaws4 2133MHz | Storage: 1 x Samsung 860 EVO 1TB | 1 x WD Green 2TB | 1 x WD Blue 500GB | PSU: Corsair RM750x | Case: Phanteks Enthoo Pro (White) | Cooling: Arctic Freezer i32

 

Mice: Logitech G Pro X Superlight (main), Logitech G Pro Wireless, Razer Viper Ultimate, Zowie S1 Divina Blue, Zowie FK1-B Divina Blue, Logitech G Pro (3366 sensor), Glorious Model O, Razer Viper Mini, Logitech G305, Logitech G502, Logitech G402

Link to post
Share on other sites

Just now, PCGuy_5960 said:

But not with web browsing... That was my point....

if a windows file got corrupted at some point, it can happen pretty randomly.

 

opening CMD as administrator and typing this should reveal if there's problems:

sfc /scannow

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×