[degenaro]

A few times each week, XP crashes. I've set up to take a kernel dump, attached below. Suggestions welcomed. (I've e-mailed seagate-maxtor, and have had no reply for 4 days).

Lou.

-----


Microsoft ® Windows Debugger Version 6.7.0005.0
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\KERNELMEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\WINDOWS\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jun 20 18:13:29.484 2007 (GMT-4)
System Uptime: 1 days 13:04:51.056
Loading Kernel Symbols
..................................................................................................................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Loading unloaded module list
........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {80000005, 8, 80000005, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+d0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 80000005, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: 80000005, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


WRITE_ADDRESS: 80000005

FAULTING_IP:
+ffffffff80000005
80000005 ?? ???

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: OneTouch.exe

TRAP_FRAME: b69afb40 -- (.trap 0xffffffffb69afb40)
ErrCode = 00000010
eax=841a26d8 ebx=841a26d8 ecx=01847691 edx=00000000 esi=841a278c edi=e3152b58
eip=80000005 esp=b69afbb4 ebp=b69afbc0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
80000005 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 8051f786 to 804f9f13

STACK_TEXT:
b69afac0 8051f786 00000050 80000005 00000008 nt!KeBugCheckEx+0x1b
b69afb28 80543908 00000008 80000005 00000000 nt!MmAccessFault+0x9a8
b69afb28 80000005 00000008 80000005 00000000 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
b69afbb0 841a26d8 00000000 00000000 b69afbe0 0x80000005
b69afbc0 805ef858 841f6020 837258d8 841a26d8 0x841a26d8
b69afbe0 805ba533 841a26d8 841a278c c0100080 nt!SeCreateAccessState+0x28
b69afc18 80574f33 00000000 00000000 768fa001 nt!ObOpenObjectByName+0x8f
b69afc94 805758aa 00f80ce4 c0100080 00f80c84 nt!IopCreateFile+0x407
b69afcf0 80577f76 00f80ce4 c0100080 00f80c84 nt!IoCreateFile+0x8e
b69afd30 805409ac 00f80ce4 c0100080 00f80c84 nt!NtCreateFile+0x30
b69afd30 7c90eb94 00f80ce4 c0100080 00f80c84 nt!KiFastCallEntry+0xfc
00f80cdc 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+d0
80543908 85c0 test eax,eax

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiTrap0E+d0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

FAILURE_BUCKET_ID: 0x50_W_nt!KiTrap0E+d0

BUCKET_ID: 0x50_W_nt!KiTrap0E+d0

Followup: MachineOwner
---------

[Advertisements]

Apart from the reference to a problem with the OneTouch backup program, I doubt many on this forum will be able to decipher the kernel dump data which is primarily intended for Microsoft tech staff. I suggest you visit the Seagate website to see if an updated OneTouch utility is available.

[pip22]

Apart from the reference to a problem with the OneTouch backup program, I doubt many on this forum will be able to decipher the kernel dump data which is primarily intended for Microsoft tech staff. I suggest you visit the Seagate website to see if an updated OneTouch utility is available.

[anzenketh]

I can read a little bit of the minidumps but I will need to view more of them to make a good probability decision.

Blue screen error messages are one of the most misunderstood error messages out there in regards to windows.According to Microsoft, only 5-20% of these errors are actually caused by the OS. Only 10% are hardware related. The other 70% are the result of faulty drivers or software incompatibility. Based on those numbers, less than 15% of blue screen errors can be permanently resolved with an OS reinstall.

So we can correctly solve this issue we need to get the minidumps.

To get the Minidumps do the following

1 > Create a new folder on the desktop and call it "dumpcheck" or whatever you like.
2 > Navigate to %systemroot%\minidump You can paste that address in address bar to get there. Then copy the last few minidump files to that folder.%systemroot% is normally c:\windows. They are numbered by date.
3 > Close the folder and right click on it and select Send to Compressed (zipped) Folder. Please do NOT compress them in .rar
4 > Use the "add reply" option upload that zip file here as an attachment.

Edited by tuxmaster, 26 June 2007 - 09:06 PM.