Windows XPPost your Windows XP related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
My desktop has been operating well for the last 5 months or so, but started getting crashes and BSODs. I started getting random BSOD crashes, a problem with the windows login process and then the safe mode bootup generated a PFN_LIST_CORRUPT BSOD screen. However, I am not seeing these problems anymore and can get into safe mode, but now I am getting a rather consistent (DRIVER_FAULT I think) BSOD crash soon after logging (clicking on the user name in the log in screen) into normal windows boot. I have attached a minidumps (since I can't see any attachment option).
Is this really a driver fault problem (and if so, which driver?), or is there something more at fault in the OS installation? Also, can I uninstall software/drivers while in the Windows safe mode, it doesn't seem let me while in safe mode. Any help will be most apprepriated.
Regards,
Phil
Windows XP Pro, SP2
Shuttle XPC ST20G5 (Socket 939)
AMD Athlon 64 3700+ San Diego
ATI Radeon X800 XL
Seagate Barracuda 7200.8 NCQ 300GB
Mitsumi FA 404M 7in1 USB 2.0 Floppy & Media Drive
Crucial 1GB (2x512MB) DDR PC3200 Ballistix Dual Channel Kit
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
MISALIGNED_IP:
nt!CcPfPrefetchSections+134
80614ad6 c429 les ebp,[ecx]
"Stop errors in a nutshell are errors that are serious enough to cause Windows to stop. They are similar to the blue screen errors that were present on Windows 9x, however there is no option to try and resume the session in a Windows NT Stop Error (Windows 2000 and all XP members included)."
Thanks for that, I will try changing the startup and recovery settings, but I have a feeling that have most of the error in the minidump...
I find this a good resource for Stop Messages: http://aumha.org/win5/kbestop.php, which seems the same as the link in the explanation link you provided me above (although does not go into too much detail on my error ).
Bugcheck code 7F with BP1 parameter D is usually related to hardware such as CPU, RAM or Motherboard. A few cases maybe related to device drivers.
Refer the following cases, they maybe useful to solve your problem.
cpc2004, thanks for the links. I see that you are the local BSOD expert over in techspot
I tested the RAM with memtest and got no errors. I didn't think that there was anything related to heat or bloated/leaky capacitors... so I looked at what I installed recently - ZoneAlarm (and I had the windows firewall already up - don't ask). I managed to uninstall this in safe mode, and restarted and I got no BSOD (yet). If this was caused by software it may make a little sense as windows did crash consistently around 5 secs after getting to the login screen, when some services/software may be loading up. Sit tight and hope I don't start getting system crashes again...
Your version of ZA is at 2002 which almost 4 years behind. According to my record, several version of ZA is 2005 cause blue screen. Probably your version of ZA conflicts with other device drivers.
I am getting the PFN_LIST_CORRUPT exception again (dump) and the following application errors:
Faulting application , version 0.0.0.0, faulting module ntlanman.dll, version 5.1.2600.2180, fault address 0x000024f6.
Faulting application winlogon.exe, version 0.0.0.0, faulting module ntlanman.dll, version 5.1.2600.2180, fault address 0x000024f6.
Faulting application rundll32.exe, version 5.1.2600.2180, faulting module appwiz.cpl, version 5.1.2600.2180, fault address 0x00026a95.
I tested the RAM and did get 3 errors (http://www.possom.net/shared/DSC05417.JPG). Is it almost certain that the RAM is the cause of my errors? I have two sticks of 512 RAM, which one is causing the errors, or will I have to replace both?
With refer to my first post, over 40% of bugcheck 7F and BP1 0x'0d' is related to faulty ram. Bugcheck code 4E with BP1 0x'00000099' maybe related to bad memory slot or your motherboard is incompatible to the memory.
).
