Jump to content

[RESOLVED]DO NOT TURN OFF ACPI AFTER LOADING>> Corrupt Win2k rep


Recommended Posts

I was playing WoW last night and had a complete freeze. Had these before (stupid WoW) but this time when I did a hard reboot (always had to before) the system told me something about a corrupt NTOSKRNL.SYS

 

I tried loading Win2k Setup to do repair but it's telling me it cannot find any hard drives installed. I only have on Seagate 7200.7 SATA drive now and windows installed fine to it but now repair is telling me it cannot see it. Any suggestions?

 

Also two questions if I may

 

1) I ran Seagate HD diagnostic from the Ultimate Boot CD and it can see the HD there (as can BIOS) and it ran a test on it and it seems okay. However when I used my floppy boot disk that I use for flashing bios (still haven't flashed it btw, it's 1/25) and I want to access C: it tells me Invalid drive. Only files on the floppy are COMMAND.COM and autoexec.bat. Do I need some other files to be able to see my HD or should the floppy as it is be able to see it and the fact it can't means the HD is pooped? Even though Seagate diagnostic tests is as completely fine?

 

2) When I was trying to load Win2k setup from the CD (slipstreamed with SP4) it kept giving me errors during the loading of the configuration files. Sometimes it would stop on Setupdd.sys sometimes on some other file, always returning error code: 4

 

After a couple of reboots it got past these files and I could get into Windows Repair but then the problems I listed above happened. Are these two issues related?

 

Thanks for any and all input

 

edit: one last note, memtest was giving me errors on my configuration that's in my sig but I never tested it before until now :( Probably why WoW was freezing for me even though OCCT 30min test was fine and no other games had problems. However, now I changed everything to auto and mem is booting at 3-3-8-3 at 2.6V (standard for VX) and memtest is passing however that had no effect on getting Windows repair to work and see the HD

Share this post


Link to post
Share on other sites

I did but then the windows setup "freezes" on the "starting windows 2000 setup" screen. basically after it's done loading all the files and it's JUST about to show the main menu where I can choose to install or repair, it just stays there for a long time. i didn't wait more then 10 minutes but I know it's not supposed to take that lone (more like 5 seconds when I do it without the driver disk)

 

However this is what confuses me. When I was installing Windows 2000 from this same CD, it found the HD no problem. Meaning that Windows 2000 setup loads all the files it does whether it uses install or repair so I don't need the disk (only if it's raid which this is not), but now it's saying it can't find it.

 

Something is very screwy here. The system was running fine for 2 weeks. Was using the 1/25 bios, most things were left on auto for timings only changed it to 2-2-8-2 and was even running 2-2-5-2 at 3.2/3.3V. Windows was loading fine as did everything else except WoW would lockup after a few hours (before latest patch that did this to my system).

 

Can ram just suddenly go bad due to a lockup from a game?

Share this post


Link to post
Share on other sites

I had similar issues with my A8N SLI Deluxe. The problem was memory - corrupting both plexes of my 7200.7 system mirror.

 

Unfortuntely, just because you are BIOS memtest stable, doesn't mean you are Windows memory stable.

 

I can run my memory at 2.6v for hours in memtest 1.51 (BIOS) without any errors.

 

If I then try and load windows - bang - sooner or later.

 

The fix was to push voltage to 2.9 .... now it never hangs (touch wood).

 

It does sound to me like its memory. You have got the drive just configured as a jbod in SATA setup haven't you ?

Share this post


Link to post
Share on other sites

jbod? I had the drive configured as I did when I first put the system together and had no problems until the last reboot as I said :(

 

 

 

edit: do you think I might get some better memory stability if I upgrade to 3.10 bios? what's confusing me is that it worked flawlessly before until this crash.. now it sounds like RAM is borked too.. can a lockup in a game and a reboot after it do this much damage?

Share this post


Link to post
Share on other sites

okay with a little bit of searching around I think I diagnosed the corruption did indeed come because of a memory failure.. I don't understand WHY all of a sudden it did when it ran fine with the timings it ran with before. I even upped the voltage to 3.3V from 3.2V just for added security and ran that fine for a few days as well. Obviously something in the new WoW patch caused this issue (lots of people are having it but I'm the only one with corruption so far)

 

So... does this mean then that my memory is PERMANENTLY bad or just that it had a bad dump which corrupted files and is now back to normal (memory, obviously not the corrupted file) ?

Share this post


Link to post
Share on other sites

hmm well I flashed to 3/10 bios and loaded optimal settings and that seemed to load windows for me.. I think even loading default in 1/25 would do that but didn't test.. this kinda happened by accident

 

then when I changed some settings for me liking (enable SMART, turn off logo, disable sound and 2nd lan) and maybe one or two other things (power managment) I again couldn't boot

 

so now I'm gonna go do it one by one and figure out what the problem is.. just posting here in case anyone else (doubt it since no replies but you never know what WoW might do) needs a head start on fixing it

Share this post


Link to post
Share on other sites

Well I managed to fix the problem.. turning ot ACPI Power function off is what caused the lack of boot.. i remembered that the last boot I turned it off though it could boot then but after the crash with wow it wouldn't anymore and still wouldn't when I was testing to isolate it. oh well it's on now and it's good.

 

Dunno if anyone cares but there you go, add resolved to this now if you wish mods :)

Share this post


Link to post
Share on other sites

Yup, I made that same mistake early on, trying to turn off stuff in BIOS I thought I'd never use. The key is to make one change at a time so you can isolate the issue and back out if Windows won't load!

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...