23 posts shown.
Larry Ortiz5 said:Why don't you try booting back into Safe Mode? Once you're there, make sure to open the command prompt as an administrator—that part is pretty important—and then just type this in:
sfc /scannow
Hit enter and just hang tight while it finishes up.
Alright, it finished. It ended up telling me "Windows Resource Protection did not find any integrity violations." So... now what?
Larry Ortiz5 said:From what I've seen, the issue usually boils down to a corrupted Windows file—you might want to try running a repair on Windows to see if that clears things up.
EDIT: Are you able to boot into Safe Mode? (just tap F8 while the computer is starting up)
Yeah, I can. But what exactly is a Windows repair? Never actually done that before.
Hey there
I just turned it down a bit before jumping into a game, and then—bam—Blue Screen of Death. It’s giving me that whole "a problem has been detected and Windows has been shut down to prevent damage" routine, blah blah blah. Below that, it lists some technical info: STOP:0x0000007F(0x0000000000000008,0x0000000080050 033,0x00000000000406F8 i 0xFFFFF96000091667)
win32.sys-Adress FFFFF9600009167 base at FFFFF96000020000, DateSta
558bc272
It also says stuff at the bottom like "collecting data for crash dump, initializing disk for crash dump, beginning dump of physical memory to disk:100" and so on.
If anyone actually knows what's going on, please let me know. This kind of thing has happened before, but back then the PC just rebooted itself—this time I had to manually restart it. If I can get an image uploaded, I'll show you guys exactly what I'm looking at.
Thanks, everyone.