Configuration options available for updating windows xp
I have just spent the entire day trying to install xp.
The pc was win98 and something nasty happened and all the profiles disappeared, so I thought xp.
My problem arises as Setup says along the bottom of blue screen "Setup is loading Files" changes to "Setup is Starting Windows" and stalls at this instance, so it is not easy updating drivers, etc with no O. I also got a PAGE_FAULT_IN_A_NON_PAGED_AREA, but I did a check on my RAM for 12 hours with only positive results, so I believe it's a driver, not my RAM.
My question is this- now that I'm pretty sure that the problem is "a driver", how do I go about narrowing things to figure out which driver is bad? I heard about the "Driver Verifier Manager" tool (WINDOWS\system32\verifier.exe), but haven't found too much documentation about it; apparently it's supposed to be used for driver writers to make sure that their drivers are good. Liam [email protected]"light the deep, and bring silence to the world.light the world, and bring depth to the silence." I've had all the above problems.
If it not on the list check the manufacturer's website fo an up to date XP driver, if they don't have one you may be out of luck. lisnag I've had a similar stop error message as rwise 2112 started this thread with the technical info being Stop: 0x000000D1 (0x00000028,0x00000002,0x00000000,0x FC406663) acpi.sys-Address FC406663 base at FC3FC000 Datestamp 3b7d8550 In my problem the situation is that I'm Trying to install Windows XP Pro in a clean install situation on new HDD'sboth SCSI and IDE. Any help forthcoming would be greatly appreciated and very educational-Yours Thankfully Billy thanks all for the helpful posts so far; I've been having this issue as well.
Hardware is Gigabyte GA-6BXDU with 750 Mg of DIMMS PC100( tried various sticks in various slots and even some 250 Mg of Dimms PC66 similarly after setting J6 and Dip switches to match), Two Intel Pentiumm III 450 Mhz Processors, ATI 7500 64Mg dvi dual Graphics card(triedothers such as Trident 1Mg ISA, Sparkle SIS 8Mg, ATI 128 Rage Pro 32 Mg and some more), Pioneer DVD-Rom IDE and others including SCSI, Maxtor 40Gb IDE HDD(tried others too and SCSI HDD. I've also received other BSOD's with different names, and I think I can see now that the issue is being caused by a driver accessing memory which it's not supposed to be.
For more information about Stop 0x D1 messages, see the Microsoft Knowledge Base link on the Web Resources page at
DRIVER_IRQL_NOT_LESS_OR_EQUALSTOP: 0x000000D1 (0x00000001, 0x00000002, 0x00000000, 0x00000001)The system is a Celeron 1300 with 128MB of RAM & 40 GB HDD. I removed one of the RAM sticks and it fixed the problem - turns out the RAM was bad... Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUALThe Stop 0x D1 message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high.We need to uninstall all the entries under network adapter, but the problem is it will not allow to do that.Even if network card is reseated, it gets loaded up again.For me, like for other people, I get this bug when playing online applet-based java games (at Yahoo! I think it can be used by consumers too, but perhaps someone might know how? I flashed and upgraded the bios and seemed to help for a short while, but then it happened again, and much more frequently.
I finally broke down and took my PC to my favorite shop for help.The problem happens infrequently, but always online when opening certain websites. Should be enough to get you started Please take out all the expansion cards and restart the sys and check if u get the it doesnt come up...start putting the expansion card one by one and after putting one card restart the sys and check if u get the u get the error on any of the check the card on another slot ..it still has the problem then there could be a problem with that expansion card. It happens consistantly on the machine I am dealing with when the user starts a new game on but otherwise he can join existing games with no problem. Drivers that have used improper addresses typically cause this error.