bsod help

Hippeh · Sep 10, 2009

As we had very similar issues, I was hoping I might contribute and help us both out. But...whatever.

zigzag3143 · Sep 10, 2009

Hippeh said:
As we had very similar issues, I was hoping I might contribute and help us both out. But...whatever.

You know you can but its somewhat bad form as it gets confusing when ssomeone says I have the exact same problem, then someone else says me too. trying to ask OP1 for info, then op2, then op3, gets strange when you have to read back thru the whole thread. the other thing is ppl search for things they are interested in so even if your problem is exactly the same if the other person doesn't title the thread right yours gets lost too.

So what would you like to do? continue here or satrt a new thread? If you need help starting a new thread let me know

Ken

Hippeh · Sep 10, 2009

No I understand, I wasn't trying to hijack this thread. I've started a new thread so all is well

Thank you!

pearcie · Sep 11, 2009

usasma said:

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

now runnig avast heres the latest dumps dont seem to bsod as often.......
View attachment 27550 but still happening............

usasma · Sep 12, 2009

When did you uninstall the Kaspersky and install the Avast? There's a dump file from 10 Sep that points to Kaspersky. Still runnin the dump files - will be back shortly

chev65 · Sep 12, 2009

I would think fixing this would be so obvious. Remove all anti virus programs, case closed. They cause more problems than they solve for me.

How hard would it be to test this,.. reinstall Win7, if crashing occurs it's not the anti virus. If crashing occurs after anti virus installation then the problem is the anti virus. But I somehow think there are more problems here than just an anti virus program. Those debuggers seldom point to the exact cause of the problem.

usasma · Sep 12, 2009

Well, the error reports are still all over the place. The most common thing present is memory corruption/improper memory access. Have you performed a memory diagnostic on the system? If not, please follow the directions here: Bootable Memory Test Diagnostics - Vox

I'd also suggest running a hard drive diagnostic (instructions here: Bootable Hard Drive Diagnostics - Vox ), and then run chkdsk /r from an elevated (Run as administrator) Command Prompt

If these tests don't find a problem, then I'll suggest running Driver Verifier - but I don't want to get into that right now as it can (with my settings) prevent the computer from booting up.

Here's the summary of the latest BSOD's

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Sep  9 17:09:51.706 2009 (GMT-4)
System Uptime: 0 days 0:06:19.314
BugCheck 1A, {41201, fffff68000128ef8, f740000049d47847, fffffa8007139ec0}
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: Wed Sep  9 18:40:08.826 2009 (GMT-4)
System Uptime: 0 days 0:03:14.433
BugCheck C2, {7, 1097, 0, fffffa8003bc5300}
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+1d7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 10 05:19:35.708 2009 (GMT-4)
System Uptime: 0 days 0:00:52.315
BugCheck D1, {fffffa805cb47a94, 2, 1, fffff88003c85329}
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : kl1.sys ( kl1+51329 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 07:44:28.491 2009 (GMT-4)
System Uptime: 0 days 1:21:03.099
BugCheck 3B, {c0000005, fffff80002affccd, fffff8800629ad20, 0}
Probably caused by : memory_corruption ( nt!MiLocateAddress+1d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TurboV.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 07:48:31.565 2009 (GMT-4)
System Uptime: 0 days 0:02:39.173
BugCheck 1000007E, {ffffffffc0000005, fffff80002c02f8c, fffff8800356b8d8, fffff8800356b130}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 13:43:00.462 2009 (GMT-4)
System Uptime: 0 days 0:04:37.069
BugCheck 19, {22, 7800001378000000, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+26d7b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 13:36:21.438 2009 (GMT-4)
System Uptime: 0 days 0:02:27.046
BugCheck 24, {1904fb, fffff880031b7878, fffff880031b70d0, fffff880014383da}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPreRequestProcessingExtend+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 08:49:08.771 2009 (GMT-4)
System Uptime: 0 days 0:02:15.378
BugCheck 3B, {c000001d, fffff880040662a8, fffff880065e5b40, 0}
Probably caused by : hardware ( dxgkrnl!DXGCONTEXT::Present+1168 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 14:03:10.408 2009 (GMT-4)
System Uptime: 0 days 0:03:00.016
BugCheck 3B, {c0000005, fffff80002dbd58e, fffff88002689e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpQuerySystemInformation+a9c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 09:01:45.590 2009 (GMT-4)
System Uptime: 0 days 0:08:24.197
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : volsnap.sys ( volsnap!ExAllocateFromNPagedLookasideList+27 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ashServ.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 20:02:51.365 2009 (GMT-4)
System Uptime: 0 days 0:47:33.054
BugCheck 3B, {c0000005, fffff88001203b07, fffff88008003cb0, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpGetStartingCallbackNode+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe

pearcie · Sep 13, 2009

usasma said:

Well, the error reports are still all over the place. The most common thing present is memory corruption/improper memory access. Have you performed a memory diagnostic on the system? If not, please follow the directions here: Bootable Memory Test Diagnostics - Vox

I'd also suggest running a hard drive diagnostic (instructions here: Bootable Hard Drive Diagnostics - Vox ), and then run chkdsk /r from an elevated (Run as administrator) Command Prompt

If these tests don't find a problem, then I'll suggest running Driver Verifier - but I don't want to get into that right now as it can (with my settings) prevent the computer from booting up.

Here's the summary of the latest BSOD's

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Sep  9 17:09:51.706 2009 (GMT-4)
System Uptime: 0 days 0:06:19.314
BugCheck 1A, {41201, fffff68000128ef8, f740000049d47847, fffffa8007139ec0}
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: Wed Sep  9 18:40:08.826 2009 (GMT-4)
System Uptime: 0 days 0:03:14.433
BugCheck C2, {7, 1097, 0, fffffa8003bc5300}
Probably caused by : ntkrnlmp.exe ( nt!KiDeliverApc+1d7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Sep 10 05:19:35.708 2009 (GMT-4)
System Uptime: 0 days 0:00:52.315
BugCheck D1, {fffffa805cb47a94, 2, 1, fffff88003c85329}
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : kl1.sys ( kl1+51329 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 07:44:28.491 2009 (GMT-4)
System Uptime: 0 days 1:21:03.099
BugCheck 3B, {c0000005, fffff80002affccd, fffff8800629ad20, 0}
Probably caused by : memory_corruption ( nt!MiLocateAddress+1d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TurboV.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 07:48:31.565 2009 (GMT-4)
System Uptime: 0 days 0:02:39.173
BugCheck 1000007E, {ffffffffc0000005, fffff80002c02f8c, fffff8800356b8d8, fffff8800356b130}
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 13:43:00.462 2009 (GMT-4)
System Uptime: 0 days 0:04:37.069
BugCheck 19, {22, 7800001378000000, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+26d7b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CoDWaW.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 13:36:21.438 2009 (GMT-4)
System Uptime: 0 days 0:02:27.046
BugCheck 24, {1904fb, fffff880031b7878, fffff880031b70d0, fffff880014383da}
Probably caused by : Ntfs.sys ( Ntfs!NtfsPreRequestProcessingExtend+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 08:49:08.771 2009 (GMT-4)
System Uptime: 0 days 0:02:15.378
BugCheck 3B, {c000001d, fffff880040662a8, fffff880065e5b40, 0}
Probably caused by : hardware ( dxgkrnl!DXGCONTEXT::Present+1168 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 14:03:10.408 2009 (GMT-4)
System Uptime: 0 days 0:03:00.016
BugCheck 3B, {c0000005, fffff80002dbd58e, fffff88002689e20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpQuerySystemInformation+a9c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 09:01:45.590 2009 (GMT-4)
System Uptime: 0 days 0:08:24.197
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : volsnap.sys ( volsnap!ExAllocateFromNPagedLookasideList+27 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ashServ.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Sep 11 20:02:51.365 2009 (GMT-4)
System Uptime: 0 days 0:47:33.054
BugCheck 3B, {c0000005, fffff88001203b07, fffff88008003cb0, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpGetStartingCallbackNode+97 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe

will give the tests ago have not done thease exact tests so will try them kaspersky should be go may be a dump left over thank you for the help

usasma · Sep 13, 2009

Removal tool for Kaspersky Lab's products: Service messages

pearcie · Sep 13, 2009

ok done the memtes86 4 passes no errors also used the seagate hdd dos tool various test again no errors used the kaspersky removal tool but it found nothing also tried some other ways to find anything to do with kaspersky but found nothing only thing i can think of is maybe the dump file which mention kaspersky was before i unistalled it completely stumped now, by the way thank you for taking time to help me usasma.........

usasma · Sep 13, 2009

Wait for the next BSOD. I'll run an analysis on it.
If I can't figure it out from that, then we'll move on to the Driver Verifier thing.

pearcie · Sep 14, 2009

here you go the latest four bsod attach thanx View attachment 27948

usasma · Sep 14, 2009

OK, nothing more significant in the dump files - so I'll suggest running Driver Verifier.
Please read the instructions thoroughly before starting - as Driver Verifier can render your system unbootable.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

pearcie · Sep 15, 2009

hi usasma the memory file was to big to upload here, so here it is RapidShare: 1-CLICK Web hosting - Easy Filehosting let me know if you dont get it i will find another way to send it, there was no mini dump. system started up to desktop for about 10 seconds then crashed done this several times could not boot back up so booted in safe mode which worked fine made a note of the blue stop screen if you need it aswell and thank you very much for this .....................anything else you need let me know.

usasma · Sep 15, 2009

I've reached my limit on RapidShare and it won't allow me to download any more.

Please repost it to another free file hosting service (I like http://www.box.net )
You'll have to share the file out, then it'll give you a link to post here.

You don't need the huge dump files. Minidump files work just as well and are easier to manipulate.

To set your system to capture minidumps, please follow the instructions here: http://www.carrona.org/setmini.html

Snufffed · Sep 15, 2009

For me this simply is:
ANOTHER GOOD REASON TO NOT INSTALL X64. OS.

pearcie · Sep 15, 2009

usasma said:
I've reached my limit on RapidShare and it won't allow me to download any more.

Please repost it to another free file hosting service (I like Box.net | Simple Online Collaboration: Online File Storage, FTP Replacement, Team Workspaces ~ Free Version )
You'll have to share the file out, then it'll give you a link to post here.

You don't need the huge dump files. Minidump files work just as well and are easier to manipulate.

To set your system to capture minidumps, please follow the instructions here: Change dump file location & size to Minidumps - Vox

tried the resize the dump file done the verifier thing again checked minidump folder but nothing was there again dunno why so anyway uploaded the file to another file hosting site hopefully you will be ok with this one http://www.mediafire.com/?sharekey=fd953167b5945cc024a64199ac7f73e5e04e75f6e8ebb871

usasma · Sep 15, 2009

This one works, but it's slow as molasses. I'll be back with the analysis when it's done.

pearcie · Sep 15, 2009

usasma said:
This one works, but it's slow as molasses. I'll be back with the analysis when it's done.

ok thank you..

usasma · Sep 15, 2009

Are you running Driver Verifier? If not, please keep it running until we get a Driver Verifier error (or we solve it another way).

Got the dump file and ran the analysis. It's a STOP 0x3B - System Service Exception It's not a Driver Verifier error - but if Driver Verifier was running when it happened, it gives us a clue that this is a program/service rather than a driver.
More info on the error here: BSOD Index

It occurred in CODWaW.exe and it was an exception while accessing memory.

Each time a MEMORY.dmp file is generated - it wipes out the old one. So I'd suggest saving them in another location (adding a date to the file name) in order to have a record of what's going on. Once the system is generating minidumps this'll be taken care of automatically.

2 more things to do while waiting for the next memory dump.
- Go to Start and type in "msinfo32" (without the quotes) and press Enter.
Save the report as an .nfo file, zip it up and upload the .zip file with your next post
- Download and run the free Windows 7 Upgrade Advisor ( http://www.microsoft.com/downloads/...90-7659-4BD9-9E51-2497C146AF15&displaylang=en ) Save the report in whatever format that it suggests, zip it up and upload it with your next post also.

Dump file analysis:

Code:

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


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Mon Sep 14 14:39:13.093 2009 (GMT-4)
System Uptime: 0 days 0:04:28.701
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ad70b6, fffff88007fe5130, 0}

PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+226 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ad70b6, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007fe5130, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KeSetEvent+226
fffff800`02ad70b6 488b09          mov     rcx,qword ptr [rcx]

CONTEXT:  fffff88007fe5130 -- (.cxr 0xfffff88007fe5130)
rax=fffffa8007b84728 rbx=fffffa8007b84720 rcx=00fffa8007b84728
rdx=0000000000000001 rsi=0000000000000000 rdi=fffff880009f2180
rip=fffff80002ad70b6 rsp=fffff88007fe5b10 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000038 r10=00fffa8007b84728
r11=00000000001f0003 r12=000000007efaa001 r13=0000000006f0fd20
r14=0000000006f0f170 r15=0000000073a92450
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
nt!KeSetEvent+0x226:
fffff800`02ad70b6 488b09          mov     rcx,qword ptr [rcx] ds:002b:00fffa80`07b84728=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  CoDWaW.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002decdf0 to fffff80002ad70b6

STACK_TEXT:  
fffff880`07fe5b10 fffff800`02decdf0 : 00000000`00000000 fffff880`00000001 fffffa80`03a37000 00000000`00000001 : nt!KeSetEvent+0x226
fffff880`07fe5b80 fffff800`02ad2153 : fffffa80`078834c0 fffff880`07fe5c60 00000000`00000000 fffffa80`07b84720 : nt!NtSetEvent+0x90
fffff880`07fe5be0 00000000`73a92dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`06f0f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73a92dd9


FOLLOWUP_IP: 
nt!KeSetEvent+226
fffff800`02ad70b6 488b09          mov     rcx,qword ptr [rcx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KeSetEvent+226

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

STACK_COMMAND:  .cxr 0xfffff88007fe5130 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!KeSetEvent+226

BUCKET_ID:  X64_0x3B_nt!KeSetEvent+226

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

bsod help

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

Closed

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

Similar threads