Solved: driver pains, nv4_disp.dll bsods Code: System information: AMD Athlon 64 X2 AM2 MSI K9N SLI motherboard nForce 570 MCP chipset, onboard audio and network. Corsair Valueselect 3GB DDR2 533MHz dual channel XFX Geforce 7600GT 256MB PCIe windows xp pro 32bit sp2 Hi everyone I just registered because I can't seem to get help anywhere else for this problem. it's, i think, the classic nvidia bsod infinite loop hell thing. I have a neat and clean running installation of xp pro sp2 (32bit) 6 months and counting, I didn't update my drivers in that time, don't fix it if it aint broken. But since some recent games had some less then expected performance and driver details mentioned that I decided it was time to do a whopping update from 93.x to the latest 163.75. I regret this decision on a daily basis now and can't seem to get it fixed. Here's what happened. I removed the driver using the software add/remove paneland rebooted in safe mode. ran sweeper and rebooted. bsod or stays black and never continues to desktop. a lot of cursing later, reboot in safe mode, install drivers reboot. working again.. humm okay. ran some games, sweet bioshock improved a bunch. my other new game (I bought a couple after a long pause in gaming) settlers 6, not as much luck. bsod nv4_disp.dll loops at certain points in the game. very recreatable. after testing other games and adding crysis to my new additions and playing thatwithout issues I concluded it must be settlers 6. I even tested crysis on max details, although it was a slideshow, it was a stable slideshow lol. now things have gotten worse. more games have started to act up now, I finished crysis by now without hitches, started a new black and white 2 profile (I have more ram since I last played it and was in the mood for it so i thought I give it a go again) it works great on max res max settings. finally. but yesterday black and white 2 crashed nv4 bsod... for some reason at the end of land 3, curiously settlers 6 seems to crash at certain specific points too (the first time you add a guard to wood delivery mission). I guess there is something wrong with the drivers still then.. weird though that it seems to rear it's ugly mug in certain games at certain points in those games though. also decided it was time to upgrade my nforce drivers.. maybe that's an issue with the new forceware or something. I didn't clean those first seeing as what happened after cleaning forceware, somewhere during setup of the new nforce drivers it hang.. -sigh- despite this everything was in working order after hitting reset. now for the forceware, this time manual cleaning without sweeper. -uninstall display drivers -hardware -> remove display device (just hoping I guess) -safe mode -remove nv4_disp.dll from system32 -purposely left the registry cleaning this time to isolate any problem -reboot... bsod kernel_data_inpage_error stop: 0x0000007A win32k.sys -reboot safe mode, cancel new hardware, install drivers -sigh- reboot normal, everything seems fine again. now settlers 6 is unchanged, crashing at the same points, black and white 2 same but add a crash with crysis now aswell. I don't have complete dumps or bsod messages atm, I will post one once I recreate a crash again. basicly I'm getting the bsod mentioned above after removing the drivers and rebooting and nv4_disp.dll infinite loop errors when my driver is insalled and 'working' it only seems to affect 3D (games), I can toil with photoshop for days if I want without issues etc. I have one example of one of the early loop crashes in settlers 6 which apart from the nasty crash tendency cleaning the display driver brought the problem to my attention: Code: Opened log file 'c:\debuglog.txt' 0: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols 0: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q Loading Kernel Symbols ........................................................................................................................................... Loading User Symbols Loading unloaded module list ................... Unable to load image nv4_disp.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nv4_disp.dll *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: bfb12f60, The address that the exception occurred at Arg3: b6db8c38, Exception Record Address Arg4: b6db8934, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt. FAULTING_IP: nv4_disp+13ff60 bfb12f60 8b4154 mov eax,dword ptr [ecx+54h] EXCEPTION_RECORD: b6db8c38 -- (.exr 0xffffffffb6db8c38) .exr 0xffffffffb6db8c38 ExceptionAddress: bfb12f60 (nv4_disp+0x0013ff60) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000054 Attempt to read from address 00000054 CONTEXT: b6db8934 -- (.cxr 0xffffffffb6db8934) .cxr 0xffffffffb6db8934 eax=00000000 ebx=e46d8c20 ecx=00000000 edx=00000000 esi=e46d8c80 edi=e249eb70 eip=bfb12f60 esp=b6db8d00 ebp=e46b4b40 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nv4_disp+0x13ff60: bfb12f60 8b4154 mov eax,dword ptr [ecx+54h] ds:0023:00000054=???????? .cxr Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: Settlers6.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt. READ_ADDRESS: 00000054 BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from bfb125c9 to bfb12f60 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b6db8cfc bfb125c9 e249e800 e46d8c80 e46b4b40 nv4_disp+0x13ff60 b6db8dac 805ce84c 88c8fa60 00000000 00000000 nv4_disp+0x13f5c9 b6db8ddc 8054535e b9c00fb0 e4201e10 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: nv4_disp+13ff60 bfb12f60 8b4154 mov eax,dword ptr [ecx+54h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nv4_disp+13ff60 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nv4_disp IMAGE_NAME: nv4_disp.dll DEBUG_FLR_IMAGE_TIMESTAMP: 470588d1 STACK_COMMAND: .cxr 0xffffffffb6db8934 ; kb FAILURE_BUCKET_ID: 0x7E_nv4_disp+13ff60 BUCKET_ID: 0x7E_nv4_disp+13ff60 Followup: MachineOwner --------- eax=00000000 ebx=e46d8c20 ecx=00000000 edx=00000000 esi=e46d8c80 edi=e249eb70 eip=bfb12f60 esp=b6db8d00 ebp=e46b4b40 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nv4_disp+0x13ff60: bfb12f60 8b4154 mov eax,dword ptr [ecx+54h] ds:0023:00000054=???????? ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. b6db8cfc bfb125c9 e249e800 e46d8c80 e46b4b40 nv4_disp+0x13ff60 b6db8dac 805ce84c 88c8fa60 00000000 00000000 nv4_disp+0x13f5c9 b6db8ddc 8054535e b9c00fb0 e4201e10 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo]) 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 start end module name 804d7000 806e3000 nt ntkrpamp.exe Mon Oct 30 10:50:10 2006 (4545CAD2) 806e3000 80703d00 hal halmacpi.dll Mon Oct 30 10:50:16 2006 (4545CAD8) b2a82000 b2aabf00 kmixer kmixer.sys Wed Aug 04 08:07:46 2004 (41107D32) b2aac000 b2aec380 HTTP HTTP.sys Wed Aug 04 08:00:09 2004 (41107B69) b63b0000 b63b2180 RivaTuner32 RivaTuner32.sys Fri Aug 04 09:36:13 2006 (44D2F8ED) b6690000 b66e2180 srv srv.sys Wed Aug 04 08:14:44 2004 (41107ED4) b67ab000 b67d2f00 secdrv secdrv.sys Tue Aug 31 15:42:55 2004 (4134805F) b68e8000 b68ead00 vstor2 vstor2.sys Fri Mar 23 18:02:01 2007 (46040809) b6900000 b6942400 atksgt atksgt.sys Fri Sep 15 12:17:58 2006 (450A7DD6) b696b000 b69d2500 vmx86 vmx86.sys Wed May 02 06:10:13 2007 (46380F25) b69e3000 b69e6100 vstor2_ws60 vstor2-ws60.sys Mon Apr 09 22:44:20 2007 (461AA5A4) b6bb0000 b6bc4400 wdmaud wdmaud.sys Wed Aug 04 08:15:03 2004 (41107EE7) b6bf5000 b6c00000 hcmon hcmon.sys Wed May 02 06:39:31 2007 (46381603) b70a6000 b70be980 dump_nvata dump_nvata.sys Tue Apr 25 02:52:25 2006 (444D72C9) b70e7000 b70f6900 Cdfs Cdfs.SYS Wed Aug 04 08:14:09 2004 (41107EB1) b7107000 b7115d80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004 (41107F1A) b7187000 b724fa60 avg7core avg7core.sys Wed Oct 10 18:23:39 2007 (470CFC8B) b7250000 b72be380 mrxsmb mrxsmb.sys Wed Aug 04 08:15:14 2004 (41107EF2) b72bf000 b72ea180 rdbss rdbss.sys Wed Aug 04 08:20:05 2004 (41108015) b72eb000 b7326000 vmm vmm.sys Sun Feb 18 09:10:42 2007 (45D80A02) b7326000 b7347d00 afd afd.sys Wed Aug 04 08:14:13 2004 (41107EB5) b7360000 b7362900 Dxapi Dxapi.sys Fri Aug 17 22:53:19 2001 (3B7D843F) b7370000 b7397c00 netbt netbt.sys Wed Aug 04 08:14:36 2004 (41107ECC) b7398000 b73b8f00 ipnat ipnat.sys Wed Aug 04 08:04:48 2004 (41107C80) b73b9000 b73d9000 NVTcp NVTcp.sys Wed Mar 22 22:23:49 2006 (4421C065) b73d9000 b7430a80 tcpip tcpip.sys Wed Aug 04 08:14:39 2004 (41107ECF) b7431000 b7443400 ipsec ipsec.sys Wed Aug 04 08:14:27 2004 (41107EC3) b74c7000 b74caa00 kbdhid kbdhid.sys Wed Aug 04 07:58:33 2004 (41107B09) b74cf000 b74d2000 mouhid mouhid.sys Fri Aug 17 22:47:57 2001 (3B7D82FD) b74d7000 b74d9580 hidusb hidusb.sys Fri Aug 17 23:02:16 2001 (3B7D8658) b74f3000 b7514700 portcls portcls.sys Tue Mar 16 19:58:17 2004 (40574E49) b7515000 b791cb80 RtkHDAud RtkHDAud.sys Wed Nov 15 07:34:28 2006 (455AB4F4) b9a1d000 b9a1ff00 ws2ifsl ws2ifsl.sys Fri Aug 17 22:55:58 2001 (3B7D84DE) b9ae5000 b9b18200 update update.sys Wed Aug 04 07:58:32 2004 (41107B08) b9b19000 b9b49100 rdpdr rdpdr.sys Wed Aug 04 08:01:10 2004 (41107BA6) b9b4a000 b9b60680 ndiswan ndiswan.sys Wed Aug 04 08:14:30 2004 (41107EC6) b9b61000 b9bc8000 ace4wpwi ace4wpwi.SYS Thu Jul 26 03:06:01 2007 (46A7F379) b9bc8000 b9bdb780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 08:07:04 2004 (41107D08) b9bdc000 ba265740 nv4_mini nv4_mini.sys Fri Oct 05 02:47:27 2007 (4705899F) ba266000 ba2b9000 NVSNPU NVSNPU.SYS Wed Mar 22 22:23:16 2006 (4421C044) ba2b9000 ba3bdf00 NVNRM NVNRM.SYS Wed Mar 22 22:23:39 2006 (4421C05B) ba3be000 ba3e3000 HDAudBus HDAudBus.sys Sat Jan 08 02:07:15 2005 (41DF3243) ba3e3000 ba405680 ks ks.sys Wed Aug 04 08:15:20 2004 (41107EF8) ba40e000 ba410a00 VMNET VMNET.SYS Fri Mar 16 11:05:31 2007 (45FA6BEB) ba412000 ba414680 vmnetadapter vmnetadapter.sys Fri Mar 16 11:06:08 2007 (45FA6C10) ba416000 ba419c80 mssmbios mssmbios.sys Wed Aug 04 08:07:47 2004 (41107D33) ba41a000 ba41c280 rasacd rasacd.sys Fri Aug 17 22:55:39 2001 (3B7D84CB) ba42e000 ba450e80 USBPORT USBPORT.SYS Wed Aug 04 08:08:34 2004 (41107D62) ba451000 ba461180 serial serial.sys Wed Aug 04 08:15:51 2004 (41107F17) ba4d2000 ba4ec580 Mup Mup.sys Wed Aug 04 08:15:20 2004 (41107EF8) ba4ed000 ba519a80 NDIS NDIS.sys Wed Aug 04 08:14:27 2004 (41107EC3) ba51a000 ba5a6480 Ntfs Ntfs.sys Wed Aug 04 08:15:06 2004 (41107EEA) ba5a7000 ba5bd780 KSecDD KSecDD.sys Wed Aug 04 07:59:45 2004 (41107B51) ba5be000 ba5cff00 sr sr.sys Wed Aug 04 08:06:22 2004 (41107CDE) ba5d0000 ba5ee780 fltMgr fltMgr.sys Wed Aug 04 08:01:17 2004 (41107BAD) ba5ef000 ba607980 nvata nvata.sys Tue Apr 25 02:52:25 2006 (444D72C9) ba608000 ba61f480 atapi atapi.sys Wed Aug 04 07:59:41 2004 (41107B4D) ba620000 ba645900 dmio dmio.sys Wed Aug 04 08:07:13 2004 (41107D11) ba646000 ba664b00 ftdisk ftdisk.sys Fri Aug 17 22:52:41 2001 (3B7D8419) ba665000 ba675a80 pci pci.sys Wed Aug 04 08:07:45 2004 (41107D31) ba676000 ba6a4080 ACPI ACPI.sys Wed Aug 04 08:07:35 2004 (41107D27) ba6a5000 ba6bc800 SCSIPORT SCSIPORT.SYS Wed Aug 04 07:59:39 2004 (41107B4B) ba6bd000 ba7a7000 sptd sptd.sys Mon Jun 18 23:13:19 2007 (4676F56F) ba8a8000 ba8b0e00 isapnp isapnp.sys Fri Aug 17 22:58:01 2001 (3B7D8559) ba8b8000 ba8c2500 MountMgr MountMgr.sys Wed Aug 04 07:58:29 2004 (41107B05) ba8c8000 ba8d5180 VolSnap VolSnap.sys Wed Aug 04 08:00:14 2004 (41107B6E) ba8d8000 ba8e0e00 disk disk.sys Wed Aug 04 07:59:53 2004 (41107B59) ba8e8000 ba8f4200 CLASSPNP CLASSPNP.SYS Wed Aug 04 08:14:26 2004 (41107EC2) ba918000 ba928000 AmdK8 AmdK8.sys Sun Jul 02 07:39:38 2006 (44A75C1A) ba938000 ba940d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 08:08:18 2004 (41107D52) ba9e8000 ba9f2380 imapi imapi.sys Wed Aug 04 08:00:12 2004 (41107B6C) ba9f8000 baa04180 cdrom cdrom.sys Wed Aug 04 07:59:52 2004 (41107B58) baa08000 baa16200 redbook redbook.sys Wed Aug 04 07:59:34 2004 (41107B46) baa18000 baa21000 nvnetbus nvnetbus.sys Wed Mar 22 22:24:01 2006 (4421C071) baa28000 baa37000 VMNetSrv VMNetSrv.sys Wed Jan 24 13:05:29 2007 (45B74B89) baa38000 baa44880 rasl2tp rasl2tp.sys Wed Aug 04 08:14:21 2004 (41107EBD) baa48000 baa52200 raspppoe raspppoe.sys Wed Aug 04 08:05:06 2004 (41107C92) baa58000 baa63d00 raspptp raspptp.sys Wed Aug 04 08:14:26 2004 (41107EC2) baa68000 baa71f00 termdd termdd.sys Wed Aug 04 07:58:52 2004 (41107B1C) baa78000 baa87000 AmdTools AmdTools.sys Wed Jun 07 21:15:29 2006 (448725D1) baa88000 baa96000 AmdLLD AmdLLD.sys Wed Nov 01 21:42:12 2006 (454906A4) baa98000 baaa1480 NDProxy NDProxy.SYS Fri Aug 17 22:55:30 2001 (3B7D84C2) baaa8000 baab6100 usbhub usbhub.sys Wed Aug 04 08:08:40 2004 (41107D68) baab8000 baac4e00 NVENETFD NVENETFD.sys Wed Mar 22 22:23:58 2006 (4421C06E) baac8000 baad6b80 drmk drmk.sys Wed Aug 04 08:07:54 2004 (41107D3A) baad8000 baae0900 msgpc msgpc.sys Wed Aug 04 08:04:11 2004 (41107C5B) baae8000 baaf0700 wanarp wanarp.sys Wed Aug 04 08:04:57 2004 (41107C89) baaf8000 bab00700 netbios netbios.sys Wed Aug 04 08:03:19 2004 (41107C27) bab18000 bab20900 Fips Fips.SYS Sat Aug 18 03:31:49 2001 (3B7DC585) bab28000 bab2e200 PCIIDEX PCIIDEX.SYS Wed Aug 04 07:59:40 2004 (41107B4C) bab30000 bab34900 PartMgr PartMgr.sys Sat Aug 18 03:32:23 2001 (3B7DC5A7) bab38000 bab3ce20 PxHelp20 PxHelp20.sys Mon Apr 25 21:48:02 2005 (426D4972) bab68000 bab6ca80 Msfs Msfs.SYS Wed Aug 04 08:00:37 2004 (41107B85) bab78000 bab7c880 TDI TDI.SYS Wed Aug 04 08:07:47 2004 (41107D33) bab80000 bab87880 Npfs Npfs.SYS Wed Aug 04 08:00:38 2004 (41107B86) bab88000 bab8c580 ptilink ptilink.sys Fri Aug 17 22:49:53 2001 (3B7D8371) bab90000 bab95480 vmnetbridge vmnetbridge.sys Fri Mar 16 11:06:36 2007 (45FA6C2C) bab98000 bab9c080 raspti raspti.sys Fri Aug 17 22:55:32 2001 (3B7D84C4) baba8000 babac680 lirsgt lirsgt.sys Sun Jan 29 12:06:18 2006 (43DCA1AA) babc0000 babc7b80 usbccgp usbccgp.sys Wed Aug 04 08:08:45 2004 (41107D6D) babf8000 babfd500 point32 point32.sys Wed Nov 08 08:02:34 2006 (4551810A) bac18000 bac1ec80 avg7rsxp avg7rsxp.sys Tue Jan 30 16:08:42 2007 (45BF5F7A) bac40000 bac44780 vmnetuserif vmnetuserif.sys Wed May 02 06:41:19 2007 (4638166F) bac48000 bac4e280 kbdclass kbdclass.sys Wed Aug 04 07:58:32 2004 (41107B08) bac50000 bac57000 nvport nvport.sys Sat May 06 04:20:59 2006 (445C080B) bac70000 bac75c00 mouclass mouclass.sys Wed Aug 04 07:58:32 2004 (41107B08) bac80000 bac84280 usbohci usbohci.sys Wed Aug 04 08:08:34 2004 (41107D62) bac88000 bac8c500 watchdog watchdog.sys Wed Aug 04 08:07:32 2004 (41107D24) bac98000 bac9e180 HIDPARSE HIDPARSE.SYS Wed Aug 04 08:08:15 2004 (41107D4F) baca8000 bacad200 vga vga.sys Wed Aug 04 08:07:06 2004 (41107D0A) bacb0000 bacb6800 usbehci usbehci.sys Wed Aug 04 08:08:34 2004 (41107D62) bacb8000 bacbb000 BOOTVID BOOTVID.dll Fri Aug 17 22:49:09 2001 (3B7D8345) bad84000 bad87180 MTictwl MTictwl.sys Mon Jun 11 04:03:18 2007 (466CAD66) bad88000 bad8bc80 serenum serenum.sys Wed Aug 04 07:59:06 2004 (41107B2A) bad8c000 bad8f700 VMkbd VMkbd.sys Wed May 02 06:52:21 2007 (46381905) bad90000 bad92580 ndistapi ndistapi.sys Fri Aug 17 22:55:29 2001 (3B7D84C1) bada0000 bada2680 pfc pfc.sys Sat Sep 28 00:53:07 2002 (3D94E153) bada8000 bada9b80 kdcom kdcom.dll Fri Aug 17 22:49:10 2001 (3B7D8346) badaa000 badab100 WMILIB WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B) badac000 badad700 dmload dmload.sys Fri Aug 17 22:58:15 2001 (3B7D8567) badc2000 badc3100 swenum swenum.sys Wed Aug 04 07:58:41 2004 (41107B11) badcc000 badcd280 USBD USBD.SYS Fri Aug 17 23:02:58 2001 (3B7D8682) badd6000 badd7f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 22:49:37 2001 (3B7D8361) badda000 baddb080 Beep Beep.SYS Fri Aug 17 22:47:33 2001 (3B7D82E5) bade0000 bade1080 mnmdd mnmdd.SYS Fri Aug 17 22:57:28 2001 (3B7D8538) bade4000 bade5080 RDPCDD RDPCDD.sys Fri Aug 17 22:46:56 2001 (3B7D82C0) bae00000 bae01080 avg7rsw avg7rsw.sys Tue Jul 26 14:10:51 2005 (42E6284B) bae10000 bae11100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 23:07:23 2001 (3B7D878B) bae4a000 bae4b360 avgtdi avgtdi.sys Thu Aug 25 11:59:58 2005 (430D969E) bae58000 bae59a00 000 000.fcl Thu May 04 04:21:48 2006 (4459653C) bae70000 bae70d00 pciide pciide.sys Fri Aug 17 22:51:49 2001 (3B7D83E5) baf5e000 baf5ec00 audstub audstub.sys Fri Aug 17 22:59:40 2001 (3B7D85BC) baf92000 baf92d00 dxgthk dxgthk.sys Fri Aug 17 22:53:12 2001 (3B7D8438) bafbe000 bafbeb80 Null Null.SYS Fri Aug 17 22:47:39 2001 (3B7D82EB) bafc2000 bafc2f80 avgclean avgclean.sys Tue Aug 22 00:55:15 2006 (44EA39D3) bf800000 bf9c0400 win32k win32k.sys Wed Aug 04 08:17:30 2004 (41107F7A) bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 08:00:51 2004 (41107B93) bf9d3000 bff56f80 nv4_disp nv4_disp.dll Fri Oct 05 02:44:01 2007 (470588D1) bff70000 bff72480 vga_bff70000 vga.dll Thu Sep 06 22:26:40 2001 (3B97DC00) bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 10:02:50 2004 (4110982A) Unloaded modules: b13dd000 b1407000 kmixer.sys Timestamp: unavailable (00000000) Checksum: 00000000 b41b4000 b41de000 kmixer.sys Timestamp: unavailable (00000000) Checksum: 00000000 b5859000 b5883000 kmixer.sys Timestamp: unavailable (00000000) Checksum: 00000000 b58cd000 b58f7000 kmixer.sys Timestamp: unavailable (00000000) Checksum: 00000000 b6b63000 b6b8d000 kmixer.sys Timestamp: unavailable (00000000) Checksum: 00000000 baf41000 baf42000 drmkaud.sys Timestamp: unavailable (00000000) Checksum: 00000000 b6c45000 b6c52000 DMusic.sys Timestamp: unavailable (00000000) Checksum: 00000000 b6b8d000 b6bb0000 aec.sys Timestamp: unavailable (00000000) Checksum: 00000000 b6c55000 b6c63000 swmidi.sys Timestamp: unavailable (00000000) Checksum: 00000000 bae5c000 bae5e000 splitter.sys Timestamp: unavailable (00000000) Checksum: 00000000 b69bf000 b69d3000 Parport.SYS Timestamp: unavailable (00000000) Checksum: 00000000 ba9d8000 ba9e6000 i8042prt.sys Timestamp: unavailable (00000000) Checksum: 00000000 bab08000 bab12000 processr.sys Timestamp: unavailable (00000000) Checksum: 00000000 bad98000 bad9c000 kbdhid.sys Timestamp: unavailable (00000000) Checksum: 00000000 bac88000 bac8d000 Cdaudio.SYS Timestamp: unavailable (00000000) Checksum: 00000000 bad78000 bad7b000 Sfloppy.SYS Timestamp: unavailable (00000000) Checksum: 00000000 bac68000 bac6d000 Flpydisk.SYS Timestamp: unavailable (00000000) Checksum: 00000000 bac50000 bac57000 Fdc.SYS Timestamp: unavailable (00000000) Checksum: 00000000 bac60000 bac66000 point32.sys Timestamp: unavailable (00000000) Checksum: 00000000 Closing open log file c:\debuglog.txt ps. since a lot of quality guides mention removing the dll not even when in safe mode but simply after deinstalling the display driver I tried that aswell, it results in windows crashing seconds/minutes after removal. I have not had a single issue with this relatively newly built rig or windows setup in the 6 months I've owned it untill I decided to upgrade my forceware drivers for bioshock. The start it seems to me was the very unexpected driver cleaning causing crashes (removing manual, sweeper or even just only the dll will make xp inoperable untill you install forceware again in safemode.) this issue has me completely frustrated, i'm not a new player in the field and usually used to being the guy to call if you have a problem, but this has got me flustered. I can't find anything wrong, no conflicts or any reports of any kind in my device manager or anywhere else that I have found. One last thing I thought of is the extra ram although huge files in photoshop, finishing crysis and so on did not seem to have issues with it I will run a memtest somewhere today (will have to go buy empty cd's to brun a bootable memtest first) but I doubt its the ram. if it were then why doesn't it crash anywhere else but in 3d games and when cleaning the display driver before installing a new one. also since when does xp bsod because some device has no driver. that's a first in all my years. I was expecting a new hardware found window on boot, not a blue screen. other things checked: complete virus scan, defrag, different graphics settings in games, registry cleaning, multiple attempt at a troublefree removal/clean and reinstall of drivers. I don't like formats, formats should always be a last resort (since formatting is not the same as fixing/learning) but I would right now. But will have to wait to get more back-up space. some stuff I can't back-up yet due to size and can't lose either. wil have to see about borrowing a second hd to do that. can't afford a purchase atm. I'm sure I missed something or screwed chronology slightly since i've been toiling with this for a few days now. (but it started with wanting to upgrade for bioshock, the crash after cleaning was the first symptom). if anyone finds this familiar or has any idea apart from formatting just quite yet. please..
there are 3 reasons for what is happening to you, the first one would be your PSU is about to give up the ghost and or failing so it isn't providing proper power to your vga card and causing all your troubles. the second reason would be your Ram and one of the sticks or even both of them are failing. third reason could be the nforce drivers specifically the Network ones, normally when you install the drivers for teh network it installs NAM (nvidia Armor firewall thing) and that's one of the biggest culprits of BSOD in windows messing with everything including your 3d card drivers so when you try to install the network and it asks to install the NAM thing cancel or do not accept it see what happend. that's all i can recommend, but i'm sure it'll end up being your PSU failing, either borrow one from a friend and try it or take a leap of faith and buy a new one.
I seriously hope it's not my psu. I cant really afford any purchases atm. Also that would be weird though. none of the hardware is older then those 6 months mentioned inc the psu (430w cooler master extreme power), I never had any issues prior to uninstalling the old forceware drivers. and despite the driver uninstall crash (replicates every single time) and crashes in settlers, it let me play through crysis completely, and for long sessions. The nam thing you have mentioned, i will try that. For some reason the specific symptoms, especially issues uninstalling forceware (which was the first symptom) make me lean toward this being the problem, or at least something with the driver anyway. I did notice in my searches for this I often see the combo of nforce and geforce mentioned. my chipset doesn't even have the hw firewall but nforce drivers insal it anyway. will try this in a coupe of hours when im back home. any suggestion on how to proceed to uninstall nforce and forceware. preferably without a bsod after cleaning the drivers lol. (i've been in computers my whole life, i have never seen removing the old nv4_disp.dll cause crashes, but then I never had an nforce mobo/geforce card combo before either). Thanks for your answer, you are one of the few that i've seen giving some helpfull idea's and not recycling cr*p that's already been said over and over and more often then not, doesn't make any sense at all. about hw issues, wouldn't the problem be more widespread then just a handfull of 3d games (although it spread to crysis afterfiddling with driver installs some more.. hmm again that driver) other things im doing which push the system (and ram e.g.) that i do: graphics design, opening and editing huge 300dpi images in photoshop eating up most of my ram while doing that. no issues. black and white 2, no issues up to land 3 (consistent) settlers 6, no issues up to the 3rd or 4th campaign mission only at certain points (e.g. sending out my first guarded wood transport) (consistent) bioshock, no issues as of yet. simcity societies, no issues (except for being the lamest sim something game ever imho) other things I tried: nvidia stress test, no issue; Performancetest benchmark, no issue. any other desktop stuff (music, video, multitasking photoshop, notepad, music, sketchup, a download in the background and msn, no issues) anyway ill uninstall all my nvidia drivers through add/remove later to try what you said, wondering if I should even attempt running sweeper or cleaning manually after. I still need to get an empty cd to do a proper memtest86, will see to getting one asap, or else ill just sacrifice a dvdr (seems such a wast burning an mbyte on to a 4.7 gig dvd lol) Edit: come to think of it, I must have a smart psu then, consistently crashing everytime I remove nv4_disp.dll after add/remove-ing the display driver. Tested 10 times, it's consistent. If it's my PSU wouldn't it be more random? I can recreate the crashes I have without fail by repeating what lead to the crash. This leads me to hope for your nam suggestion. I'm home now, I'm going to try to simply remove that piece first. see if it helps. If not I will reinstall all my nforce and geforce drivers but without that part and again see what happens.
question, maybe my logic is failing me here. a faulty ra stick, could that cause such specific and recreatable crashes? I would think crashes would be random. I think one of my month old ram sticks might be causing it, memtest did display some errors but I did not have time to extensively test it yet to see which stick it is specifically. If a faulty ram stick can cause the very specific settlers crash and driver removal crash then I might just be in luck, i'm still within the time that I can simply go back to the store and not have to call corsair etc. ow well and if it's not the cause it will be the cause of something some day. I'll test the sticks soon as i have time for it and post here if it fixed all the issues after replacing it.
ok... I downloaded memtest86 latest version, burnt the image to a bootable cd, and let it check my ram yesterday, it boots checks and gives me a list after a little while containing the following: Code: Test Errors Error Confidence Value: 0 56 Lowest Error Address 00000000000 - 0.0Mb 1 24 Highest Error Address 000FFFFFFFF - 4095.9Mb 2 40 Bits in error mask: 0001FFFC 3 56 Bits in error-total: 15 min: 0 max: 14 avg: 8 7 4 72 Max contiquous errors: 2 5 88 ECC Correctable errors: 84208028 6 104 Errors per memory slot 7 120 8 136 538982199 9 152 10 168 So my ram is faulty right? Well possibly but definitely not definite because here are the results from running a memtest on my the pc at my mothers home, It's a totally different system, diff type of ram, diff cpu, diff socket, diff graphics card, different everything and I get the following results from memtest: Code: Test Errors Error Confidence Value: 0 56 Lowest Error Address 00000000000 - 0.0Mb 1 24 Highest Error Address 000FFFFFFFF - 4095.9Mb 2 40 Bits in error mask: 0001FFFC 3 56 Bits in error-total: 15 min: 0 max: 14 avg: 8 7 4 72 Max contiquous errors: 2 5 88 ECC Correctable errors: 84208028 6 104 Errors per memory slot 7 120 8 136 538982199 9 152 10 168 identical results from 2 completely different machines, what gives? Something must be wrong with my memtest, isn't it like an astronomical chance to get exactly identical results (at mom's I also switched out dimms and slots but got the same result no matter the configuration) it's not even the same sie or type of ram (she's got SD Ive got ddr2, she's got 2x256mb, I got 2x512+2x1024) I can't really be sure or test which stick might be actually faulty with these results. But seeing this means my memtest testing results are bullocks at the moment correct? Anyone more experienced with memtest who might be able to tell me what im doing wrong or if memtest has a known bug causing this. I couldn't find anything on memtest's site. I was actually happy to see mem errors yesterday, at least that's easily fixable, I wouldn't even need to call corsair because I'm still within the period I can simply exchange the sticks at the store, but since I get identical (and thus bogus?) results on a totally different system I can't really be sure what to make of it, or test the seperate dimms on my machine if the results are the same for every dimm and even pc. help.... lol
I am getting the exact same errors on mine for memtest too. My pc has been running fine for almost 2 years no crashes.. I was going to oc a bit but now I have to figure this memtest error out. Very interesting that we are getting the exact same errors. I can't find any info on it either. This guys having it to but I can't read it
Thought I wouldn't get a reply anymore Same numbers and all? Did you use the latest memtest86 or latest memtest86+ (confusing) I'm going to test the + today if I don't forget to buy new cd's (I have some dvd's here but I want to test the tester by running it again on my mom's machine aswell and she doesn't have a dvd rom in it, don't trust the tester like this) are you also having issues like me or is it just that you wanted to test and noted it's not working? personally im wondering how non-random the symptoms of faulty memory or a dieing psu could be. my logic would say it should be pretty random but my issues are not. at least a working memtest could have narrowed it down to memory or excluded it from my list of possibilities. Played crysis yesterday for 4 hours without issues :s some other games. no go. pretty important to know if it's the ram since this is not just a gaming home entertainment system. Nice to know i'm not just crazy though
A good hardware tester is the Dell diagnostics. Works on any PC and is available for download on the dell support site by selecting any desktop (XPS series have the best diags) from support.euro.dell.com I used them on my water cooled rig I built a couple of years ago and found a fault with the memory on my graphics card that plagued me for some time. I tried loads of testers from various places and reccomendations on forums, but nothing worked like the Dell diags. They also pointed out errors on a friends computer with his RAM which solved a similar problem you are having. I don't know why the Dell diags are so good, but they are so give them a shot for total PC diags that work. knivestv
That's funny. I'm out of cd's too. Only dvd's. Here's a little background. I'm not having any issues or bsods like you mentioned. I'v been running this pc for about 1 1/2 years with no problems. Been playing UT2K4 maxed out since I built the thing and recently FEAR and UT3 with no major problems. Since UT3 is so demanding I've decided to OC this sucker up to around 2.4-2.5 for a little boost. That's what prompted me to run memtest86. Low and behold I get that summary screen after about 5 seconds of it running. Now. I've run the windows based memtest for hours... No errors I'm running Prime95 as I speak. Nothing yet. <--- will update for memtest 86. tested each stick individually in dim b-1 <-- same error Then b-2 for ****s and giggles. <----same error I don't know about the dell diagnostics. I'll have to think about that one.
Yep. Some pretty neat technology in this beast, including super low power usage. It can also run at extreme temperatures without failing. The graphics card temperature warning is set by the driver at 109 degrees c. I guess that explains the higher price, at least it explains some of it anyway. Performance is incredible. I have every game that I play running at 1920X1200 res which my desktop just can't do. I love it. knivestv
I'm guessing the original memtest86 has issues with modern technogoly despite the recent updates, honestly I should have gone for the updated memtest + the first time. http://www.memtest.org I got some cd's yesterday and burned a bootable with memtest86+ I've tested my ram for 8 hours, totalling 6 passes overnight. I have 0 errors as is should be: (im not sure if im happy with the no errors results, if something were wrong with the test (motherbard or ram) I at least would have a culprit to blame. now back to reading the replies I can try the dell tool, but i'm 99% sure the internal code it uses to test mainboard en ram is memtest. The reason to use memtest is that the only thing missing is an official label as the standard testing tool for ram and motherboard faults. It's pretty much an accepted standard in the industry. If I go to the store and tell the clerk memtest showed me my new dimms are flawed he won't ask anything else. alas it's not my ram. Any way to test the psu? the values I can read out in windows seem stable enough and correct. You know what strikes me, I'v played crysis again yesterday for 4 hours before I started this test and went to bed. no issues. other game, 20 mins and I get somekind of nv4_disp.dll issue. I mean, Crysis runs lol, would laugh my ass off if it weren't so annoying. I think it's nvidia. it all started wth weird driver cleaning issues.. I still can't clean my driver. if I remove it, restart (or not doesnt matter really) in safe mode and remove nv4_disp.dll (one of the things the cleaning util does) and reboot in normal mode, I won't reach my desktop. if I remove it in normal mode, the computer will crawl down to a bsod within a minute. never ever had that in my whole life and i'm an avid nvidia user. Might be a clue but I wouldn't know of what. I never had issues with this, so im betting it's not the cause of my current problems either but anyone have the same motherboard as me? MSI K9N SLi (nforce 570mcp). I have had this system since I built it in january, I've let the mobo decide most of my settings using the settings the hardware tells it (e.g. spd's of the dimms and cpu) but since the past week or so that im having issues i've been diving into the bios more often and find it's not very accurate. But then I don't usually keep track of itty bitty details like does amd stock cpu speeds differ from the label, e.g. x2 4200+ 11x200=2200mhz becomes 2211 mhz. (this is the setting it set itself to out of the box.) ram set to 9v instead of 8 (ow well that one's no problem else memtest would have choked somewhere in the 8 hours worth of testing) I highly doubt this is the cause since i've been using the system happily for quite a while, it still has the first xp install even, haven't had a need to reinstall. (i keep things neat and tidy maintenance wise). But with the problems you just can't help but doubt even though the clockspeed never was an issue before, and it wasn't an issue playing crysis for 4 hours yesterday. This is getting me really frustrated. anyone ever had that cleaning forceware (especially nv4_disp.dll) causes crashes? (for those that prefer the utilities out there like driver sweeper and driver cleaner, they do the same thing and cause the same issue here.) gambl3, as I mentioned get the plus version from the link, it will run with our 'exotic' hardware . While the test within windows is a good indicator it's not as definitive in finding either issues from your oc or hardware faults in your sticks/mobo. It can't test the parts that are already resered by windows, that is why it's so important to run it from boot, memtest does not even use dos to boot itself to avoid any and all os or somesuch files preventing it from testing certain area's of your ram. also it's just a test and not a diagnostic you would need to find a way to exclude things if you would find any error to find out what it is exactly. One last thing, 1 error in memtest is just as bad as 2000 errors in memtest. I'm sure you probably know all this, I just thought I'd mention it just in case and for anyone else having issues that might stumble across this thread while looking for help.
Hey worked for me too!!!!!!!!!!!!! so memtest86 is just not compatible with newer systems. Sorry about your other problems Good luck man
yes!..... ok perhaps not. I found it was indeed nvidia's NAM Network Access Manager causing the crash when I try to clean the nv4_disp.dll file. I removed the nam installation, cleaned the registry and retried the normal dirver update/rollback procedure. And finally no crash from cleaning the old files!!! I was really ecstatic thought I finally solved it. the procedure now went as it should, I checked the files afterwards for version numbers and they check out. So I finally thought I might have solved it, but no, black and white 2 still bsods, just this time it was more optimized I guess, it crashed faster after loading then before. Crysis still doesn't seem to mind and runs happily. settlers 6 bsods at certain points. I'm out of idea's... ram and mobo's tested, temps check out, driver installation works as it's supposed to again, the os is pretty darn clean, the only thing I haven't tried is the 169.x beta drivers. but seriously 163 can't be so bad that I need to update to a beta driver.
Well it's 'fixed' now, Ive tried several crashhappy games and the bsod is gone. I found out the factory clock on my xfx 7600gt (i shoud pay more attention to this) was overclocked, despite running fine since january, not having oc'ed myself (it's the model, checked their site) this was causing my nightmares. I've set it back to nvidia recommended stock speeds which is quite a bit slower but the bsod's gone now. (had to google for it, nvidia didnt have that tech info online anymore about the 7 series :s) Despite being very happy that the bsods are gone I can't help but feel a bit screwed. I did not purposely buy this specific card because of the higher clocks, But regardless, I'm now having performance lower then was promised by the product and what i paid for (though i didn't notice at the time) My warranty is still valid if I'm not mistaen and can find all the paperwork. Should I give xfx a call/e-mail? one last question, why do they overclock factory cards? (ok dumb question to compete ofcourse but still, whats a faster clock if it causes one after the other nv4_disp bsod after working for more then half a year without a hitch, faster wear and tear due to the oc?) Also this card apparently was designed by xfx to be overclocked quite a bit I noticed yesterday, not talking 10 mhz differences here. Yet the cooling build does not seem really made for the task (I never had heat issues though) And next time zI expect the box to say factory oc'ed at xxxmhz and xxxmhz in big fat letters on the box There's no hint on the box at all that this is anything else but a simple default 7600gt. also the psu might still be the culprit, lowering the clocks lowered the demand on the psu too... right? the final question remains, how would you go about this, contact xfx or not. it's stable at nvidia recommended safe values now, but it's not at factory settings. Also wonder why I haven't had any problems with it except for now. it's been quite a while since january. also wonder why crysis didn't seem to have any issues with it, but black and white 2 for example did. The fix did cost me 10 fps in crysis, not too much but not very nice either seeing as crysis didn't complain about any issues. stil weird but at least i can relax with a game other then crysis now and then again and i've been updated a bit again, ow we what do you expect from someone who was stuck at a geforce 3 ti-200 for years and years before being able to afford building this system edit: changed thread title to reflect it's solved status, added nv4_disp.dll in the title to aid anyone else looking for help on his or her nvidia issues.
