Hi I've been having some trouble with my new pc.
MSI P67A-GD65
Intel i5-2500
Corsair 2x4GB CMX8GX3M2A1333C9
Nvidia Geforce 560 Ti
Windows X64, newly installed
I've been having usb trouble which has been solved as far as i can tell, but I'm still having BSOD's. Somwhat points to a memory error, but I'm not sure. I've tested with memtest86+, windows diagnostic and BIOS diagnostic, all came out fine. Could anyone make something out of the report?
Thanks
MSI P67A-GD65
Intel i5-2500
Corsair 2x4GB CMX8GX3M2A1333C9
Nvidia Geforce 560 Ti
Windows X64, newly installed
I've been having usb trouble which has been solved as far as i can tell, but I'm still having BSOD's. Somwhat points to a memory error, but I'm not sure. I've tested with memtest86+, windows diagnostic and BIOS diagnostic, all came out fine. Could anyone make something out of the report?
Thanks
so what im getting from this report is that your usb drive can't be found? Is that correct
Hi ,
Had a look through your DMP files and came across a few things
Its a driver for zone alarm and may have caused a BSOD, I suggest removing it and replacing with Microsoft Security Essentials.
Also I found this particular driver which causes alot of BSOD's and may be a problem.
Try removing Alcohol 120% and then removing STPD using this tool Duplex Secure
Also NVLDDMKM.SYS seemed to casue quite a few
It's your Nvidia GPU driver,but it seems up to date -
Perhaps try uninstalling the driver and do a fresh install incase the driver is corrupted. You can find your drivers at Nvidia
If it the above do not fix the problem Id suggest running Driver Verifier to see if it picks up on any bad drivers.
Had a look through your DMP files and came across a few things
Code:
Unable to load image \SystemRoot\system32\DRIVERS\vsdatant.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for vsdatant.sys *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys Probably caused by : vsdatant.sys ( vsdatant+90104 )
Also I found this particular driver which causes alot of BSOD's and may be a problem.
Code:
sptd sptd.sys Tue Aug 24 07:13:12 2010 (4C7362F8)
Also NVLDDMKM.SYS seemed to casue quite a few
Code:
*** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+1b3cb4 )
Code:
nvlddmkm nvlddmkm.sys Sat Mar 26 06:53:38 2011 (4D8D8D72)
If it the above do not fix the problem Id suggest running Driver Verifier to see if it picks up on any bad drivers.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dan\Desktop\Windows_NT6_BSOD_jcgriff2\041511-33774-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329be50 Debug session time: Fri Apr 15 00:06:19.694 2011 (GMT+1) System Uptime: 0 days 1:33:25.208 Loading Kernel Symbols ............................................................... ................................................................ ................................... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1, {7747f72a, 0, ffff, fffff8800b33ac60} Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* APC_INDEX_MISMATCH (1) This is a kernel internal error. The most common reason to see this bugcheck is when a filesystem or a driver has a mismatched number of calls to disable and re-enable APCs. The key data item is the Thread->KernelApcDisable field. A negative value indicates that a driver has disabled APC calls without re-enabling them. A positive value indicates that the reverse is true. This check is made on exit from a system call. Arguments: Arg1: 000000007747f72a, address of system function (system call) Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex Arg3: 000000000000ffff, Thread->KernelApcDisable Arg4: fffff8800b33ac60, Previous KernelApcDisable Debugging Details: ------------------ FAULTING_IP: +0 00000000`7747f72a ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800030cdca9 to fffff800030ce740 STACK_TEXT: fffff880`0b33aa28 fffff800`030cdca9 : 00000000`00000001 00000000`7747f72a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx fffff880`0b33aa30 fffff800`030cdbe0 : 00000000`00234000 00000000`00233ff8 00000000`018aef00 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0b33ab70 00000000`7747f72a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245 00000000`018ae668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7747f72a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiSystemServiceExit+245 fffff800`030cdbe0 4883ec50 sub rsp,50h SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiSystemServiceExit+245 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245 BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245 Followup: MachineOwner --------- 2: kd> lmntsm start end module name fffff880`10d45000 fffff880`10d83000 1394ohci 1394ohci.sys Tue Jul 14 01:07:12 2009 (4A5BCC30) fffff880`00f46000 fffff880`00f9d000 ACPI ACPI.sys Tue Jul 14 00:19:34 2009 (4A5BC106) fffff880`02e3e000 fffff880`02ec8000 afd afd.sys Tue Jul 14 00:21:40 2009 (4A5BC184) fffff880`041e6000 fffff880`041fc000 AgileVpn AgileVpn.sys Tue Jul 14 01:10:24 2009 (4A5BCCF0) fffff880`08ed5000 fffff880`08edd000 ALSysIO64 ALSysIO64.sys Sun Apr 19 20:41:04 2009 (49EB7E50) fffff880`0137a000 fffff880`01385000 amdxata amdxata.sys Tue May 19 18:56:59 2009 (4A12F2EB) fffff880`01021000 fffff880`0102a000 atapi atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`00c00000 fffff880`00c2a000 ataport ataport.SYS Tue Jul 14 00:19:52 2009 (4A5BC118) fffff880`0667c000 fffff880`06699000 avgntflt avgntflt.sys Thu Nov 11 15:59:48 2010 (4CDC12F4) fffff880`0418e000 fffff880`041b0000 avipbb avipbb.sys Mon Feb 22 10:08:50 2010 (4B8257B2) fffff880`1000c000 fffff880`10050000 aw6b1a9p aw6b1a9p.SYS Sat Jul 17 11:58:04 2010 (4C418CBC) fffff880`01a33000 fffff880`01a3a000 Beep Beep.SYS Tue Jul 14 01:00:13 2009 (4A5BCA8D) fffff880`0417d000 fffff880`0418e000 blbdrive blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF) fffff880`075bd000 fffff880`075db000 bowser bowser.sys Wed Feb 23 05:15:06 2011 (4D6497DA) fffff960`00710000 fffff960`00737000 cdd cdd.dll unavailable (00000000) fffff880`08fb1000 fffff880`08fce000 cdfs cdfs.sys Tue Jul 14 00:19:46 2009 (4A5BC112) fffff880`01a00000 fffff880`01a2a000 cdrom cdrom.sys Tue Jul 14 00:19:54 2009 (4A5BC11A) fffff880`00d1d000 fffff880`00ddd000 CI CI.dll Tue Jul 14 02:32:13 2009 (4A5BE01D) fffff880`01b81000 fffff880`01bb1000 CLASSPNP CLASSPNP.SYS Tue Jul 14 00:19:58 2009 (4A5BC11E) fffff880`00cbf000 fffff880`00d1d000 CLFS CLFS.SYS Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`0125e000 fffff880`012d1000 cng cng.sys Tue Jul 14 00:49:40 2009 (4A5BC814) fffff880`041d6000 fffff880`041e6000 CompositeBus CompositeBus.sys Tue Jul 14 01:00:33 2009 (4A5BCAA1) fffff880`06954000 fffff880`06962000 crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD) fffff880`040dc000 fffff880`0415f000 csc csc.sys Tue Jul 14 00:24:26 2009 (4A5BC22A) fffff880`0415f000 fffff880`0417d000 dfsc dfsc.sys Tue Jul 14 00:23:44 2009 (4A5BC200) fffff880`040cd000 fffff880`040dc000 discache discache.sys Tue Jul 14 00:37:18 2009 (4A5BC52E) fffff880`01b6b000 fffff880`01b81000 disk disk.sys Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`05987000 fffff880`059a9000 drmk drmk.sys Tue Jul 14 02:01:25 2009 (4A5BD8E5) fffff880`0696e000 fffff880`06977000 dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`06962000 fffff880`0696e000 dump_dumpata dump_dumpata.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`06977000 fffff880`0698a000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F) fffff880`069cc000 fffff880`069d8000 Dxapi Dxapi.sys Tue Jul 14 00:38:28 2009 (4A5BC574) fffff880`042e2000 fffff880`043d6000 dxgkrnl dxgkrnl.sys Wed Jan 26 04:22:56 2011 (4D3FA1A0) fffff880`04200000 fffff880`04246000 dxgmms1 dxgmms1.sys Wed Jan 26 04:22:12 2011 (4D3FA174) fffff880`013d1000 fffff880`013e5000 fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481) fffff880`01385000 fffff880`013d1000 fltmgr fltmgr.sys Tue Jul 14 00:19:59 2009 (4A5BC11F) fffff880`01411000 fffff880`0141b000 Fs_Rec Fs_Rec.sys Tue Jul 14 00:19:45 2009 (4A5BC111) fffff880`01b31000 fffff880`01b6b000 fvevol fvevol.sys Sat Sep 26 03:34:26 2009 (4ABD7DB2) fffff880`0168b000 fffff880`016d5000 fwpkclnt fwpkclnt.sys Tue Jul 14 00:21:08 2009 (4A5BC164) fffff800`03015000 fffff800`0305e000 hal hal.dll Tue Jul 14 02:27:36 2009 (4A5BDF08) fffff880`04246000 fffff880`0426a000 HDAudBus HDAudBus.sys Tue Jul 14 01:06:13 2009 (4A5BCBF5) fffff880`0426a000 fffff880`0427b000 HECIx64 HECIx64.sys Tue Sep 21 17:59:04 2010 (4C98E458) fffff880`0660e000 fffff880`06627000 HIDCLASS HIDCLASS.SYS Tue Jul 14 01:06:21 2009 (4A5BCBFD) fffff880`06627000 fffff880`0662f080 HIDPARSE HIDPARSE.SYS Tue Jul 14 01:06:17 2009 (4A5BCBF9) fffff880`06600000 fffff880`0660e000 hidusb hidusb.sys Tue Jul 14 01:06:22 2009 (4A5BCBFE) fffff880`074f5000 fffff880`075bd000 HTTP HTTP.sys Tue Jul 14 00:22:16 2009 (4A5BC1A8) fffff880`01b28000 fffff880`01b31000 hwpolicy hwpolicy.sys Tue Jul 14 00:19:22 2009 (4A5BC0FA) fffff880`043d8000 fffff880`043f6000 i8042prt i8042prt.sys Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`10050000 fffff880`10066000 intelppm intelppm.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD) fffff880`00e5c000 fffff880`00e7d000 jraid jraid.sys Tue Sep 07 03:37:00 2010 (4C85A54C) fffff880`10de9000 fffff880`10df8000 kbdclass kbdclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116) fffff880`06630000 fffff880`0663e000 kbdhid kbdhid.sys Tue Jul 14 01:00:20 2009 (4A5BCA94) fffff800`00ba5000 fffff800`00baf000 kdcom kdcom.dll Sat Feb 05 12:21:45 2011 (4D4D40D9) fffff880`08f56000 fffff880`08f5d000 KernExplorer64 KernExplorer64.sys Thu Feb 03 14:28:26 2011 (4D4ABB8A) fffff880`05840000 fffff880`05883000 ks ks.sys Thu Mar 04 04:32:25 2010 (4B8F37D9) fffff880`015de000 fffff880`015f8000 ksecdd ksecdd.sys Tue Jul 14 00:20:54 2009 (4A5BC156) fffff880`01660000 fffff880`0168b000 ksecpkg ksecpkg.sys Fri Dec 11 06:03:32 2009 (4B21E0B4) fffff880`059a9000 fffff880`059ae200 ksthunk ksthunk.sys Tue Jul 14 01:00:19 2009 (4A5BCA93) fffff880`013e5000 fffff880`013fa000 Lbd Lbd.sys Thu Feb 03 14:23:53 2011 (4D4ABA79) fffff880`059af000 fffff880`059c4000 lltdio lltdio.sys Tue Jul 14 01:08:50 2009 (4A5BCC92) fffff880`06659000 fffff880`0667c000 luafv luafv.sys Tue Jul 14 00:26:13 2009 (4A5BC295) fffff880`06946000 fffff880`06954000 MBfilt64 MBfilt64.sys Fri Jul 31 04:40:32 2009 (4A7267B0) fffff880`00c67000 fffff880`00cab000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 02:29:10 2009 (4A5BDF66) fffff880`0664b000 fffff880`06659000 monitor monitor.sys Tue Jul 14 00:38:52 2009 (4A5BC58C) fffff880`02e2f000 fffff880`02e3e000 mouclass mouclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116) fffff880`0663e000 fffff880`0664b000 mouhid mouhid.sys Tue Jul 14 01:00:20 2009 (4A5BCA94) fffff880`00fd0000 fffff880`00fea000 mountmgr mountmgr.sys Tue Jul 14 00:19:54 2009 (4A5BC11A) fffff880`075db000 fffff880`075f3000 mpsdrv mpsdrv.sys Tue Jul 14 01:08:25 2009 (4A5BCC79) fffff880`07400000 fffff880`0742d000 mrxsmb mrxsmb.sys Wed Feb 23 05:15:23 2011 (4D6497EB) fffff880`0742d000 fffff880`0747b000 mrxsmb10 mrxsmb10.sys Wed Feb 23 05:15:14 2011 (4D6497E2) fffff880`0747b000 fffff880`0749e000 mrxsmb20 mrxsmb20.sys Wed Feb 23 05:15:13 2011 (4D6497E1) fffff880`017e1000 fffff880`017ec000 Msfs Msfs.SYS Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`011bf000 fffff880`011c9000 msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE) fffff880`01200000 fffff880`0125e000 msrpc msrpc.sys Tue Jul 14 00:21:32 2009 (4A5BC17C) fffff880`040c2000 fffff880`040cd000 mssmbios mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE) fffff880`01b16000 fffff880`01b28000 mup mup.sys Tue Jul 14 00:23:45 2009 (4A5BC201) fffff880`01017000 fffff880`01021000 mv91cons mv91cons.sys Fri Oct 01 04:29:09 2010 (4CA55585) fffff880`012e5000 fffff880`01372000 mv91xx mv91xx.sys Fri Oct 01 04:27:07 2010 (4CA5550B) fffff880`01372000 fffff880`0137a000 mvxxmm mvxxmm.sys Fri Oct 01 04:26:49 2010 (4CA554F9) fffff880`016ef000 fffff880`017e1000 ndis ndis.sys Tue Jul 14 00:21:40 2009 (4A5BC184) fffff880`04024000 fffff880`04030000 ndistapi ndistapi.sys Tue Jul 14 01:10:00 2009 (4A5BCCD8) fffff880`04030000 fffff880`0405f000 ndiswan ndiswan.sys Tue Jul 14 01:10:11 2009 (4A5BCCE3) fffff880`05908000 fffff880`0591d000 NDProxy NDProxy.SYS Tue Jul 14 01:10:05 2009 (4A5BCCDD) fffff880`02fd1000 fffff880`02fe0000 netbios netbios.sys Tue Jul 14 01:09:26 2009 (4A5BCCB6) fffff880`02ec8000 fffff880`02f0d000 netbt netbt.sys Tue Jul 14 00:21:28 2009 (4A5BC178) fffff880`01600000 fffff880`01660000 NETIO NETIO.SYS Tue Jul 14 00:21:46 2009 (4A5BC18A) fffff880`017ec000 fffff880`017fd000 Npfs Npfs.SYS Tue Jul 14 00:19:48 2009 (4A5BC114) fffff880`040b6000 fffff880`040c2000 nsiproxy nsiproxy.sys Tue Jul 14 00:21:02 2009 (4A5BC15E) fffff800`0305e000 fffff800`0363b000 nt ntkrnlmp.exe Wed Oct 27 03:43:09 2010 (4CC791BD) fffff880`0143b000 fffff880`015de000 Ntfs Ntfs.sys Tue Jul 14 00:20:47 2009 (4A5BC14F) fffff880`01a2a000 fffff880`01a33000 Null Null.SYS Tue Jul 14 00:19:37 2009 (4A5BC109) fffff880`058ef000 fffff880`05908000 nusb3hub nusb3hub.sys Thu Sep 30 05:00:03 2010 (4CA40B43) fffff880`10d15000 fffff880`10d45000 nusb3xhc nusb3xhc.sys Thu Sep 30 05:00:03 2010 (4CA40B43) fffff880`10d13000 fffff880`10d14180 nvBridge nvBridge.kmd Sat Mar 26 06:48:01 2011 (4D8D8C21) fffff880`0591d000 fffff880`0594a000 nvhda64v nvhda64v.sys Thu Mar 03 15:59:02 2011 (4D6FBAC6) fffff880`10071000 fffff880`10d12980 nvlddmkm nvlddmkm.sys Sat Mar 26 06:53:38 2011 (4D8D8D72) fffff880`02fab000 fffff880`02fd1000 pacer pacer.sys Tue Jul 14 01:09:41 2009 (4A5BCCC5) fffff880`011d6000 fffff880`011eb000 partmgr partmgr.sys Tue Jul 14 00:19:58 2009 (4A5BC11E) fffff880`00f9d000 fffff880`00fd0000 pci pci.sys Tue Jul 14 00:19:51 2009 (4A5BC117) fffff880`01000000 fffff880`01007000 pciide pciide.sys Tue Jul 14 00:19:49 2009 (4A5BC115) fffff880`01007000 fffff880`01017000 PCIIDEX PCIIDEX.SYS Tue Jul 14 00:19:48 2009 (4A5BC114) fffff880`01400000 fffff880`01411000 pcw pcw.sys Tue Jul 14 00:19:27 2009 (4A5BC0FF) fffff880`08a4a000 fffff880`08af0000 peauth peauth.sys Tue Jul 14 02:01:19 2009 (4A5BD8DF) fffff880`0594a000 fffff880`05987000 portcls portcls.sys Tue Jul 14 01:06:27 2009 (4A5BCC03) fffff880`00cab000 fffff880`00cbf000 PSHED PSHED.dll Tue Jul 14 02:32:23 2009 (4A5BE027) fffff880`04000000 fffff880`04024000 rasl2tp rasl2tp.sys Tue Jul 14 01:10:11 2009 (4A5BCCE3) fffff880`00c2a000 fffff880`00c45000 raspppoe raspppoe.sys Tue Jul 14 01:10:17 2009 (4A5BCCE9) fffff880`00c45000 fffff880`00c66000 raspptp raspptp.sys Tue Jul 14 01:10:18 2009 (4A5BCCEA) fffff880`00ddd000 fffff880`00df7000 rassstp rassstp.sys Tue Jul 14 01:10:25 2009 (4A5BCCF1) fffff880`04065000 fffff880`040b6000 rdbss rdbss.sys Tue Jul 14 00:24:09 2009 (4A5BC219) fffff880`10066000 fffff880`10071000 rdpbus rdpbus.sys Tue Jul 14 01:17:46 2009 (4A5BCEAA) fffff880`01a7d000 fffff880`01a86000 RDPCDD RDPCDD.sys Tue Jul 14 01:16:34 2009 (4A5BCE62) fffff880`01be7000 fffff880`01bf0000 rdpencdd rdpencdd.sys Tue Jul 14 01:16:34 2009 (4A5BCE62) fffff880`01bf0000 fffff880`01bf9000 rdprefmp rdprefmp.sys Tue Jul 14 01:16:35 2009 (4A5BCE63) fffff880`01adc000 fffff880`01b16000 rdyboost rdyboost.sys Tue Jul 14 00:34:34 2009 (4A5BC48A) fffff880`059c4000 fffff880`059dc000 rspndr rspndr.sys Tue Jul 14 01:08:50 2009 (4A5BCC92) fffff880`10d83000 fffff880`10de9000 Rt64win7 Rt64win7.sys Thu Nov 11 06:35:36 2010 (4CDB8EB8) fffff880`066dc000 fffff880`06945800 RTKVHD64 RTKVHD64.sys Tue Nov 02 11:25:59 2010 (4CCFF547) fffff880`01190000 fffff880`011bf000 SCSIPORT SCSIPORT.SYS Tue Jul 14 01:01:04 2009 (4A5BCAC0) fffff880`08af0000 fffff880`08afb000 secdrv secdrv.SYS Wed Sep 13 14:18:38 2006 (4508052E) fffff880`10000000 fffff880`1000c000 serenum serenum.sys Tue Jul 14 01:00:33 2009 (4A5BCAA1) fffff880`02fe0000 fffff880`02ffd000 serial serial.sys Tue Jul 14 01:00:40 2009 (4A5BCAA8) fffff880`01ad4000 fffff880`01adc000 spldr spldr.sys Mon May 11 17:56:27 2009 (4A0858BB) fffff880`08ee5000 fffff880`08f56000 spsys spsys.sys Mon May 11 18:20:58 2009 (4A085E7A) fffff880`0102a000 fffff880`01187000 sptd sptd.sys Tue Aug 24 07:13:12 2010 (4C7362F8) fffff880`08e40000 fffff880`08ed5000 srv srv.sys Wed Feb 23 05:16:24 2011 (4D649828) fffff880`08b3a000 fffff880`08ba1000 srv2 srv2.sys Wed Feb 23 05:15:59 2011 (4D64980F) fffff880`08afb000 fffff880`08b28000 srvnet srvnet.sys Wed Feb 23 05:15:49 2011 (4D649805) fffff880`10df8000 fffff880`10df9480 swenum swenum.sys Tue Jul 14 01:00:18 2009 (4A5BCA92) fffff880`01803000 fffff880`01a00000 tcpip tcpip.sys Mon Jun 14 04:39:04 2010 (4C15A458) fffff880`08b28000 fffff880`08b3a000 tcpipreg tcpipreg.sys Tue Jul 14 01:09:49 2009 (4A5BCCCD) fffff880`012d1000 fffff880`012de000 TDI TDI.SYS Tue Jul 14 00:21:18 2009 (4A5BC16E) fffff880`0141b000 fffff880`01439000 tdx tdx.sys Tue Jul 14 00:21:15 2009 (4A5BC16B) fffff880`02e1b000 fffff880`02e2f000 termdd termdd.sys Tue Jul 14 01:16:36 2009 (4A5BCE64) fffff960`00440000 fffff960`0044a000 TSDDD TSDDD.dll Tue Jul 14 01:16:34 2009 (4A5BCE62) fffff880`08edd000 fffff880`08ee5000 TuneUpUtilitiesDriver64 TuneUpUtilitiesDriver64.sys Thu Sep 17 12:54:52 2009 (4AB2238C) fffff880`041b0000 fffff880`041d6000 tunnel tunnel.sys Tue Jul 14 01:09:37 2009 (4A5BCCC1) fffff880`08f5d000 fffff880`08fb1000 udfs udfs.sys Tue Jul 14 00:23:37 2009 (4A5BC1F9) fffff880`05883000 fffff880`05895000 umbus umbus.sys Tue Jul 14 01:06:56 2009 (4A5BCC20) fffff880`069d8000 fffff880`069f5000 usbccgp usbccgp.sys Tue Jul 14 01:06:45 2009 (4A5BCC15) fffff880`043d6000 fffff880`043d7f00 USBD USBD.SYS Tue Jul 14 01:06:23 2009 (4A5BCBFF) fffff880`0427b000 fffff880`0428c000 usbehci usbehci.sys Tue Jul 14 01:06:30 2009 (4A5BCC06) fffff880`05895000 fffff880`058ef000 usbhub usbhub.sys Tue Jul 14 01:07:09 2009 (4A5BCC2D) fffff880`0428c000 fffff880`042e2000 USBPORT USBPORT.SYS Tue Jul 14 01:06:31 2009 (4A5BCC07) fffff880`011c9000 fffff880`011d6000 vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB) fffff880`01a3a000 fffff880`01a48000 vga vga.sys Tue Jul 14 00:38:47 2009 (4A5BC587) fffff880`01a48000 fffff880`01a6d000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B) fffff880`016d5000 fffff880`016e5000 vmstorfl vmstorfl.sys Tue Jul 14 00:42:54 2009 (4A5BC67E) fffff880`011eb000 fffff880`01200000 volmgr volmgr.sys Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`00e00000 fffff880`00e5c000 volmgrx volmgrx.sys Tue Jul 14 00:20:33 2009 (4A5BC141) fffff880`01a88000 fffff880`01ad4000 volsnap volsnap.sys Tue Jul 14 00:20:08 2009 (4A5BC128) fffff880`02f0d000 fffff880`02fa2000 vsdatant vsdatant.sys Sun May 09 17:28:58 2010 (4BE6E2CA) fffff880`02e00000 fffff880`02e1b000 wanarp wanarp.sys Tue Jul 14 01:10:21 2009 (4A5BCCED) fffff880`01a6d000 fffff880`01a7d000 watchdog watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F) fffff880`00e93000 fffff880`00f37000 Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F) fffff880`00f37000 fffff880`00f46000 WDFLDR WDFLDR.SYS Tue Jul 14 00:19:54 2009 (4A5BC11A) fffff880`02fa2000 fffff880`02fab000 wfplwf wfplwf.sys Tue Jul 14 01:09:26 2009 (4A5BCCB6) fffff960`000d0000 fffff960`003e2000 win32k win32k.sys Thu Mar 03 03:58:01 2011 (4D6F11C9) fffff880`08fce000 fffff880`08fdf000 WinUSB WinUSB.sys Tue Jul 14 01:06:28 2009 (4A5BCC04) fffff880`043f6000 fffff880`043ff000 wmiacpi wmiacpi.sys Tue Jul 14 00:31:02 2009 (4A5BC3B6) fffff880`01187000 fffff880`01190000 WMILIB WMILIB.SYS Tue Jul 14 00:19:51 2009 (4A5BC117) fffff880`06699000 fffff880`066ba000 WudfPf WudfPf.sys Tue Jul 14 01:05:37 2009 (4A5BCBD1) fffff880`08e00000 fffff880`08e31000 WUDFRd WUDFRd.sys Tue Jul 14 01:06:06 2009 (4A5BCBEE) Unloaded modules: fffff880`0698a000 fffff880`069bb000 WUDFRd.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`066ba000 fffff880`066cb000 WinUSB.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0698a000 fffff880`0699b000 WinUSB.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0699b000 fffff880`069cc000 WUDFRd.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01bb1000 fffff880`01bbf000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01bbf000 fffff880`01bcb000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01bcb000 fffff880`01bd4000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01bd4000 fffff880`01be7000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 @WindowSkull: I've had some problems, but it appeared to be working, I'll check again
@SmurofNeves: I followed that post, did I do something wrong?
@Minotar: I like zoneAlarm, but if neccesary I'll try MSE. Beside that, the report doesn't show WHY it's going bad?
Had some problems with Alcohol the time I installed, it could mount a virtual drive, I removed it an reinstalled, but not STPD, i'll try again. When I just installed windows, I used 270.xx beta driver. As I suspected the driver being faulty. I switched to 266.66, which is doing better so far.
I'll try to reinstall and then check drivers, I'll be back.
Thanks so far.
@SmurofNeves: I followed that post, did I do something wrong?
@Minotar: I like zoneAlarm, but if neccesary I'll try MSE. Beside that, the report doesn't show WHY it's going bad?
Had some problems with Alcohol the time I installed, it could mount a virtual drive, I removed it an reinstalled, but not STPD, i'll try again. When I just installed windows, I used 270.xx beta driver. As I suspected the driver being faulty. I switched to 266.66, which is doing better so far.
I'll try to reinstall and then check drivers, I'll be back.
Thanks so far.
No problem.
I'll keep an eye on the thread.
I'll keep an eye on the thread.
I ran verifier today, and it keeps giving BSOD'd on the windows loading screen, you know, where these four colored balls emerge and spin a little and form the windows logo. There's not much in the BSOD itself, no title I can google, no driver that gives the error, just a stop code:
0x0000001E (0xFFFFFFFF0000005,
0xFFFFF8000308EE36,
0x0000000000000000,
0x0000000000000000)
What does this tell me?
0x0000001E (0xFFFFFFFF0000005,
0xFFFFF8000308EE36,
0x0000000000000000,
0x0000000000000000)
What does this tell me?
Hi again,
You can boot into safe mode and disable Driver Verifier and it will boot.
Have you removed SPTD yet? If not can you please run this tool : DuplexSecure
Also,I made a mistake earlier on vsdatant.sys ,its a firewall,not an AV.
Installing MSE wouldn't hurt though,and use the Microsfot firewall instead
You can boot into safe mode and disable Driver Verifier and it will boot.
Have you removed SPTD yet? If not can you please run this tool : DuplexSecure
Also,I made a mistake earlier on vsdatant.sys ,its a firewall,not an AV.
Installing MSE wouldn't hurt though,and use the Microsfot firewall instead
Hi again,
I've deleted STPD and zonealarm. I also tried verifier again, but selecting only a couple the first time and more if it all goes well. Got me some BSOD's on the second try and finally one that gave me kernexplorer64.sys, which is Ad-Aware, anti ad-ware software. I also just had an win32k.sys BSOD during some game. All these driver errors, is something wrong with my windows install? Could reinstalling help?
I've deleted STPD and zonealarm. I also tried verifier again, but selecting only a couple the first time and more if it all goes well. Got me some BSOD's on the second try and finally one that gave me kernexplorer64.sys, which is Ad-Aware, anti ad-ware software. I also just had an win32k.sys BSOD during some game. All these driver errors, is something wrong with my windows install? Could reinstalling help?
Upload the DMP's and I'll take a look.
It's possible a re-install will work,but probably because you won't be using any 3rd party drivers more so than fixing windows ones.
It's possible a re-install will work,but probably because you won't be using any 3rd party drivers more so than fixing windows ones.
One cause could be a nearly full HDD, check for the amount of free space.
Another cause could be RAM, you mentioned running memtest86+, how long did you run it?
See this tutorial for testing procedure, RAM - Test with Memtest86+, first test with all RAM cards installed for 7 passes or overnight.
You have 2x4GB RAM, have you increase the integrated memory controller voltage?
With 4GB RAM or more, 2GB RAM cards or 4 RAM cards installed, you will normally need to bump the memory controller voltage.
Are your RAM cards in the blue slots DIMM 1&3 or black slots DIMM 2&4?
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and memory controller voltages are.
Memory controller voltage is CPU IO.
Another cause could be RAM, you mentioned running memtest86+, how long did you run it?
See this tutorial for testing procedure, RAM - Test with Memtest86+, first test with all RAM cards installed for 7 passes or overnight.
You have 2x4GB RAM, have you increase the integrated memory controller voltage?
With 4GB RAM or more, 2GB RAM cards or 4 RAM cards installed, you will normally need to bump the memory controller voltage.
Are your RAM cards in the blue slots DIMM 1&3 or black slots DIMM 2&4?
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and memory controller voltages are.
Memory controller voltage is CPU IO.
Hi,
I have 3 HDD's running, of which 1 (WD15EARS) is used only for storage of movies and some backup. The movie partition has 4 of 1344 GB free, and all other partitions have over 15GB free. The movies hdd has been this way for a while, and also in another pc.
When i checked I think I ran about 10 passes but will do it again tomorrow.
The modules are in slot 1&3 now and when I tested, but have been in 1&2 for a couple of days.
Haven't changed any voltages, and they are:
CPU Core: 1.208
CPU I/O: 1.040:
System agent: 0.920
DRAM: 1.488
3.3V: 3.280
5V: 5.045
12V: 12.232
i've been running CoreTemp, which shows about 35 Celsius, with no overclock, the stock cpu cooler, and 3 120mm fans running some 800rpm. I have a Coolermaster 212+ cooler waiting to be installed.
I'll post some screenshots in a bit and will try to check under load, if it holds without BSODing. I'll let you know how the test goes tomorrow night.
The new dmp file zip will be included in a minute. This has been without zonealarm and STPD.
Also, when I'm playing fullscreen (NFS hot pursuit) everything is fine, but I've got a tower defense game (Defense Grid), played windowed mode, which allways first gets the nvidia driver to freak out and causes windows to switch to the basic theme, and then cause an BSOD. usually without any notice of what caused it.
Thanks for your replies.
I have 3 HDD's running, of which 1 (WD15EARS) is used only for storage of movies and some backup. The movie partition has 4 of 1344 GB free, and all other partitions have over 15GB free. The movies hdd has been this way for a while, and also in another pc.
When i checked I think I ran about 10 passes but will do it again tomorrow.
The modules are in slot 1&3 now and when I tested, but have been in 1&2 for a couple of days.
Haven't changed any voltages, and they are:
CPU Core: 1.208
CPU I/O: 1.040:
System agent: 0.920
DRAM: 1.488
3.3V: 3.280
5V: 5.045
12V: 12.232
i've been running CoreTemp, which shows about 35 Celsius, with no overclock, the stock cpu cooler, and 3 120mm fans running some 800rpm. I have a Coolermaster 212+ cooler waiting to be installed.
I'll post some screenshots in a bit and will try to check under load, if it holds without BSODing. I'll let you know how the test goes tomorrow night.
The new dmp file zip will be included in a minute. This has been without zonealarm and STPD.
Also, when I'm playing fullscreen (NFS hot pursuit) everything is fine, but I've got a tower defense game (Defense Grid), played windowed mode, which allways first gets the nvidia driver to freak out and causes windows to switch to the basic theme, and then cause an BSOD. usually without any notice of what caused it.
Thanks for your replies.
Hi again,
Alot of the dmps seem to be attributed to lavasoft ad-aware,I'd suggest uninstalling it to see if it is a problem.
Also your Nvidia driver seems to have casued at least one
Its not too much out of date but it won't hurt to update it - Update Link
Another was attributed to your direct x,usually windows drivers are not to blame so hopefully the above driver will solve it,but I suspect it may be the actual game Defense Grid as it was the top process when it crashed
Also Id suggest updating to Service Pack 1 -SP1 Update
Dan
Alot of the dmps seem to be attributed to lavasoft ad-aware,I'd suggest uninstalling it to see if it is a problem.
Code:
STACK_TEXT: fffff880`09d0f618 fffff800`035093dc : 00000000`000000c4 00000000`000000f6 00000000`00000004 fffffa80`0a2a8b30 : nt!KeBugCheckEx fffff880`09d0f620 fffff800`0351eae4 : 00000000`00000004 fffffa80`0a2a8b30 00000000`00000002 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`09d0f660 fffff800`032d9030 : fffff800`03370960 fffff880`09d0f890 00000000`00000000 fffffa80`07de8e00 : nt!VfCheckUserHandle+0x1b4 fffff880`09d0f740 fffff800`033532e5 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`03353200 : nt! ?? ::NNGAKEGL::`string'+0x20b4e fffff880`09d0f810 fffff800`0351e878 : 00000000`000003e0 fffffa80`07de8e40 fffff880`09d0f8f0 fffff880`06fbbb32 : nt!ObReferenceObjectByHandle+0x25 fffff880`09d0f860 fffff880`06fbb277 : 00000000`00000000 fffffa80`08a0a000 fffffa80`07de8e40 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48 fffff880`09d0f8b0 00000000`00000000 : fffffa80`08a0a000 fffffa80`07de8e40 00000000`00000000 fffff880`09d0f970 : KernExplorer64+0x1277
Code:
PROCESS_NAME: AAWService.exe
Code:
Probably caused by : nvlddmkm.sys ( nvlddmkm+fd4e7 )
Code:
STACK_TEXT: fffff880`05dfb530 fffff880`101254e7 : fffffa80`08c2ed10 fffffa80`086e6010 fffffa80`086e6258 00020000`00000000 : nt!KeAcquireInStackQueuedSpinLock+0x5f fffff880`05dfb580 fffffa80`08c2ed10 : fffffa80`086e6010 fffffa80`086e6258 00020000`00000000 00000000`00000000 : nvlddmkm+0xfd4e7 fffff880`05dfb588 fffffa80`086e6010 : fffffa80`086e6258 00020000`00000000 00000000`00000000 00044000`14841150 : 0xfffffa80`08c2ed10 fffff880`05dfb590 fffffa80`086e6258 : 00020000`00000000 00000000`00000000 00044000`14841150 00000000`00000000 : 0xfffffa80`086e6010 fffff880`05dfb598 00020000`00000000 : 00000000`00000000 00044000`14841150 00000000`00000000 00000000`00000000 : 0xfffffa80`086e6258 fffff880`05dfb5a0 00000000`00000000 : 00044000`14841150 00000000`00000000 00000000`00000000 fffffa80`09765000 : 0x20000`00000000
Another was attributed to your direct x,usually windows drivers are not to blame so hopefully the above driver will solve it,but I suspect it may be the actual game Defense Grid as it was the top process when it crashed
Code:
Probably caused by : dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::`scalar deleting destructor'+b6 ) PROCESS_NAME: DefenseGrid.ex
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dan\Desktop\Windows_NT6_BSOD_jcgriff2\041711-22963-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`0300e000 PsLoadedModuleList = 0xfffff800`0324be50 Debug session time: Sun Apr 17 12:44:58.300 2011 (GMT+1) System Uptime: 0 days 0:15:09.269 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88001004fa9, fffff880083a2970, 0} Probably caused by : fltmgr.sys ( fltmgr!GetContextFromStreamList+99 ) 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: fffff88001004fa9, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880083a2970, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: fltmgr!GetContextFromStreamList+99 fffff880`01004fa9 488b4820 mov rcx,qword ptr [rax+20h] CONTEXT: fffff880083a2970 -- (.cxr 0xfffff880083a2970) rax=fa8008ce57880460 rbx=0000000000000000 rcx=fa8008ce57880460 rdx=fffffa80084f6bb0 rsi=fffffa800987c7b0 rdi=fffffa800987c760 rip=fffff88001004fa9 rsp=fffff880083a3340 rbp=fffff880083a3480 r8=0000000000000000 r9=fffff880083a3478 r10=fffffa800987c768 r11=fffff880083a3330 r12=fffff880083a3478 r13=fffffa80073805b0 r14=0000000000000000 r15=fffffa80084f6bb0 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 fltmgr!GetContextFromStreamList+0x99: fffff880`01004fa9 488b4820 mov rcx,qword ptr [rax+20h] ds:002b:fa8008ce`57880480=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: AAWService.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88001004fa9 STACK_TEXT: fffff880`083a3340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!GetContextFromStreamList+0x99 FOLLOWUP_IP: fltmgr!GetContextFromStreamList+99 fffff880`01004fa9 488b4820 mov rcx,qword ptr [rax+20h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: fltmgr!GetContextFromStreamList+99 FOLLOWUP_NAME: MachineOwner MODULE_NAME: fltmgr IMAGE_NAME: fltmgr.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11f STACK_COMMAND: .cxr 0xfffff880083a2970 ; kb FAILURE_BUCKET_ID: X64_0x3B_fltmgr!GetContextFromStreamList+99 BUCKET_ID: X64_0x3B_fltmgr!GetContextFromStreamList+99 Followup: MachineOwner --------- 1: kd> lmntsm start end module name fffff880`03e86000 fffff880`03ec4000 1394ohci 1394ohci.sys Tue Jul 14 01:07:12 2009 (4A5BCC30) fffff880`00ee8000 fffff880`00f3f000 ACPI ACPI.sys Tue Jul 14 00:19:34 2009 (4A5BC106) fffff880`02c36000 fffff880`02cc0000 afd afd.sys Tue Jul 14 00:21:40 2009 (4A5BC184) fffff880`0439e000 fffff880`043b4000 AgileVpn AgileVpn.sys Tue Jul 14 01:10:24 2009 (4A5BCCF0) fffff880`086ca000 fffff880`086d2000 ALSysIO64 ALSysIO64.sys Sun Apr 19 20:41:04 2009 (49EB7E50) fffff880`011c9000 fffff880`011d4000 amdxata amdxata.sys Tue May 19 18:56:59 2009 (4A12F2EB) fffff880`01101000 fffff880`0110a000 atapi atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`0110a000 fffff880`01134000 ataport ataport.SYS Tue Jul 14 00:19:52 2009 (4A5BC118) fffff880`06453000 fffff880`06470000 avgntflt avgntflt.sys Thu Nov 11 15:59:48 2010 (4CDC12F4) fffff880`03fa5000 fffff880`03fc7000 avipbb avipbb.sys Mon Feb 22 10:08:50 2010 (4B8257B2) fffff880`01899000 fffff880`018a0000 Beep Beep.SYS Tue Jul 14 01:00:13 2009 (4A5BCA8D) fffff880`03f94000 fffff880`03fa5000 blbdrive blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF) fffff880`06b64000 fffff880`06b82000 bowser bowser.sys Wed Feb 23 05:15:06 2011 (4D6497DA) fffff960`00690000 fffff960`006b7000 cdd cdd.dll unavailable (00000000) fffff880`01866000 fffff880`01890000 cdrom cdrom.sys Tue Jul 14 00:19:54 2009 (4A5BC11A) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Tue Jul 14 02:32:13 2009 (4A5BE01D) fffff880`01800000 fffff880`01830000 CLASSPNP CLASSPNP.SYS Tue Jul 14 00:19:58 2009 (4A5BC11E) fffff880`00d31000 fffff880`00d8f000 CLFS CLFS.SYS Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`01463000 fffff880`014d6000 cng cng.sys Tue Jul 14 00:49:40 2009 (4A5BC814) fffff880`0438e000 fffff880`0439e000 CompositeBus CompositeBus.sys Tue Jul 14 01:00:33 2009 (4A5BCAA1) fffff880`0677c000 fffff880`0678a000 crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD) fffff880`03ef3000 fffff880`03f76000 csc csc.sys Tue Jul 14 00:24:26 2009 (4A5BC22A) fffff880`03f76000 fffff880`03f94000 dfsc dfsc.sys Tue Jul 14 00:23:44 2009 (4A5BC200) fffff880`00cc0000 fffff880`00ccf000 discache discache.sys Tue Jul 14 00:37:18 2009 (4A5BC52E) fffff880`019e7000 fffff880`019fd000 disk disk.sys Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`0536a000 fffff880`0538c000 drmk drmk.sys Tue Jul 14 02:01:25 2009 (4A5BD8E5) fffff880`06796000 fffff880`0679f000 dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`0678a000 fffff880`06796000 dump_dumpata dump_dumpata.sys Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`0679f000 fffff880`067b2000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F) fffff880`06770000 fffff880`0677c000 Dxapi Dxapi.sys Tue Jul 14 00:38:28 2009 (4A5BC574) fffff880`10a80000 fffff880`10b74000 dxgkrnl dxgkrnl.sys Wed Jan 26 04:22:56 2011 (4D3FA1A0) fffff880`10b74000 fffff880`10bba000 dxgmms1 dxgmms1.sys Wed Jan 26 04:22:12 2011 (4D3FA174) fffff880`0104c000 fffff880`01060000 fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481) fffff880`01000000 fffff880`0104c000 fltmgr fltmgr.sys Tue Jul 14 00:19:59 2009 (4A5BC11F) fffff880`014e7000 fffff880`014f1000 Fs_Rec Fs_Rec.sys Tue Jul 14 00:19:45 2009 (4A5BC111) fffff880`019ad000 fffff880`019e7000 fvevol fvevol.sys Sat Sep 26 03:34:26 2009 (4ABD7DB2) fffff880`018aa000 fffff880`018f4000 fwpkclnt fwpkclnt.sys Tue Jul 14 00:21:08 2009 (4A5BC164) fffff800`035eb000 fffff800`03634000 hal hal.dll Tue Jul 14 02:27:36 2009 (4A5BDF08) fffff880`10bba000 fffff880`10bde000 HDAudBus HDAudBus.sys Tue Jul 14 01:06:13 2009 (4A5BCBF5) fffff880`10bde000 fffff880`10bef000 HECIx64 HECIx64.sys Tue Sep 21 17:59:04 2010 (4C98E458) fffff880`06400000 fffff880`06419000 HIDCLASS HIDCLASS.SYS Tue Jul 14 01:06:21 2009 (4A5BCBFD) fffff880`06419000 fffff880`06421080 HIDPARSE HIDPARSE.SYS Tue Jul 14 01:06:17 2009 (4A5BCBF9) fffff880`067dd000 fffff880`067eb000 hidusb hidusb.sys Tue Jul 14 01:06:22 2009 (4A5BCBFE) fffff880`06a9c000 fffff880`06b64000 HTTP HTTP.sys Tue Jul 14 00:22:16 2009 (4A5BC1A8) fffff880`019a4000 fffff880`019ad000 hwpolicy hwpolicy.sys Tue Jul 14 00:19:22 2009 (4A5BC0FA) fffff880`04336000 fffff880`04354000 i8042prt i8042prt.sys Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`04378000 fffff880`0438e000 intelppm intelppm.sys Tue Jul 14 00:19:25 2009 (4A5BC0FD) fffff880`00fdd000 fffff880`00ffe000 jraid jraid.sys Tue Sep 07 03:37:00 2010 (4C85A54C) fffff880`04354000 fffff880`04363000 kbdclass kbdclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116) fffff880`06445000 fffff880`06453000 kbdhid kbdhid.sys Tue Jul 14 01:00:20 2009 (4A5BCA94) fffff800`00b9f000 fffff800`00ba9000 kdcom kdcom.dll Sat Feb 05 12:21:45 2011 (4D4D40D9) fffff880`086da000 fffff880`086e1000 KernExplorer64 KernExplorer64.sys Thu Feb 03 14:28:26 2011 (4D4ABB8A) fffff880`05227000 fffff880`0526a000 ks ks.sys Thu Mar 04 04:32:25 2010 (4B8F37D9) fffff880`013df000 fffff880`013f9000 ksecdd ksecdd.sys Tue Jul 14 00:20:54 2009 (4A5BC156) fffff880`01200000 fffff880`0122b000 ksecpkg ksecpkg.sys Fri Dec 11 06:03:32 2009 (4B21E0B4) fffff880`0538c000 fffff880`05391200 ksthunk ksthunk.sys Tue Jul 14 01:00:19 2009 (4A5BCA93) fffff880`01060000 fffff880`01075000 Lbd Lbd.sys Thu Feb 03 14:23:53 2011 (4D4ABA79) fffff880`0649e000 fffff880`064b3000 lltdio lltdio.sys Tue Jul 14 01:08:50 2009 (4A5BCC92) fffff880`06422000 fffff880`06445000 luafv luafv.sys Tue Jul 14 00:26:13 2009 (4A5BC295) fffff880`06762000 fffff880`06770000 MBfilt64 MBfilt64.sys Fri Jul 31 04:40:32 2009 (4A7267B0) fffff880`00cd9000 fffff880`00d1d000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 02:29:10 2009 (4A5BDF66) fffff880`067b2000 fffff880`067c0000 monitor monitor.sys Tue Jul 14 00:38:52 2009 (4A5BC58C) fffff880`04290000 fffff880`0429f000 mouclass mouclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116) fffff880`06470000 fffff880`0647d000 mouhid mouhid.sys Tue Jul 14 01:00:20 2009 (4A5BCA94) fffff880`010e7000 fffff880`01101000 mountmgr mountmgr.sys Tue Jul 14 00:19:54 2009 (4A5BC11A) fffff880`06b82000 fffff880`06b9a000 mpsdrv mpsdrv.sys Tue Jul 14 01:08:25 2009 (4A5BCC79) fffff880`06b9a000 fffff880`06bc7000 mrxsmb mrxsmb.sys Wed Feb 23 05:15:23 2011 (4D6497EB) fffff880`06a00000 fffff880`06a4e000 mrxsmb10 mrxsmb10.sys Wed Feb 23 05:15:14 2011 (4D6497E2) fffff880`06a4e000 fffff880`06a71000 mrxsmb20 mrxsmb20.sys Wed Feb 23 05:15:13 2011 (4D6497E1) fffff880`010dc000 fffff880`010e7000 Msfs Msfs.SYS Tue Jul 14 00:19:47 2009 (4A5BC113) fffff880`00f48000 fffff880`00f52000 msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE) fffff880`01075000 fffff880`010d3000 msrpc msrpc.sys Tue Jul 14 00:21:32 2009 (4A5BC17C) fffff880`02dec000 fffff880`02df7000 mssmbios mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE) fffff880`01992000 fffff880`019a4000 mup mup.sys Tue Jul 14 00:23:45 2009 (4A5BC201) fffff880`00fd3000 fffff880`00fdd000 mv91cons mv91cons.sys Fri Oct 01 04:29:09 2010 (4CA55585) fffff880`01134000 fffff880`011c1000 mv91xx mv91xx.sys Fri Oct 01 04:27:07 2010 (4CA5550B) fffff880`011c1000 fffff880`011c9000 mvxxmm mvxxmm.sys Fri Oct 01 04:26:49 2010 (4CA554F9) fffff880`014f1000 fffff880`015e3000 ndis ndis.sys Tue Jul 14 00:21:40 2009 (4A5BC184) fffff880`043d8000 fffff880`043e4000 ndistapi ndistapi.sys Tue Jul 14 01:10:00 2009 (4A5BCCD8) fffff880`04200000 fffff880`0422f000 ndiswan ndiswan.sys Tue Jul 14 01:10:11 2009 (4A5BCCE3) fffff880`052ef000 fffff880`05304000 NDProxy NDProxy.SYS Tue Jul 14 01:10:05 2009 (4A5BCCDD) fffff880`02d34000 fffff880`02d43000 netbios netbios.sys Tue Jul 14 01:09:26 2009 (4A5BCCB6) fffff880`02cc0000 fffff880`02d05000 netbt netbt.sys Tue Jul 14 00:21:28 2009 (4A5BC178) fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Tue Jul 14 00:21:46 2009 (4A5BC18A) fffff880`00deb000 fffff880`00dfc000 Npfs Npfs.SYS Tue Jul 14 00:19:48 2009 (4A5BC114) fffff880`02de0000 fffff880`02dec000 nsiproxy nsiproxy.sys Tue Jul 14 00:21:02 2009 (4A5BC15E) fffff800`0300e000 fffff800`035eb000 nt ntkrnlmp.exe Wed Oct 27 03:43:09 2010 (4CC791BD) fffff880`0123c000 fffff880`013df000 Ntfs Ntfs.sys Tue Jul 14 00:20:47 2009 (4A5BC14F) fffff880`01890000 fffff880`01899000 Null Null.SYS Tue Jul 14 00:19:37 2009 (4A5BC109) fffff880`052d6000 fffff880`052ef000 nusb3hub nusb3hub.sys Thu Sep 30 05:00:03 2010 (4CA40B43) fffff880`03e56000 fffff880`03e86000 nusb3xhc nusb3xhc.sys Thu Sep 30 05:00:03 2010 (4CA40B43) fffff880`10a7e000 fffff880`10a7f180 nvBridge nvBridge.kmd Fri Jan 14 03:48:07 2011 (4D2FC777) fffff880`05304000 fffff880`0532d000 nvhda64v nvhda64v.sys Thu Nov 11 23:10:36 2010 (4CDC77EC) fffff880`0fe1f000 fffff880`10a7d980 nvlddmkm nvlddmkm.sys Fri Jan 14 03:53:26 2011 (4D2FC8B6) fffff880`02d0e000 fffff880`02d34000 pacer pacer.sys Tue Jul 14 01:09:41 2009 (4A5BCCC5) fffff880`00f92000 fffff880`00fa7000 partmgr partmgr.sys Tue Jul 14 00:19:58 2009 (4A5BC11E) fffff880`00f5f000 fffff880`00f92000 pci pci.sys Tue Jul 14 00:19:51 2009 (4A5BC117) fffff880`00fbc000 fffff880`00fc3000 pciide pciide.sys Tue Jul 14 00:19:49 2009 (4A5BC115) fffff880`00fc3000 fffff880`00fd3000 PCIIDEX PCIIDEX.SYS Tue Jul 14 00:19:48 2009 (4A5BC114) fffff880`014d6000 fffff880`014e7000 pcw pcw.sys Tue Jul 14 00:19:27 2009 (4A5BC0FF) fffff880`07e38000 fffff880`07ede000 peauth peauth.sys Tue Jul 14 02:01:19 2009 (4A5BD8DF) fffff880`0532d000 fffff880`0536a000 portcls portcls.sys Tue Jul 14 01:06:27 2009 (4A5BCC03) fffff880`00d1d000 fffff880`00d31000 PSHED PSHED.dll Tue Jul 14 02:32:23 2009 (4A5BE027) fffff880`043b4000 fffff880`043d8000 rasl2tp rasl2tp.sys Tue Jul 14 01:10:11 2009 (4A5BCCE3) fffff880`0422f000 fffff880`0424a000 raspppoe raspppoe.sys Tue Jul 14 01:10:17 2009 (4A5BCCE9) fffff880`0424a000 fffff880`0426b000 raspptp raspptp.sys Tue Jul 14 01:10:18 2009 (4A5BCCEA) fffff880`0426b000 fffff880`04285000 rassstp rassstp.sys Tue Jul 14 01:10:25 2009 (4A5BCCF1) fffff880`02d8f000 fffff880`02de0000 rdbss rdbss.sys Tue Jul 14 00:24:09 2009 (4A5BC219) fffff880`04285000 fffff880`04290000 rdpbus rdpbus.sys Tue Jul 14 01:17:46 2009 (4A5BCEAA) fffff880`018a0000 fffff880`018a9000 RDPCDD RDPCDD.sys Tue Jul 14 01:16:34 2009 (4A5BCE62) fffff880`015f1000 fffff880`015fa000 rdpencdd rdpencdd.sys Tue Jul 14 01:16:34 2009 (4A5BCE62) fffff880`010d3000 fffff880`010dc000 rdprefmp rdprefmp.sys Tue Jul 14 01:16:35 2009 (4A5BCE63) fffff880`01958000 fffff880`01992000 rdyboost rdyboost.sys Tue Jul 14 00:34:34 2009 (4A5BC48A) fffff880`064b3000 fffff880`064cb000 rspndr rspndr.sys Tue Jul 14 01:08:50 2009 (4A5BCC92) fffff880`042d0000 fffff880`04336000 Rt64win7 Rt64win7.sys Thu Nov 11 06:35:36 2010 (4CDB8EB8) fffff880`064f8000 fffff880`06761800 RTKVHD64 RTKVHD64.sys Tue Nov 02 11:25:59 2010 (4CCFF547) fffff880`00e00000 fffff880`00e2f000 SCSIPORT SCSIPORT.SYS Tue Jul 14 01:01:04 2009 (4A5BCAC0) fffff880`07ede000 fffff880`07ee9000 secdrv secdrv.SYS Wed Sep 13 14:18:38 2006 (4508052E) fffff880`04363000 fffff880`0436f000 serenum serenum.sys Tue Jul 14 01:00:33 2009 (4A5BCAA1) fffff880`02d43000 fffff880`02d60000 serial serial.sys Tue Jul 14 01:00:40 2009 (4A5BCAA8) fffff880`01950000 fffff880`01958000 spldr spldr.sys Mon May 11 17:56:27 2009 (4A0858BB) fffff880`086e1000 fffff880`08752000 spsys spsys.sys Mon May 11 18:20:58 2009 (4A085E7A) fffff880`08635000 fffff880`086ca000 srv srv.sys Wed Feb 23 05:16:24 2011 (4D649828) fffff880`07f28000 fffff880`07f8f000 srv2 srv2.sys Wed Feb 23 05:15:59 2011 (4D64980F) fffff880`07ee9000 fffff880`07f16000 srvnet srvnet.sys Wed Feb 23 05:15:49 2011 (4D649805) fffff880`0429f000 fffff880`042a0480 swenum swenum.sys Tue Jul 14 01:00:18 2009 (4A5BCA92) fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Mon Jun 14 04:39:04 2010 (4C15A458) fffff880`07f16000 fffff880`07f28000 tcpipreg tcpipreg.sys Tue Jul 14 01:09:49 2009 (4A5BCCCD) fffff880`02c29000 fffff880`02c36000 TDI TDI.SYS Tue Jul 14 00:21:18 2009 (4A5BC16E) fffff880`02c0b000 fffff880`02c29000 tdx tdx.sys Tue Jul 14 00:21:15 2009 (4A5BC16B) fffff880`02d7b000 fffff880`02d8f000 termdd termdd.sys Tue Jul 14 01:16:36 2009 (4A5BCE64) fffff960`005d0000 fffff960`005da000 TSDDD TSDDD.dll Tue Jul 14 01:16:34 2009 (4A5BCE62) fffff880`086d2000 fffff880`086da000 TuneUpUtilitiesDriver64 TuneUpUtilitiesDriver64.sys Thu Sep 17 12:54:52 2009 (4AB2238C) fffff880`03fc7000 fffff880`03fed000 tunnel tunnel.sys Tue Jul 14 01:09:37 2009 (4A5BCCC1) fffff880`0526a000 fffff880`0527c000 umbus umbus.sys Tue Jul 14 01:06:56 2009 (4A5BCC20) fffff880`067c0000 fffff880`067dd000 usbccgp usbccgp.sys Tue Jul 14 01:06:45 2009 (4A5BCC15) fffff880`0fe00000 fffff880`0fe01f00 USBD USBD.SYS Tue Jul 14 01:06:23 2009 (4A5BCBFF) fffff880`10bef000 fffff880`10c00000 usbehci usbehci.sys Tue Jul 14 01:06:30 2009 (4A5BCC06) fffff880`0527c000 fffff880`052d6000 usbhub usbhub.sys Tue Jul 14 01:07:09 2009 (4A5BCC2D) fffff880`03e00000 fffff880`03e56000 USBPORT USBPORT.SYS Tue Jul 14 01:06:31 2009 (4A5BCC07) fffff880`00f52000 fffff880`00f5f000 vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB) fffff880`015e3000 fffff880`015f1000 vga vga.sys Tue Jul 14 00:38:47 2009 (4A5BC587) fffff880`011d4000 fffff880`011f9000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B) fffff880`018f4000 fffff880`01904000 vmstorfl vmstorfl.sys Tue Jul 14 00:42:54 2009 (4A5BC67E) fffff880`00fa7000 fffff880`00fbc000 volmgr volmgr.sys Tue Jul 14 00:19:57 2009 (4A5BC11D) fffff880`00d8f000 fffff880`00deb000 volmgrx volmgrx.sys unavailable (00000000) fffff880`01904000 fffff880`01950000 volsnap volsnap.sys Tue Jul 14 00:20:08 2009 (4A5BC128) fffff880`02d60000 fffff880`02d7b000 wanarp wanarp.sys Tue Jul 14 01:10:21 2009 (4A5BCCED) fffff880`0122b000 fffff880`0123b000 watchdog watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F) fffff880`00e35000 fffff880`00ed9000 Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F) fffff880`00ed9000 fffff880`00ee8000 WDFLDR WDFLDR.SYS Tue Jul 14 00:19:54 2009 (4A5BC11A) fffff880`02d05000 fffff880`02d0e000 wfplwf wfplwf.sys Tue Jul 14 01:09:26 2009 (4A5BCCB6) fffff960`00060000 fffff960`00372000 win32k win32k.sys Thu Mar 03 03:58:01 2011 (4D6F11C9) fffff880`0436f000 fffff880`04378000 wmiacpi wmiacpi.sys Tue Jul 14 00:31:02 2009 (4A5BC3B6) fffff880`00f3f000 fffff880`00f48000 WMILIB WMILIB.SYS Tue Jul 14 00:19:51 2009 (4A5BC117) fffff880`0647d000 fffff880`0649e000 WudfPf WudfPf.sys Tue Jul 14 01:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`01830000 fffff880`0183e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0183e000 fffff880`0184a000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0184a000 fffff880`01853000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01853000 fffff880`01866000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Which BIOS version are you using?
Seems to be some issues with some versions.
...I see you have BIOS version 1.9.
Did you notice much difference in the RAM when in single channel mode?
With 8GB RAM and (2x)4GB cards you need to bump the integrated memory controller voltage.
Change the CPU I/O to 1.100v then run memtest86+ for minimum 7 passes or overnight, if you get any errors you can stop the test.
If you get memtest86+ errors or BSoDs, bump the CPU I/O to 1.150v and run memtest86+ again, same as above.
Improper RAM settings can cause BSoDs, driver crashes and other problems.
Let us know the results.
The CM Hyper 212 Plus CPU Cooler is good, you will see a nice CPU temp drop, should be below 30c depending on ambient.
Your temps are good for the stock CPU cooler.
Seems to be some issues with some versions.
...I see you have BIOS version 1.9.
Did you notice much difference in the RAM when in single channel mode?
With 8GB RAM and (2x)4GB cards you need to bump the integrated memory controller voltage.
Change the CPU I/O to 1.100v then run memtest86+ for minimum 7 passes or overnight, if you get any errors you can stop the test.
If you get memtest86+ errors or BSoDs, bump the CPU I/O to 1.150v and run memtest86+ again, same as above.
Improper RAM settings can cause BSoDs, driver crashes and other problems.
Let us know the results.
The CM Hyper 212 Plus CPU Cooler is good, you will see a nice CPU temp drop, should be below 30c depending on ambient.
Your temps are good for the stock CPU cooler.
@ Minotar: I've noticed the errors on ad-aware too, and I get your point of uninstalling, but everytime (after zonealarm and STPD) something else keeps giving errors it seems. All of these software works fine on other pc's, even my last one, so why not here? Still, I will uninstall.
Defense Grid is not installed, I have it as a rar which can be unpacked an played, does it matter?
I already am running the 266.66 driver. Had the 270.51(?) beta first, but removed it and used the latest official.
I also updated yesterday to SP1.
@Dave76: When I was on the MSI forums, I also noticed A LOT of threads about the GD65, mostly on USB issues. I ahd these issues, but there mostly gone, I have 1 every two weeks. I will try the bump ad then the test. I'll have my usb stick back today to test. I'll let you know how i goes.
Defense Grid is not installed, I have it as a rar which can be unpacked an played, does it matter?
I already am running the 266.66 driver. Had the 270.51(?) beta first, but removed it and used the latest official.
I also updated yesterday to SP1.
@Dave76: When I was on the MSI forums, I also noticed A LOT of threads about the GD65, mostly on USB issues. I ahd these issues, but there mostly gone, I have 1 every two weeks. I will try the bump ad then the test. I'll have my usb stick back today to test. I'll let you know how i goes.
If you follow Minotar's suggestions you can narrow down the causes and hopefully stop the BSoDs. After your system is stable you can add these back one at a time, test for stability - BSoDs, and you will know what the cause is.
Your issues could be caused by drivers, programs, other software and/or hardware.
It is best to keep working on the BSoD analysis, and try the memory controller bump at some point.
I have seen these issues solved by bumping the memory controller voltage when you have 4GB RAm or more.
Let us know how it's going.
Your issues could be caused by drivers, programs, other software and/or hardware.
It is best to keep working on the BSoD analysis, and try the memory controller bump at some point.
I have seen these issues solved by bumping the memory controller voltage when you have 4GB RAm or more.
Let us know how it's going.
�� Quote: Originally Posted by skandalouz 
@ Minotar: I've noticed the errors on ad-aware too, and I get your point of uninstalling, but everytime (after zonealarm and STPD) something else keeps giving errors it seems. All of these software works fine on other pc's, even my last one, so why not here? Still, I will uninstall.
Defense Grid is not installed, I have it as a rar which can be unpacked an played, does it matter?
I already am running the 266.66 driver. Had the 270.51(?) beta first, but removed it and used the latest official.
I also updated yesterday to SP1.
@Dave76: When I was on the MSI forums, I also noticed A LOT of threads about the GD65, mostly on USB issues. I ahd these issues, but there mostly gone, I have 1 every two weeks. I will try the bump ad then the test. I'll have my usb stick back today to test. I'll let you know how i goes.
Defense Grid is not installed, I have it as a rar which can be unpacked an played, does it matter?
I already am running the 266.66 driver. Had the 270.51(?) beta first, but removed it and used the latest official.
I also updated yesterday to SP1.
@Dave76: When I was on the MSI forums, I also noticed A LOT of threads about the GD65, mostly on USB issues. I ahd these issues, but there mostly gone, I have 1 every two weeks. I will try the bump ad then the test. I'll have my usb stick back today to test. I'll let you know how i goes.
Its as dave said,its simply eliminating possible causes,then once its cured you can put them back on one at a time and you'll know exactly which one is at fault and hopefully keep 90% of the programs you want,or at least find the problem with the program.
I know it can be a pain,especially when you like the software, I have instances where I've had to uninstall software for similar reasons,but sometimes the developers website can find the particular fault with the programs and fix it for you
Honestly not sure,I've never used Defense Grid,maybe,try extracting it and running it,most programs will tell you they run better unpacked.
Hi there,
I just ran 5 passes on 1.110V, but when watching a movie (the second of the night) it BSOD'd twice. It played from the almost filled up partition. I'll try the second bump and test overnight.
If it doesn't work, shoul I keep increasing voltage? To what extend is it safe?
Also, when I'm in the bios, the cpu temp is just over 50 celsius, this can't be right? I'll install the cooler first thing tomorrow.
Thanks
I just ran 5 passes on 1.110V, but when watching a movie (the second of the night) it BSOD'd twice. It played from the almost filled up partition. I'll try the second bump and test overnight.
If it doesn't work, shoul I keep increasing voltage? To what extend is it safe?
Also, when I'm in the bios, the cpu temp is just over 50 celsius, this can't be right? I'll install the cooler first thing tomorrow.
Thanks
You have to be very careful with the CPU integrated memory controller voltage, too high a voltage can damage the CPU.
The max voltage setting is 1.200v, I wouldn't go past 1.170v.
Bump the CPU I/O to 1.150v then run memtest86+ again for 7 passes or overnight.
A full HDD can cause problems, this could be giving you BSoDs, the HDD needs some free space to work properly.
Move or delete some files to get a minimum of 15GB free space.
Can you post the CPUZ snips of the CPU, Mainboard, Memory, and SPD tabs?
This will let us check the settings, see if something needs adjusting.
The max voltage setting is 1.200v, I wouldn't go past 1.170v.
Bump the CPU I/O to 1.150v then run memtest86+ again for 7 passes or overnight.
A full HDD can cause problems, this could be giving you BSoDs, the HDD needs some free space to work properly.
Move or delete some files to get a minimum of 15GB free space.
Can you post the CPUZ snips of the CPU, Mainboard, Memory, and SPD tabs?
This will let us check the settings, see if something needs adjusting.
Hi there,
Just moved some of the files to create space, I'll check if it works now.
These are the shots:
Just moved some of the files to create space, I'll check if it works now.
These are the shots:
Go to your BIOS, DRAM timing settings and change the 'Command Rate' from 1T to 2T.
This will help the RAM stability.
Run memtest86+ for minimum 7 passes, best to run overnight.
Let us know how the the tests go.
This will help the RAM stability.
Run memtest86+ for minimum 7 passes, best to run overnight.
Let us know how the the tests go.
Hi,
ran 10 tests last night on 1.150V. Installed the cooler, which in bios gave a nice temp drop, but in windows didn't do all that much. Had two BSOD's last night, SYSTEM_SERVICE_EXEPTION and MEMORY_MANAGEMENT. I must admit I hadn't removed ad-aware yet. Today it won't boot anymore. Just installed my last hdd for which I had to get a power cable first. I won't work with or without that hdd. An underscore keeps blinking where windows should kick in. If I boot with the MSI disc in, it says it can't find a operating system... What to do here?
ran 10 tests last night on 1.150V. Installed the cooler, which in bios gave a nice temp drop, but in windows didn't do all that much. Had two BSOD's last night, SYSTEM_SERVICE_EXEPTION and MEMORY_MANAGEMENT. I must admit I hadn't removed ad-aware yet. Today it won't boot anymore. Just installed my last hdd for which I had to get a power cable first. I won't work with or without that hdd. An underscore keeps blinking where windows should kick in. If I boot with the MSI disc in, it says it can't find a operating system... What to do here?
Can you fill in your system specs, in the lower left corner of any of your posts, "My System Specs". Include as much detail as you can.
Check that you didn't bump any cables on your motherboard, check that all of them are tight.
If the CPU fan power cable came loose, the computer won't boot, check it.
If I understand correctly, you install another HDD and it wouldn't boot, you took that HDD out and it still wouldn't boot, is this correct?
Double check the hard drive cables, disconnect them check them and re-connect, make sure you have the OS drive in port0.
Check that you didn't bump any cables on your motherboard, check that all of them are tight.
If the CPU fan power cable came loose, the computer won't boot, check it.
If I understand correctly, you install another HDD and it wouldn't boot, you took that HDD out and it still wouldn't boot, is this correct?
Double check the hard drive cables, disconnect them check them and re-connect, make sure you have the OS drive in port0.
You had it correct there. Had a dvd writer and my OS hdd on a sata-600 port, but it seems I switched them. Put the writer in a sata-300 port, the hdd back in the first and now it works again!.
Having quite some BSOD's right now btw, I'll upload the dumps in a sec. I'll also change the command rate.
I can't seem to find any command rate settings, could it have a different name?
Also, I noticed the last dmp file has a april 17 date, it seems no new dmp are created?
Some BSOD's i got:
PFN LIST CORRUPT
SYSTEM SERVICE EXEPTION
MEMORY MANAGEMENT
and one about fltmgr.sys
Also, is there any chance it could be a hardware issue? Memtest always passes, but somehow is suspect it to be a motherboard error. Even though I appreciate the effort you're putting into this, a brand new pc bought under 1,5 month ago causing nothing but errors, bluescreens and usb issues with over a dozen windows installs just doesn't seem right to me. I'd like to rule things out now.
Having quite some BSOD's right now btw, I'll upload the dumps in a sec. I'll also change the command rate.
I can't seem to find any command rate settings, could it have a different name?
Also, I noticed the last dmp file has a april 17 date, it seems no new dmp are created?
Some BSOD's i got:
PFN LIST CORRUPT
SYSTEM SERVICE EXEPTION
MEMORY MANAGEMENT
and one about fltmgr.sys
Also, is there any chance it could be a hardware issue? Memtest always passes, but somehow is suspect it to be a motherboard error. Even though I appreciate the effort you're putting into this, a brand new pc bought under 1,5 month ago causing nothing but errors, bluescreens and usb issues with over a dozen windows installs just doesn't seem right to me. I'd like to rule things out now.
It can be caused by hardware,
Run Data Lifeguard Diagnostic for Windows
Also take a look at this: WD Caviar Green HDDs Suffer from a Critical Design Flaw
For the command rate, got to Advanced DRAM Configuration > Command Rate2
Run Data Lifeguard Diagnostic for Windows
Also take a look at this: WD Caviar Green HDDs Suffer from a Critical Design Flaw
For the command rate, got to Advanced DRAM Configuration > Command Rate2
I ran Data lifeguard diagnostic yesterday on the last added drive, it came out fine (extended test). I'll try the others too. I'll also run the fix.
I was more referring to the new hardware. I can test memory with memtest, is there a way to check the motherboard and processor?
I was more referring to the new hardware. I can test memory with memtest, is there a way to check the motherboard and processor?
CPU - Stress Test with Prime95
Prime95 Torture test
If memtest86+ passes then run Prime95 torture test.
First open CoreTemp to monitor CPU temperatures, don't go over 77degC.
Open Prime95 and stop the test, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 4, then click OK to start the test.
This will run your CPU at max frequency. Watch the core temps until they level off.
Prime95 Torture test
If memtest86+ passes then run Prime95 torture test.
First open CoreTemp to monitor CPU temperatures, don't go over 77degC.
Open Prime95 and stop the test, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 4, then click OK to start the test.
This will run your CPU at max frequency. Watch the core temps until they level off.
Thanks. I'll be out for about two days but then I'll test.
Ok, let us know the results.
Just set the command rate to 2T. Had to change DRAM Timing Mode to either Link or Unlink (set it to Link) to be able to enter advanced dram setting. Also had 3T optional, does this matter?
Also changed the idle settings of the hdd. About to run memtest again overnight. Also, just had an BUGCODE_USB_DRIVER on win7 again, and somewhat later even a MEMORY_MANAGEMENT bluescreen. And the C:\windows\minidump folder doesn't contain any dmp files newer than april 17, something I turned off?
Ran the prime95 test, didn't go over 57 celsius. I'll come back with the memtest results.
Just had a look at the MSI test results, and my memory isn't listed, just like my PSU or graphics card. Does any of this matter?
Also changed the idle settings of the hdd. About to run memtest again overnight. Also, just had an BUGCODE_USB_DRIVER on win7 again, and somewhat later even a MEMORY_MANAGEMENT bluescreen. And the C:\windows\minidump folder doesn't contain any dmp files newer than april 17, something I turned off?
Ran the prime95 test, didn't go over 57 celsius. I'll come back with the memtest results.
Just had a look at the MSI test results, and my memory isn't listed, just like my PSU or graphics card. Does any of this matter?
The Command Rate 2T will be good, I'll check on the Link/Unlink setting.
Can you post the current CPUZ tabs again, to check if anything has changed.
Go to the BIOS and check what the DRAM voltage is set at, post in your next reply.
Good temps for the Prime95 test.
No motherboard company can test all the RAM that is available, I'll look at the RAM again and let you know.
The PSU and graphics card should be fine.
Let us know how the memtest86+ went.
Can you post the current CPUZ tabs again, to check if anything has changed.
Go to the BIOS and check what the DRAM voltage is set at, post in your next reply.
Good temps for the Prime95 test.
No motherboard company can test all the RAM that is available, I'll look at the RAM again and let you know.
The PSU and graphics card should be fine.
Let us know how the memtest86+ went.
Hi,
I've contacted MSI over this, and they said it could be the motherboard, and recommend I return it to have it tested, so thats what I'm about to do.
Thanks for all the help.
I've contacted MSI over this, and they said it could be the motherboard, and recommend I return it to have it tested, so thats what I'm about to do.
Thanks for all the help.
You're welcome.
Hopefully this will solve the crashes, let us know how the new board works out.
Hopefully this will solve the crashes, let us know how the new board works out.
Hi again,
So I've sent it back where it came from, they've ran a memtest test for 13+ hours and did a burn-in test on the motherboard. Both came out great. So they've returned the same products to me. Just did a fresh install of Windows, wouldn't work, found out by error code a fix could be to remove usb devices. Did so, installed perfectly. Put in the MSI cd to install all drivers (for which I had to use my USB mouse). Now... updating 74 updates, and by the end of it.. no mouse response! Again! And as usual, windows won't shut down.
The only thing I did was a graphics driver install. Updated the bios the moment it got back, to 1.11. Any suggestions?
So I've sent it back where it came from, they've ran a memtest test for 13+ hours and did a burn-in test on the motherboard. Both came out great. So they've returned the same products to me. Just did a fresh install of Windows, wouldn't work, found out by error code a fix could be to remove usb devices. Did so, installed perfectly. Put in the MSI cd to install all drivers (for which I had to use my USB mouse). Now... updating 74 updates, and by the end of it.. no mouse response! Again! And as usual, windows won't shut down.
The only thing I did was a graphics driver install. Updated the bios the moment it got back, to 1.11. Any suggestions?
Did you note the update installed when the mouse stopped working?
Do you have another mouse to try for testing purposes?
Did you install a driver for the mouse?
Which graphics driver did you install?
Try another older version.
Do you have another mouse to try for testing purposes?
Did you install a driver for the mouse?
Which graphics driver did you install?
Try another older version.
Sorry I was busy on my laptop so wasn't paying attention to the updating.
I've tried another Win7 install. My first dvd gave some data corruption when extracting the files, the second and third gave me an error code I've come across before (0x80070570) which could be solved by unplugging any usb devices. That worked, but why? On the mouse I've been using so far, and on another simple mouse and keyboar (keyboard in ps/2 port).
The mouse/keyboard set I was using has been in use on a Windows XP system over a day now without problems.
The graphics driver is the newest from Nvidia, 270.??.
The logitech mouse and keyboard have no win7 drivers, they're too old.
I've had contact with MSI, and they told me to try to set the DRAM voltage at 1.65V, and I'm now running a memtest, 6 passes already.
Greetz
I've tried another Win7 install. My first dvd gave some data corruption when extracting the files, the second and third gave me an error code I've come across before (0x80070570) which could be solved by unplugging any usb devices. That worked, but why? On the mouse I've been using so far, and on another simple mouse and keyboar (keyboard in ps/2 port).
The mouse/keyboard set I was using has been in use on a Windows XP system over a day now without problems.
The graphics driver is the newest from Nvidia, 270.??.
The logitech mouse and keyboard have no win7 drivers, they're too old.
I've had contact with MSI, and they told me to try to set the DRAM voltage at 1.65V, and I'm now running a memtest, 6 passes already.
Greetz
Did you install the logitech mouse and keyboard drivers in Vista or XP compatibility mode?
Did you change the CPU I/O to 1.170v as mentioned in post#19?
You need to keep the CPU I/O voltage within 0.50v of the DRAM voltage, this is a known issue and can cause CPU damage.
Did you change the CPU I/O to 1.170v as mentioned in post#19?
You need to keep the CPU I/O voltage within 0.50v of the DRAM voltage, this is a known issue and can cause CPU damage.
Hi
Haven't installed any drivers. Just noticed there are Vista drivers, I'll try those.
No sorry kept it at 1.150, I'll change it now.
I'll try to install again, Let you know how it goes.
Haven't installed any drivers. Just noticed there are Vista drivers, I'll try those.
No sorry kept it at 1.150, I'll change it now.
I'll try to install again, Let you know how it goes.
Thanks for the update.
Let us know if you get any crashes.
Let us know if you get any crashes.
Hi there,
couldn't install Win7 at all. All three disks gave me error 0x80070570. Tried on another hdd, worked after a couple of tries. BSOD'd when i tried to copy some videos to an external drive.
couldn't install Win7 at all. All three disks gave me error 0x80070570. Tried on another hdd, worked after a couple of tries. BSOD'd when i tried to copy some videos to an external drive.
A couple possible solutions in this thread, read through it there are things to try on several different posts.
Windows 7 - 0x80070570 Error Code on install - One Easy Solution
Try taking out one of your RAM cards and intall Win7 with only one RAM card.
Windows 7 - 0x80070570 Error Code on install - One Easy Solution
Try taking out one of your RAM cards and intall Win7 with only one RAM card.
Không có nhận xét nào:
Đăng nhận xét