Emergency!!!

chaosrealm93 · Oct 27, 2009

after the RAM problems i posted earlier, i got these:

ntoskrnl.sys
dxgkrnl.sys
volsnap.sys
0x0000001E
BAD_POOL_CALLER 0x000000C2
SYSTEM_SERVICE_EXCEPTION 0x0000003B
IRQL_NOT_LESS_OR_EQUAL 0x0000000A
DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000D1 ataport.sys

and this one was just plain scary:

a driver has overrun a stack based buffer. this overrun could potentially allowa milicious use to gain control of this machine 0x000000F7

if anyone knows a fix for this (even if it means i have to reformat), a post would be greatly appreciated.

zigzag3143 · Oct 27, 2009

chaosrealm93 said:
after the RAM problems i posted earlier, i got these:

ntoskrnl.sys
dxgkrnl.sys
volsnap.sys
0x0000001E
BAD_POOL_CALLER 0x000000C2
SYSTEM_SERVICE_EXCEPTION 0x0000003B
IRQL_NOT_LESS_OR_EQUAL 0x0000000A
DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000D1 ataport.sys

and this one was just plain scary:

a driver has overrun a stack based buffer. this overrun could potentially allowa milicious use to gain control of this machine 0x000000F7

if anyone knows a fix for this (even if it means i have to reformat), a post would be greatly appreciated.

All these errors are still memory related. bad pool, irqlessthan, all of them a re still memory related. Re-installing isnt going to do anything.

What memory problems? how much ram?

Ken

chaosrealm93 · Oct 27, 2009

i have the corsair dominator 1066MHz 5-5-5-15 (its all in my system specs). im running the memory at their recommended timings. after i changed the timings from the stock system defaults to 5-5-5-15, i noticed a decline in MEMORY_MANAGEMENTs. not much decline for SYSTEM_SERVICE_EXCEPTION though...

usasma · Oct 27, 2009

Please upload the memory dump files so we can have a look at them.
The STOP 0xF7 is the BSOD that indicates a Buffer Overrun - this is the typical malware attack on a system, so you should scan for malware just to be sure.

chaosrealm93 · Oct 27, 2009

here they are.

chaosrealm93 · Oct 27, 2009

on a side note, can you teach me how to read those minidump files? is there are program you have to DL or can you just open them in notepad?

usasma · Oct 27, 2009

Most of the info that I know about minidumps is from here (my personal webpage): BSOD

Also read the help files for the Windows Debugging tools
Also read Windows Internals v5 by Russinovich, Solomon, and Ionescue
Also read Advanced Windows Debugging by Hewardt and Pravat

usasma · Oct 27, 2009

OK, I'm running the first 19 minidumps and will post the results.
Then I'll run the remaining 26 and will post the results for those.
Then we'll go over them in detail.

Depending on the speed of my network connection, I may/may not finish this tonight. If not, then I'll finish it tomorrow night (I work tomorrow).

chaosrealm93 · Oct 27, 2009

thank you so much! =)

usasma · Oct 27, 2009

First set of older drivers:

Code:

mv61xx.sys   Thu Oct 18 23:22:18 2007
AtiPcie.sys  Mon Nov 06 11:59:54 2006
ASACPI.sys   Mon Oct 30 22:09:12 2006
AsIO.sys     Mon Dec 17 04:11:49 2007

First set of BSOD summaries:

Code:

Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sat Oct 17 21:31:26.952 2009 (GMT-4)
System Uptime: 0 days 1:46:32.099
BugCheck A, {fffff68000052098, 0, 0, fffff80003159161}
Probably caused by : memory_corruption ( nt!MiEmptyWorkingSet+171 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sun Oct 18 13:36:17.086 2009 (GMT-4)
System Uptime: 0 days 14:16:28.493
BugCheck 4E, {99, bccb, 2, 3f79f}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 20 10:32:28.116 2009 (GMT-4)
System Uptime: 0 days 18:12:04.144
BugCheck 4E, {99, 205be, 2, 2143a}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 20 15:55:54.412 2009 (GMT-4)
System Uptime: 0 days 5:21:28.008
BugCheck 50, {ffffffff00000010, 0, fffff8000309390a, 5}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 20 16:02:00.351 2009 (GMT-4)
System Uptime: 0 days 0:02:15.586
BugCheck 50, {fffff8808f3cba60, 1, fffff80003198470, 5}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1a0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Wed Oct 21 11:48:46.679 2009 (GMT-4)
System Uptime: 0 days 18:17:39.622
BugCheck 1A, {41284, e535001, 0, fffff70001080000}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Wed Oct 21 21:39:17.581 2009 (GMT-4)
System Uptime: 0 days 5:22:16.597
BugCheck BE, {fffffa6000ba2080, 3e1a121, fffffa600c2af4f0, a}
*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.sys
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 05:22:22.375 2009 (GMT-4)
System Uptime: 0 days 7:38:13.737
BugCheck 3B, {c0000005, fffff800030e424e, fffffa600ceafb80, 0}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 14:05:26.412 2009 (GMT-4)
System Uptime: 0 days 6:14:22.588
BugCheck 3B, {c0000005, fffff8000306a7d9, fffffa600cc4f080, 0}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+274d3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 16:01:23.535 2009 (GMT-4)
System Uptime: 0 days 0:02:29.771
BugCheck 1A, {5003, fffff70001080000, 1a6f, 1a71800034de}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wlcomm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 17:05:12.334 2009 (GMT-4)
System Uptime: 0 days 0:54:21.696
BugCheck 1A, {41790, fffffa80002d1fb0, ffff, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  hl2.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 20:20:03.481 2009 (GMT-4)
System Uptime: 0 days 3:09:29.183
BugCheck 1A, {41284, fffff900c3034001, 3ee2, fffff90000812000}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+1f3bd4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 20:27:14.428 2009 (GMT-4)
System Uptime: 0 days 0:02:24.664
BugCheck 50, {fffff8808ea4b7e8, 0, fffffa600101360c, 5}
Probably caused by : Ntfs.sys ( Ntfs!NtfsLookupAllocation+ec )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchIndexer.e
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 20:49:44.026 2009 (GMT-4)
System Uptime: 0 days 0:18:29.301
BugCheck 24, {1904aa, fffffa600ae62588, fffffa600ae61f60, fffff800030287d9}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+41e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  VSSVC.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 21:00:22.565 2009 (GMT-4)
System Uptime: 0 days 0:09:40.816
BugCheck 50, {fffff88094b26290, 1, fffff80003145470, 5}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  lsass.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Thu Oct 22 22:52:19.085 2009 (GMT-4)
System Uptime: 0 days 1:46:24.205
BugCheck 3B, {c0000005, fffff96000112af3, fffffa600b568050, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+a2af3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Fri Oct 23 00:17:47.157 2009 (GMT-4)
System Uptime: 0 days 0:12:27.416
BugCheck 124, {0, fffffa8007621030, b678c000, 145}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  prime95.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Fri Oct 23 15:33:56.021 2009 (GMT-4)
System Uptime: 0 days 15:14:43.125
BugCheck D1, {fffff800070abc7f, c, 8, fffff800070abc7f}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+20b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  lsm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Fri Oct 23 20:23:00.248 2009 (GMT-4)
System Uptime: 0 days 4:48:03.785
BugCheck 1A, {30, fffffa8004f26710, fffffa600df2f000, fffff8800eb4a81a}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe

usasma · Oct 28, 2009

Second set of older drivers:

Code:

mv61xx.sys   Thu Oct 18 23:22:18 2007
AtiPcie.sys  Mon Nov 06 11:59:54 2006
ASACPI.sys   Mon Oct 30 22:09:12 2006
AsIO.sys     Mon Dec 17 04:11:49 2007

Summary of last 26 BSOD's:

Code:

Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Fri Oct 23 23:17:44.823 2009 (GMT-4)
System Uptime: 0 days 2:53:33.478
BugCheck 3B, {c0000005, fffff800030797af, fffffa600c52d080, 0}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SearchProtocolH
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Fri Oct 23 23:29:05.097 2009 (GMT-4)
System Uptime: 0 days 0:06:20.338
BugCheck 1A, {41790, fffffa80002fa630, ffff, 0}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sat Oct 24 12:30:53.558 2009 (GMT-4)
System Uptime: 0 days 12:53:49.677
BugCheck 1E, {ffffffffc0000005, fffffa6000acf40c, 1, 15c}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sat Oct 24 12:41:02.898 2009 (GMT-4)
System Uptime: 0 days 0:04:34.135
BugCheck 50, {fffffa8002922150, 0, fffff800030ce116, 2}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sat Oct 24 14:47:24.230 2009 (GMT-4)
System Uptime: 0 days 2:05:21.392
BugCheck 1A, {41201, fffff680002ae838, f1c0000100447867, fffffa80085524c0}
Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  hl2.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sun Oct 25 21:58:29.458 2009 (GMT-4)
System Uptime: 0 days 0:00:25.690
BugCheck 124, {0, fffffa80075d2030, b26cc000, 175}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LogonUI.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sun Oct 25 22:35:57.834 2009 (GMT-4)
System Uptime: 0 days 0:27:14.129
BugCheck 124, {0, fffffa800753c030, b26d4000, 175}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Sun Oct 25 23:29:03.027 2009 (GMT-4)
System Uptime: 0 days 0:47:57.389
BugCheck 124, {0, fffffa8007832030, b26b4000, 175}
Probably caused by : hardware
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Mon Oct 26 15:34:09.072 2009 (GMT-4)
System Uptime: 0 days 15:57:51.236
BugCheck 50, {fffff80011e8e070, 0, fffff800032b3554, 2}
*** WARNING: Unable to verify timestamp for klif.sys
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
Probably caused by : klif.sys ( klif+17127 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  wlcomm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Mon Oct 26 16:06:09.487 2009 (GMT-4)
System Uptime: 0 days 0:27:04.582
BugCheck 50, {fffff88115c5e418, 0, fffffa6007ad1747, 5}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::xWaitForAllEngines+a3 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Crysis.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Mon Oct 26 21:21:03.122 2009 (GMT-4)
System Uptime: 0 days 1:13:56.531
BugCheck 50, {fffffa000876dc0c, 0, fffffa6007ac6eb2, 5}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::ReferenceDmaBuffer+2a6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Crysis.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 07:15:06.528 2009 (GMT-4)
System Uptime: 0 days 9:47:16.212
BugCheck 50, {fffff908c0a24827, 0, fffff96000113262, 5}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+33262 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  msnmsgr.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 07:18:05.788 2009 (GMT-4)
System Uptime: 0 days 0:01:20.990
BugCheck A, {fffffa0008156100, c, 1, fffff800030b6184}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueueApc+1a4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LogTransport2.e
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 07:40:27.007 2009 (GMT-4)
System Uptime: 0 days 0:01:18.835
BugCheck 3B, {c0000005, fffff800033711ec, fffffa600a212020, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObpPreInterceptHandleDuplicate+bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 07:46:44.102 2009 (GMT-4)
System Uptime: 0 days 0:01:29.351
BugCheck 1E, {ffffffffc0000005, fffff8000333b434, 1, b824a3}
Probably caused by : ntkrnlmp.exe ( nt!NtSetInformationProcess+60b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 07:59:11.680 2009 (GMT-4)
System Uptime: 0 days 0:10:31.935
BugCheck A, {fffffa0008cb9718, c, 0, fffff8000308cc5e}
Probably caused by : ntkrnlmp.exe ( nt!KeQueryValuesProcess+a6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avp.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 08:14:56.405 2009 (GMT-4)
System Uptime: 0 days 0:05:07.647
BugCheck A, {fffff6fd0004c358, 2, 0, fffff80003022668}
Probably caused by : memory_corruption ( nt!MiOutPageSingleKernelStack+cc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 15:41:40.854 2009 (GMT-4)
System Uptime: 0 days 7:20:22.157
BugCheck D1, {ffffffffc35e30c5, 2, 1, fffffa60007a48bc}
Probably caused by : ataport.SYS ( ataport!IdepInterpretTransportErrors+224 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 15:44:10.133 2009 (GMT-4)
System Uptime: 0 days 0:01:27.961
BugCheck D1, {ac95007fb8, 2, 1, fffffa60011b41e7}
Probably caused by : hardware ( volsnap!VspWriteTableUpdatesCompletion+147 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 15:46:08.231 2009 (GMT-4)
System Uptime: 0 days 0:01:06.449
BugCheck A, {39, 2, 0, fffff80003085de4}
Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+2c4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  soffice.bin
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 15:51:43.615 2009 (GMT-4)
System Uptime: 0 days 0:02:13.475
BugCheck 50, {fffffab008a5bfc0, 0, fffff800030d3d27, 5}
Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+118 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  googletalk.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 16:30:27.472 2009 (GMT-4)
System Uptime: 0 days 0:37:15.418
BugCheck C2, {7, 110b, a79c63, fffffa600b161288}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+4fd5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ipoint.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 16:33:23.940 2009 (GMT-4)
System Uptime: 0 days 0:01:29.173
BugCheck F7, {50b1bd283845, 50b1bd28386c, ffffaf4e42d7c793, 0}
Probably caused by : hardware ( nt!_report_gsfailure+25 )
DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 17:00:29.114 2009 (GMT-4)
System Uptime: 0 days 0:07:15.362
BugCheck 50, {fffff8001073a650, 0, fffffa6007ac6fa7, 2}
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  GTAIV.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 17:05:31.389 2009 (GMT-4)
System Uptime: 0 days 0:03:33.593
BugCheck 50, {fffff80010d651e0, 0, fffffa6007ac4fa7, 2}
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  GTAIV.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 6002.18082.amd64fre.vistasp2_gdr.090803-2339
Debug session time: Tue Oct 27 18:23:55.041 2009 (GMT-4)
System Uptime: 0 days 1:17:01.079
BugCheck 50, {fffff8001012a610, 0, fffffa6007cc7191, 2}
Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDMM_GLOBAL::ReferenceDmaBuffer+585 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  GTAIV.exe

usasma · Oct 28, 2009

Update video drivers.
Uninstall Kaspersky and reinstall.

totaly chill · Sep 10, 2010

Have you tried the DNA version of the ATI drivers? its at : DNA-ATi 10.8.2 | Do Not Argue i tried it and so far after 42 minuites it only crashed once which is an improvement but if it is the memory i may upgrade to a branded memory ill keep you informed on my progress =D

totaly chill · Sep 10, 2010

I have just updated windows and another 40 mins has passed no crashes

totaly chill · Sep 13, 2010

Hmm after a total run time of 4 hours at different speeds of cpu gpu and memory load all seems well has been shutting down downloading games drivers programs and doing all sorts of trouble shooting methods all seems to be well! no need to get new memory!

Emergency!!!

My Computer

Banned

My Computer

My Computer

Old and cranky

My Computer

Attachments

My Computer

My Computer

Old and cranky

My Computer

Old and cranky

My Computer

My Computer

Old and cranky

My Computer

Old and cranky

My Computer

Old and cranky

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer