BSOS 0x7E

  • Thread starter Thread starter Charlie
  • Start date Start date
C

Charlie

My h/c daughter's computer running XP pro gets an 0x7E ((0xC0000005) BSOD at
shutdown. I have tried all that MS suggests that I have been able to find. My
son used this computer before he went to college - now he has his own. He
tapped into the hard drive to move stuff over. His new computer in not Intel,
so thought that was the problem. In the root, I was hoping to modify value
for "Intelppm". However, "Intelide" was the only thing I found. Modified from
0 to 4 anyway but that didn't help.
New Logitech keyboard/mouse - so reinstalled software with 3/4/09 release.
Encouraged by thee date but that didn't help either.
Some basic info - old Dell 4100 - came with Win98 - upgraded by a friend of
mine to XP Pro. I do not have CD.
Perhaps I need to go through each driver and update it? Yikes!
If it helps, here are the three codes I am dealing with
0xF7A719AC
0xF7B209B4
0xF7B206B0

kbdclass.sys - Address F7A719AC base at F7A71000

Cheese & crackers, if you know what that means you're far smarter than I.

Charlie
 
Sounds like memory,does pc have 3 memory sticks installed,if so try
switching them to diffrent slots.Also,try setting virtual memory to: "let
system
manage" click set 2X,close out.Another trick (this one does work),go to run,
type:regedit In regedit,expand:HKEY_CURRENT_USER/controlpanel/open
desktop,L.click on:AutoEndTasks Go to edit,modify,set to 1 From 0 Close
out
regedit.This simply ends processes sooner than xps lag time to shut down or
restart pc....One can alao download & run microsoft memory tester,get at:
http://oca.microsoft.com/en/windiag.asp
 
Andrew, thank you for your response. Two memory sticks, Switched them. No
help, Virtual memory reset as advised. Registry values reset.
The only thing that is different is that now I get a BSOD that says 0xD1.
I did try to go to http://oca.microsoft.com/en/windlag/asp but I couldn't
get there. Thought maybe you meant "winlag" so omitted the d but that was the
same.
I did try restoring the registry to a 4/28 set of values, thinking daughter
had installed something, but still get the 0xD1. Progress might have been
getting it back to 0x7E, but nooo. just joking.

Charlie
 
Back
Top