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.
have been having trouble with my PC for the last year with intermittent crashes (blue Screens). This can happen at anytime, but mostly after an hour or so of use. It occurs when I am on the net and off line and in any application. Also I can pretty much guaranty it will crash if I am on the pc for more than an hour or so when I switch users in XP.
When I go to the Microsoft web site I get that the crash is caused by a device driver.
We have tried everything as follows:
Wiped the pc altogether and loaded everything again (4 times)
Connected my NTL Broadband via Ethernet instead of USB (therefore no drivers)
Checked / updated all the drivers
Checked the heat during running
Checked the Hard Drive
Checked the Memory
Run Spybot and Addware
My friend took the pc to his house and wiped it clean and reloaded everything. It worked fine all the time playing dvdýs all night an did not crash at all. As soon as I had it back and connected to the net + the printer is started crashing.
I thought it could be the printer drivers, but I have deleted and re-installed from the HP website. Although I am a bit wary that it maybe the printer drivers. Has anyone had any problems with HP drivers and XP
Can anyone help ????
PC details are : (Made up PC)
AMD Athlon XP3000+ 2.17Ghz
512mb RAM
Motherboard = Gigabye K7 Triton 400 Series
Graphics = Nvidia GForce FX5200
XP Pro SP2
Printer = HP 1355 AIO
I get System Error 102
Event ID 1003
With error codes
1000000a, parameter1 826ee258, para 2 00000002, para 3, 00000000, para4 806ee2d6.
Also
1000000a, parameter1 65909409, para 2 00000002, para 3, 00000000, para4 804ee61e.
1000000a, parameter1 760c7d3b, para 2 00000002, para 3, 00000000, para4 804eb3eb.
Those are the last 3 errors on the log, Microsoft.com doesnýt help. Do you know where / how I can get info on these codes ?
Didn't find the information you thought to find? Check out these Similar Threads
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: f8966c2b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804eb972, address which referenced memory
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt.
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get MmPageSize (0x0) - probably bad symbols
f8966c2b
Your minidump is corrupted and it is the sign of hardware error (ie faulty RAM). Do you have another minidump or full dump?
HI,
Sorry to come back !
But I thought I cracked it by re-installing the HP printer drivers + taking loads of programs out of start up + opening the side of the case to make sure not overheating !!!
It has been working fine for some weeks now (the longest ever with know crashes). But !!! I have just installed some education software for my daughter called Web Land. It's an online magazine which is downloaded and worked on off line. It only has the amount of graphics you would get in a normal game. But as soon as we started to play the BSOD is back !
I have run MEMTEST & Hard drive diagnostics (all OK).
I have been told that Nvidia Geforce FX5200 card is not that good so I went on the Nvidia site and noticed there were newer drivers. Have now downloaded these but still get the BSOD every time I go into the WEB-LAND game.
Please see the below dump. Can anyone help !! do I need a new graphics card or a new pc alltogether.
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022706-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Mon Feb 27 22:51:15.765 2006 (GMT+0)
System Uptime: 0 days 0:06:44.312
Loading Kernel Symbols
........................................................................... .......................................
Loading User Symbols
Loading unloaded module list
........
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck A, {760c7d3b, 2, 0, 804eb3eb}
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+184 )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 760c7d3b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804eb3eb, address which referenced memory
Your windows have two culprits
1) Your version of ZoneAlarm has known software problem. De-install or upgrade ZA
2) Faulty ram. Run memtest to stress the ram.
Your windows have two culprits
1) Your version of ZoneAlarm has known software problem. De-install or upgrade ZA
2) Faulty ram. Run memtest to stress the ram.
Hi,
Sorry i am back agian !.
I re-installed ZA + got some new RAM (512mb samsung PC 3200 DDR400).
The pc runs fine untill I go into this childrens learning software, after about 5 minutes I get the crash. The first crash was exactly the same codes as before. Therefore I re-installed ZA again + put my other RAM back in as well. So now running on 1GB. Still crashed after 5 mins. The new dump is below.
Can you possibly help again. Thanks
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini030506-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sun Mar 5 15:24:43.421 2006 (GMT+0)
System Uptime: 0 days 0:04:52.998
Loading Kernel Symbols
........................................................................... .......................................
Loading User Symbols
Loading unloaded module list
.........
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 50, {a05560d5, 0, 8054a8e9, 0}
Could not read faulting driver name
Unable to load image \SystemRoot\system32\drivers\sysaudio.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for sysaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys
Unable to load image wdmaud.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for wdmaud.sys
*** ERROR: Module load completed but symbols could not be loaded for wdmaud.sys
Probably caused by : sysaudio.sys ( sysaudio+1fe7 )
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a05560d5, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8054a8e9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: a05560d5
FAULTING_IP:
nt!ExFreePoolWithTag+3c5
8054a8e9 f6050160558001 test byte ptr [nt!ExpPoolFlags+0x1 (80556001)],0x1
Your first bugcheck code is 0A and the latest bugcheck code is D1. The stack trace of both dumps are different. The latest minidump is also related to memory problem. Probably your new ram is incompatible with your m/b. Try downclock the ram. For problem isolation you had better de-install ZA as your version is very current. Maybe it is unstable. Install sygate firewall which is free.
Your first bugcheck code is 0A and the latest bugcheck code is D1. The stack trace of both dumps are different. The latest minidump is also related to memory problem. Probably your new ram is incompatible with your m/b. Try downclock the ram. For problem isolation you had better de-install ZA as your version is very current. Maybe it is unstable. Install sygate firewall which is free.
Hello again, I am now using Sunbelt Kerio Firewall (deleted ZA). Checked my new RAM before purchasing it is Samsung DDR 400 which the M/B instructions confirm is recommended. Looked at Bios for the clocking looks like its running at 333 and not 400.
So went into the Web-Land gome thing again - 5 Mintues crash with the 0A one.
Below Dump ! Can I assume the Firewall is OK now.
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini030506-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sun Mar 5 22:31:25.281 2006 (GMT+0)
System Uptime: 0 days 0:08:04.828
Loading Kernel Symbols
........................................................................... .......................................
Loading User Symbols
Loading unloaded module list
........
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck A, {760c7d3b, 2, 0, 804eb3eb}
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+184 )
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 760c7d3b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804eb3eb, address which referenced memory
Your latest dump also crashes with memory corruption and it is caused faulty memory. Faulty memory means faulty ram, cache memory of CPU or video memory. Forward your problem to Microsoft to confirm whether the problem is related to faulty memory or not.
BugCheck A, {760c7d3b, 2, 0, 804eb3eb}
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+184 )
