BSOD on Start Up- Driver Issue?

[BrainSWilliams]

Hi folks I need some help.

My computer started running a checkdisk on startup and I was impatient so I restarted the machine to run the "Start Windows Normally" option. But now I get a BSOD on startup. I've restarted during a checkdisk before and never had a problem.

Unlike a normal BSOD that has a whole screen of info, the BSOD I'm getting is just minimal info.

Blue Screen Reads:
"A problem has been detected and windows has been shut down to prevent damage to your computer.......blah, blah, blah............

Technical Information:

*** STOP: 0x00000024 (0x0000000000190494, 0xFFFFFA800475E860, 0xFFFFFFFFC0000102, 0x0000000000000000)"


It won't run in any Safe Mode, it won't let me do a System Restore claiming there are no restore points even though there are, or were. Repair mode doesn't work either.

The repair tool says it's a bad hard drive,but I don't think that's correct.

My hard drive is partitioned to have a C drive for my OS and programs, and a D drive for other stuff like my music collection and ebook collection.

When I go through the tools to the "Re-Image Your Computer" mode, I can see each and every file on the D partition but no files whatsoever show up on the C partition.

It's is a Samsung RV511 laptop. It has a Samsung Recovery Solution tool that can be run at start up, but it just says it can't detect a drive or partition. I can't choose the entire backup option since I've got files I need on the C drive.

I know almost nothing about hardware, but I'm pretty sure that if the hard drive was no good then I wouldn't be able to see any files on either the C or D partition. So I'm suspecting it's a driver issue.

Any advice on how I can get it working again is greatly appreciated because I can't afford to get it repaired.

Thanks in advance.

 

[BorisTheAnimal]

Hello BrainSWilliams and welcome to 7 Forums!

The 0x00000024 bug check indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

Now the best solution would be if you could get to a command prompt window and run this command:

SFC /scannow

The command will scan your computer for broken files and drivers and will try to repair them, in the end it will save all information to a text file.

Here is detailed information about using SFC /scannow:

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

And here is a tutorial on how to enter command prompt if Windows can't boot:

http://www.sevenforums.com/tutorials/682-command-prompt-startup.html

Cheers, Boris