Solved BSOD after "Starting Windows" screen, receive STOP: 0x

[likeitsillegal]

I didn't think the list of errors I got would fit the title. I also figure that posting a log isn't possible because I can't properly boot into windows. Anyways, a bit of backstory. For the past few days my PC has been behaving oddly. It would take much longer than usual to begin booting, usually 10-15 seconds for the first screen to appear. At times my PC would refuse to recognize any GPU but my onboard one, which could only be repaired by resetting to my Fail-Safe Defaults in BIOS. When booting, I would sometimes receive attempts by my PC to run a disk check on my HDD, but would receive an error concerning software stopping it (and it persisted, even with antivirus off). I intended to do a system restore, but failures with it working in the past lead me to put it off. And yesterday, everything booted up fine, miraculously; no long boot-up, my GPU being detected, no disk check. So I naively believed that my problems had been resolved.

Then this morning, the same things begin happening again. Long boot up, only my onboard card being detected, etc. When I attempted to perform the same fix as before via BIOS, I was instead met with a BSOD after the first Windows splash screen (the black one, not the all blue one). Here are the errors as I wrote them down.

*** STOP: 0x0000000000190494, 0xfffffa80033d03a0, 0xffffffffc0000102, 0x0000000000000000

Nothing appeared after this and I'm sort of at a loss for the meaning. Will running a system repair fix this?

 

[HarriePateman]

This is all i can really gather from what you have written can you please attach some dump files.

http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

[COLOR="Blue"]0x0000000000190494[/COLOR]

Bug Check 0x24: NTFS_FILE_SYSTEM - This indicates a problem occurred in ntfs.sys , the driver file that allows the system to read and write to NTFS drives.

Run [COLOR="Red"]Chkdsk /f /r in Command Prompt[/COLOR] to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

 

[likeitsillegal]

Is it possible to generate a dump when Windows isn't starting up at all? I read the thread before and I thought both utilities were something you needed to run off your desktop?

 

[HarriePateman]

can you get into safe mode?

 

[likeitsillegal]

I wasn't able to before.

However, following your advice and what I had seen from previous searching into the issue, I dug up my Windows disc and did a restore of Windows Startup. Windows was able to launch on the first try afterwards, so the assumption that it was a corrupted NTSF file seems to have been correct.

Should I force a disc heck or system restore for safety at this point? Or is it not necessary?

 

[HarriePateman]

Just for precaution i would create a system restore point. Just incase you need something to fall back on.

Take this time to do a full virus scan, have a clean up ECT.