bsod help

pearcie · 09 Sep 2009

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems Attachment 27253

done loads of hardware test but everything seems to come out ok im worried if it is a hardware problem i may not be able to detect it.hopeing its not anyway and if it was you would think the 32 bit os would crash....

Snufffed · 09 Sep 2009

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems 090909-20170-01.zip

Have you thought of letting win7 install the default drivers. and test with them. Just a thought.

pearcie · 09 Sep 2009

Snuffy said:

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems 090909-20170-01.zip

Have you thought of letting win7 install the default drivers. and test with them. Just a thought.

thanx but yes done that

zigzag3143 · 09 Sep 2009

pearcie said:

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems Attachment 27253

done loads of hardware test but everything seems to come out ok im worried if it is a hardware problem i may not be able to detect it.hopeing its not anyway and if it was you would think the 32 bit os would crash....

You know there is enough info here for one of our guru's with debugging to check for you . Im going to send the thread link to someone that specializes in these. 32 bit will give you less grief though.

Ken

pearcie · 10 Sep 2009

zigzag3143 said:

pearcie said:

thanx again for help didnt seem to work uninstalled old graphics driver,downloaded and installed latest ati driver still crashed bsod heres all the dump files includeing latest weird how on my partioned windows 7 pro 32 bit its as stable as hell no problems Attachment 27253

done loads of hardware test but everything seems to come out ok im worried if it is a hardware problem i may not be able to detect it.hopeing its not anyway and if it was you would think the 32 bit os would crash....

You know there is enough info here for one of our guru's with debugging to check for you . Im going to send the thread link to someone that specializes in these. 32 bit will give you less grief though.

Ken

thanx for your help, yeh probly 32 bit would be easier but lots of people seem to rave about how good 64 is up to 32 bit so would love to run 64 bit lets hope hope one of the gurus can shed some light thanx again..........

usasma · 10 Sep 2009

18 dump files and only one mentions kl1.sys (took a "quick" look) - a long shot, but I'd suggest:

- Downloading a free antivirus (for use while testing). I recommend Avast Free for x64 systems - just google for it.
- Gathering up your Kaspersky product key (in case you want to reinstall later on).
- Uninstall the Kaspersky products from your system.
- IMMEDIATELY install and update the free antivirus
- Reboot and test for problems.

Running all 18 dump files now - be back in a while!

usasma · 10 Sep 2009

The common thread in most of the BSOD's is a memory access violation (c0000005). This is a common trait of a malfunctioning Internet Security application. I'd suggest removing Kaspersky as discussed above.

This is the dump file that blames Kaspersky: 090609-26332-01.dmp It's a STOP 0x1E error about 12th down the list.

Older drivers (2007 and earlier) loaded when the last BSOD occurred:

Code:

None

Summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 10:37:57.916 2009 (GMT-4)
System Uptime: 0 days 1:14:37.524
BugCheck A, {28, 2, 0, fffff80002b03090}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 19:59:31.482 2009 (GMT-4)
System Uptime: 0 days 0:13:01.089
BugCheck 24, {1904fb, fffff880031af658, fffff880031aeeb0, fffff80002abd871}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFreeNonpagedDataFcb+20 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 19:45:22.507 2009 (GMT-4)
System Uptime: 0 days 0:07:00.115
BugCheck 1E, {ffffffffc0000005, fffff80002afc35f, 0, ffffffffffffffff}
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep  4 20:50:25.091 2009 (GMT-4)
System Uptime: 0 days 0:49:45.698
BugCheck 1000007E, {ffffffffc0000005, fffff80002d44b9b, fffff88003324868, fffff880033240c0}
Probably caused by : ntkrnlmp.exe ( nt!PspDereferenceQuotaBlock+17 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 15:02:31.628 2009 (GMT-4)
System Uptime: 0 days 1:26:32.236
BugCheck C2, {7, 1097, 405000a, fffffa8003ebfe60}
Probably caused by : dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+b6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 05:33:09.262 2009 (GMT-4)
System Uptime: 0 days 0:01:38.870
BugCheck 3B, {c0000005, fffff9600011da7d, fffff880074810a0, 0}
Probably caused by : win32k.sys ( win32k!InternalBuildHwndList+39 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 15:33:12.909 2009 (GMT-4)
System Uptime: 0 days 0:01:24.516
BugCheck 3B, {c0000005, fffff80002db3a5e, fffff88002661d50, 0}
Probably caused by : ntkrnlmp.exe ( nt!PspThreadDelete+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wmi64.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Sep  5 13:34:18.680 2009 (GMT-4)
System Uptime: 0 days 0:28:33.287
BugCheck 1000007E, {ffffffffc0000005, fffff88005140ff3, fffff880055d2658, fffff880055d1eb0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 09:53:39.154 2009 (GMT-4)
System Uptime: 0 days 0:05:29.762
BugCheck 1A, {41201, fffff68000111408, a45000003e5a4867, fffffa80068bb280}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 09:47:20.567 2009 (GMT-4)
System Uptime: 0 days 0:23:29.643
BugCheck 1A, {41201, fffff68000123090, d430000029504847, fffffa80084d4420}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 07:20:33.356 2009 (GMT-4)
System Uptime: 0 days 2:33:58.964
BugCheck 1A, {41289, 74a04001, 1695, d700000074a04c05}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a89 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 09:22:57.440 2009 (GMT-4)
System Uptime: 0 days 2:01:30.048
BugCheck 1E, {ffffffffc0000005, fffff88003ca52b0, 0, ffffffffffffffff}
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : kl1.sys ( kl1+382b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep  7 12:26:40.603 2009 (GMT-4)
System Uptime: 0 days 0:56:15.086
BugCheck 3B, {c0000005, fffff80002dd1cd6, fffff88005b4a060, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpDestroyBlob+26 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep  7 11:51:39.378 2009 (GMT-4)
System Uptime: 0 days 0:19:17.594
BugCheck 1000007E, {ffffffffc0000005, fffff8800458cff0, fffff88004fbc658, fffff88004fbbeb0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Sep  7 17:35:37.836 2009 (GMT-4)
System Uptime: 0 days 3:05:08.444
BugCheck 3B, {c0000005, fffff80002bf40f3, fffff88006f2cb40, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep  6 19:33:54.732 2009 (GMT-4)
System Uptime: 0 days 0:05:33.339
BugCheck 3B, {c0000005, fffff880042b23a6, fffff880026cb800, 0}
Probably caused by : atikmdag.sys ( atikmdag+2843a6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Sep  8 19:03:30.420 2009 (GMT-4)
System Uptime: 0 days 0:00:12.902
BugCheck A, {fffffa0006093300, 2, 0, fffff80002ad2719}
Probably caused by : serial.sys ( serial!SerialIoControl+9a1 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Sep  9 14:26:11.914 2009 (GMT-4)
System Uptime: 0 days 0:34:15.522
BugCheck 1A, {41201, fffff68000102720, 9e10000059e0c847, fffffa8004600810}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaWmp.exe

pearcie · 10 Sep 2009

will try the antivirus thing and get back with any dump files if bsod occurs and for taking the trouble to help me out really appreciate it.............

Hippeh · 10 Sep 2009

I'm experiencing the same BSODs on Win7 Enterprise x64 RTM. It seems to be aggrivated by 3D gaming, though I've had it crash and restart while perfoming virus scans or even sitting idle. Since I can almost guarantee that it will crash while playing Call of Duty: World at War, I've been using that to test for results.

I've had at least 5 different reported drivers as the culprit, but atikmdag.sys seems to be the most prevalent. The latest showed ks.sys to have caused the crash. My system had been completely stable since built, and I had made no change before I started experiencing the crashes.

I was using Avast av when I first started experiencing the crashes. I tried running with AVG, BitDefender and even with no av. Each change made little difference. I had also been running the 9.7 ATI drivers for my HD4870 gfx card. After the crashes started, I tried upgrading to 9.8, then adding the 9.8 hotfix, to no avail. The most significant difference was when I tried running with no driver, instead letting it revert back to the Win7 drivers. I was able to play for about 30 minutes before it finally crashed, right about the time I thought I had figured it out.

I've also run the Windows memory test and it showed no faults. I've tried various BIOS settings starting from default and working back to where I had adjusted/tweaked. Mind you, this system was perfectly stable with slight overclocking on the CPU.

I'm in process of unistalling drivers until I hit something that seems to stabilize it again. I've just done the Audigy SE sound card drivers but have yet to stress test it, and the only thing left would be the motherboard drivers. When I get home this evening, I'll post my dumps if someone would care to compare them to pearcie's to see if there's some common link here. I get the feeling that something got buggy, perhaps with an update? I could be grasping at straws though...

BTW, you've got a wonderful community here. I'm glad to be part of it.

EDIT: I just noticed the dump summary for pearcie's crashes has alot of references to codwaw.exe/codwawmp.exe. Hmmmmm.......

usasma · 10 Sep 2009

Hippeh - Please start your own thread for your issues.