[cronos47]

So, nearest I can tell, my computer overheated, despite having the case off to allow it more ventilation, and afterwards, it complained about not being able to find the file "C:\Windows\System\System32". Of course that doesn't make sense because it said it couldn't find a file... and then points me to a folder.

After that, I tried using the recovery console on my restoration CD. When I tried to access my windows installation I got:

PAGE_FAULT_IN_NONPAGED_AREA

with the error code:
0x00000050 (0xC6640000, 0x00000001, 0x08094AF46, 0x00000000)

Every time I boot, I get that error, whether it is standard boot, safe-mode boot, or the recovery console. When loading safemode, the last driver it loads is "giveio.sys", which is apparently part of speedfan that I might have installed a while back (don't remember, frankly).

So yeah.... I'd want to remove that driver to see if it is the problem... but If I can't access my drives or installations, I have no idea how. I have a gentoo live CD, but I've heard NTFS writing from that can be worse than the original error. Plus, my main drive is a Serial ATA drive, and this is the only computer that can read those in the whole house, so can't just mess with it in another computer.

So yeah... any help on how to fix this kind of error?

 

[thebof1993]

PAGE_FAULT_IN_NONPAGED_AREA

Hi the error above will be displayed when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk, this area being C:\Windows\System\System32. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software or a corrupted NTFS volume can all generate this type of error. To try to fix this:
1. Restart your computer
2. Keep tapping F8
3. When you get to the advanced options menu, choose the Last Known Good Configuration option.

If all this allows you to boot log-into your account an do this:
1. Go to Start and click Run
2. Type into run 'cmd' this will load up Command Prompt
3. Type in into Command Prompt 'chkdsk /f /r'

The info in 'here' is the only bit you need to type in don't include the ' 's.
Report back here if this worked!

 

[cronos47]

Just tried to load with the last known configuration like oyu said, and same error (although i think it was a different number than the 0xC6640000 as the second one, but that shouldn't change anything). BUt yeah, it still bluescreens, so I can't access it.

So.... yeah, any idea how to force this to let me log in to remove problematic parts? Some way to force it to only load what I tell it to load?

I don't know, just something to give me access to fix it.

 

[thebof1993]

Ok this could possibly be a RAM problem how many sticks of RAM do you have? because you'll need more than one for the test. I would advise you take one of them out and try to boot again. If this fails go through each stick in turn until you have tried all combonations!