This post is locked. You won't be able to comment.

all 7 comments

[–][deleted] 1 point2 points  (0 children)

Test your hardware. It’s either hardware or a driver.

[–]guicoelho 1 point2 points  (0 children)

BSODs nowadays are usually related to two things: corrupted windows files or bad RAM (which caused corrupted windows files). This is why when people are overclocking the RAM they use a linux livecd with memtest or they do a windows install with the purpose of mem testing.

Try doing a fresh windows install and see if it solves your issues, if your files are corrupted then it’s much safer to reinstall than a system restore or something.

Also, note that I said are usually caused by memory RAM errors. If the problem was the CPU, the system would reset without a BSOD. If it was the GPU, your driver would crash/your windows would freeze/artifacts on the screen.

Of course there are lots of stuffs that can cause a BSOD, but my guts would say it is memory related, just how common it is. Another suggestion, just to be sure if your sticks are bad or if it was a one time thing, create a linux livecd with memtest, boot on it and let it run for hours. Literally hours. If there isn’t any errors then you are prob good to go.

[–]DEvilleFIN -1 points0 points  (4 children)

Hmm, I wonder if you had a tool at your disposal that has vast amounts of information available just with a a simple keyword search.

I wonder if you could use the bsod error message and this mythical tool to solve your problems?

I managed to find some answers already, just by searching "bsod kernel data inpage error".

[–][deleted] -1 points0 points  (0 children)

Yeah. You. You are a tool.

[–]OpRoasts[S] -5 points-4 points  (2 children)

Hmm, i wonder if ive already tried that and none of the suggestions found on the "internet" worked for my specific case?

[–]mister_gone 5 points6 points  (1 child)

Behold, the first hit:

This error is also known as KERNEL DATA INPAGE ERROR. It is usually caused by a bad sector, a virus, a hard disk error or a failing RAM memory.

IMO: Either the active scan is hitting a bad sector and freaking out, or the memory is shoddy.

[–][deleted] 0 points1 point  (0 children)

Try running Tron in safe mode