Help! Fried Windows .. Physical dump/shadowing/caching

Hey, just thought I'd post this here and see if anyone knew how this problem could be remedied. I went to turn my PC on the other day and ended up getting a major error - a dreaded blue screen! It mentions turning off caching and shadowing, easy enough? Not. I poked around in BIOS and was unable to find either a caching OR a shadowing option. Is there any other ways to disable these features? Would any other information help?Windows XP Pro with Service Pack 1 .. Intel Pentium 4 processor .. BIOS version is 2350_A02. So yeah, ANY help appreciated!

I've also had this problem. Unfortunately for your situation, a)the hints about uncacheing and shadowing, etc. seldom work. there are various messages displayed on BSoD, if you could give us the specific erro emssage it would helpful and we could tell you how to fix it.~Viz

Hey, just thought I'd post this here and see if anyone knew how this problem could be remedied. I went to turn my PC on the other day and ended up getting a major error - a dreaded blue screen! It mentions turning off caching and shadowing, easy enough? Not. I poked around in BIOS and was unable to find either a caching OR a shadowing option. Is there any other ways to disable these features? Would any other information help?

 

Windows XP Pro with Service Pack 1 .. Intel Pentium 4 processor .. BIOS version is 2350_A02. So yeah, ANY help appreciated!

1064322785[/snapback]

I would try a Last Known Boot configuration. I don't think you altered anything in the BIOS right?

 

If you did alter something in the BIOS then it seems to be referring to Shadowing of the Video card and Caching of the CMOS startup, just to increase their loading speed.

 

To do the Last Known Boot just after the BIOS screen and after the Search for bootable devices press F8 and you should get the Windows XP startup menu, select Last Known Good Boot (or something like that) and see if that resolves the problem.

 

However being a blue screen I'm not sure how much XP relies on the BIOS when it reaches that stage.

 

 

Cheers,

 

 

MC

Tried that, MC, but it didnt work. Looks like I'm gonna have to re-install, bah. I'll try and get the compy to spit out another screen, which isnt too hard seeing as all I really have to do is boot it up and let it sit a min.

Okay ... heres the stuff:

PAGE_FAULT_IN_NONPAGED_AREATech Info: *** Stop: 0x00000050 (0x82400000, 0x00000000, 0x81D84A83, 0x00000000)

And then it does a physical memory dump and recommends that I contact my system administrator.

sounds like an error occuring pretty soon after protected mode is enabled, ty last known good configuration like MC said. If that doesn't work, boot to the basic Safe Mode and login as administrator, then just shutdown. Then try booting again.~Viz

That doesnt work. I'm thinking pretty soon I'll just bring out the Windows CD and re-install. Thing is, my last backup was done August 20th, and I do them every 5 weeks - so I've lost a lot of stuff. Grr. :/

I understand your feeling, that's what I had to do as well.~Viz

I like how vague Windows Stop Errors are.Basically, it's failing writing (0x0) to some memory location, which it lists two address for that. Now I wouldn't know what those addresses refer to, but it could be anything from L2 Cache, Video RAM, Memory or even Page File. It could even be related to a hardware address, if any new devices were installed or drivers, etc, it would pay to roll them back or get rid of them. Antivirus or similar software could have similar effects.If it is corrupted memory, I would not try reinstalling until I can honestly rule out that it's not a fault that would affect the installation, else you could make it worse than better.It's quite hard to know what to do in this situation without physically being there and testing every possibility.Cheers,MC

About backing up - is there another computer you could drop your HD in just to copy the important stuff off (i.e., boot off of the other OS)? That way, you could at least save some of your stuff. (If all you have is Win98 or something early, there is a utility that allows older OSes to copy files off NTFS drives.)

Hmmm, I did this once to my cousins computer on windows ME.Back then they didn't have a limit to how much virtual memory you could set aside for your computer from your harddrive.Well yeah, I did that...And then the comp kept crashing till I went into safe mode and fixed the problem.Did you mess with the virtual memory at all? I know windows xp has the limit...But you never know, right?

Let Linux to rescue your system, u ask how? If you have another computer, burn a copy of knoppix (http://www.knoppix.org/) or ultimate bootcd (http://www.ultimatebootcd.com/), then boot from it, it can read NTFS, FAT32 system as well. Just transfer it to a USB disc or something like that, else, type smb:/ to search your Windows network at its file manager and copy everything to your networked computer.I really suggest you use Linux permanently since these memory errors never happens. I recommend SuSE, easy to setup, easy to get around. That is, if you don't have games on it (Most Windows games don't work on Linux)xboxrulz

If I was the only user of the computer I'd have long ago switched to Linux, Xboxrulz. Unfortunately it's shared with a few other folks in my family, some of who play games, and others who'd not appreciate an OS change. But thanks anyways. B)Spacewaste, I havent changed the VM. :/Retaining - great idea! Will try it tommorow and let you know how it turns out. Theres only a few things that I "really" need - a couple of databases and whatnot. Except I've got one question. The computer that crashed was XP Pro. The computer I'd be putting the Pro's HD in is a XP Home. Is that gonna cause problems? :SThanks all others who've offered help!

It shouldn't cause problems. As far as file storage goes, both Home and Pro use NTFS,so the data will be fine. The issue comes with boot order. Obviously the bad HD is still bootable (according to BIOS) or windows never would've had a chance to display BSoD. So make sure when you put it into the new shell, you make it the slave HD. Also, make sure BIOS is set to boot from the master HD before the slave HD (some BIOSes identify HDs according to windows nomnclature in which case C: is primary).~Viz

XP Home may have a problem... but I'm going to say it won't.When you do use XP Home, the administrator must claim ownership of the directories/subdirectories if any of them reside in an area where you can't get to. Hopefully XP Home can do this but I'm uncertain because I don't use XP Home, nor do I do anything like this on computers that do run XP Home since the problem is usually different.Cheers,MC