Dump Data ugCheck C2, {40, 0, 80000000, 0}

Help, I cannot seem to get the usb flash drive to work. It keeps crashing and giving me the BSOD.
Here is the debuglog.txt

Thank you,
Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


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

************************************************************************
WARNING: Dump file has inconsistent set-bit count. Data may be missing.
************************************************************************
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINNT;C:\WINNT\system32;C:\WINNT\system32\drivers
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
Product: WinNt
Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
Debug session time: Sun Aug 13 03:29:01.429 2006 (GMT-7)
System Uptime: 0 days 0:09:58.139
Loading Kernel Symbols
................Page 1b57 not present in the dump file. Type ".hh dbgerr004" for details
.......Page 1b67 not present in the dump file. Type ".hh dbgerr004" for details
..............................................Page 36c9 not present in the dump file. Type ".hh dbgerr004" for details
...........................................
Loading User Symbols

Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {40, 0, 80000000, 0}

Probably caused by : MountMgr.sys ( MountMgr!MountMgrMountedDeviceRemoval+110 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000040, Attempt to free usermode address to kernel pool
Arg2: 00000000, Starting address
Arg3: 80000000, Start of system address space
Arg4: 00000000, 0

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


FAULTING_IP:
MountMgr!MountMgrMountedDeviceRemoval+110
ed2944b6 53 push ebx

BUGCHECK_STR: 0xc2_40

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8046ac4d to 8046bb4b

STACK_TEXT:
bd3bdba0 8046ac4d 00000000 8046aae4 e4989d88 nt!MiFreePoolPages+0x79
bd3bdbcc 8046aaef 00000000 00000000 ed2944b6 nt!ExFreePoolWithTag+0xdb
bd3bdbd8 ed2944b6 00000000 ed290890 bd3bdc90 nt!ExFreePool+0xb
bd3bdbf4 ed293c1b e4989d88 e4989da0 80477e60 MountMgr!MountMgrMountedDeviceRemoval+0x110
bd3bdc0c 804a5fd4 bd3bdc7c e4989d88 8053225a MountMgr!MountMgrTargetDeviceNotification+0x29
bd3bdc18 8053225a bd3bdc94 80477e60 804019c8 nt!IopPnPHydraCallback+0xc
bd3bdc58 804a5312 ed293bf2 804a5fc8 bd3bdc94 nt!MmDispatchWin32Callout+0x4e
bd3bdcb4 8050d35e 804019d8 811f0810 00000000 nt!IopNotifyTargetDeviceChange+0x11a
bd3bdd3c 8050d70f 00000001 80063028 e2a74088 nt!PiProcessQueryRemoveAndEject+0x748
bd3bdd54 8050c499 bd3bdd74 8123a468 8047479c nt!PiProcessTargetDeviceEvent+0x33
bd3bdd78 80416bfa 8123a468 00000000 00000000 nt!PiWalkDeviceList+0xf7
bd3bdda8 80454ab6 8123a468 00000000 00000000 nt!ExpWorkerThread+0xae
bd3bdddc 804692a2 80416b4c 80000001 00000000 nt!PspSystemThreadStartup+0x54
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
MountMgr!MountMgrMountedDeviceRemoval+110
ed2944b6 53 push ebx

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: MountMgr

IMAGE_NAME: MountMgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3e401f53

SYMBOL_NAME: MountMgr!MountMgrMountedDeviceRemoval+110

FAILURE_BUCKET_ID: 0xc2_40_MountMgr!MountMgrMountedDeviceRemoval+110

BUCKET_ID: 0xc2_40_MountMgr!MountMgrMountedDeviceRemoval+110

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

eax=ffdff13c ebx=000000c2 ecx=00000001 edx=bd3bddcc esi=80474c60 edi=00000000
eip=8046bb4b esp=bd3bdb6c ebp=bd3bdba0 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00200286
nt!MiFreePoolPages+0x79:
8046bb4b 33c9 xor ecx,ecx
ChildEBP RetAddr Args to Child
bd3bdba0 8046ac4d 00000000 8046aae4 e4989d88 nt!MiFreePoolPages+0x79 (FPO: [Non-Fpo])
bd3bdbcc 8046aaef 00000000 00000000 ed2944b6 nt!ExFreePoolWithTag+0xdb (FPO: [Non-Fpo])
bd3bdbd8 ed2944b6 00000000 ed290890 bd3bdc90 nt!ExFreePool+0xb (FPO: [1,0,0])
bd3bdbf4 ed293c1b e4989d88 e4989da0 80477e60 MountMgr!MountMgrMountedDeviceRemoval+0x110 (FPO: [Non-Fpo])
bd3bdc0c 804a5fd4 bd3bdc7c e4989d88 8053225a MountMgr!MountMgrTargetDeviceNotification+0x29 (FPO: [2,0,3])
bd3bdc18 8053225a bd3bdc94 80477e60 804019c8 nt!IopPnPHydraCallback+0xc (FPO: [1,0,0])
bd3bdc58 804a5312 ed293bf2 804a5fc8 bd3bdc94 nt!MmDispatchWin32Callout+0x4e (FPO: [Non-Fpo])
bd3bdcb4 8050d35e 804019d8 811f0810 00000000 nt!IopNotifyTargetDeviceChange+0x11a (FPO: [Non-Fpo])
bd3bdd3c 8050d70f 00000001 80063028 e2a74088 nt!PiProcessQueryRemoveAndEject+0x748 (FPO: [Non-Fpo])
bd3bdd54 8050c499 bd3bdd74 8123a468 8047479c nt!PiProcessTargetDeviceEvent+0x33 (FPO: [Uses EBP] [1,0,4])
bd3bdd78 80416bfa 8123a468 00000000 00000000 nt!PiWalkDeviceList+0xf7 (FPO: [Non-Fpo])
bd3bdda8 80454ab6 8123a468 00000000 00000000 nt!ExpWorkerThread+0xae (FPO: [Non-Fpo])
bd3bdddc 804692a2 80416b4c 80000001 00000000 nt!PspSystemThreadStartup+0x54 (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start end module name
80062000 80072520 hal halacpi.dll Thu Mar 20 18:04:40 2003 (3E7A7338)
80400000 8059cd00 nt ntoskrnl.exe Fri Jun 16 00:04:41 2006 (44925809)
a0000000 a0190000 win32k win32k.sys Thu Oct 06 02:33:42 2005 (4344EF76)
bca48000 bca6c240 kmixer kmixer.sys Tue Apr 15 21:02:03 2003 (3E9CD5BB)
bcb85000 bcb98ac0 ipsec ipsec.sys Mon Apr 21 11:19:40 2003 (3EA4363C)
bd021000 bd05b5a0 srv srv.sys Thu Apr 20 09:54:35 2006 (4447BCCB)
bd084000 bd096e60 mqac mqac.sys Mon Oct 18 13:23:10 2004 (4174262E)
bd29c000 bd2adf80 wdmaud wdmaud.sys Tue Apr 15 21:23:02 2003 (3E9CDAA6)
bd326000 bd32e240 Fips Fips.SYS Tue May 09 08:28:29 2000 (39182E9D)
bd3c6000 bd3e5140 afd afd.sys Mon Apr 11 14:31:21 2005 (425AECA9)
bd436000 bd4900a0 BsUDF BsUDF.SYS Thu Oct 10 02:51:23 2002 (3DA54D9B)
bd4b9000 bd500320 ATMFD ATMFD.DLL Thu Jun 19 19:43:49 2003 (3EF274E5)
bd589000 bd5948c0 sysaudio sysaudio.sys Tue Apr 15 21:21:44 2003 (3E9CDA58)
bd872000 bdc7ec00 nv4_disp nv4_disp.dll Mon Oct 06 17:03:41 2003 (3F8202DD)
be9c1000 be9d6180 dump_atapi dump_atapi.sys Tue Apr 01 10:08:25 2003 (3E89D599)
be9ff000 bea64620 mrxsmb mrxsmb.sys Wed May 31 00:14:13 2006 (447D4245)
bea9f000 beac8a20 rdbss rdbss.sys Mon Jul 18 22:42:03 2005 (42DC92AB)
beac9000 beadcf00 savonaccesscontrol savonaccesscontrol.sys Thu Jan 05 07:43:42 2006 (43BD3EAE)
beadd000 beb07d00 netbt netbt.sys Fri Apr 01 17:23:24 2005 (424DF40C)
beb98000 beba7620 Udfs Udfs.SYS Thu Dec 02 19:37:25 2004 (41AFDF75)
beba8000 bebf6240 tcpip tcpip.sys Tue Apr 25 06:38:49 2006 (444E2669)
bfc37000 bfc613a0 update update.sys Tue Apr 15 21:22:01 2003 (3E9CDA69)
bfc7a000 bfc7dfe0 USBNEOD USBNEOD.SYS Wed Apr 10 05:38:02 2002 (3CB4322A)
bfc8a000 bfca0ba0 ndiswan ndiswan.sys Tue Apr 29 16:05:01 2003 (3EAF051D)
bfca1000 bfcc0d00 KS KS.SYS Wed Dec 04 09:09:38 2002 (3DEE36D2)
bfcc1000 bfce51e0 portcls portcls.sys Tue Apr 15 21:11:22 2003 (3E9CD7EA)
bfce6000 bfd11000 vinyl97 vinyl97.sys Tue Feb 01 00:39:02 2005 (41FF4026)
bfd11000 bfd32b20 USBPORT USBPORT.SYS Mon Mar 10 07:47:39 2003 (3E6CB39B)
bfd33000 bfd44000 Rtlnic Rtlnic.sys Thu Jul 15 23:20:16 2004 (40F773A0)
bfd44000 bfea9be0 nv4_mini nv4_mini.sys Mon Oct 06 16:56:53 2003 (3F820145)
bfeca000 bfedfbe0 Mup Mup.sys Thu Dec 02 19:37:23 2004 (41AFDF73)
bfee0000 bfef17c0 KSecDD KSecDD.sys Sat Sep 20 17:32:19 2003 (3F6CF193)
bfef2000 bff14ac0 Fastfat Fastfat.sys Tue Jul 19 03:44:42 2005 (42DCD99A)
Page 1b67 not present in the dump file. Type ".hh dbgerr004" for details
bff15000 bff37000 fltmgr fltmgr.sys unavailable (FFFFFFFE)
bff37000 bff4c180 atapi atapi.sys Tue Apr 01 10:08:25 2003 (3E89D599)
bff4d000 bff6e9c0 dmio dmio.sys Wed Jan 15 11:47:04 2003 (3E25BAB8)
bff6f000 bff8b5a0 ftdisk ftdisk.sys Thu Dec 02 19:29:58 2004 (41AFDDB6)
bff8c000 bffb5aa0 NDIS NDIS.SYS Tue Apr 29 16:05:01 2003 (3EAF051D)
bffb6000 bffd8000 SSIDRV SSIDRV.SYS Thu Aug 03 18:33:15 2006 (44D2A3DB)
bffd8000 bffffc20 ACPI ACPI.sys Wed Jan 15 11:44:22 2003 (3E25BA16)
ed000000 ed00e6a0 pci pci.sys Wed Jan 15 11:44:07 2003 (3E25BA07)
ed010000 ed01b680 isapnp isapnp.sys Wed Jan 15 11:43:47 2003 (3E25B9F3)
ed020000 ed029000 SSHRMD SSHRMD.SYS Thu Aug 03 18:33:22 2006 (44D2A3E2)
ed030000 ed038700 CLASSPNP CLASSPNP.SYS Wed Jan 15 11:42:51 2003 (3E25B9BB)
ed060000 ed06c4c0 VIDEOPRT VIDEOPRT.SYS Wed Jan 15 11:47:20 2003 (3E25BAC8)
ed070000 ed07b680 i8042prt i8042prt.sys Tue Apr 15 21:00:59 2003 (3E9CD57B)
ed080000 ed08c000 sskbfd sskbfd.sys Thu Aug 03 18:33:20 2006 (44D2A3E0)
ed090000 ed09d440 AFS2K AFS2K.SYS Mon Feb 25 15:05:13 2002 (3C7AC329)
ed0a0000 ed0ae180 Cdr4_2K Cdr4_2K.SYS Tue Sep 24 14:21:41 2002 (3D90D765)
ed0b0000 ed0bf400 serial serial.sys Tue Apr 15 21:19:39 2003 (3E9CD9DB)
ed0c0000 ed0cca80 rasl2tp rasl2tp.sys Tue Apr 29 16:05:06 2003 (3EAF0522)
ed0d0000 ed0dbc40 raspptp raspptp.sys Wed May 14 16:47:00 2003 (3EC2D574)
ed0e0000 ed0eea20 parallel parallel.sys Wed Jan 15 11:47:14 2003 (3E25BAC2)
ed0f0000 ed0f9be0 usbhub usbhub.sys Tue Mar 18 15:30:41 2003 (3E77AC21)
ed100000 ed10c160 usbhub20 usbhub20.sys Wed Jan 15 11:45:59 2003 (3E25BA77)
ed120000 ed129ce0 NDProxy NDProxy.SYS Thu Sep 30 16:25:35 1999 (37F3F16F)
ed130000 ed138fa0 Npfs Npfs.SYS Sat Oct 09 16:58:07 1999 (37FFD68F)
ed140000 ed148680 msgpc msgpc.sys Wed Jan 15 11:54:25 2003 (3E25BC71)
ed150000 ed1581a0 netbios netbios.sys Tue Oct 12 12:34:19 1999 (38038D3B)
ed170000 ed17c640 HPZid412 HPZid412.sys Fri Jan 03 05:25:01 2003 (3E158F2D)
ed270000 ed27f600 Cdfs Cdfs.SYS Fri Apr 01 17:23:36 2005 (424DF418)
ed280000 ed288000 SSFS0509 SSFS0509.SYS Thu Aug 03 18:33:18 2006 (44D2A3DE)
ed288000 ed28d520 PCIIDEX PCIIDEX.SYS Tue Feb 25 10:31:08 2003 (3E5BB66C)
ed290000 ed297140 MountMgr MountMgr.sys Tue Feb 04 12:15:15 2003 (3E401F53)
ed298000 ed29f720 disk disk.sys Wed Jan 15 11:43:05 2003 (3E25B9C9)
ed2a0000 ed2a5800 viaagp1 viaagp1.sys Wed Sep 26 11:05:51 2001 (3BB218FF)
ed2a8000 ed2ad320 USBSTOR USBSTOR.SYS Wed Jan 15 11:45:52 2003 (3E25BA70)
ed2c0000 ed2c7f40 uhcd uhcd.sys Wed Jan 15 11:45:50 2003 (3E25BA6E)
ed2c8000 ed2cfd00 wanarp wanarp.sys Fri Aug 16 05:25:01 2002 (3D5CEF1D)
ed2d8000 ed2dcfc0 USBD USBD.SYS Wed Jan 22 09:05:33 2003 (3E2ECF5D)
ed2e0000 ed2e52c0 HPZius12 HPZius12.sys Tue Feb 04 22:40:52 2003 (3E40B1F4)
ed2e8000 ed2ecc00 usbehci usbehci.sys Mon May 05 13:50:04 2003 (3EB6CE7C)
ed2f8000 ed2fd400 mouclass mouclass.sys Thu Feb 20 08:37:45 2003 (3E550459)
ed300000 ed306280 savonaccessfilter savonaccessfilter.sys Thu Jan 05 07:43:37 2006 (43BD3EA9)
ed308000 ed30dec0 kbdclass kbdclass.sys Thu Feb 20 08:37:30 2003 (3E55044A)
ed318000 ed31d460 usbprint usbprint.sys Wed Jan 15 11:44:07 2003 (3E25BA07)
ed328000 ed32e3a0 MxlW2k MxlW2k.SYS Wed Apr 30 11:02:40 2003 (3EB00FC0)
ed340000 ed346c40 cdrom cdrom.sys Wed Jan 15 11:43:04 2003 (3E25B9C8)
ed350000 ed355560 Cdralw2k Cdralw2k.SYS Tue Sep 24 14:20:49 2002 (3D90D731)
ed370000 ed376580 fdc fdc.sys Wed Jan 15 11:42:51 2003 (3E25B9BB)
ed388000 ed38e100 parport parport.sys Wed Jan 15 11:47:13 2003 (3E25BAC1)
ed3a8000 ed3ac400 ptilink ptilink.sys Wed Jan 15 11:47:15 2003 (3E25BAC3)
ed3b8000 ed3bc0e0 raspti raspti.sys Fri Oct 08 13:45:10 1999 (37FE57D6)
ed3d8000 ed3dca60 flpydisk flpydisk.sys Wed Jan 15 11:42:52 2003 (3E25B9BC)
ed3f8000 ed3fd900 HIDPARSE HIDPARSE.SYS Tue Apr 08 10:34:46 2003 (3E930836)
ed408000 ed40d240 Msfs Msfs.SYS Tue Oct 26 16:21:32 1999 (3816377C)
ed410000 ed412a20 BOOTVID BOOTVID.dll Wed Nov 03 17:24:33 1999 (3820E051)
ed414000 ed417e60 TDI TDI.SYS Wed Jan 15 11:56:26 2003 (3E25BCEA)
ed418000 ed41ad00 PartMgr PartMgr.sys Wed Jan 15 11:43:07 2003 (3E25B9CB)
ed478000 ed47b020 usbscan usbscan.sys Wed Jan 15 11:45:45 2003 (3E25BA69)
ed480000 ed483dc0 HPZipr12 HPZipr12.sys Fri Jan 03 05:25:03 2003 (3E158F2F)
ed48c000 ed48f640 serenum serenum.sys Wed Jan 15 11:47:01 2003 (3E25BAB5)
ed494000 ed496540 gameenum gameenum.sys Wed Jan 15 11:45:32 2003 (3E25BA5C)
ed49c000 ed49e2e0 ndistapi ndistapi.sys Wed Jan 15 11:54:15 2003 (3E25BC67)
ed4ac000 ed4ae600 viausb1 viausb1.sys Tue Sep 18 22:28:49 2001 (3BA82D11)
ed4d4000 ed4d7580 vga vga.sys Sat Sep 25 11:37:40 1999 (37ED1674)
ed500000 ed501d20 Diskperf Diskperf.sys Wed Feb 12 13:34:38 2003 (3E4ABDEE)
Page 1b57 not present in the dump file. Type ".hh dbgerr004" for details
ed502000 ed504000 dmload dmload.sys unavailable (FFFFFFFE)
ed504000 ed5056a0 viaide viaide.sys Wed Oct 17 23:11:14 2001 (3BCE7282)
ed512000 ed513ca0 Fs_Rec Fs_Rec.SYS Wed Jan 15 11:53:30 2003 (3E25BC3A)
ed51a000 ed51be40 rasacd rasacd.sys Sat Sep 25 11:41:23 1999 (37ED1753)
ed55a000 ed55b4a0 TICalc TICalc.SYS Sun Apr 18 18:29:53 1999 (371A8711)
ed5a4000 ed5a5860 ParVdm ParVdm.SYS Mon Sep 27 20:28:16 1999 (37F035D0)
ed5c8000 ed5c8f80 WMILIB WMILIB.SYS Sat Sep 25 11:36:47 1999 (37ED163F)
ed5c9000 ed5c9b00 pciide pciide.sys Wed Jan 15 11:43:03 2003 (3E25B9C7)
ed5ed000 ed5eda00 msmpu401 msmpu401.sys Sat Sep 25 11:35:15 1999 (37ED15E3)
ed5ef000 ed5efa40 audstub audstub.sys Sat Sep 25 11:35:33 1999 (37ED15F5)
ed5f8000 ed5f9000 swenum swenum.sys Wed Dec 04 09:10:07 2002 (3DEE36EF)
Page 36c9 not present in the dump file. Type ".hh dbgerr004" for details
ed606000 ed607000 Null Null.SYS unavailable (FFFFFFFE)
ed608000 ed608ee0 Beep Beep.SYS Wed Oct 20 15:18:59 1999 (380E3FD3)
ed60a000 ed60ab40 VIAPFD VIAPFD.SYS Mon Dec 17 22:45:02 2001 (3C1EE5EE)
ed60f000 ed60ff80 mnmdd mnmdd.SYS Sat Sep 25 11:37:40 1999 (37ED1674)
ed644000 ed644f80 dump_WMILIB dump_WMILIB.SYS Sat Sep 25 11:36:47 1999 (37ED163F)

Unloaded modules:
bd15f000 bd184000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bd529000 bd536000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bd539000 bd547000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
bdc6a000 bdc7f000 VGA.dll
Timestamp: unavailable (00000000)
Checksum: 00000000
bd872000 bdc7f000 nv4_disp.dll
Timestamp: unavailable (00000000)
Checksum: 00000000
ed160000 ed169000 redbook.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ed4cc000 ed4d0000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ed3e8000 ed3ed000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ed4c4000 ed4c7000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Help Please

Could anyone provide some insight please or point me to a debugging tutorial where I can teach myself how to help myself?

From what I can tell, it would seem the MS file mountmgr is the problem, but I have the latest version, and there doesn't seem to be any kb help at MS.

Please?

 

Removed USB in Safe Mode

Thanks for responding.
1. Did a lot of troubleshooting before posting.
2. I already tried to remove all USB in normal and safe mode, and allowing Win 2k to reinstall, but no difference.
3. I tried rolling back the mountmgr file, since on the hard drive I found all the versions back to 2002. Apparently everytime MS does update, it archives the old files. No difference though.
4. Do you agree the debugger file would indicate it is a problem with the mountmgr file?
5. Is there something else I should be looking at from the dump Data?
6. Is it time to call MS?

 

Memory isn't the problem

Again, THANK YOU, for responding and trying to help me.

I used both MS memory testing program and mem86.
Let them both run for 12 hours each, through multiple passes.
Nothing was discovered by either program.

I didn't replace the memory with other chips cause I presumed if it was a memory issue those programs would have found something.

Should I swap out the chips just to see? or would that be a waste of my time.

Regarding the mountmgr file describing the exact problem I am having with USB flash drives, I found this for windows2003 server, not win2k..

http://support.microsoft.com/kb/892926/en-us

Do you think this could be the same issue for both OS? or would the hot fix for 2003 not work on 2000. More importantly would they not give me the hotfix to try?

Also, I found a more recent file of mountmgr than 12/2004 in this KB
http://support.microsoft.com/kb/904564/en-us

It doesn't describe the problem I am having, but the files are much more recent then the ones on my machine. The file in this KB is 08/2005

When searching the internet, one of the other fixes someone tried was copying the file from one machine that was working to the one that wasn't, givent he OS's were the same, and it worked for him. Unfortunately, I don't have that option, and there was no link or email to request the file from that person, and the thread was already closed about 6 months ago.

Don't know what else to do.

Thoughts?

 

Thank YOU

I will do what you suggest, and let you know.

 

Crash Reproduced Here is the Latest Dump Data, Any Thoughts?

I posted and then I noticed the debug file said the same date and time of the session above, so I edited it and deleted it.

I don't know how to get the memory.dmp data to be new, while keeping the old. I unchecked the overwrite box, figuring like the minidump data, windows would just add a number to memory like memory1, then memory2, etc as more dumps were recorded, but that doesn't seem to be the case. I reproduced the crash 3 times, and no new data is written.

What am I doing wrong.
How do I get Win2k to write the memory dump each time and not delete the old memory.dmp data. I would think if I check the box to overwrite, then the memory.dmp file will only be the last, and there won't be a list/history of memory.dmp files to see what is happening as time goes on.

Can you help me please.

 

Memory.dmp

So your saying, manually, if I rename the file, the new file will be recorded as memory.dmp.

However, isn't there a way to have Windows2k do this like with the minidump files?

On the other machines that I don't have immediate access to, I would like to have a history of memory.dmp files so that by the time I can get some time to try and solve the problem, I can see a few of them to follow what was happening before I was called to check out the crash.

What is the "overwrite" check box for?
Isn't the "overwrite" check box action the same for minidumps and memory.dmp files?
i.e. meaning rename old file and record new file, if the box is uncheck or don't rename old file, just overwrite old file, if the box is checked.

I'm confused.
Isn't the purpose of the dump files to see what immediately happened with the current crash AND what happened before, that probably led up to the current crash?