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.
COULD SOMEONE PLEASE ANALYSE THIS DEBUG LOG. I UNDERSTAND IT IS A PROBLEM WITH WIN32K.SYS DRIVER. BASICALLY WHAT HAPPENS IS WHEN THE COMPUTER IS IDLE FOR AWHILE IT WILL CRASH AND REBOOT. RAN DEBUGWIZ AND HERE IS THE LOG. THANK YOU FOR YOUR HELP..OH AND HERE IS PC SETUP:
Intel P4 3.4Ghz (Hyperthreading enabled)
MSI 865PE NEO2-V MOBO
Dual Channel 1GB HyperX DDR400
ATI Radeon 9800Pro 128MB
2x 400GB Maxtor HDD's
Running Windows XP Pro Corp. SP2, with all current updates.
_________________________________________________________________
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini011906-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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Jan 19 14:41:15.859 2006 (GMT-5)
System Uptime: 0 days 12:14:23.547
Loading Kernel Symbols
........................................................................... ..............................................
Loading unloaded module list
...........
Loading User Symbols
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {f968a0bc, 1, 0, 804e8d6a}
Probably caused by : win32k.sys ( win32k!PALLOCMEM+2c )
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: f968a0bc, memory referenced
Arg2: 00000001, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804e8d6a, address which referenced memory
Thank you guys for your replies. I have run several stress tests. All conclude Mem is OK. Also, this comp has been recently formatted after similar problems pre-reformat. So, obviously we are looking at a hardware problem. I will submit debuglog to MS support and see what they say.
Also, after searching through the forums. I found one thread stating problems similar to mine stating "after resuming from idle with 2 hard drives freeze ups and crashes occur". I dont know??
Some faulty ram can pass memtest. Reseat the ram to another memory slot may resolve the problem. How often do you get the blue screen? Attach the debug report in this thread if you have another minidumps.
I just had another crash about 2 minutes ago. I was in the middle of a defrag when it happened. There are no Blue Screens, PC just reboots itself. Unfortunetly I cant reconnect to my PC via VNC now. I would like to get the new dump log but im stuck at work. I will post once I get back in or get back home.
I have tried reseating the mem. I just need to try some different RAM and see if problem occurs again. I was assuming it was a problem with the Onboard Sound at first because before recent reformat my PC would only crash while I was playing Battlefield 2. Screen would freeze and sound would echo. EA Support told me it was the sound, but what do they know . But, I dont know I am going to try new RAM tonight and I will let you know.
OK so hear is the new debuglog. Doesnt make sense to me:
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini012006-01.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
Mini Kernel Dump does not contain driver list
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri Jan 20 11:13:30.640 2006 (GMT-5)
System Uptime: 0 days 14:41:47.329
Mini Kernel Dump does not contain driver list
Debugger can not determine kernel base address
Loading Kernel Symbols
Mini Kernel Dump does not contain driver list
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {4, 2, 0, f88309b2}
***** Debugger could not find nt in module list, module list might be corrupt.
***** Followup with Debugger team
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Probably caused by : Unknown_Image
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f88309b2, address which referenced memory
Debugging Details:
------------------
***** Debugger could not find nt in module list, module list might be corrupt.
***** Followup with Debugger team
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000004
eax=8212a669 ebx=8218e0e0 ecx=00000000 edx=00000000 esi=8204f180 edi=00000039
eip=f88309b2 esp=805562e0 ebp=80556304 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
f88309b2 8b4104 mov eax,[ecx+0x4] ds:0023:00000004=????????
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
80556304 f806be14 8218e9dc 8204f180 82020c94 0xf88309b2
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
8055634c f806c55a 8218e028 8204f008 804e56fc 0xf806be14
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
805563a0 f8071ed0 8218e028 00000003 804e56fc 0xf806e98c
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
8055640c f8080128 8218e028 00000001 80560f00 0xf807ffb0
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
80556428 804dcd22 8218e64c 6b755044 00000000 0xf8080128
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
ffdff980 00000000 f8951000 00099015 00000000 0x804dcd22
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
start end module name
_________________________________________________________________
I erased about 300 lines of the "Mini Kernel Dump does not contain driver list"
Too long for post, but you get the point
OK, here is the latest debuglog:
Same thing reboot no, bluescreen
___________________________________________________________
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini012106-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) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Jan 21 18:38:07.656 2006 (GMT-5)
System Uptime: 0 days 1:04:09.343
Loading Kernel Symbols
........................................................................... ..............................................
Loading unloaded module list
........
Loading User Symbols
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, 82021cf0, 82021d88, a130005}
GetUlongFromAddress: unable to read from 8056a9f0
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+2c1 )
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 82021cf0, The pool entry we were looking for within the page.
Arg3: 82021d88, The next pool entry.
Arg4: 0a130005, (reserved)
Do ya think I have enough power. I have never had a problem with the PSU but. And I defenitely dont thinks its overheating.
Heres my setup:
Intel P4 3.4Ghz Prescott
MSI 865PE NEO2-V MOBO
Dual Channel 1GB HyperX DDR400
ATI Radeon 9800Pro 128MB
2x 400GB Maxtor HDD's
Thermaltake Tsunami Dream Case
couple extra fans
All of this is run on an Antec Blue Power 350Watt PSU.
Think thats enough power?
Havent switched the RAM out yet but I really think thats the source of the problem. Just ordered some new RAM. SO, I will see when it arrives.
Do ya think I have enough power. I have never had a problem with the PSU but. And I defenitely dont thinks its overheating.
Heres my setup:
Intel P4 3.4Ghz Prescott
MSI 865PE NEO2-V MOBO
Dual Channel 1GB HyperX DDR400
ATI Radeon 9800Pro 128MB
2x 400GB Maxtor HDD's
Thermaltake Tsunami Dream Case
couple extra fans
All of this is run on an Antec Blue Power 350Watt PSU.
Think thats enough power?
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: b8738000, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 8050389d, address which referenced memory
Your latest minidump is crashed at IRQL x'1c' which is the timer interrupt IRQL. Timer IRQL routine is a stable routine and it crashes only if hardware error. According to my record, I have 22 cases with confirmed culprit and 18 unconfirmed culprits (ie because the problem owners do not feed back the culprit and I hope you are not one of them). For the confirmed cases, 8 cases is ram, 6 cases is CPU and 3 cases is m/b.
Most probably the culprit is faulty ram. What firewall are you using?
Hello CPC,
Thanks again for the help. I have Windows XP firewall disabled. All I am using for security would be my Linksys Wireless Router (#WRT54G). I have Windows FWall disabled because it always gives me problems with VNC (which I use alot) and my FTP server.
Could that be a factor?
Do you think my ONBoard Sound could be a factor as well?