Random Reboots II (Dump Data)

Finally a Stop that's not in the 0XA's. Did the special pool catch this one?

Mark

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\MEMORY_050411_0532.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 = 0x80480780
Debug session time: Mon Apr 11 05:30:21.953 2005 (GMT+12)
System Uptime: 1 days 15:40:19.635
Loading Kernel Symbols
................................................................................................Page 505f6 not present in the dump file. Type ".hh dbgerr004" for details
.
Loading unloaded module list
.......................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {8f, 2e7cd, 5b60d, 0}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+ae )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000008f, The free or zeroed page listhead is corrupt
Arg2: 0002e7cd, new page
Arg3: 0005b60d, old page
Arg4: 00000000, 0

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


OVERLAPPED_MODULE:

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x4E

LAST_CONTROL_TRANSFER: from 805464b2 to 804482e2

STACK_TEXT:
f681ba5c 805464b2 00000000 00000000 00000000 nt!MmZeroPageThread+0xae
f681bda8 80453a20 80087000 00000000 00000000 nt!Phase1Initialization+0xc32
f681bddc 804681f2 80545880 80087000 00000000 nt!PspSystemThreadStartup+0x54
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
nt!MmZeroPageThread+ae
804482e2 57 push edi

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MmZeroPageThread+ae

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41773335

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_nt!MmZeroPageThread+ae

BUCKET_ID: 0x4E_nt!MmZeroPageThread+ae

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

eax=ffdff13c ebx=0000004e ecx=89999e80 edx=0000000d esi=80064bd4 edi=0005b60d
eip=804482e2 esp=f681ba24 ebp=f681ba5c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!MmZeroPageThread+0xae:
804482e2 57 push edi
ChildEBP RetAddr Args to Child
f681ba5c 805464b2 00000000 00000000 00000000 nt!MmZeroPageThread+0xae (FPO: [Non-Fpo])
f681bda8 80453a20 80087000 00000000 00000000 nt!Phase1Initialization+0xc32 (FPO: [Non-Fpo])
f681bddc 804681f2 80545880 80087000 00000000 nt!PspSystemThreadStartup+0x54 (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start end module name

 

this looks like bad RAM. in light of the other stuff, it would be premature to think its a bad stick as opposed to some artifact of the bad driver we are chasing.

 

Thanks for the comment Joe. The RAM is new with the Motherboard + powersupply upgrade I did a few weeks ago to try and fix the problem. Maybe it's coincidence, and the problems before and after the motherboard upgrade are unrelated, but I think it's unlikely. I'm using the same graphics card and DVD burner now as before.

My suspicions are with the graphics card (NVIDIA GeForce FX5200), which I bought in January. At least one of the crashes was caused by the graphics card driver corrupting pool memory. I haven't caught a crash with a DE stop since I enabled the special pool, although the frequency of the crashes has reduced after I back rev'd the graphics card driver. It crashes every couple of days now instead of a couple of times every day. Do you reckon I should try going to the latest drivers again and try and catch one with the special pool?

Alternatively I could see if I can borrow another graphics card for a while.

By the way, there are no problems with the tests in DirectX Diagnostic tool.

Mark

 

Do you reckon I should try going to the latest drivers again and try and catch one with the special pool?

Well, thats up to you. It has been my experience that unless you can call up and talk like you debugged it, it can be challenging trying to engage hardware vendors with valid data.

Usually, I just tell people to fool around with the versions until they find a stable one, and then leave it alone. You rarely need the 'latest' driver.

 

Hi Joe,

I've left everything as is for now. Today I got this dump which looks like it got caught by the special pool. Can you see anything new from this?

Mark

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\MEMORY_050415_2006.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 = 0x804814c0
Debug session time: Fri Apr 15 20:04:00.015 2005 (GMT+12)
System Uptime: 0 days 21:26:18.686
Loading Kernel Symbols
....................................Page 183a5 not present in the dump file. Type ".hh dbgerr004" for details
...........................................................
Loading unloaded module list
................
Loading User Symbols
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {bfdf0fc8, bfdf0f2c, c1008031, 23}

Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+14d )

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

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: bfdf0fc8, address trying to free
Arg2: bfdf0f2c, address where bits are corrupted
Arg3: c1008031, (reserved)
Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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


OVERLAPPED_MODULE: nv4_disp

BUGCHECK_STR: 0xC1_23

SPECIAL_POOL_CORRUPTION_TYPE: 23

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8046aad4 to 805347cd

STACK_TEXT:
aeae4bf8 8046aad4 bfdf0fc8 3b9aca07 bfdf0fcc nt!MmFreeSpecialPool+0x14d
aeae4c24 8051b8cb bfdf0fc8 e24e4d43 80474360 nt!ExFreePoolWithTag+0x22
aeae4c38 8051b98b bfdf0fc8 80474360 80474360 nt!CmpDereferenceNameControlBlockWithLock+0x53
aeae4c48 8051bde2 bcebcfc0 80474360 8051bd3c nt!CmpCleanUpKcbCacheWithLock+0x1b
aeae4c54 8051bd3c e3b8dfa8 e3b8dfe0 80520b1f nt!CmpDereferenceKeyControlBlockWithLock+0x9a
aeae4c60 80520b1f e3b8dfa8 00000000 e5b4d9dc nt!CmpDereferenceKeyControlBlock+0x16
aeae4c74 804d5d96 e5b4d9e0 e5b4d9c8 b1a5cf50 nt!CmpDeleteKeyObject+0x4f
aeae4c90 8044e981 e5b4d9e0 e5b4c960 e5b4d9c8 nt!ObpRemoveObjectRoutine+0xd6
aeae4cb4 8044ecc0 aeae4d64 00adf050 b0155ee0 nt!ObfDereferenceObject+0x149
aeae4d58 80464f84 000000b0 75620b0e 636a7375 nt!NtClose+0x1f8
aeae4d58 77f828d3 000000b0 75620b0e 636a7375 nt!KiSystemService+0xc4
00adf044 7c2d1889 000000b0 7c2d18bf 00adf0a8 ntdll!NtClose+0xb
00adf054 7c2d184f 00adf06c 7c2d1918 00adf06c ADVAPI32!BaseRegCloseKeyInternal+0x4f
00adf05c 7c2d1918 00adf06c 63037bdb 000000b0 ADVAPI32!LocalBaseRegCloseKey+0x9
00adf064 63037bdb 000000b0 00000002 00adf5b0 ADVAPI32!RegCloseKey+0x74
00adf0a8 63027e29 00000002 0013d048 00000002 wininet!IE5_REGISTRYSET:etermineKeyPlacing+0xd8
00adf0b8 63027a65 00000002 0013d048 0013d048 wininet!IE5_REGISTRYSET::SetWorkingContainer+0x13
00adf840 63028a78 6307b01c 0013d048 00adf88c wininet!CConMgr::GetCacheConfigInfo+0x74
00adf858 63028a41 0013d048 63028a33 63028788 wininet!CConMgr::ConfigureCache+0x31
00adf860 63028a33 63028788 630036c1 00000001 wininet!CConMgr::Init+0x8
00adf868 630036c1 00000001 0000009c 00000000 wininet!CConMgr::CConMgr+0x2a
00adf88c 63013336 63027fa4 0000000e 6307af94 wininet!InitGlobals+0x13b
00adf890 63027fa4 0000000e 6307af94 00000000 wininet!GetUrlCacheHeaderData+0x5
00adf9cc 63006517 00adff74 63029cc5 00000001 wininet!GlobalDataInitialize+0x129
00adfa24 77fccef6 ffffffff 00130000 00136d40 wininet!InitAutodialModule+0x16
00adfa5c 77fcd045 00000258 00136d10 00000000 ntdll!RtlpFindAndCommitPages+0xa7
00adfa90 77fcc603 77fcc4c9 77fcc4e0 00000788 ntdll!RtlpExtendHeap+0x1cd
00000166 00000000 00000000 00000000 00000000 ntdll!RtlAllocateHeap+0x617


FOLLOWUP_IP:
nt!MmFreeSpecialPool+14d
805347cd 8b4dfc mov ecx,[ebp-0x4]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MmFreeSpecialPool+14d

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 42258bd8

STACK_COMMAND: kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_23_nt!MmFreeSpecialPool+14d

BUCKET_ID: 0xC1_23_nt!MmFreeSpecialPool+14d

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

eax=ffdff13c ebx=000000c1 ecx=bfdf0000 edx=00000030 esi=00000031 edi=c02ff7c0
eip=805347cd esp=aeae4bbc ebp=aeae4bf8 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!MmFreeSpecialPool+0x14d:
805347cd 8b4dfc mov ecx,[ebp-0x4] ss:0010:aeae4bf4=bfdf0000
ChildEBP RetAddr Args to Child
aeae4bf8 8046aad4 bfdf0fc8 3b9aca07 bfdf0fcc nt!MmFreeSpecialPool+0x14d (FPO: [Non-Fpo])
aeae4c24 8051b8cb bfdf0fc8 e24e4d43 80474360 nt!ExFreePoolWithTag+0x22 (FPO: [Non-Fpo])
aeae4c38 8051b98b bfdf0fc8 80474360 80474360 nt!CmpDereferenceNameControlBlockWithLock+0x53 (FPO: [1,0,2])
aeae4c48 8051bde2 bcebcfc0 80474360 8051bd3c nt!CmpCleanUpKcbCacheWithLock+0x1b (FPO: [1,0,2])
aeae4c54 8051bd3c e3b8dfa8 e3b8dfe0 80520b1f nt!CmpDereferenceKeyControlBlockWithLock+0x9a (FPO: [1,0,1])
aeae4c60 80520b1f e3b8dfa8 00000000 e5b4d9dc nt!CmpDereferenceKeyControlBlock+0x16 (FPO: [1,0,1])
aeae4c74 804d5d96 e5b4d9e0 e5b4d9c8 b1a5cf50 nt!CmpDeleteKeyObject+0x4f (FPO: [1,0,3])
aeae4c90 8044e981 e5b4d9e0 e5b4c960 e5b4d9c8 nt!ObpRemoveObjectRoutine+0xd6 (FPO: [Non-Fpo])
aeae4cb4 8044ecc0 aeae4d64 00adf050 b0155ee0 nt!ObfDereferenceObject+0x149 (FPO: [Non-Fpo])
aeae4d58 80464f84 000000b0 75620b0e 636a7375 nt!NtClose+0x1f8 (FPO: [Non-Fpo])
aeae4d58 77f828d3 000000b0 75620b0e 636a7375 nt!KiSystemService+0xc4 (FPO: [0,0] TrapFrame @ aeae4d64)
00adf044 7c2d1889 000000b0 7c2d18bf 00adf0a8 ntdll!NtClose+0xb (FPO: [1,0,0])
00adf054 7c2d184f 00adf06c 7c2d1918 00adf06c ADVAPI32!BaseRegCloseKeyInternal+0x4f (FPO: [Non-Fpo])
00adf05c 7c2d1918 00adf06c 63037bdb 000000b0 ADVAPI32!LocalBaseRegCloseKey+0x9 (FPO: [1,0,0])
00adf064 63037bdb 000000b0 00000002 00adf5b0 ADVAPI32!RegCloseKey+0x74 (FPO: [1,0,0])
00adf0a8 63027e29 00000002 0013d048 00000002 wininet!IE5_REGISTRYSET:etermineKeyPlacing+0xd8 (FPO: [Non-Fpo])
00adf0b8 63027a65 00000002 0013d048 0013d048 wininet!IE5_REGISTRYSET::SetWorkingContainer+0x13 (FPO: [1,0,2])
00adf840 63028a78 6307b01c 0013d048 00adf88c wininet!CConMgr::GetCacheConfigInfo+0x74 (FPO: [Non-Fpo])
00adf858 63028a41 0013d048 63028a33 63028788 wininet!CConMgr::ConfigureCache+0x31 (FPO: [EBP 0x00adf88c] [0,1,4])
00adf860 63028a33 63028788 630036c1 00000001 wininet!CConMgr::Init+0x8 (FPO: [0,0,1])
start end module name
00400000 0041f000 NDETECT NDETECT.EXE Wed Dec 15 09:22:42 2004 (41BF4B92)
63000000 63096000 wininet wininet.dll Wed Dec 08 13:36:55 2004 (41B64CA7)
70a70000 70ad6000 SHLWAPI SHLWAPI.dll Wed Dec 08 15:11:49 2004 (41B662E5)
71710000 71794000 COMCTL32 COMCTL32.dll Fri Aug 30 02:13:07 2002 (3D6E2BF3)
76620000 76630000 MPR MPR.DLL Wed Mar 24 14:17:02 2004 (4060EF9E)
77430000 77440000 MSASN1 MSASN1.DLL Wed Mar 24 14:17:00 2004 (4060EF9C)
77800000 7781e000 WINSPOOL WINSPOOL.DRV Fri Jun 20 14:43:41 2003 (3EF274DD)
779b0000 77a4b000 OLEAUT32 OLEAUT32.dll Fri Jun 20 14:43:41 2003 (3EF274DD)
77a50000 77b3f000 ole32 ole32.dll Fri Jan 14 14:27:08 2005 (41E71FEC)
77d30000 77da1000 RPCRT4 RPCRT4.DLL Fri Mar 12 10:29:21 2004 (4050DA31)
77e10000 77e6f000 USER32 USER32.dll Sat Mar 12 20:54:53 2005 (4232A04D)
77f40000 77f7b000 GDI32 GDI32.dll Fri Jun 18 11:05:28 2004 (40D223B8)
77f80000 77ffd000 ntdll ntdll.dll Wed Mar 24 14:16:59 2004 (4060EF9B)
78000000 78045000 msvcrt msvcrt.dll Wed Mar 12 07:55:17 2003 (3E6E3115)
782f0000 78535000 SHELL32 SHELL32.dll Fri Mar 04 19:57:01 2005 (422806BD)
7c2d0000 7c332000 ADVAPI32 ADVAPI32.dll Wed Mar 24 14:17:00 2004 (4060EF9C)
7c570000 7c623000 KERNEL32 KERNEL32.dll Fri Jun 18 11:05:28 2004 (40D223B8)
7c740000 7c7c7000 CRYPT32 CRYPT32.dll Wed Mar 24 14:17:00 2004 (4060EF9C)
80062000 80076100 hal halaacpi.dll Fri Mar 21 14:04:40 2003 (3E7A7338)
80400000 8059cb80 nt ntoskrnl.exe Wed Mar 02 22:48:08 2005 (42258BD8)
a0000000 a018ee40 win32k win32k.sys Sat Feb 19 13:28:34 2005 (42168832)
ad752000 ad762980 NAVENG NAVENG.Sys Wed Mar 16 09:35:44 2005 (42374720)
ad763000 ad7fbe20 NavEx15 NavEx15.Sys Wed Mar 16 09:51:30 2005 (42374AD2)
ae851000 ae87bc00 NAVAP NAVAP.SYS Sun Dec 09 11:59:59 2001 (3C129B6F)
ae926000 ae9483c0 Fastfat Fastfat.SYS Thu Jan 16 08:48:39 2003 (3E25BB17)
aebf1000 aec2cbc0 srv srv.sys Wed Apr 30 11:05:07 2003 (3EAF0523)
aec7a000 aec8bf80 wdmaud wdmaud.sys Wed Apr 16 16:23:02 2003 (3E9CDAA6)
aecfc000 aed0afe0 Cdfs Cdfs.SYS Wed Apr 16 15:58:53 2003 (3E9CD4FD)
aedae000 aedcb4a0 afd afd.sys Wed Apr 30 20:45:29 2003 (3EAF8D29)
aedec000 aedee780 CdaC15BA CdaC15BA.SYS Mon Apr 08 20:50:52 2002 (3CB159EC)
aee7c000 aee878c0 sysaudio sysaudio.sys Wed Apr 16 16:21:44 2003 (3E9CDA58)
aeeee000 af289100 nv4_disp nv4_disp.dll Fri Jun 11 09:32:04 2004 (40C8D354)
b0045000 b005a180 dump_atapi dump_atapi.sys Wed Apr 02 06:08:25 2003 (3E89D599)
b0083000 b00e7ca0 mrxsmb mrxsmb.sys Thu Jan 20 20:25:21 2005 (41EF5CE1)
b00fa000 b0123900 rdbss rdbss.sys Fri Dec 03 16:37:11 2004 (41AFDF67)
b0124000 b014be00 netbt netbt.sys Thu Jul 17 07:44:26 2003 (3F15AB1A)
b014c000 b015ca60 SYMEVENT SYMEVENT.SYS Wed May 14 17:45:43 2003 (3EC1D807)
b015d000 b019cda0 SYMTDI SYMTDI.SYS Sat Jan 22 18:55:40 2005 (41F1EADC)
b019d000 b01ef1a0 tcpip tcpip.sys Sat Feb 26 11:37:45 2005 (421FA8B9)
b12e2000 b130c3a0 update update.sys Wed Apr 16 16:22:01 2003 (3E9CDA69)
b1345000 b134a060 SYMREDRV SYMREDRV.SYS Sat Jan 22 18:58:32 2005 (41F1EB88)
b135d000 b1373ba0 ndiswan ndiswan.sys Wed Apr 30 11:05:01 2003 (3EAF051D)
b139c000 b13bbd00 KS KS.SYS Thu Dec 05 06:09:38 2002 (3DEE36D2)
b13bc000 b13e01e0 portcls portcls.sys Wed Apr 16 16:11:22 2003 (3E9CD7EA)
b13e1000 b140c000 vinyl97 vinyl97.sys Tue Feb 01 21:39:02 2005 (41FF4026)
b140c000 b142db20 USBPORT USBPORT.SYS Tue Mar 11 04:47:39 2003 (3E6CB39B)
b142e000 b16658c0 nv4_mini nv4_mini.sys Fri Jun 11 09:36:05 2004 (40C8D445)
b1686000 b1689580 vga vga.sys Sun Sep 26 06:37:40 1999 (37ED1674)
bfeae000 bfec3640 Mup Mup.sys Thu Jan 16 08:54:01 2003 (3E25BC59)
bfec4000 bfeedaa0 NDIS NDIS.sys Wed Apr 30 11:05:01 2003 (3EAF051D)
bfeee000 bff705a0 Ntfs Ntfs.sys Sat May 10 07:46:45 2003 (3EBC05A5)
bff71000 bff827c0 KSecDD KSecDD.sys Sun Sep 21 12:32:19 2003 (3F6CF193)
bff83000 bff98180 atapi atapi.sys Wed Apr 02 06:08:25 2003 (3E89D599)
bff99000 bffba9c0 dmio dmio.sys Thu Jan 16 08:47:04 2003 (3E25BAB8)
bffbb000 bffd7220 ftdisk ftdisk.sys Tue Apr 01 10:21:58 2003 (3E88BF86)
bffd8000 bffffc20 ACPI ACPI.sys Thu Jan 16 08:44:22 2003 (3E25BA16)
f6400000 f640e6a0 pci pci.sys Thu Jan 16 08:44:07 2003 (3E25BA07)
f6410000 f641b680 isapnp isapnp.sys Thu Jan 16 08:43:47 2003 (3E25B9F3)
f6420000 f6428700 CLASSPNP CLASSPNP.SYS Thu Jan 16 08:42:51 2003 (3E25B9BB)
f6450000 f645c4c0 VIDEOPRT VIDEOPRT.SYS Thu Jan 16 08:47:20 2003 (3E25BAC8)
f6460000 f646a600 fetnd5bv fetnd5bv.sys Fri Jan 28 18:57:51 2005 (41F9D45F)
f6470000 f647f400 serial serial.sys Wed Apr 16 16:19:39 2003 (3E9CD9DB)
f6480000 f648b680 i8042prt i8042prt.sys Wed Apr 16 16:00:59 2003 (3E9CD57B)
f6490000 f649ca80 rasl2tp rasl2tp.sys Wed Apr 30 11:05:06 2003 (3EAF0522)
f64a0000 f64abc40 raspptp raspptp.sys Thu May 15 11:47:00 2003 (3EC2D574)
f64b0000 f64bea20 parallel parallel.sys Thu Jan 16 08:47:14 2003 (3E25BAC2)
f64c0000 f64c9be0 usbhub usbhub.sys Wed Mar 19 11:30:41 2003 (3E77AC21)
f64d0000 f64dc160 usbhub20 usbhub20.sys Thu Jan 16 08:45:59 2003 (3E25BA77)
f64f0000 f64f9ce0 NDProxy NDProxy.SYS Fri Oct 01 11:25:35 1999 (37F3F16F)
f6500000 f6508fa0 Npfs Npfs.SYS Sun Oct 10 12:58:07 1999 (37FFD68F)
f6510000 f6518680 msgpc msgpc.sys Thu Jan 16 08:54:25 2003 (3E25BC71)
f6520000 f65281a0 netbios netbios.sys Wed Oct 13 08:34:19 1999 (38038D3B)
f65f0000 f65f8240 Fips Fips.SYS Wed May 10 03:28:29 2000 (39182E9D)
f6680000 f6685520 PCIIDEX PCIIDEX.SYS Wed Feb 26 07:31:08 2003 (3E5BB66C)
f6688000 f668f4c0 MountMgr MountMgr.sys Wed Feb 11 08:47:53 2004 (40293569)
f6690000 f6697720 disk disk.sys Thu Jan 16 08:43:05 2003 (3E25B9C9)
f6698000 f669ed00 viaagp1 viaagp1.sys Wed Jul 02 22:19:52 2003 (3F02B1C8)
f66b0000 f66b4a60 flpydisk flpydisk.sys Thu Jan 16 08:42:52 2003 (3E25B9BC)
f66c0000 f66c5200 iviaspi iviaspi.sys Thu Sep 11 18:36:53 2003 (3F601805)
f66d0000 f66d6c40 cdrom cdrom.sys Thu Jan 16 08:43:04 2003 (3E25B9C8)
f66d8000 f66dff40 uhcd uhcd.sys Thu Jan 16 08:45:50 2003 (3E25BA6E)
f66e0000 f66e6a20 EFS EFS.SYS Thu Jan 16 08:46:55 2003 (3E25BAAF)
f66f0000 f66f4fc0 USBD USBD.SYS Thu Jan 23 06:05:33 2003 (3E2ECF5D)
f6700000 f6704c00 usbehci usbehci.sys Tue May 06 08:50:04 2003 (3EB6CE7C)
f6710000 f6715240 Msfs Msfs.SYS Wed Oct 27 12:21:32 1999 (3816377C)
Page 183a5 not present in the dump file. Type ".hh dbgerr004" for details
f6720000 f6727000 fdc fdc.sys unavailable (FFFFFFFE)
f6730000 f6737d00 wanarp wanarp.sys Sat Aug 17 00:25:01 2002 (3D5CEF1D)
f6738000 f673e100 parport parport.sys Thu Jan 16 08:47:13 2003 (3E25BAC1)
f6748000 f674d400 mouclass mouclass.sys Fri Feb 21 05:37:45 2003 (3E550459)
f6758000 f675dec0 kbdclass kbdclass.sys Fri Feb 21 05:37:30 2003 (3E55044A)
f6760000 f6765460 usbprint usbprint.sys Thu Jan 16 08:44:07 2003 (3E25BA07)
f6778000 f677c400 ptilink ptilink.sys Thu Jan 16 08:47:15 2003 (3E25BAC3)
f6788000 f678c0e0 raspti raspti.sys Sat Oct 09 09:45:10 1999 (37FE57D6)
f6810000 f6812a20 BOOTVID BOOTVID.dll Thu Nov 04 14:24:33 1999 (3820E051)
f6814000 f6816d00 PartMgr PartMgr.sys Thu Jan 16 08:43:07 2003 (3E25B9CB)
f6874000 f6876880 pfc pfc.sys Sat Sep 20 11:47:22 2003 (3F6B958A)
f6880000 f6883640 serenum serenum.sys Thu Jan 16 08:47:01 2003 (3E25BAB5)
f688c000 f688e2e0 ndistapi ndistapi.sys Thu Jan 16 08:54:15 2003 (3E25BC67)
f689c000 f689fe60 TDI TDI.SYS Thu Jan 16 08:56:26 2003 (3E25BCEA)
f68a8000 f68aa900 vulfntr vulfntr.sys Wed Nov 13 22:34:04 2002 (3DD21C8C)
f6900000 f6901d20 Diskperf Diskperf.sys Thu Feb 13 10:34:38 2003 (3E4ABDEE)
f6902000 f6903b80 dmload dmload.sys Thu Jan 16 08:47:06 2003 (3E25BABA)
f6904000 f69056a0 viaide viaide.sys Thu Oct 18 19:11:14 2001 (3BCE7282)
f6910000 f6911ca0 Fs_Rec Fs_Rec.SYS Thu Jan 16 08:53:30 2003 (3E25BC3A)
f6918000 f6919e40 rasacd rasacd.sys Sun Sep 26 06:41:23 1999 (37ED1753)
f6972000 f6973860 ParVdm ParVdm.SYS Tue Sep 28 15:28:16 1999 (37F035D0)
f69c8000 f69c8f80 WMILIB WMILIB.SYS Sun Sep 26 06:36:47 1999 (37ED163F)
f69c9000 f69c9b00 pciide pciide.sys Thu Jan 16 08:43:03 2003 (3E25B9C7)
f69ec000 f69ecf80 dump_WMILIB dump_WMILIB.SYS Sun Sep 26 06:36:47 1999 (37ED163F)
f69ed000 f69eda40 audstub audstub.sys Sun Sep 26 06:35:33 1999 (37ED15F5)
f69f7000 f69f8000 swenum swenum.sys Thu Dec 05 06:10:07 2002 (3DEE36EF)
f6a08000 f6a089e0 Null Null.SYS Sun Sep 26 06:34:58 1999 (37ED15D2)
f6a0a000 f6a0aee0 Beep Beep.SYS Thu Oct 21 11:18:59 1999 (380E3FD3)
f6a0d000 f6a0df80 mnmdd mnmdd.SYS Sun Sep 26 06:37:40 1999 (37ED1674)

Unloaded modules:
ad5bb000 ad5e0000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad72d000 ad752000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad72d000 ad752000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad72d000 ad752000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ae87c000 ae915000 NavEx15.Sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ae915000 ae926000 NAVENG.Sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ae28f000 ae2b4000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ae73c000 ae761000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
aec2d000 aec52000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6630000 f663d000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6620000 f662e000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
af275000 af28a000 VGA.dll
Timestamp: unavailable (00000000)
Checksum: 00000000
aeeee000 af28a000 nv4_disp.dll
Timestamp: unavailable (00000000)
Checksum: 00000000
f6530000 f6539000 redbook.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f66f8000 f66fd000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f68c4000 f68c7000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Hello... You are SO far over my head on this that I'm looking behind myself on the floor to see if I see my brain sitting there...

First trip out of the hardware forum and my head is spinning!

On what I'm going to suggest I have to admit that I scrolled through the dumps and may have missed a reference to this that was already there. I don't follow a thing on the dumps but I do know a bit about hardware...

I believe it was said that video drivers were updated. I also believe that the origional install drivers were re-installed. Now I do know that going back on drivers does not mean that ALL of the updated drivers are disabled or rewritten. Looking from a hardware direction I would suggest flashing the bios with the most current and re-installing the updated video drivers.

With the high level of the discusion here the above has probably already been done but it's a thought.

 

Thanks for your suggestion Jay. I didn't go to that length when I re-installed the old drivers. I just uninstalled the NVIDIA Drivers from Add/Remove Programs in the Control Panel. I restarted and then re-installed the original drivers.

There's a tab in the display properties that lists the files and versions being used by the graphics card driver:

nv4_disp.dll version 6.14.10.6136
nv4_mini.sys version 6.14.10.6136
nvoglnt.dll version 6.14.10.6136
nvcpl.dll version 6.14.10.6136
nview.dll version 6.14.10.6136
nvshell.dll version 6.14.10.6136
nvwdmcpl.dll version 6.14.10.6136

This version (6.1.3.6) is the original one that came on CD with the hardware. Seeing these files all reference that version, is it still necesary to flash the bios and re-install, do you think? (I've never flashed the bios before and I'm worried about stuffing it up!!)

Mark

 

You will always hear horror stories about flashing bios but I've done it many, many times without ever getting a failure. Just make sure to check the board's site and follow instructions exactly. From boards I've been working with it would seem that most makes have automated the flashing. Download the flash, run it to make a bootable floppy, boot from that floppy and run the bios updater. Will probably even allow you to make a backup of your old bios first in case there is a problem and you need to go back.

One note... NEVER flash a bios on a stormy day! A power outage durring a flash can cause you real problems.

On the thought that DM is showing all the proper drivers from the origional install... Dosen't mean that there are not artifacts left over from the updated install. Some of these could still be hooked into the system.

Since the posts you were sending were so far over my head it would be a real ego boost if I solved your problem!

If you want to send me the board manufacturer, model number and so on I'll check it out and see if there is likely to be a problem flashing. If the bios happens to be Award, you should be in like Flint!

 

Hi Jay, I have to admit, it's all a bit over my head too... I just want to get my PC sorted and I'm happy to consider any educated advice! The motherboard is an ECS K8T800-A v1.0. I've just had a look on the ECS website and I see that the BIOS can be updated with the AWARD Flash Utility. Would you recommend the DOS or Windows version? (The DOS methods looks a little clearer to me...) Also, what happens to the other drivers? Would they all need to be re-installed too?

(It would still be nice to know for sure whether it is the graphics card driver that's causing the problems...!)

Mark

 

I would assume that the windows version of the flash utility just makes a boot floppy for you. If not, use the dos version. And if your going to flash might as well do it all and check to be sure you have the latest board drivers.

As far as any device drivers the flash shouldn't have any effect on them. But after the bios and board drivers are all up to date I would probably reinstall the updated video drivers.

 

I'll give it a go and let you know if it makes a difference...

Mark