My computer is fucked

2011-03-24 06:01:55

#1

ghettoperson: Member; +1,943|6642

Hello everyone,

My computer this morning kept getting stuck at loading USB controllers, so after a couple of attempts I pulled the RAM, and restarted it. Everything seemed fine from from there, till it gets to the little Win7 spinny logo thing, at which point it threw a bluescreen and restarted immediately. I tried this a couple of times with no luck, so then tried Safe Mode. That hung at classpnp.sys. I then tried the Windows repair tool which did nothing, but it then threw another bluescreen which pointed the issue to ntfs.sys.

That's as far as I've gotten, but I thought I'd see what you all thought as I go trawl the internet for some answers.

2011-03-24 06:10:54

#2

AussieReaper: ( ͡° ͜ʖ ͡°); +5,761|6146|what

Grab another HDD, boot from it. Grab what you can from your original HDD now.

NOW! Damn it. GO!

2011-03-24 06:10:59

#3

13urnzz: Banned; +5,830|6490

if you can,

https://static.bf2s.com/files/user/21025/ss/uncheck.JPG

if it is ntfs.sys, you may have hosed the file system.

2011-03-24 06:26:40

#4

ghettoperson: Member; +1,943|6642

Can't get into Windows. But you reckon it's a software issue rather than hardware?

2011-03-24 06:28:22

#5

menzo: ̏̏̏̏̏̏̏̏&#; +616|6439|Amsterdam‫

bios reset helps sometimes

https://i231.photobucket.com/albums/ee37/menzo2003/fredbf2.png

2011-03-24 06:49:32

#6

13urnzz: Banned; +5,830|6490

menzo wrote:
bios reset helps sometimes

also, ntfs.sys is the system file driver, it tells windows how to 'read' your HDD. you may have to boot from another drive to save your midget goat porn.

here's a tip for everyone - you only get five reboots before the option for "Last known good configuration" becomes corrupt.

if you get two BSOD's in a row, put down the computer, and walk away slowly. don't get caught up in the idea that 'next time, it will boot for sure!'.

a blue screen always has a faulting module (ntfs.sys) and an error code (0x000007d). the error code is most important for troubleshooting.

one blue screen = you get off your ass and find a pencil and paper, write the error code down . . .

2011-03-24 06:51:39

#7

ghettoperson: Member; +1,943|6642

Pretty sure it's my mobo, stuff is starting to lock up when I'm playing around in the BIOS.

2011-03-24 06:55:46

#8

ghettoperson: Member; +1,943|6642

Hmmm, loaded up an old BIOS profile and its working fine again. Stil won't load windows though. Currently running a CHDSK. I really, really don't want to have to buy any new hardware.

2011-03-24 07:02:03

#9

ghettoperson: Member; +1,943|6642

Ok, so CHKDSK came up with nothing, but I started it in low res video mode, and it's up and running. Now that I'm in Windows, any ideas for diagnostics tools I should run to find out what the problem is?

2011-03-24 07:08:59