Guest Gary Roach Posted June 11, 2008 Posted June 11, 2008 I've got a computer with a crash problem that happens occasionally (approx. once a week). The minidump analysis is below. It seems to indicate a problem with the parallel port. Since this is not being used I disabled it in Windows. I want to know if there's any further action required. I'm waiting to see if the crash reoccurs. Thanks for any help. Microsoft ® Windows Debugger Version 6.9.0003.113 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [c:\windows\minidump\Mini061008-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\i386 Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt Built by: 2600.xpsp_sp2_gdr.070227-2254 Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620 Debug session time: Tue Jun 10 08:02:13.953 2008 (GMT-4) System Uptime: 0 days 1:47:13.522 Loading Kernel Symbols .................................................................................................................................................................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {aa06c8, 9, 1, f69ea3fb} Unable to load image \SystemRoot\system32\DRIVERS\i8042prt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for i8042prt.sys *** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys Probably caused by : i8042prt.sys ( i8042prt+3fb ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 00aa06c8, memory referenced Arg2: 00000009, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: f69ea3fb, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 00aa06c8 CURRENT_IRQL: 9 FAULTING_IP: i8042prt+3fb f69ea3fb ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: 80550284 -- (.trap 0xffffffff80550284) ErrCode = 00000002 eax=8055031b ebx=805503d0 ecx=00000002 edx=00000064 esi=8523e0d8 edi=85019918 eip=f69ea3fb esp=805502f8 ebp=8055031c iopl=0 nv up ei pl nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216 i8042prt+0x3fb: f69ea3fb ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from f69ea3fb to 804e187f STACK_TEXT: 80550284 f69ea3fb badb0d00 00000064 0000002e nt!KiTrap0E+0x233 WARNING: Stack unwind information not available. Following frames may be wrong. 805502f4 f69f1dc6 00000002 8055031b 8523e0e0 i8042prt+0x3fb 8055031c 804da915 85019918 8523e020 00010009 i8042prt+0x7dc6 8055031c f6a4bc46 85019918 8523e020 00010009 nt!KiInterruptDispatch+0x3d 805503d0 804dbb37 00000000 0000000e 00000000 processr!AcpiC1Idle+0x12 805503d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10 STACK_COMMAND: kb FOLLOWUP_IP: i8042prt+3fb f69ea3fb ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: i8042prt+3fb FOLLOWUP_NAME: MachineOwner MODULE_NAME: i8042prt IMAGE_NAME: i8042prt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: 0xD1_W_i8042prt+3fb BUCKET_ID: 0xD1_W_i8042prt+3fb Followup: MachineOwner --------- -- Gary Roach ADB Services
Guest John John (MVP) Posted June 11, 2008 Posted June 11, 2008 Re: Need minidump analyzed Gary Roach wrote: > I've got a computer with a crash problem that happens occasionally (approx. > once a week). The minidump analysis is below. It seems to indicate a problem > with the parallel port. i8042prt.sys is the Mouse/Keyboard driver for PS2 port. John
Guest Gerry Posted June 11, 2008 Posted June 11, 2008 Re: Need minidump analyzed Gary Try Start, Run, type "sfc /scannow" without quotes and hit Enter. Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe) http://support.microsoft.com/default.aspx?scid=kb;en-us;310747 You will need your Windows XP CD. You may encounter problems if your CD does not include SP3 as seems likely. Read this link as it contains a way forward if you have no CD http://ask-leo.com/i_dont_have_an_installation_cd_for_windows_xp_what_if_i_need_one.html If you need to point to a folder choose I386. -- Hope this helps. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ Gary Roach wrote: > I've got a computer with a crash problem that happens occasionally > (approx. once a week). The minidump analysis is below. It seems to > indicate a problem with the parallel port. Since this is not being > used I disabled it in Windows. I want to know if there's any further > action required. I'm waiting to see if the crash reoccurs. Thanks for > any help. > > Microsoft ® Windows Debugger Version 6.9.0003.113 X86 > Copyright © Microsoft Corporation. All rights reserved. > > > Loading Dump File [c:\windows\minidump\Mini061008-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\i386 > Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible > Product: WinNt > Built by: 2600.xpsp_sp2_gdr.070227-2254 > Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620 > Debug session time: Tue Jun 10 08:02:13.953 2008 (GMT-4) > System Uptime: 0 days 1:47:13.522 > Loading Kernel Symbols > ................................................................................................................................................................... > Loading User Symbols > Loading unloaded module list > ............ > ******************************************************************************* > * > * > * Bugcheck Analysis > * > * > * > ******************************************************************************* > > Use !analyze -v to get detailed debugging information. > > BugCheck D1, {aa06c8, 9, 1, f69ea3fb} > > Unable to load image \SystemRoot\system32\DRIVERS\i8042prt.sys, Win32 > error 0n2 > *** WARNING: Unable to verify timestamp for i8042prt.sys > *** ERROR: Module load completed but symbols could not be loaded for > i8042prt.sys > Probably caused by : i8042prt.sys ( i8042prt+3fb ) > > Followup: MachineOwner > --------- > > kd> !analyze -v > ******************************************************************************* > * > * > * Bugcheck Analysis > * > * > * > ******************************************************************************* > > 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: 00aa06c8, memory referenced > Arg2: 00000009, IRQL > Arg3: 00000001, value 0 = read operation, 1 = write operation > Arg4: f69ea3fb, address which referenced memory > > Debugging Details: > ------------------ > > > WRITE_ADDRESS: 00aa06c8 > > CURRENT_IRQL: 9 > > FAULTING_IP: > i8042prt+3fb > f69ea3fb ?? ??? > > CUSTOMER_CRASH_COUNT: 1 > > DEFAULT_BUCKET_ID: DRIVER_FAULT > > BUGCHECK_STR: 0xD1 > > TRAP_FRAME: 80550284 -- (.trap 0xffffffff80550284) > ErrCode = 00000002 > eax=8055031b ebx=805503d0 ecx=00000002 edx=00000064 esi=8523e0d8 > edi=85019918 > eip=f69ea3fb esp=805502f8 ebp=8055031c iopl=0 nv up ei pl nz > ac pe nc > cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 > efl=00010216 > i8042prt+0x3fb: > f69ea3fb ?? ??? > Resetting default scope > > LAST_CONTROL_TRANSFER: from f69ea3fb to 804e187f > > STACK_TEXT: > 80550284 f69ea3fb badb0d00 00000064 0000002e nt!KiTrap0E+0x233 > WARNING: Stack unwind information not available. Following frames may > be wrong. > 805502f4 f69f1dc6 00000002 8055031b 8523e0e0 i8042prt+0x3fb > 8055031c 804da915 85019918 8523e020 00010009 i8042prt+0x7dc6 > 8055031c f6a4bc46 85019918 8523e020 00010009 > nt!KiInterruptDispatch+0x3d 805503d0 804dbb37 00000000 0000000e > 00000000 processr!AcpiC1Idle+0x12 805503d4 00000000 0000000e 00000000 > 00000000 nt!KiIdleLoop+0x10 > > STACK_COMMAND: kb > > FOLLOWUP_IP: > i8042prt+3fb > f69ea3fb ?? ??? > > SYMBOL_STACK_INDEX: 1 > > SYMBOL_NAME: i8042prt+3fb > > FOLLOWUP_NAME: MachineOwner > > MODULE_NAME: i8042prt > > IMAGE_NAME: i8042prt.sys > > DEBUG_FLR_IMAGE_TIMESTAMP: 0 > > FAILURE_BUCKET_ID: 0xD1_W_i8042prt+3fb > > BUCKET_ID: 0xD1_W_i8042prt+3fb > > Followup: MachineOwner > ---------
Guest Gary Roach Posted June 11, 2008 Posted June 11, 2008 Re: Need minidump analyzed Oops! I was thinking the printer port for some reason. Any idea what to do about this crash problem? "John John (MVP)" <audetweld@nbnet.nb.ca> wrote in message news:%23dJAfH%23yIHA.4168@TK2MSFTNGP06.phx.gbl... > Gary Roach wrote: > >> I've got a computer with a crash problem that happens occasionally >> (approx. once a week). The minidump analysis is below. It seems to >> indicate a problem with the parallel port. > > i8042prt.sys is the Mouse/Keyboard driver for PS2 port. > > John >
Guest John John (MVP) Posted June 11, 2008 Posted June 11, 2008 Re: Need minidump analyzed Try Gerry's suggestion and do a sfc /scannow. John Gary Roach wrote: > Oops! I was thinking the printer port for some reason. Any idea what to do > about this crash problem? > > > "John John (MVP)" <audetweld@nbnet.nb.ca> wrote in message > news:%23dJAfH%23yIHA.4168@TK2MSFTNGP06.phx.gbl... > >>Gary Roach wrote: >> >> >>>I've got a computer with a crash problem that happens occasionally >>>(approx. once a week). The minidump analysis is below. It seems to >>>indicate a problem with the parallel port. >> >>i8042prt.sys is the Mouse/Keyboard driver for PS2 port. >> >>John >> > > >
Recommended Posts