I been having lots of BSOD's. I just need to know which line is the excpetion address in the dumpchk file so i can compare it to pstat and find the fauly device driver. heres 1 of many dmpchk's. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\>d: D:\>cd program files D:\Program Files>cd support tools D:\Program Files\Support Tools>dumpchk d11.dmp Loading dump file d11.dmp ----- 32 bit Kernel Mini Dump Analysis DUMP_HEADER32: MajorVersion 0000000f MinorVersion 00000a28 DirectoryTableBase 1d7c4000 PfnDataBase 80c51000 PsLoadedModuleList 8053e628 PsActiveProcessHead 80540658 MachineImageType 0000014c NumberProcessors 00000001 BugCheckCode 1000008e BugCheckParameter1 c0000005 BugCheckParameter2 000000b5 BugCheckParameter3 ef536cc8 BugCheckParameter4 00000000 PaeEnabled 00000000 KdDebuggerDataBlock 805305e0 MiniDumpFields 00000dff TRIAGE_DUMP32: ServicePackBuild 00000000 SizeOfDump 00010000 ValidOffset 0000fffc ContextOffset 00000320 ExceptionOffset 000007d0 MmOffset 00001068 UnloadedDriversOffset 000010a0 PrcbOffset 00001878 ProcessOffset 000024c8 ThreadOffset 00002720 CallStackOffset 00002978 SizeOfCallStack 000002c4 DriverListOffset 00002ed0 DriverCount 0000008d StringPoolOffset 000058b0 StringPoolSize 00001380 BrokenDriverOffset 00000000 TriageOptions 00000041 TopOfStack ef536d3c DebuggerDataOffset 00002c40 DebuggerDataSize 00000290 DataBlocksOffset 00006c30 DataBlocksCount 00000003 Windows XP Kernel Version 2600 UP Free x86 compatible Kernel base = 0x804d0000 PsLoadedModuleList = 0x8053e628 Debug session time: Fri Nov 19 22:47:09 2004 System Uptime: 0 days 1:10:08 start end module name 804d0000 8069b800 nt Checksum: 001D1157 Timestamp: Tue Oct 19 02: 03:29 2004 (417467E1) Unloaded modules: eea28000 eea4f000 kmixer.sys Timestamp: unavailable (00000000) ee9b5000 ee9cb000 hiber_atapi. Timestamp: unavailable (00000000) ee9cb000 eea28000 3C154G72.sys Timestamp: unavailable (00000000) eeac8000 eeaef000 kmixer.sys Timestamp: unavailable (00000000) ef19b000 ef1c2000 kmixer.sys Timestamp: unavailable (00000000) f8baf000 f8bb0000 drmkaud.sys Timestamp: unavailable (00000000) ef447000 ef454000 DMusic.sys Timestamp: unavailable (00000000) ef9ef000 ef9fd000 swmidi.sys Timestamp: unavailable (00000000) ef1c2000 ef1de000 aec.sys Timestamp: unavailable (00000000) f8a6c000 f8a6e000 splitter.sys Timestamp: unavailable (00000000) f888e000 f8895000 fdc.sys Timestamp: unavailable (00000000) f88c6000 f88cb000 flpydisk.sys Timestamp: unavailable (00000000) efc81000 efc97000 hiber_atapi. Timestamp: unavailable (00000000) efde9000 efdfd000 wdmaud.sys Timestamp: unavailable (00000000) f89de000 f89e2000 kbdhid.sys Timestamp: unavailable (00000000) f88ce000 f88d3000 Cdaudio.SYS Timestamp: unavailable (00000000) f89da000 f89dd000 Sfloppy.SYS Timestamp: unavailable (00000000) Finished dump check

Check the event viewer for the problem. Please post back within 24 hours or I will delete the post from my follow up list. Thanks. It would be a courtesy if you would post back and let us know if the fix worked or not.

The failing instruction is at 00000B5 which is at Windows low memory. Windows does not allow read and write to first 64K hence it fails with access violation C0000005. You have to examinate the stack trace in order to find out the culprit module issue the invalid branch. However the minidump only provides two to three stack trace and I don't think you can find out the culprit from the above information. I suggest you copy the content of all system event 1001 and paste back here so I can analyse them and give you some suggestion. Control Panel -> System Adminstrative Tools -> Event Viewer -> System -> Record 1001 (ie sysdump). Disable the auto-reboot when Windows crash. If BSOD occurs, it can show the failing module if the failing module is not ntoskrnl.exe (ie windows kernel). Note : the failing moudle may not be the culprit but they are very useful to find out culprit. Hope it can help you

Thanks per I will lookin to the Event view again on Friday when the machine comes home again .

Thanks Martin I will try your suggestion on Friday and post a result back.