Here's what happened.
A few months ago I posted here regarding BSOD.
I found it it was the motherboard ICH10 chipset malfunctioned, it detected 1 USB plugged in when there was nothing. It was a dead port. Device manager showed 'Unknown device'.
Asus took 2 months to replace the motherboard for me, it looks like a repaired unit.
I got it home, and using it for a while i got bsod.
So I did a fresh win7 install.
And still got BSOD.
But after each BSOD, i can't even get past post.
It just gets stuck with fans, HDD, CDrom all working/spinning/having power.
Sometimes this happens when I unplugged my computer when leaving the house, returning several hours later. I thought this was due to a bad battery, which I have since changed.
I have also flashed the bios to remove any potential corruption on the old one.
Problem still persisted, so I suspected the PSU, I changed it today and I just got a BSOD.
I also reinstalled the LAN driver to a more recent version, it was giving me some problems unable to detect network etc.
CPU core temp at no load is around 46 degrees C, full load is 71 degrees C.
I have run Memtest86+ numerous times, each with at least 6 passes or more, and found no errors.
I have also followed the posting request and zipped up the necessary files required.
If there is any more information I'd glady post.
Is Windows 7 . . . - 64bit
- full retail version?
- What is the age of system (hardware)? CPU - 2 years
Motherboard - Just got RMA and replacement from ASUS, the previous one got RMAed and didn't fix the problem (Chipset burnt)
Graphics card - 2 years
HDDs - 2 years
PSU - Just changed today (I thought PSU was the problem, so changed the old one, apparently not)
Everything else is 2 years old, RAM, etc.
- Fresh win 7 install, and continuous BSOD
A few months ago I posted here regarding BSOD.
I found it it was the motherboard ICH10 chipset malfunctioned, it detected 1 USB plugged in when there was nothing. It was a dead port. Device manager showed 'Unknown device'.
Asus took 2 months to replace the motherboard for me, it looks like a repaired unit.
I got it home, and using it for a while i got bsod.
So I did a fresh win7 install.
And still got BSOD.
But after each BSOD, i can't even get past post.
It just gets stuck with fans, HDD, CDrom all working/spinning/having power.
Sometimes this happens when I unplugged my computer when leaving the house, returning several hours later. I thought this was due to a bad battery, which I have since changed.
I have also flashed the bios to remove any potential corruption on the old one.
Problem still persisted, so I suspected the PSU, I changed it today and I just got a BSOD.
I also reinstalled the LAN driver to a more recent version, it was giving me some problems unable to detect network etc.
CPU core temp at no load is around 46 degrees C, full load is 71 degrees C.
I have run Memtest86+ numerous times, each with at least 6 passes or more, and found no errors.
I have also followed the posting request and zipped up the necessary files required.
If there is any more information I'd glady post.
Is Windows 7 . . . - 64bit
- full retail version?
- What is the age of system (hardware)? CPU - 2 years
Motherboard - Just got RMA and replacement from ASUS, the previous one got RMAed and didn't fix the problem (Chipset burnt)
Graphics card - 2 years
HDDs - 2 years
PSU - Just changed today (I thought PSU was the problem, so changed the old one, apparently not)
Everything else is 2 years old, RAM, etc.
- Fresh win 7 install, and continuous BSOD
Just an updated, I did the verifier test, and I get BSOD/system freeze before entering windows.
BSOD only happened once, subsequent 3 times were all system freeze.
I have a memory dump file of it, will it be useful to anyone?
Zipped is 36megs though.
BSOD only happened once, subsequent 3 times were all system freeze.
I have a memory dump file of it, will it be useful to anyone?
Zipped is 36megs though.
Update your drivers, starting with ATK0110 ACPI:
ASACPI.sys Mon Mar 28 05:30:36 2005
ATK0110 ACPI
ASUSTeK Computer Inc.-Support-
L1E62x64.sys Thu Jun 11 09:45:22 2009
Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
sptd.sys Sun Oct 11 23:55:14 2009
Daemon Tools
If bsod's continue, uninstall AvG and replace it with Microsoft Security Essentials:
vgldx64.sys Fri Jun 04 00:06:48 2010
avgmfx64.sys Mon Apr 26 00:06:15 2010
AVG
AVG Worldwide - Download tools
http://www.microsoft.com/security_essentials/
Check RAM with memtest:
RAM - Test with Memtest86+
ASACPI.sys Mon Mar 28 05:30:36 2005
ATK0110 ACPI
ASUSTeK Computer Inc.-Support-
L1E62x64.sys Thu Jun 11 09:45:22 2009
Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)
sptd.sys Sun Oct 11 23:55:14 2009
Daemon Tools
If bsod's continue, uninstall AvG and replace it with Microsoft Security Essentials:
vgldx64.sys Fri Jun 04 00:06:48 2010
avgmfx64.sys Mon Apr 26 00:06:15 2010
AVG
AVG Worldwide - Download tools
http://www.microsoft.com/security_essentials/
Check RAM with memtest:
RAM - Test with Memtest86+
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\100310-22698-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002a9f86e, fffff880099bf3f0, 0} Probably caused by : memory_corruption ( nt!MiLocateWsle+e ) 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: fffff80002a9f86e, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880099bf3f0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text> FAULTING_IP: nt!MiLocateWsle+e fffff800`02a9f86e 418b5320 mov edx,dword ptr [r11+20h] CONTEXT: fffff880099bf3f0 -- (.cxr 0xfffff880099bf3f0) rax=0000000000094b10 rbx=f3b0000094b10963 rcx=fffff8a009201000 rdx=fffff80002c05b40 rsi=ffffffffffffffff rdi=fffffa8006ccda10 rip=fffff80002a9f86e rsp=fffff880099bfdc0 rbp=fffffa8001be1300 r8=fffff8a009201000 r9=0000000000007f3b r10=0000000fffffffff r11=bffff781c0000000 r12=0000007ffffffff8 r13=fffff80002c05b40 r14=fffff6fc50049008 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!MiLocateWsle+0xe: fffff800`02a9f86e 418b5320 mov edx,dword ptr [r11+20h] ds:002b:bffff781`c0000020=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: TrustedInstall CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002a6f339 to fffff80002a9f86e STACK_TEXT: fffff880`099bfdc0 fffff800`02a6f339 : 00000000`00040001 00000000`00000001 00000000`00000000 00000000`00000000 : nt!MiLocateWsle+0xe fffff880`099bfe00 fffff800`02a6ed49 : 00000000`00000000 00000000`00000003 00000000`00000000 00000000`00000000 : nt!MiDeleteSystemPagableVm+0x179 fffff880`099bff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFreePagedPoolPages+0x129 FOLLOWUP_IP: nt!MiLocateWsle+e fffff800`02a9f86e 418b5320 mov edx,dword ptr [r11+20h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiLocateWsle+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880099bf3f0 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MiLocateWsle+e BUCKET_ID: X64_0x3B_nt!MiLocateWsle+e Followup: MachineOwner --------- 1: kd> lmtn start end module name fffff800`00b9e000 fffff800`00ba8000 kdcom kdcom.dll Tue Jul 14 04:31:07 2009 (4A5BDFDB) fffff800`02a09000 fffff800`02fe5000 nt ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9) fffff800`02fe5000 fffff800`0302e000 hal hal.dll Tue Jul 14 04:27:36 2009 (4A5BDF08) fffff880`00c00000 fffff880`00c57000 ACPI ACPI.sys Tue Jul 14 02:19:34 2009 (4A5BC106) fffff880`00c57000 fffff880`00c9b000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66) fffff880`00c9b000 fffff880`00caf000 PSHED PSHED.dll Tue Jul 14 04:32:23 2009 (4A5BE027) fffff880`00caf000 fffff880`00d0d000 CLFS CLFS.SYS Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00d0d000 fffff880`00dcd000 CI CI.dll Tue Jul 14 04:32:13 2009 (4A5BE01D) fffff880`00dcd000 fffff880`00dfc000 SCSIPORT SCSIPORT.SYS Tue Jul 14 03:01:04 2009 (4A5BCAC0) fffff880`00e07000 fffff880`00eab000 Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F) fffff880`00eab000 fffff880`00eba000 WDFLDR WDFLDR.SYS Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00eba000 fffff880`00fe0000 sptd sptd.sys Sun Oct 11 23:55:14 2009 (4AD24632) fffff880`00fe0000 fffff880`00fe9000 WMILIB WMILIB.SYS Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00fe9000 fffff880`00ff3000 msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE) fffff880`00ff3000 fffff880`01000000 vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB) fffff880`01000000 fffff880`0104c000 fltmgr fltmgr.sys Tue Jul 14 02:19:59 2009 (4A5BC11F) fffff880`0104c000 fffff880`01060000 fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481) fffff880`01060000 fffff880`0108a000 cdrom cdrom.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`0108a000 fffff880`01098000 vga vga.sys Tue Jul 14 02:38:47 2009 (4A5BC587) fffff880`01098000 fffff880`010ac000 vpcnfltr vpcnfltr.sys Thu Jul 23 01:20:17 2009 (4A6790A1) fffff880`010b7000 fffff880`010ea000 pci pci.sys Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`010ea000 fffff880`010ff000 partmgr partmgr.sys Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`010ff000 fffff880`01114000 volmgr volmgr.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`01114000 fffff880`01170000 volmgrx volmgrx.sys Tue Jul 14 02:20:33 2009 (4A5BC141) fffff880`01170000 fffff880`01177000 pciide pciide.sys Tue Jul 14 02:19:49 2009 (4A5BC115) fffff880`01177000 fffff880`01187000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`01187000 fffff880`011a1000 mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`011a1000 fffff880`011aa000 atapi atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`011aa000 fffff880`011d4000 ataport ataport.SYS Tue Jul 14 02:19:52 2009 (4A5BC118) fffff880`011d4000 fffff880`011df000 msahci msahci.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`011df000 fffff880`011ea000 amdxata amdxata.sys Tue May 19 20:56:59 2009 (4A12F2EB) fffff880`01200000 fffff880`01215000 lltdio lltdio.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`01216000 fffff880`013b9000 Ntfs Ntfs.sys Tue Jul 14 02:20:47 2009 (4A5BC14F) fffff880`013b9000 fffff880`013e9000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`013f5000 fffff880`013fe000 Null Null.SYS Tue Jul 14 02:19:37 2009 (4A5BC109) fffff880`01400000 fffff880`0144c000 volsnap volsnap.sys Tue Jul 14 02:20:08 2009 (4A5BC128) fffff880`0144c000 fffff880`01486000 rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A) fffff880`01486000 fffff880`01498000 mup mup.sys Tue Jul 14 02:23:45 2009 (4A5BC201) fffff880`01498000 fffff880`014ae000 disk disk.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`014b6000 fffff880`01514000 msrpc msrpc.sys Tue Jul 14 02:21:32 2009 (4A5BC17C) fffff880`01514000 fffff880`0152e000 ksecdd ksecdd.sys Tue Jul 14 02:20:54 2009 (4A5BC156) fffff880`0152e000 fffff880`015a1000 cng cng.sys Tue Jul 14 02:49:40 2009 (4A5BC814) fffff880`015a1000 fffff880`015b2000 pcw pcw.sys Tue Jul 14 02:19:27 2009 (4A5BC0FF) fffff880`015b2000 fffff880`015bc000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:19:45 2009 (4A5BC111) fffff880`015bc000 fffff880`015f6000 fvevol fvevol.sys Tue Jul 14 02:22:15 2009 (4A5BC1A7) fffff880`01600000 fffff880`0164a000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164) fffff880`0164a000 fffff880`0165a000 vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E) fffff880`0165a000 fffff880`01662000 spldr spldr.sys Mon May 11 19:56:27 2009 (4A0858BB) fffff880`01662000 fffff880`0166b000 hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA) fffff880`0166b000 fffff880`01672000 Beep Beep.SYS Tue Jul 14 03:00:13 2009 (4A5BCA8D) fffff880`01673000 fffff880`01765000 ndis ndis.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`01765000 fffff880`017c5000 NETIO NETIO.SYS Tue Jul 14 02:21:46 2009 (4A5BC18A) fffff880`017c5000 fffff880`017f0000 ksecpkg ksecpkg.sys Fri Dec 11 08:03:32 2009 (4B21E0B4) fffff880`01803000 fffff880`01a00000 tcpip tcpip.sys Mon Jun 14 06:39:04 2010 (4C15A458) fffff880`02c00000 fffff880`02c8a000 afd afd.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`02c8a000 fffff880`02c93000 wfplwf wfplwf.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02c93000 fffff880`02ca2000 netbios netbios.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02ca6000 fffff880`02ccb000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B) fffff880`02ccb000 fffff880`02cdb000 watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F) fffff880`02cdb000 fffff880`02ce4000 RDPCDD RDPCDD.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`02ce4000 fffff880`02ced000 rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`02ced000 fffff880`02cf6000 rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63) fffff880`02cf6000 fffff880`02d01000 Msfs Msfs.SYS Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`02d01000 fffff880`02d12000 Npfs Npfs.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`02d12000 fffff880`02d30000 tdx tdx.sys Tue Jul 14 02:21:15 2009 (4A5BC16B) fffff880`02d30000 fffff880`02d3d000 TDI TDI.SYS Tue Jul 14 02:21:18 2009 (4A5BC16E) fffff880`02d3d000 fffff880`02d8e000 avgtdia avgtdia.sys Fri Jun 04 00:09:57 2010 (4C081A25) fffff880`02d8e000 fffff880`02dd3000 netbt netbt.sys Tue Jul 14 02:21:28 2009 (4A5BC178) fffff880`02dd3000 fffff880`02df9000 pacer pacer.sys Tue Jul 14 03:09:41 2009 (4A5BCCC5) fffff880`03a01000 fffff880`03a1e000 serial serial.sys Tue Jul 14 03:00:40 2009 (4A5BCAA8) fffff880`03a1e000 fffff880`03a39000 wanarp wanarp.sys Tue Jul 14 03:10:21 2009 (4A5BCCED) fffff880`03a39000 fffff880`03a8ec00 vpcvmm vpcvmm.sys Thu Jul 23 01:20:22 2009 (4A6790A6) fffff880`03a8f000 fffff880`03aa3000 termdd termdd.sys Tue Jul 14 03:16:36 2009 (4A5BCE64) fffff880`03aa3000 fffff880`03af4000 rdbss rdbss.sys Tue Jul 14 02:24:09 2009 (4A5BC219) fffff880`03af4000 fffff880`03b00000 nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E) fffff880`03b00000 fffff880`03b0b000 mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE) fffff880`03b0b000 fffff880`03b1a000 discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E) fffff880`03b1a000 fffff880`03b9d000 csc csc.sys Tue Jul 14 02:24:26 2009 (4A5BC22A) fffff880`03b9d000 fffff880`03bbb000 dfsc dfsc.sys Tue Jul 14 02:23:44 2009 (4A5BC200) fffff880`03bbb000 fffff880`03bcc000 blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF) fffff880`03bcc000 fffff880`03bd3080 avgmfx64 avgmfx64.sys Mon Apr 26 00:06:15 2010 (4BD4AEC7) fffff880`03bd4000 fffff880`03bea000 AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0) fffff880`03bea000 fffff880`03bff000 NDProxy NDProxy.SYS Tue Jul 14 03:10:05 2009 (4A5BCCDD) fffff880`03c00000 fffff880`03cf4000 dxgkrnl dxgkrnl.sys Fri Oct 02 04:00:14 2009 (4AC5509E) fffff880`03cf8000 fffff880`03d3f000 avgldx64 avgldx64.sys Fri Jun 04 00:06:48 2010 (4C081968) fffff880`03d3f000 fffff880`03d65000 tunnel tunnel.sys Tue Jul 14 03:09:37 2009 (4A5BCCC1) fffff880`03d65000 fffff880`03d7b000 intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD) fffff880`03d7b000 fffff880`03d99000 i8042prt i8042prt.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`03d99000 fffff880`03dde000 ai8tydqa ai8tydqa.SYS Wed Jul 15 00:12:55 2009 (4A5CF4D7) fffff880`03dde000 fffff880`03dee000 CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`04000000 fffff880`0401d000 vpcusb vpcusb.sys Thu Jul 23 01:20:23 2009 (4A6790A7) fffff880`0401d000 fffff880`0402c000 usbrpm usbrpm.sys Tue Jul 14 03:35:14 2009 (4A5BD2C2) fffff880`0402c000 fffff880`0402df00 USBD USBD.SYS Tue Jul 14 03:06:23 2009 (4A5BCBFF) fffff880`0402e000 fffff880`0406a000 vpchbus vpchbus.sys Thu Jul 23 01:20:23 2009 (4A6790A7) fffff880`0406a000 fffff880`040c4000 usbhub usbhub.sys Tue Jul 14 03:07:09 2009 (4A5BCC2D) fffff880`040ce000 fffff880`040f2000 rasl2tp rasl2tp.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`040f2000 fffff880`040fe000 ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8) fffff880`040fe000 fffff880`0412d000 ndiswan ndiswan.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`0412d000 fffff880`04148000 raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9) fffff880`04148000 fffff880`04169000 raspptp raspptp.sys Tue Jul 14 03:10:18 2009 (4A5BCCEA) fffff880`04169000 fffff880`04183000 rassstp rassstp.sys Tue Jul 14 03:10:25 2009 (4A5BCCF1) fffff880`04183000 fffff880`0418e000 rdpbus rdpbus.sys Tue Jul 14 03:17:46 2009 (4A5BCEAA) fffff880`0418e000 fffff880`0419d000 mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`0419d000 fffff880`0419e480 swenum swenum.sys Tue Jul 14 03:00:18 2009 (4A5BCA92) fffff880`0419f000 fffff880`041e2000 ks ks.sys Tue Jul 14 03:00:31 2009 (4A5BCA9F) fffff880`041e2000 fffff880`041f4000 umbus umbus.sys Tue Jul 14 03:06:56 2009 (4A5BCC20) fffff880`041f4000 fffff880`041ff000 flpydisk flpydisk.sys Tue Jul 14 03:00:54 2009 (4A5BCAB6) fffff880`05600000 fffff880`0560d000 mouhid mouhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`0560d000 fffff880`05621000 LMouFilt LMouFilt.Sys Thu Mar 18 10:51:24 2010 (4BA1E98C) fffff880`05621000 fffff880`05644000 luafv luafv.sys Tue Jul 14 02:26:13 2009 (4A5BC295) fffff880`05644000 fffff880`05665000 WudfPf WudfPf.sys Tue Jul 14 03:05:37 2009 (4A5BCBD1) fffff880`0566e000 fffff880`056ca000 HdAudio HdAudio.sys Tue Jul 14 03:06:59 2009 (4A5BCC23) fffff880`056ca000 fffff880`05707000 portcls portcls.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`05707000 fffff880`05729000 drmk drmk.sys Tue Jul 14 04:01:25 2009 (4A5BD8E5) fffff880`05729000 fffff880`0572e200 ksthunk ksthunk.sys Tue Jul 14 03:00:19 2009 (4A5BCA93) fffff880`0572f000 fffff880`0573d000 crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`0573d000 fffff880`05749000 dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`05749000 fffff880`05752000 dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`05752000 fffff880`05765000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F) fffff880`05765000 fffff880`05771000 Dxapi Dxapi.sys Tue Jul 14 02:38:28 2009 (4A5BC574) fffff880`05771000 fffff880`0577f000 monitor monitor.sys Tue Jul 14 02:38:52 2009 (4A5BC58C) fffff880`0577f000 fffff880`0579a000 USBSTOR USBSTOR.SYS Tue Jul 14 03:06:34 2009 (4A5BCC0A) fffff880`0579a000 fffff880`057b7000 usbccgp usbccgp.sys Tue Jul 14 03:06:45 2009 (4A5BCC15) fffff880`057b7000 fffff880`057c5000 hidusb hidusb.sys Tue Jul 14 03:06:22 2009 (4A5BCBFE) fffff880`057c5000 fffff880`057de000 HIDCLASS HIDCLASS.SYS Tue Jul 14 03:06:21 2009 (4A5BCBFD) fffff880`057de000 fffff880`057e6080 HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9) fffff880`057e7000 fffff880`057fc000 LHidFilt LHidFilt.Sys Thu Mar 18 10:51:17 2010 (4BA1E985) fffff880`05800000 fffff880`0582d000 mrxsmb mrxsmb.sys Sat Feb 27 09:52:19 2010 (4B88CF33) fffff880`0582d000 fffff880`0587b000 mrxsmb10 mrxsmb10.sys Sat Feb 27 09:52:28 2010 (4B88CF3C) fffff880`0587b000 fffff880`0589e000 mrxsmb20 mrxsmb20.sys Sat Feb 27 09:52:26 2010 (4B88CF3A) fffff880`058d8000 fffff880`058f0000 rspndr rspndr.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`058f0000 fffff880`059b8000 HTTP HTTP.sys Tue Jul 14 02:22:16 2009 (4A5BC1A8) fffff880`059b8000 fffff880`059d6000 bowser bowser.sys Tue Jul 14 02:23:50 2009 (4A5BC206) fffff880`059d6000 fffff880`059ee000 mpsdrv mpsdrv.sys Tue Jul 14 03:08:25 2009 (4A5BCC79) fffff880`06000000 fffff880`06071000 spsys spsys.sys Mon May 11 20:20:58 2009 (4A085E7A) fffff880`060a8000 fffff880`0614e000 peauth peauth.sys Tue Jul 14 04:01:19 2009 (4A5BD8DF) fffff880`0614e000 fffff880`06159000 secdrv secdrv.SYS Wed Sep 13 16:18:38 2006 (4508052E) fffff880`06159000 fffff880`06186000 srvnet srvnet.sys Tue Jun 22 06:20:32 2010 (4C202C00) fffff880`06186000 fffff880`06198000 tcpipreg tcpipreg.sys Tue Jul 14 03:09:49 2009 (4A5BCCCD) fffff880`06198000 fffff880`06200000 srv2 srv2.sys Tue Jun 22 06:20:47 2010 (4C202C0F) fffff880`06e07000 fffff880`06e9d000 srv srv.sys Tue Jun 22 06:21:11 2010 (4C202C27) fffff880`06e9d000 fffff880`06ed3000 fastfat fastfat.SYS Tue Jul 14 02:23:28 2009 (4A5BC1F0) fffff880`06ed3000 fffff880`06f04000 WUDFRd WUDFRd.sys Tue Jul 14 03:06:06 2009 (4A5BCBEE) fffff880`0fe00000 fffff880`0fe12000 L1E62x64 L1E62x64.sys Thu Jun 11 09:45:22 2009 (4A30A802) fffff880`0fe12000 fffff880`0fe50000 1394ohci 1394ohci.sys Tue Jul 14 03:07:12 2009 (4A5BCC30) fffff880`0fe50000 fffff880`0fe5d000 fdc fdc.sys Tue Jul 14 03:00:54 2009 (4A5BCAB6) fffff880`0fe5d000 fffff880`0fe65000 ASACPI ASACPI.sys Mon Mar 28 05:30:36 2005 (42476C4C) fffff880`0fe65000 fffff880`0fe71000 serenum serenum.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`0fe71000 fffff880`0fe80000 kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`0fe8c000 fffff880`10b1de00 nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:58 2010 (4C37918E) fffff880`10b1e000 fffff880`10b1f180 nvBridge nvBridge.kmd Sat Jul 10 00:07:54 2010 (4C378FAA) fffff880`10b20000 fffff880`10b66000 dxgmms1 dxgmms1.sys Tue Jul 14 02:38:32 2009 (4A5BC578) fffff880`10b66000 fffff880`10b73000 usbuhci usbuhci.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`10b73000 fffff880`10bc9000 USBPORT USBPORT.SYS Tue Jul 14 03:06:31 2009 (4A5BCC07) fffff880`10bc9000 fffff880`10bda000 usbehci usbehci.sys Tue Jul 14 03:06:30 2009 (4A5BCC06) fffff880`10bda000 fffff880`10bfe000 HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5) fffff960`000a0000 fffff960`003af000 win32k win32k.sys Sat Jun 19 07:31:59 2010 (4C1C483F) fffff960`004e0000 fffff960`004ea000 TSDDD TSDDD.dll Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff960`00670000 fffff960`00697000 cdd cdd.dll unavailable (00000000) fffff960`00850000 fffff960`008b1000 ATMFD ATMFD.DLL Thu May 27 07:11:31 2010 (4BFDF0F3) Unloaded modules: fffff880`017f0000 fffff880`017fe000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`013e9000 fffff880`013f5000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`015f6000 fffff880`015ff000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01200000 fffff880`01213000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Hi Cybercore - Thank you for your reply.
ATK110 is the latest I've downloaded from ASUS.
Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20) -> I just updated this 2 days ago from the atheros website using their latest drivers
Daemon tools is a program, can the drivers be updated?
Just 30min ago, I have tried the following after the verifier test showed I had driver issues. I restarted into windows mode by disabling verifier before startup (F8)
I updated my:
nvidia driver to the latest via the nvidia website
soundcard driver according to latest via asus website
After I updated, I swtiched on verifier again, with the same settings as posted on this forum.
Then I managed to boot into windows no BSOD.
Is there any way I can 'force' a BSOD besides verifier?
On memtest86+
I have run at multiple times with at least 6 full passes, no errors.
ATK110 is the latest I've downloaded from ASUS.
Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20) -> I just updated this 2 days ago from the atheros website using their latest drivers
Daemon tools is a program, can the drivers be updated?
Just 30min ago, I have tried the following after the verifier test showed I had driver issues. I restarted into windows mode by disabling verifier before startup (F8)
I updated my:
nvidia driver to the latest via the nvidia website
soundcard driver according to latest via asus website
After I updated, I swtiched on verifier again, with the same settings as posted on this forum.
Then I managed to boot into windows no BSOD.
Is there any way I can 'force' a BSOD besides verifier?
On memtest86+
I have run at multiple times with at least 6 full passes, no errors.
You must update this one, 2005 is not the latest for Windows 7:
ASACPI.sys Mon Mar 28 05:30:36 2005
ATK0110 ACPI
ASUSTeK Computer Inc.-Support-
Go to ASUS support site, search for your motherboard (e.g. P5Q), and choose Windows 7 from the drop down list. Under utilities you'll find ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit. Download and install your version, 32/64 - it has 2 folders inside the archive.
~~~~~~~~~~~~~~~~~~~~~~
sptd.sys Sun Oct 11 23:55:14 2009
Daemon Tools, Alcohol 120%, or in rare cases something else using sptd.sys by Duplex Secure - reinstalling the software with the latest version will update it
DuplexSecure - FAQ
DuplexSecure - Downloads
ASACPI.sys Mon Mar 28 05:30:36 2005
ATK0110 ACPI
ASUSTeK Computer Inc.-Support-
Go to ASUS support site, search for your motherboard (e.g. P5Q), and choose Windows 7 from the drop down list. Under utilities you'll find ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit. Download and install your version, 32/64 - it has 2 folders inside the archive.
~~~~~~~~~~~~~~~~~~~~~~
sptd.sys Sun Oct 11 23:55:14 2009
Daemon Tools, Alcohol 120%, or in rare cases something else using sptd.sys by Duplex Secure - reinstalling the software with the latest version will update it
DuplexSecure - FAQ
DuplexSecure - Downloads
�� Quote: Originally Posted by cybercore 
You must update this one, 2005 is not the latest for Windows 7:
ASACPI.sys Mon Mar 28 05:30:36 2005
ATK0110 ACPI
ASUSTeK Computer Inc.-Support-
ASACPI.sys Mon Mar 28 05:30:36 2005
ATK0110 ACPI
ASUSTeK Computer Inc.-Support-
Yup, 2009-05-05 is what you need, much better than 2005.
If you're getting any fresh crash dumps other than what you've already posted, feel free to attach them.
If you're getting any fresh crash dumps other than what you've already posted, feel free to attach them.
I tried to update the driver for ATK110 and immediately it gave me a BSOD.
Do you want me to paste this most recent BSOD?
Update 1: I've just now managed to get back to windows, uninstalled the old driver. And waiting to boot up again.
Update 2: Managed to reinstall with newer driver- Thanks for the verification that the driver is old. No idea why i got the old driver from Asus website. I got my motherboard back about 2 weeks ago. And just formatted again a few days back.
Update 3: Running the BSOD tool again. Will put up a zip file soon.
Do you want me to paste this most recent BSOD?
Update 1: I've just now managed to get back to windows, uninstalled the old driver. And waiting to boot up again.
Update 2: Managed to reinstall with newer driver- Thanks for the verification that the driver is old. No idea why i got the old driver from Asus website. I got my motherboard back about 2 weeks ago. And just formatted again a few days back.
Update 3: Running the BSOD tool again. Will put up a zip file soon.
Uploading the data from the latest crash.
Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes - Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
Notice the usual causes. I suggest that while you are troubleshooting you uninstall AVG. AVG, as well as most third party antivirus programs, cause BSOD's on some Win 7 systems. Use this uninstall tool: Tool (32bit) - Tool (64 bit). If you have installed AVG Identity Protection, uninstall it with this tool: Tool. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on. Reboot and let's see how your system does.
Notice the usual causes. I suggest that while you are troubleshooting you uninstall AVG. AVG, as well as most third party antivirus programs, cause BSOD's on some Win 7 systems. Use this uninstall tool: Tool (32bit) - Tool (64 bit). If you have installed AVG Identity Protection, uninstall it with this tool: Tool. Download and install Microsoft Security Essentials in its place and make sure Windows Firewall is turned on. Reboot and let's see how your system does.
Code:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50 Debug session time: Tue Oct 5 09:39:05.167 2010 (GMT-4) System Uptime: 0 days 0:00:13.868 Loading Kernel Symbols ............................................................... ............................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff80000000009, 2, 1, fffff80002a9a44b} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+126d ) Followup: Pool_corruption --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff80000000009, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002a9a44b, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb20e0 fffff80000000009 CURRENT_IRQL: 2 FAULTING_IP: nt!IopCompleteRequest+c88 fffff800`02a9a44b 48894108 mov qword ptr [rcx+8],rax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System IRP_ADDRESS: fffff7ffffffff89 TRAP_FRAME: fffff88002fedfb0 -- (.trap 0xfffff88002fedfb0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff98002c64ff0 rbx=0000000000000000 rcx=fffff80000000001 rdx=fffff88002feefb8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a9a44b rsp=fffff88002fee140 rbp=fffff88002fee290 r8=fffff88002fee248 r9=fffff88002fee240 r10=0000000000000002 r11=fffff80002a997d0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!IopCompleteRequest+0xc88: fffff800`02a9a44b 48894108 mov qword ptr [rcx+8],rax ds:a000:fffff800`00000009=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a79ca9 to fffff80002a7a740 STACK_TEXT: fffff880`02fede68 fffff800`02a79ca9 : 00000000`0000000a fffff800`00000009 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`02fede70 fffff800`02a78920 : 00000000`80000000 fffff980`02fe6ee0 00000000`02fee0d0 fffff880`02fef0e0 : nt!KiBugCheckDispatch+0x69 fffff880`02fedfb0 fffff800`02a9a44b : ffffffff`80000234 fffff880`02ff0000 00000000`00000004 00000000`0000001b : nt!KiPageFault+0x260 fffff880`02fee140 fffff800`02a570c7 : fffff800`00000001 fffff880`02fee290 fffff880`02fee500 fffff880`00000000 : nt!IopCompleteRequest+0xc88 fffff880`02fee210 fffff800`02a57487 : fffff800`02c82000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7 fffff880`02fee290 fffff800`02a530af : fffff880`00000003 00000000`00458a19 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0xd7 fffff880`02fee420 fffff800`02a52e62 : fffff800`02d171f9 fffff880`02fee630 fffffa80`045ca618 fffff880`02fee610 : nt!RtlLookupFunctionTable+0x12f fffff880`02fee480 fffff800`02a1ab16 : 00000000`0002f790 00000000`00000000 fffff880`02fee610 00000000`00000000 : nt!RtlpLookupFunctionEntryForStackWalks+0x32 fffff880`02fee4f0 fffff800`02a1a967 : fffffa80`045ca618 fffff880`00000011 00000000`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x18e fffff880`02feeb90 fffff800`02b3dc2b : 00000000`00000003 fffffa80`045ca618 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x73 fffff880`02feebc0 fffff800`02f110dc : fffffa80`045ca600 00000000`00000040 00000000`00000003 fffff800`02b711d1 : nt!RtlCaptureStackBackTrace+0x4b fffff880`02feebf0 fffff800`02f1333a : fffff880`02fea000 fffff880`02ff0000 00000000`00000000 fffff800`02d5e630 : nt!IovpLogStackCallout+0x1c fffff880`02feec20 fffff800`02f15c9a : fffff8a0`00794090 00000000`00000004 00000000`00000001 00000000`00000003 : nt!ViPoolLogStackTrace+0x8a fffff880`02feec50 fffff800`02bad67c : fffff8a0`00794080 00000000`00000040 00000000`00000003 00000000`00000001 : nt!VfFreePoolNotification+0x4a fffff880`02feec80 fffff800`02e2bd66 : fffff8a0`00063190 fffff800`02d17b71 fffff880`02feee30 01cb6492`00000000 : nt!ExDeferredFreePool+0x126d fffff880`02feed30 fffff800`02dacbf0 : 00000000`00000010 fffff880`02feee30 fffff8a0`00065500 00000000`00000010 : nt!CmpCallCallBacks+0x4f6 fffff880`02feee00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1394b STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+126d fffff800`02bad67c 90 nop SYMBOL_STACK_INDEX: e SYMBOL_NAME: nt!ExDeferredFreePool+126d FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: X64_0xA_VRF_nt!ExDeferredFreePool+126d BUCKET_ID: X64_0xA_VRF_nt!ExDeferredFreePool+126d Followup: Pool_corruption --------- 1: kd> lmtsmn start end module name fffff880`00f62000 fffff880`00fb9000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02c45000 fffff880`02ccf000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`00fb9000 fffff880`00fc4000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`01041000 fffff880`0104a000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e76000 fffff880`00ea0000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`03cc7000 fffff880`03d0e000 avgldx64 avgldx64.sys Thu Jun 03 17:06:48 2010 (4C081968) fffff880`03bcc000 fffff880`03bd3080 avgmfx64 avgmfx64.sys Sun Apr 25 17:06:15 2010 (4BD4AEC7) fffff880`02d80000 fffff880`02dd1000 avgtdia avgtdia.sys Thu Jun 03 17:09:57 2010 (4C081A25) fffff880`0124c000 fffff880`01253000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03bbb000 fffff880`03bcc000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`00dd4000 fffff880`00dfe000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00c00000 fffff880`00cc0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`01200000 fffff880`01230000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d2a000 fffff880`00d88000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`014a8000 fffff880`0151b000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`01416000 fffff880`01424000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03a00000 fffff880`03a83000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`03a83000 fffff880`03aa1000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03bac000 fffff880`03bbb000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01400000 fffff880`01416000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`015f6000 fffff880`015ff000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`01424000 fffff880`01430000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`01230000 fffff880`01243000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`03e60000 fffff880`03f54000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`03f54000 fffff880`03f9a000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`00fc4000 fffff880`00fd8000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`00d88000 fffff880`00dd4000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`0152c000 fffff880`01536000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`015bc000 fffff880`015f6000 fvevol fvevol.sys Mon Jul 13 19:22:15 2009 (4A5BC1A7) fffff880`01792000 fffff880`017dc000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02fe6000 fffff800`0302f000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`017f4000 fffff880`017fd000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`03d34000 fffff880`03d4a000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff800`00bac000 fffff800`00bb6000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`0148e000 fffff880`014a8000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01767000 fffff880`01792000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`00cd2000 fffff880`00d16000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66) fffff880`00e5c000 fffff880`00e76000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00ea0000 fffff880`00eab000 msahci msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`02d39000 fffff880`02d44000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`011af000 fffff880`011b9000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`01430000 fffff880`0148e000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03ba1000 fffff880`03bac000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`01600000 fffff880`01612000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01615000 fffff880`01707000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`02cd8000 fffff880`02ce7000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02c00000 fffff880`02c45000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01707000 fffff880`01767000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02d44000 fffff880`02d55000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03b95000 fffff880`03ba1000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02a0a000 fffff800`02fe6000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01257000 fffff880`013fa000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`01243000 fffff880`0124c000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`10b93000 fffff880`10b94180 nvBridge nvBridge.kmd Sat Apr 03 19:50:52 2010 (4BB7D45C) fffff880`0fe69000 fffff880`10b92700 nvlddmkm nvlddmkm.sys Sat Apr 03 20:06:21 2010 (4BB7D7FD) fffff880`02dd1000 fffff880`02df7000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`01000000 fffff880`01015000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`011c6000 fffff880`011f9000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`0102a000 fffff880`01031000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`01031000 fffff880`01041000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`0151b000 fffff880`0152c000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`00d16000 fffff880`00d2a000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`03b44000 fffff880`03b95000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`02d1e000 fffff880`02d27000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02d27000 fffff880`02d30000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02d30000 fffff880`02d39000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`01582000 fffff880`015bc000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`01180000 fffff880`011af000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0) fffff880`03aa2000 fffff880`03abf000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`017ec000 fffff880`017f4000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`01051000 fffff880`01177000 sptd sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632) fffff880`01802000 fffff880`019ff000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`02d73000 fffff880`02d80000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02d55000 fffff880`02d73000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03b30000 fffff880`03b44000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff880`03d0e000 fffff880`03d34000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`03fa7000 fffff880`03ffd000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`03f9a000 fffff880`03fa7000 usbuhci usbuhci.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`011b9000 fffff880`011c6000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`00fd8000 fffff880`00fe6000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02ce9000 fffff880`02d0e000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`017dc000 fffff880`017ec000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`01015000 fffff880`0102a000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e00000 fffff880`00e5c000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01536000 fffff880`01582000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`00fe6000 fffff880`00ffa000 vpcnfltr vpcnfltr.sys Wed Jul 22 18:20:17 2009 (4A6790A1) fffff880`03ada000 fffff880`03b2fc00 vpcvmm vpcvmm.sys Wed Jul 22 18:20:22 2009 (4A6790A6) fffff880`03abf000 fffff880`03ada000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02d0e000 fffff880`02d1e000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00eaf000 fffff880`00f53000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f53000 fffff880`00f62000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02ccf000 fffff880`02cd8000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`01177000 fffff880`01180000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) Thanks Carl,
I will update the progress here.
I will update the progress here.
You are welcome. I did not mean to butt in. When I came online, cybercore was not online. I see he is now. But maybe getting rid of AVG will work for you.
�� Quote: Originally Posted by CarlTR6 You are welcome. I did not mean to butt in. When I came online, cybercore was not online. I see he is now. But maybe getting rid of AVG will work for you.
I can't seem to use the AVG removal tools you linked.
It just doesn't work. I got this log file posted:
It basically said I didn't have anything installed?
Update 1: I uninstalled using the uninstall for AVG in the start menu. Will download MS essentials now.
Thank you for attaching the latest info. Ok, let's see:
100610-23930-01.dmp
Caused by : ASACPI.sys
100610-23930-01.dmp
Caused by : ASACPI.sys
100510-31449-01.dmp
Caused by : Pool_Corruption
It's still bugging out:
ASACPI.sys Mon Mar 28 05:30:36 2005
Update it before we proceed to Memtest86+ - Advanced Memory Diagnostic Tool.
100610-23930-01.dmp
Caused by : ASACPI.sys
100610-23930-01.dmp
Caused by : ASACPI.sys
100510-31449-01.dmp
Caused by : Pool_Corruption
It's still bugging out:
ASACPI.sys Mon Mar 28 05:30:36 2005
Update it before we proceed to Memtest86+ - Advanced Memory Diagnostic Tool.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\100610-23930-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50 System Uptime: 0 days 2:40:17.023 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ .................................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {22f, fffff8800fe829a0, fffff9801cf74cf0, 0} Unable to load image \SystemRoot\system32\DRIVERS\ASACPI.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ASACPI.sys *** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys Probably caused by : ASACPI.sys ( ASACPI+19a0 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 000000000000022f, The caller has completed an untouched IRP_MJ_PNP (instead of passing the IRP down), or non-PDO has failed the IRP using incorrect value of STATUS_NOT_SUPPORTED. Arg2: fffff8800fe829a0, The address in the driver's code where the error was detected. Arg3: fffff9801cf74cf0, IRP address. Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0xc9_22f DRIVER_VERIFIER_IO_VIOLATION_TYPE: 22f FAULTING_IP: ASACPI+19a0 fffff880`0fe829a0 53 push rbx FOLLOWUP_IP: ASACPI+19a0 fffff880`0fe829a0 53 push rbx IRP_ADDRESS: fffff9801cf74cf0 DEVICE_OBJECT: fffffa80060a7610 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LOCK_ADDRESS: fffff80002e74400 -- (!locks fffff80002e74400) Resource @ nt!PiEngineLock (0xfffff80002e74400) Available WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted. WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted. 1 total locks PNP_TRIAGE: Lock address : 0xfffff80002e74400 Thread Count : 0 Thread address: 0x0000000000000000 Thread wait : 0x0 LAST_CONTROL_TRANSFER: from fffff800030fa3dc to fffff80002c70740 STACK_TEXT: fffff880`02fe1368 fffff800`030fa3dc : 00000000`000000c9 00000000`0000022f fffff880`0fe829a0 fffff980`1cf74cf0 : nt!KeBugCheckEx fffff880`02fe1370 fffff800`0310447a : fffff800`030f89f0 fffff880`0fe829a0 fffff980`1cf74cf0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`02fe13b0 fffff800`03105483 : 00000000`0000022f fffff980`1cf74cf0 fffff980`1cf74cf0 00000000`ffffffff : nt!ViErrorFinishReport+0xda fffff880`02fe1400 fffff800`03110eed : 00000000`00000000 00000000`00000000 fffff800`02dfd440 00000000`00000000 : nt!VfErrorReport1+0x63 fffff880`02fe14a0 fffff800`030fa04e : fffffa80`04ae23a8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!VfPnpVerifyIrpStackUpward+0xdd fffff880`02fe1500 fffff800`03106b2d : fffffa80`058385f0 fffffa80`04ae2010 fffff980`1cf74cf0 fffff980`1cf74cf0 : nt!VfMajorVerifyIrpStackUpward+0x6e fffff880`02fe1540 fffff800`0311850d : fffff980`1cf74f70 fffff880`02fe1720 00000000`c00000bb fffff980`1cf74f70 : nt!IovpCompleteRequest2+0xad fffff880`02fe15b0 fffff800`02c72d26 : fffff980`1cf74f73 fffff800`00000000 00000000`00000001 fffff880`00000005 : nt!IovpLocalCompletionRoutine+0x9d fffff880`02fe1610 fffff800`0311019f : fffff980`1cf74cf0 00000000`00000000 fffffa80`060a7b00 00000000`00000000 : nt!IopfCompleteRequest+0x3a6 fffff880`02fe16f0 fffff880`0fe82a13 : fffff880`02fe1878 fffff800`031032a7 00000000`c00000bb fffffa80`060a7bd0 : nt!IovCompleteRequest+0x19f fffff880`02fe17c0 fffff880`02fe1878 : fffff800`031032a7 00000000`c00000bb fffffa80`060a7bd0 fffff980`1cf74fb8 : ASACPI+0x1a13 fffff880`02fe17c8 fffff800`031032a7 : 00000000`c00000bb fffffa80`060a7bd0 fffff980`1cf74fb8 fffffa80`05405ba0 : 0xfffff880`02fe1878 fffff880`02fe17d0 fffff800`03116c16 : fffff980`1cf74cf0 00000000`00000002 fffff980`1cf74cf0 fffff800`0311237e : nt!VfIrpAllocateCallDriverData+0x47 fffff880`02fe1800 fffff800`0311952a : fffff980`1cf74f70 fffffa80`060a7bd0 fffffa80`060a7610 fffffa80`05405ba0 : nt!IovCallDriver+0x566 fffff880`02fe1860 fffff800`03116c16 : fffff980`1cf74cf0 00000000`00000002 fffffa80`060a7610 fffffa80`055219a0 : nt!ViFilterDispatchPnp+0x13a fffff880`02fe1890 fffff800`0302f06e : fffff980`1cf74cf0 fffff880`02fe1970 fffffa80`060a7610 fffffa80`055219a0 : nt!IovCallDriver+0x566 fffff880`02fe18f0 fffff800`03050f4a : fffffa80`05623060 fffff880`02fe1a40 00000000`00000000 00000000`00000000 : nt!PnpAsynchronousCall+0xce fffff880`02fe1930 fffff800`03051047 : 00000000`00000010 00000000`00010246 fffff880`02fe1b40 fffff880`02fe1c38 : nt!PiIrpQueryRemoveDevice+0xda fffff880`02fe1a10 fffff800`0305a3cd : 00000000`00000000 fffffa80`05625890 fffff880`02fe1b40 00000000`00000000 : nt!PnpQueryRemoveLockedDeviceNode+0x67 fffff880`02fe1a40 fffff800`0305a490 : 00000000`00000000 fffff8a0`08bd6501 fffff8a0`02704bd0 ffffe6c5`0e43fa5f : nt!PnpDeleteLockedDeviceNode+0x8d fffff880`02fe1a70 fffff800`030ea5b4 : 00000000`00000002 00000000`00000000 fffffa80`05625890 fffff8a0`08bd6550 : nt!PnpDeleteLockedDeviceNodes+0xa0 fffff880`02fe1ae0 fffff800`030eafdc : fffff880`00000000 00000000`00010200 fffff880`02fe1c00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0x864 fffff880`02fe1c20 fffff800`02fd60dc : 00000000`00000000 fffffa80`07758940 fffff8a0`08bd6550 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`02fe1c50 fffff800`02c7d961 : fffff800`02edc008 fffff8a0`08bd6550 fffff800`02e155f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x58ffb fffff880`02fe1cb0 fffff800`02f14c06 : 00000000`00000000 fffffa80`04607040 00000000`00000080 fffffa80`039ea040 : nt!ExpWorkerThread+0x111 fffff880`02fe1d40 fffff800`02c4ec26 : fffff880`009ec180 fffffa80`04607040 fffff880`009f6f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`02fe1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb SYMBOL_NAME: ASACPI+19a0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ASACPI IMAGE_NAME: ASACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 42476c4c FAILURE_BUCKET_ID: X64_0xc9_22f_VRF_ASACPI+19a0 BUCKET_ID: X64_0xc9_22f_VRF_ASACPI+19a0 Followup: MachineOwner --------- 1: kd> lmvm ASACPI start end module name fffff880`0fe81000 fffff880`0fe89000 ASACPI T (no symbols) Loaded symbol image file: ASACPI.sys Image path: \SystemRoot\system32\DRIVERS\ASACPI.sys Image name: ASACPI.sys Timestamp: Mon Mar 28 05:30:36 2005 (42476C4C) CheckSum: 00003C77 ImageSize: 00008000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\100510-31449-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c47e50 System Uptime: 0 days 0:00:13.868 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ............................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff80000000009, 2, 1, fffff80002a9a44b} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+126d ) Followup: Pool_corruption --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff80000000009, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002a9a44b, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb20e0 fffff80000000009 CURRENT_IRQL: 2 FAULTING_IP: nt!IopCompleteRequest+c88 fffff800`02a9a44b 48894108 mov qword ptr [rcx+8],rax CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System IRP_ADDRESS: fffff7ffffffff89 TRAP_FRAME: fffff88002fedfb0 -- (.trap 0xfffff88002fedfb0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff98002c64ff0 rbx=0000000000000000 rcx=fffff80000000001 rdx=fffff88002feefb8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a9a44b rsp=fffff88002fee140 rbp=fffff88002fee290 r8=fffff88002fee248 r9=fffff88002fee240 r10=0000000000000002 r11=fffff80002a997d0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!IopCompleteRequest+0xc88: fffff800`02a9a44b 48894108 mov qword ptr [rcx+8],rax ds:a000:fffff800`00000009=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a79ca9 to fffff80002a7a740 STACK_TEXT: fffff880`02fede68 fffff800`02a79ca9 : 00000000`0000000a fffff800`00000009 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`02fede70 fffff800`02a78920 : 00000000`80000000 fffff980`02fe6ee0 00000000`02fee0d0 fffff880`02fef0e0 : nt!KiBugCheckDispatch+0x69 fffff880`02fedfb0 fffff800`02a9a44b : ffffffff`80000234 fffff880`02ff0000 00000000`00000004 00000000`0000001b : nt!KiPageFault+0x260 fffff880`02fee140 fffff800`02a570c7 : fffff800`00000001 fffff880`02fee290 fffff880`02fee500 fffff880`00000000 : nt!IopCompleteRequest+0xc88 fffff880`02fee210 fffff800`02a57487 : fffff800`02c82000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7 fffff880`02fee290 fffff800`02a530af : fffff880`00000003 00000000`00458a19 00000000`00000000 00000000`00000000 : nt!KiApcInterrupt+0xd7 fffff880`02fee420 fffff800`02a52e62 : fffff800`02d171f9 fffff880`02fee630 fffffa80`045ca618 fffff880`02fee610 : nt!RtlLookupFunctionTable+0x12f fffff880`02fee480 fffff800`02a1ab16 : 00000000`0002f790 00000000`00000000 fffff880`02fee610 00000000`00000000 : nt!RtlpLookupFunctionEntryForStackWalks+0x32 fffff880`02fee4f0 fffff800`02a1a967 : fffffa80`045ca618 fffff880`00000011 00000000`00000000 fffff800`00000004 : nt!RtlpWalkFrameChain+0x18e fffff880`02feeb90 fffff800`02b3dc2b : 00000000`00000003 fffffa80`045ca618 00000000`00000000 00000000`00000000 : nt!RtlWalkFrameChain+0x73 fffff880`02feebc0 fffff800`02f110dc : fffffa80`045ca600 00000000`00000040 00000000`00000003 fffff800`02b711d1 : nt!RtlCaptureStackBackTrace+0x4b fffff880`02feebf0 fffff800`02f1333a : fffff880`02fea000 fffff880`02ff0000 00000000`00000000 fffff800`02d5e630 : nt!IovpLogStackCallout+0x1c fffff880`02feec20 fffff800`02f15c9a : fffff8a0`00794090 00000000`00000004 00000000`00000001 00000000`00000003 : nt!ViPoolLogStackTrace+0x8a fffff880`02feec50 fffff800`02bad67c : fffff8a0`00794080 00000000`00000040 00000000`00000003 00000000`00000001 : nt!VfFreePoolNotification+0x4a fffff880`02feec80 fffff800`02e2bd66 : fffff8a0`00063190 fffff800`02d17b71 fffff880`02feee30 01cb6492`00000000 : nt!ExDeferredFreePool+0x126d fffff880`02feed30 fffff800`02dacbf0 : 00000000`00000010 fffff880`02feee30 fffff8a0`00065500 00000000`00000010 : nt!CmpCallCallBacks+0x4f6 fffff880`02feee00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1394b STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+126d fffff800`02bad67c 90 nop SYMBOL_STACK_INDEX: e SYMBOL_NAME: nt!ExDeferredFreePool+126d FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: X64_0xA_VRF_nt!ExDeferredFreePool+126d BUCKET_ID: X64_0xA_VRF_nt!ExDeferredFreePool+126d Followup: Pool_corruption --------- Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\100310-22698-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50 System Uptime: 0 days 0:03:58.523 Loading Kernel Symbols . Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. .............................................................. ................................................................ ................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002a9f86e, fffff880099bf3f0, 0} Probably caused by : memory_corruption ( nt!MiLocateWsle+e ) 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: fffff80002a9f86e, Address of the exception record for the exception that caused the bugcheck Arg3: fffff880099bf3f0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text> FAULTING_IP: nt!MiLocateWsle+e fffff800`02a9f86e 418b5320 mov edx,dword ptr [r11+20h] CONTEXT: fffff880099bf3f0 -- (.cxr 0xfffff880099bf3f0) rax=0000000000094b10 rbx=f3b0000094b10963 rcx=fffff8a009201000 rdx=fffff80002c05b40 rsi=ffffffffffffffff rdi=fffffa8006ccda10 rip=fffff80002a9f86e rsp=fffff880099bfdc0 rbp=fffffa8001be1300 r8=fffff8a009201000 r9=0000000000007f3b r10=0000000fffffffff r11=bffff781c0000000 r12=0000007ffffffff8 r13=fffff80002c05b40 r14=fffff6fc50049008 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!MiLocateWsle+0xe: fffff800`02a9f86e 418b5320 mov edx,dword ptr [r11+20h] ds:002b:bffff781`c0000020=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: TrustedInstall CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002a6f339 to fffff80002a9f86e STACK_TEXT: fffff880`099bfdc0 fffff800`02a6f339 : 00000000`00040001 00000000`00000001 00000000`00000000 00000000`00000000 : nt!MiLocateWsle+0xe fffff880`099bfe00 fffff800`02a6ed49 : 00000000`00000000 00000000`00000003 00000000`00000000 00000000`00000000 : nt!MiDeleteSystemPagableVm+0x179 fffff880`099bff60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFreePagedPoolPages+0x129 FOLLOWUP_IP: nt!MiLocateWsle+e fffff800`02a9f86e 418b5320 mov edx,dword ptr [r11+20h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!MiLocateWsle+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 STACK_COMMAND: .cxr 0xfffff880099bf3f0 ; kb IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x3B_nt!MiLocateWsle+e BUCKET_ID: X64_0x3B_nt!MiLocateWsle+e Followup: MachineOwner --------- 1: kd> lmtn start end module name fffff800`00b9e000 fffff800`00ba8000 kdcom kdcom.dll Tue Jul 14 04:31:07 2009 (4A5BDFDB) fffff800`02a09000 fffff800`02fe5000 nt ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9) fffff800`02fe5000 fffff800`0302e000 hal hal.dll Tue Jul 14 04:27:36 2009 (4A5BDF08) fffff880`00c00000 fffff880`00c57000 ACPI ACPI.sys Tue Jul 14 02:19:34 2009 (4A5BC106) fffff880`00c57000 fffff880`00c9b000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66) fffff880`00c9b000 fffff880`00caf000 PSHED PSHED.dll Tue Jul 14 04:32:23 2009 (4A5BE027) fffff880`00caf000 fffff880`00d0d000 CLFS CLFS.SYS Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00d0d000 fffff880`00dcd000 CI CI.dll Tue Jul 14 04:32:13 2009 (4A5BE01D) fffff880`00dcd000 fffff880`00dfc000 SCSIPORT SCSIPORT.SYS Tue Jul 14 03:01:04 2009 (4A5BCAC0) fffff880`00e07000 fffff880`00eab000 Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F) fffff880`00eab000 fffff880`00eba000 WDFLDR WDFLDR.SYS Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00eba000 fffff880`00fe0000 sptd sptd.sys Sun Oct 11 23:55:14 2009 (4AD24632) fffff880`00fe0000 fffff880`00fe9000 WMILIB WMILIB.SYS Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00fe9000 fffff880`00ff3000 msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE) fffff880`00ff3000 fffff880`01000000 vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB) fffff880`01000000 fffff880`0104c000 fltmgr fltmgr.sys Tue Jul 14 02:19:59 2009 (4A5BC11F) fffff880`0104c000 fffff880`01060000 fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481) fffff880`01060000 fffff880`0108a000 cdrom cdrom.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`0108a000 fffff880`01098000 vga vga.sys Tue Jul 14 02:38:47 2009 (4A5BC587) fffff880`01098000 fffff880`010ac000 vpcnfltr vpcnfltr.sys Thu Jul 23 01:20:17 2009 (4A6790A1) fffff880`010b7000 fffff880`010ea000 pci pci.sys Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`010ea000 fffff880`010ff000 partmgr partmgr.sys Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`010ff000 fffff880`01114000 volmgr volmgr.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`01114000 fffff880`01170000 volmgrx volmgrx.sys Tue Jul 14 02:20:33 2009 (4A5BC141) fffff880`01170000 fffff880`01177000 pciide pciide.sys Tue Jul 14 02:19:49 2009 (4A5BC115) fffff880`01177000 fffff880`01187000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`01187000 fffff880`011a1000 mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`011a1000 fffff880`011aa000 atapi atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`011aa000 fffff880`011d4000 ataport ataport.SYS Tue Jul 14 02:19:52 2009 (4A5BC118) fffff880`011d4000 fffff880`011df000 msahci msahci.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`011df000 fffff880`011ea000 amdxata amdxata.sys Tue May 19 20:56:59 2009 (4A12F2EB) fffff880`01200000 fffff880`01215000 lltdio lltdio.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`01216000 fffff880`013b9000 Ntfs Ntfs.sys Tue Jul 14 02:20:47 2009 (4A5BC14F) fffff880`013b9000 fffff880`013e9000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`013f5000 fffff880`013fe000 Null Null.SYS Tue Jul 14 02:19:37 2009 (4A5BC109) fffff880`01400000 fffff880`0144c000 volsnap volsnap.sys Tue Jul 14 02:20:08 2009 (4A5BC128) fffff880`0144c000 fffff880`01486000 rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A) fffff880`01486000 fffff880`01498000 mup mup.sys Tue Jul 14 02:23:45 2009 (4A5BC201) fffff880`01498000 fffff880`014ae000 disk disk.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`014b6000 fffff880`01514000 msrpc msrpc.sys Tue Jul 14 02:21:32 2009 (4A5BC17C) fffff880`01514000 fffff880`0152e000 ksecdd ksecdd.sys Tue Jul 14 02:20:54 2009 (4A5BC156) fffff880`0152e000 fffff880`015a1000 cng cng.sys Tue Jul 14 02:49:40 2009 (4A5BC814) fffff880`015a1000 fffff880`015b2000 pcw pcw.sys Tue Jul 14 02:19:27 2009 (4A5BC0FF) fffff880`015b2000 fffff880`015bc000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:19:45 2009 (4A5BC111) fffff880`015bc000 fffff880`015f6000 fvevol fvevol.sys Tue Jul 14 02:22:15 2009 (4A5BC1A7) fffff880`01600000 fffff880`0164a000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164) fffff880`0164a000 fffff880`0165a000 vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E) fffff880`0165a000 fffff880`01662000 spldr spldr.sys Mon May 11 19:56:27 2009 (4A0858BB) fffff880`01662000 fffff880`0166b000 hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA) fffff880`0166b000 fffff880`01672000 Beep Beep.SYS Tue Jul 14 03:00:13 2009 (4A5BCA8D) fffff880`01673000 fffff880`01765000 ndis ndis.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`01765000 fffff880`017c5000 NETIO NETIO.SYS Tue Jul 14 02:21:46 2009 (4A5BC18A) fffff880`017c5000 fffff880`017f0000 ksecpkg ksecpkg.sys Fri Dec 11 08:03:32 2009 (4B21E0B4) fffff880`01803000 fffff880`01a00000 tcpip tcpip.sys Mon Jun 14 06:39:04 2010 (4C15A458) fffff880`02c00000 fffff880`02c8a000 afd afd.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`02c8a000 fffff880`02c93000 wfplwf wfplwf.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02c93000 fffff880`02ca2000 netbios netbios.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02ca6000 fffff880`02ccb000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B) fffff880`02ccb000 fffff880`02cdb000 watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F) fffff880`02cdb000 fffff880`02ce4000 RDPCDD RDPCDD.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`02ce4000 fffff880`02ced000 rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`02ced000 fffff880`02cf6000 rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63) fffff880`02cf6000 fffff880`02d01000 Msfs Msfs.SYS Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`02d01000 fffff880`02d12000 Npfs Npfs.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`02d12000 fffff880`02d30000 tdx tdx.sys Tue Jul 14 02:21:15 2009 (4A5BC16B) fffff880`02d30000 fffff880`02d3d000 TDI TDI.SYS Tue Jul 14 02:21:18 2009 (4A5BC16E) fffff880`02d3d000 fffff880`02d8e000 avgtdia avgtdia.sys Fri Jun 04 00:09:57 2010 (4C081A25) fffff880`02d8e000 fffff880`02dd3000 netbt netbt.sys Tue Jul 14 02:21:28 2009 (4A5BC178) fffff880`02dd3000 fffff880`02df9000 pacer pacer.sys Tue Jul 14 03:09:41 2009 (4A5BCCC5) fffff880`03a01000 fffff880`03a1e000 serial serial.sys Tue Jul 14 03:00:40 2009 (4A5BCAA8) fffff880`03a1e000 fffff880`03a39000 wanarp wanarp.sys Tue Jul 14 03:10:21 2009 (4A5BCCED) fffff880`03a39000 fffff880`03a8ec00 vpcvmm vpcvmm.sys Thu Jul 23 01:20:22 2009 (4A6790A6) fffff880`03a8f000 fffff880`03aa3000 termdd termdd.sys Tue Jul 14 03:16:36 2009 (4A5BCE64) fffff880`03aa3000 fffff880`03af4000 rdbss rdbss.sys Tue Jul 14 02:24:09 2009 (4A5BC219) fffff880`03af4000 fffff880`03b00000 nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E) fffff880`03b00000 fffff880`03b0b000 mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE) fffff880`03b0b000 fffff880`03b1a000 discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E) fffff880`03b1a000 fffff880`03b9d000 csc csc.sys Tue Jul 14 02:24:26 2009 (4A5BC22A) fffff880`03b9d000 fffff880`03bbb000 dfsc dfsc.sys Tue Jul 14 02:23:44 2009 (4A5BC200) fffff880`03bbb000 fffff880`03bcc000 blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF) fffff880`03bcc000 fffff880`03bd3080 avgmfx64 avgmfx64.sys Mon Apr 26 00:06:15 2010 (4BD4AEC7) fffff880`03bd4000 fffff880`03bea000 AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0) fffff880`03bea000 fffff880`03bff000 NDProxy NDProxy.SYS Tue Jul 14 03:10:05 2009 (4A5BCCDD) fffff880`03c00000 fffff880`03cf4000 dxgkrnl dxgkrnl.sys Fri Oct 02 04:00:14 2009 (4AC5509E) fffff880`03cf8000 fffff880`03d3f000 avgldx64 avgldx64.sys Fri Jun 04 00:06:48 2010 (4C081968) fffff880`03d3f000 fffff880`03d65000 tunnel tunnel.sys Tue Jul 14 03:09:37 2009 (4A5BCCC1) fffff880`03d65000 fffff880`03d7b000 intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD) fffff880`03d7b000 fffff880`03d99000 i8042prt i8042prt.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`03d99000 fffff880`03dde000 ai8tydqa ai8tydqa.SYS Wed Jul 15 00:12:55 2009 (4A5CF4D7) fffff880`03dde000 fffff880`03dee000 CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`04000000 fffff880`0401d000 vpcusb vpcusb.sys Thu Jul 23 01:20:23 2009 (4A6790A7) fffff880`0401d000 fffff880`0402c000 usbrpm usbrpm.sys Tue Jul 14 03:35:14 2009 (4A5BD2C2) fffff880`0402c000 fffff880`0402df00 USBD USBD.SYS Tue Jul 14 03:06:23 2009 (4A5BCBFF) fffff880`0402e000 fffff880`0406a000 vpchbus vpchbus.sys Thu Jul 23 01:20:23 2009 (4A6790A7) fffff880`0406a000 fffff880`040c4000 usbhub usbhub.sys Tue Jul 14 03:07:09 2009 (4A5BCC2D) fffff880`040ce000 fffff880`040f2000 rasl2tp rasl2tp.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`040f2000 fffff880`040fe000 ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8) fffff880`040fe000 fffff880`0412d000 ndiswan ndiswan.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`0412d000 fffff880`04148000 raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9) fffff880`04148000 fffff880`04169000 raspptp raspptp.sys Tue Jul 14 03:10:18 2009 (4A5BCCEA) fffff880`04169000 fffff880`04183000 rassstp rassstp.sys Tue Jul 14 03:10:25 2009 (4A5BCCF1) fffff880`04183000 fffff880`0418e000 rdpbus rdpbus.sys Tue Jul 14 03:17:46 2009 (4A5BCEAA) fffff880`0418e000 fffff880`0419d000 mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`0419d000 fffff880`0419e480 swenum swenum.sys Tue Jul 14 03:00:18 2009 (4A5BCA92) fffff880`0419f000 fffff880`041e2000 ks ks.sys Tue Jul 14 03:00:31 2009 (4A5BCA9F) fffff880`041e2000 fffff880`041f4000 umbus umbus.sys Tue Jul 14 03:06:56 2009 (4A5BCC20) fffff880`041f4000 fffff880`041ff000 flpydisk flpydisk.sys Tue Jul 14 03:00:54 2009 (4A5BCAB6) fffff880`05600000 fffff880`0560d000 mouhid mouhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`0560d000 fffff880`05621000 LMouFilt LMouFilt.Sys Thu Mar 18 10:51:24 2010 (4BA1E98C) fffff880`05621000 fffff880`05644000 luafv luafv.sys Tue Jul 14 02:26:13 2009 (4A5BC295) fffff880`05644000 fffff880`05665000 WudfPf WudfPf.sys Tue Jul 14 03:05:37 2009 (4A5BCBD1) fffff880`0566e000 fffff880`056ca000 HdAudio HdAudio.sys Tue Jul 14 03:06:59 2009 (4A5BCC23) fffff880`056ca000 fffff880`05707000 portcls portcls.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`05707000 fffff880`05729000 drmk drmk.sys Tue Jul 14 04:01:25 2009 (4A5BD8E5) fffff880`05729000 fffff880`0572e200 ksthunk ksthunk.sys Tue Jul 14 03:00:19 2009 (4A5BCA93) fffff880`0572f000 fffff880`0573d000 crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`0573d000 fffff880`05749000 dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`05749000 fffff880`05752000 dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`05752000 fffff880`05765000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F) fffff880`05765000 fffff880`05771000 Dxapi Dxapi.sys Tue Jul 14 02:38:28 2009 (4A5BC574) fffff880`05771000 fffff880`0577f000 monitor monitor.sys Tue Jul 14 02:38:52 2009 (4A5BC58C) fffff880`0577f000 fffff880`0579a000 USBSTOR USBSTOR.SYS Tue Jul 14 03:06:34 2009 (4A5BCC0A) fffff880`0579a000 fffff880`057b7000 usbccgp usbccgp.sys Tue Jul 14 03:06:45 2009 (4A5BCC15) fffff880`057b7000 fffff880`057c5000 hidusb hidusb.sys Tue Jul 14 03:06:22 2009 (4A5BCBFE) fffff880`057c5000 fffff880`057de000 HIDCLASS HIDCLASS.SYS Tue Jul 14 03:06:21 2009 (4A5BCBFD) fffff880`057de000 fffff880`057e6080 HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9) fffff880`057e7000 fffff880`057fc000 LHidFilt LHidFilt.Sys Thu Mar 18 10:51:17 2010 (4BA1E985) fffff880`05800000 fffff880`0582d000 mrxsmb mrxsmb.sys Sat Feb 27 09:52:19 2010 (4B88CF33) fffff880`0582d000 fffff880`0587b000 mrxsmb10 mrxsmb10.sys Sat Feb 27 09:52:28 2010 (4B88CF3C) fffff880`0587b000 fffff880`0589e000 mrxsmb20 mrxsmb20.sys Sat Feb 27 09:52:26 2010 (4B88CF3A) fffff880`058d8000 fffff880`058f0000 rspndr rspndr.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`058f0000 fffff880`059b8000 HTTP HTTP.sys Tue Jul 14 02:22:16 2009 (4A5BC1A8) fffff880`059b8000 fffff880`059d6000 bowser bowser.sys Tue Jul 14 02:23:50 2009 (4A5BC206) fffff880`059d6000 fffff880`059ee000 mpsdrv mpsdrv.sys Tue Jul 14 03:08:25 2009 (4A5BCC79) fffff880`06000000 fffff880`06071000 spsys spsys.sys Mon May 11 20:20:58 2009 (4A085E7A) fffff880`060a8000 fffff880`0614e000 peauth peauth.sys Tue Jul 14 04:01:19 2009 (4A5BD8DF) fffff880`0614e000 fffff880`06159000 secdrv secdrv.SYS Wed Sep 13 16:18:38 2006 (4508052E) fffff880`06159000 fffff880`06186000 srvnet srvnet.sys Tue Jun 22 06:20:32 2010 (4C202C00) fffff880`06186000 fffff880`06198000 tcpipreg tcpipreg.sys Tue Jul 14 03:09:49 2009 (4A5BCCCD) fffff880`06198000 fffff880`06200000 srv2 srv2.sys Tue Jun 22 06:20:47 2010 (4C202C0F) fffff880`06e07000 fffff880`06e9d000 srv srv.sys Tue Jun 22 06:21:11 2010 (4C202C27) fffff880`06e9d000 fffff880`06ed3000 fastfat fastfat.SYS Tue Jul 14 02:23:28 2009 (4A5BC1F0) fffff880`06ed3000 fffff880`06f04000 WUDFRd WUDFRd.sys Tue Jul 14 03:06:06 2009 (4A5BCBEE) fffff880`0fe00000 fffff880`0fe12000 L1E62x64 L1E62x64.sys Thu Jun 11 09:45:22 2009 (4A30A802) fffff880`0fe12000 fffff880`0fe50000 1394ohci 1394ohci.sys Tue Jul 14 03:07:12 2009 (4A5BCC30) fffff880`0fe50000 fffff880`0fe5d000 fdc fdc.sys Tue Jul 14 03:00:54 2009 (4A5BCAB6) fffff880`0fe5d000 fffff880`0fe65000 ASACPI ASACPI.sys Mon Mar 28 05:30:36 2005 (42476C4C) fffff880`0fe65000 fffff880`0fe71000 serenum serenum.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`0fe71000 fffff880`0fe80000 kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`0fe8c000 fffff880`10b1de00 nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:58 2010 (4C37918E) fffff880`10b1e000 fffff880`10b1f180 nvBridge nvBridge.kmd Sat Jul 10 00:07:54 2010 (4C378FAA) fffff880`10b20000 fffff880`10b66000 dxgmms1 dxgmms1.sys Tue Jul 14 02:38:32 2009 (4A5BC578) fffff880`10b66000 fffff880`10b73000 usbuhci usbuhci.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`10b73000 fffff880`10bc9000 USBPORT USBPORT.SYS Tue Jul 14 03:06:31 2009 (4A5BCC07) fffff880`10bc9000 fffff880`10bda000 usbehci usbehci.sys Tue Jul 14 03:06:30 2009 (4A5BCC06) fffff880`10bda000 fffff880`10bfe000 HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5) fffff960`000a0000 fffff960`003af000 win32k win32k.sys Sat Jun 19 07:31:59 2010 (4C1C483F) fffff960`004e0000 fffff960`004ea000 TSDDD TSDDD.dll Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff960`00670000 fffff960`00697000 cdd cdd.dll unavailable (00000000) fffff960`00850000 fffff960`008b1000 ATMFD ATMFD.DLL Thu May 27 07:11:31 2010 (4BFDF0F3) Unloaded modules: fffff880`017f0000 fffff880`017fe000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`013e9000 fffff880`013f5000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`015f6000 fffff880`015ff000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01200000 fffff880`01213000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 I think the dmp files for the ACPI bug I managed to clear.
The BSOD tool dumped it into the same folder, and I followed instructions into not modifying the folder.
But for ATK110, I have updated and it's driver is dated 2009 at the moment.
The latest crash after I updated everything except ATK110 was 100610-23930-01.dmp based on the timing of the file on my computer; this was before I updated ATK110. This crash came about when I tried to do an 'update' to ATK110 driver.
I rebooted and uninstalled the driver, rebooted, and installed the new one. It's updated now. No crashes thus far.
Uninstalled AVG, getting MS essentials now.
The BSOD tool dumped it into the same folder, and I followed instructions into not modifying the folder.
But for ATK110, I have updated and it's driver is dated 2009 at the moment.
The latest crash after I updated everything except ATK110 was 100610-23930-01.dmp based on the timing of the file on my computer; this was before I updated ATK110. This crash came about when I tried to do an 'update' to ATK110 driver.
I rebooted and uninstalled the driver, rebooted, and installed the new one. It's updated now. No crashes thus far.
Uninstalled AVG, getting MS essentials now.
�� Quote: Originally Posted by CarlTR6 You are welcome. I did not mean to butt in. When I came online, cybercore was not online. I see he is now. But maybe getting rid of AVG will work for you.
�� Quote: Originally Posted by lightice I think the dmp files for the ACPI bug I managed to clear.
The BSOD tool dumped it into the same folder, and I followed instructions into not modifying the folder.
But for ATK110, I have updated and it's driver is dated 2009 at the moment.
The latest crash after I updated everything except ATK110 was 100610-23930-01.dmp based on the timing of the file on my computer; this was before I updated ATK110. This crash came about when I tried to do an 'update' to ATK110 driver.
I rebooted and uninstalled the driver, rebooted, and installed the new one. It's updated now. No crashes thus far.
Uninstalled AVG, getting MS essentials now.
The BSOD tool dumped it into the same folder, and I followed instructions into not modifying the folder.
But for ATK110, I have updated and it's driver is dated 2009 at the moment.
The latest crash after I updated everything except ATK110 was 100610-23930-01.dmp based on the timing of the file on my computer; this was before I updated ATK110. This crash came about when I tried to do an 'update' to ATK110 driver.
I rebooted and uninstalled the driver, rebooted, and installed the new one. It's updated now. No crashes thus far.
Uninstalled AVG, getting MS essentials now.
Good, please keep us updated on how it goes.
Thanks Cybercore and Carl, I will let the system run a while.
Before I sleep I'll do memtest and let it get through a few passes.
Will update here.
Update 1: I ran 6 full passes of memtest86, no errors.
Anything I should do next?
Before I sleep I'll do memtest and let it get through a few passes.
Will update here.
Update 1: I ran 6 full passes of memtest86, no errors.
Anything I should do next?
�� Quote: Originally Posted by lightice Thanks Cybercore and Carl, I will let the system run a while.
Before I sleep I'll do memtest and let it get through a few passes.
Will update here.
Update 1: I ran 6 full passes of memtest86, no errors.
Anything I should do next?
Before I sleep I'll do memtest and let it get through a few passes.
Will update here.
Update 1: I ran 6 full passes of memtest86, no errors.
Anything I should do next?
You should have left it run overnight. (Sometimes it takes to isolate sticks to get errors detected. (Up to you.) If you have any fresh crash dumps, please attach them.
I did let it run overnight, and it was only 6 passes.
Windows did freeze again, just.
I am not sure if there was an actual dump file for this one.
I have uninstalled AVG and pretty much everything else.
Windows did freeze again, just.
I am not sure if there was an actual dump file for this one.
I have uninstalled AVG and pretty much everything else.
There are no new dump files, I checked. Only 3, which are the same exact ones.
Why did the computer lockup? :s
Why did the computer lockup? :s
How did it lockup, you can't boot, can't login?
It booted up normally.
Entered windows.
I went to the washroom.
Came back, and it just froze after booting into windows.
Mouse won't respond, no keystroke response.
Entered windows.
I went to the washroom.
Came back, and it just froze after booting into windows.
Mouse won't respond, no keystroke response.
That maybe caused by the video card/driver. I went through that with my video card before I got the right driver.
Currently, I installed the latest driver from the nvidia website.
At the moment, the computer is acting worst.
I can't even boot to windows. It freezes at the point where the coloured dots are supposed to become the windows logo.
After a few minutes at this state, the computer screen turns black, and the CPU gives out multiple beeping non stop.
I have run memtest86 overnight with no issues.
Now, I tried to restart the computer and it freezes again.
After that, I rebooted and it refuses to show post.
Fans etc all spinning
I got it to enter bios, but I tried to save settings and it just hung.
Should I reflash bios?
Update 1: I reflashed to an earlier rom, version 2002.
Now i managed to repair windows, it is repairing at the moment.
I have entered windows, waiting for it to load.
Load seems successful
Checking if there are new dump files available
There are no new dump files apart from the 3 we have already analysed and tackled.
I have however, added in a fresh zip file and perfmon report if it is of any use.
At the moment, the computer is acting worst.
I can't even boot to windows. It freezes at the point where the coloured dots are supposed to become the windows logo.
After a few minutes at this state, the computer screen turns black, and the CPU gives out multiple beeping non stop.
I have run memtest86 overnight with no issues.
Now, I tried to restart the computer and it freezes again.
After that, I rebooted and it refuses to show post.
Fans etc all spinning
I got it to enter bios, but I tried to save settings and it just hung.
Should I reflash bios?
Update 1: I reflashed to an earlier rom, version 2002.
Now i managed to repair windows, it is repairing at the moment.
I have entered windows, waiting for it to load.
Load seems successful
Checking if there are new dump files available
There are no new dump files apart from the 3 we have already analysed and tackled.
I have however, added in a fresh zip file and perfmon report if it is of any use.
Quote:
I got it to enter bios, but I tried to save settings and it just hung.
Should I reflash bios?
Should I reflash bios?
1. Remove the videocard and try to boot without it. I reckon I also had random restarts before and after entering windows when my old GF6600 bit the dust a couple years ago.
2. Isolate and test the ram sticks separately and in different slots. I know it's a PITA doing that, but you need to be sure it's not the RAM.
I flashed the bios with 1 version earlier. It was on the latest.
I will try the RAM tomorrow.
As for the video card, I did the video card stress test and let it run, no observed artifacts at all.
I don't have built in GFX though.
Also, now I managed to enter windows after a bio flash to 1 version earlier.
I also did a windows startup repair ( windows requested this )
I will try the RAM tomorrow.
As for the video card, I did the video card stress test and let it run, no observed artifacts at all.
I don't have built in GFX though.
Also, now I managed to enter windows after a bio flash to 1 version earlier.
I also did a windows startup repair ( windows requested this )
Fingures crossed, keep us updated.
�� Quote: Originally Posted by cybercore Fingures crossed, keep us updated.
And if so, is there any way I can deal with it?
�� Quote: Originally Posted by lightice �� Quote: Originally Posted by cybercore Fingures crossed, keep us updated.
And if so, is there any way I can deal with it?
You should know better if there's a problem with the registry, if you actually did something to get it messed up.
Run memtest overnight.
I didn't do anything to the registry, I always do uninstalls correctly and don't manually mess with the registry.
Well, I just got a BSOD again.
When I can get the computer to startup, I'll post the necessary files.
And again I can't get past post. Nothing shows after I try to reboot.
I got BSOD again. This was when I was trying to get my LAN to connect so I could post the dmp file.
Well, I just got a BSOD again.
When I can get the computer to startup, I'll post the necessary files.
And again I can't get past post. Nothing shows after I try to reboot.
I got BSOD again. This was when I was trying to get my LAN to connect so I could post the dmp file.
Well, my LAN port somehow stopped working, I tried to "repair" and it gave me BSOD. So I'm reinstalling the driver.
Okay, this is weird, I tried reinstalling the driver and configuring the IP address, but the adaptor doesn't recognise the network. It keeps giving me 'unidentified network' and won't connect me even though I entered the correct IP/subnet values.
I can't get my network adaptor on the P5Q-pro to work now, it just gives me 'unidentified network'.
Here are the latests dmp files.
Only those dated 10/10/2010 are the recent ones,2 of them.
Okay, this is weird, I tried reinstalling the driver and configuring the IP address, but the adaptor doesn't recognise the network. It keeps giving me 'unidentified network' and won't connect me even though I entered the correct IP/subnet values.
I can't get my network adaptor on the P5Q-pro to work now, it just gives me 'unidentified network'.
Here are the latests dmp files.
Only those dated 10/10/2010 are the recent ones,2 of them.
Have you tried using only two sticks of RAM?
I did a bit of searching in relation to my old blue screens, and it seems that some of the P5Q boards (including the P5Q and the P5Q Pro) can exhibit odd behaviour with 4 sticks of RAM. One symptom that someone posted about was the onboard LAN 'disappearing', and there are a lot of "random" blue screen reports.
While it may be a bit of a long shot, as you've built the system yourself, I can't see giving it a shot doing any harm.
I did a bit of searching in relation to my old blue screens, and it seems that some of the P5Q boards (including the P5Q and the P5Q Pro) can exhibit odd behaviour with 4 sticks of RAM. One symptom that someone posted about was the onboard LAN 'disappearing', and there are a lot of "random" blue screen reports.
While it may be a bit of a long shot, as you've built the system yourself, I can't see giving it a shot doing any harm.
�� Quote: Originally Posted by Pirl Have you tried using only two sticks of RAM?
I did a bit of searching in relation to my old blue screens, and it seems that some of the P5Q boards (including the P5Q and the P5Q Pro) can exhibit odd behaviour with 4 sticks of RAM. One symptom that someone posted about was the onboard LAN 'disappearing', and there are a lot of "random" blue screen reports.
While it may be a bit of a long shot, as you've built the system yourself, I can't see giving it a shot doing any harm.
I did a bit of searching in relation to my old blue screens, and it seems that some of the P5Q boards (including the P5Q and the P5Q Pro) can exhibit odd behaviour with 4 sticks of RAM. One symptom that someone posted about was the onboard LAN 'disappearing', and there are a lot of "random" blue screen reports.
While it may be a bit of a long shot, as you've built the system yourself, I can't see giving it a shot doing any harm.
Well it suddenly started working again, the lan that is. :S
By 'disappearing' I mean that it no longer shows up in Windows.
Oh, it shows up in windows. I checked everything it shows that it is 'working correctly'.
But unfortunately it shows 'unidentified network' and 'unable to connect to network'.
Sometimes it shows network cable unplugged.
Now it's working fine, after i did a diagnose and repair. The repair message was "DNS server address incorrect" or something of that sort. But I followed the exact same DNS server as my netbook.
After 3 reboots since getting back network access, it seems to be working.
This happened previously as well, but not so serious.
Could this be the problem to my BSODs?
But unfortunately it shows 'unidentified network' and 'unable to connect to network'.
Sometimes it shows network cable unplugged.
Now it's working fine, after i did a diagnose and repair. The repair message was "DNS server address incorrect" or something of that sort. But I followed the exact same DNS server as my netbook.
After 3 reboots since getting back network access, it seems to be working.
This happened previously as well, but not so serious.
Could this be the problem to my BSODs?
I'm about 12 hours off confirming that my blue screens were related to having four sticks of RAM installed (any combination of which, in pairs of two, seem to be fine)
�� Quote: Originally Posted by Pirl I'm about 12 hours off confirming that my blue screens were related to having four sticks of RAM installed (any combination of which, in pairs of two, seem to be fine)
You take two sticks out and see if you get the blue screens anywhere near as often.
For me, I was getting them randomly between a few minutes after boot to ~a day after boot.
Since I took two sticks out ~2.5 days ago I haven't had one.
If I get 3 days of uptime without a blue screen with 2 sticks when I could hardly get 1 day with 4 sticks, I see it as a reasonable assumption that it's somehow related to having 4 sticks in.
For me, I was getting them randomly between a few minutes after boot to ~a day after boot.
Since I took two sticks out ~2.5 days ago I haven't had one.
If I get 3 days of uptime without a blue screen with 2 sticks when I could hardly get 1 day with 4 sticks, I see it as a reasonable assumption that it's somehow related to having 4 sticks in.
�� Quote: Originally Posted by Pirl You take two sticks out and see if you get the blue screens anywhere near as often.
For me, I was getting them randomly between a few minutes after boot to ~a day after boot.
Since I took two sticks out ~2.5 days ago I haven't had one.
If I get 3 days of uptime without a blue screen with 2 sticks when I could hardly get 1 day with 4 sticks, I see it as a reasonable assumption that it's somehow related to having 4 sticks in.
For me, I was getting them randomly between a few minutes after boot to ~a day after boot.
Since I took two sticks out ~2.5 days ago I haven't had one.
If I get 3 days of uptime without a blue screen with 2 sticks when I could hardly get 1 day with 4 sticks, I see it as a reasonable assumption that it's somehow related to having 4 sticks in.
The problem is I can't leave the computer on when I leave the house, my area is prone to unexpected weather changes and thunderstorms can occur out of the blue.
My house is quite prone to lightning strikes, so I usually unplug when I leave the house.
�� Quote: Originally Posted by lightice Well, my LAN port somehow stopped working, I tried to "repair" and it gave me BSOD. So I'm reinstalling the driver.
Okay, this is weird, I tried reinstalling the driver and configuring the IP address, but the adaptor doesn't recognise the network. It keeps giving me 'unidentified network' and won't connect me even though I entered the correct IP/subnet values.
I can't get my network adaptor on the P5Q-pro to work now, it just gives me 'unidentified network'.
Here are the latests dmp files.
Only those dated 10/10/2010 are the recent ones,2 of them.
Okay, this is weird, I tried reinstalling the driver and configuring the IP address, but the adaptor doesn't recognise the network. It keeps giving me 'unidentified network' and won't connect me even though I entered the correct IP/subnet values.
I can't get my network adaptor on the P5Q-pro to work now, it just gives me 'unidentified network'.
Here are the latests dmp files.
Only those dated 10/10/2010 are the recent ones,2 of them.
Ok you have quite the mix of causes.
1-memory corruption directly in two of these.
2-SPTD.sys (a virtual dvd driver that almost always causes bsod's)
3-ASACPI.sys (driver verified) (not sure if still installed--)
here is what I would do
1-remove the virtual drive software (Alcohol, daemon tools.)
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
[/quote]
You can use MagicDisc as an alternative.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
2-Re-install the ASACPI.sys file with the newest possible version date
ASACPI.sys Sun Mar 27 22:30:36 2005
Quote:
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
4-Run a system file check
SFC /SCANNOW Command - System File Checker
Let us know the results
Ken J
Hi Ken,
I have daemon tools installed.
I'll install magicdisc, thanks for the recommendation.
As for the ASACPI.sys , I do have the latest 2009 (driver date: 5/5/2009) version of the driver.
I will run a system file check in a while. Saving my documents now. Thanks.
Update 1:
Uninstalled daemon tools
Used the SPTD removal tool to uninstall
Downloaded magicdisk, not yet installed.
Update 2:
SFC complete, here is the log file.
Update 3:
I found the file from the windows DVD, it took me a while cause it wasn't in alphabetical order. *sigh*.
Running sfc again now to check if there are any more errors.
I followed the steps listed in this forum and microsoft regarding ownership taking and replacing the dll.mui file.
Update 4:
Replacing the file didn't work! ****
I have daemon tools installed.
I'll install magicdisc, thanks for the recommendation.
As for the ASACPI.sys , I do have the latest 2009 (driver date: 5/5/2009) version of the driver.
I will run a system file check in a while. Saving my documents now. Thanks.
Update 1:
Uninstalled daemon tools
Used the SPTD removal tool to uninstall
Downloaded magicdisk, not yet installed.
Update 2:
SFC complete, here is the log file.
Update 3:
I found the file from the windows DVD, it took me a while cause it wasn't in alphabetical order. *sigh*.
Running sfc again now to check if there are any more errors.
I followed the steps listed in this forum and microsoft regarding ownership taking and replacing the dll.mui file.
Update 4:
Replacing the file didn't work! ****
I did all the steps you listed above.
Yet today, after having my computer off for 4h and 30min. I came back and swtiched it on, used windows for 5 minutes and i got BSOD.
Earlier, I could use windows for a few hours no issues.
When I can manage to enter windows again, I'd post the dmp file.
This is the dmp file that is of the latest BSOD: 101110-18891-01.dmp
Yet today, after having my computer off for 4h and 30min. I came back and swtiched it on, used windows for 5 minutes and i got BSOD.
Earlier, I could use windows for a few hours no issues.
When I can manage to enter windows again, I'd post the dmp file.
This is the dmp file that is of the latest BSOD: 101110-18891-01.dmp
101110-18891-01.dmp
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
This is the general bug check code for fatal errors found by Driver Verifier.
BugCheck C4, {91, 0, fffffa8006bd5b60, 0}
win32k.sys ( win32k!xxxRealSleepThread+291 )
I suspect a hardware issue:
memtest86 RAM - Test with Memtest86+
hdd scan (SMART) HDDScan
Up to you to update this one, it's not gonna fix it anyway:
RTKVHD64.sys Fri May 22 21:04:20 2009
Realtek Audio (latest is Aug. 2010)
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
This is the general bug check code for fatal errors found by Driver Verifier.
BugCheck C4, {91, 0, fffffa8006bd5b60, 0}
win32k.sys ( win32k!xxxRealSleepThread+291 )
I suspect a hardware issue:
memtest86 RAM - Test with Memtest86+
hdd scan (SMART) HDDScan
Code:
fffff880`0895ea88 fffff800`02d1624a : 00000000`000000c4 00000000`00000091 00000000`00000000 fffffa80`06bd5b60 : nt!KeBugCheckEx fffff880`0895ea90 fffff800`02cee6b3 : fffff8a0`01bea020 fffff880`0895eb70 00000000`00000003 fffff800`02fb410a : nt! ?? ::FNODOBFM::`string'+0x4904 fffff880`0895ead0 fffff800`02cfb9ef : fffff880`0895f978 fffff880`0895f6e0 fffff880`0895fa20 00000000`00000001 : nt!RtlDispatchException+0x33 fffff880`0895f1b0 fffff800`02cc0d82 : fffff880`0895f978 00000000`000024ff fffff880`0895fa20 00000000`00000001 : nt!KiDispatchException+0x16f fffff880`0895f840 fffff800`02cbf68a : 00000000`ffffffff fffff880`00000001 00000000`000ceb10 fffffa80`06bd5c68 : nt!KiExceptionDispatch+0xc2 fffff880`0895fa20 fffff960`0016b591 : bffff960`0016b5f1 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a fffff880`0895fbb8 bffff960`0016b5f1 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!xxxRealSleepThread+0x291 fffff880`0895fbc0 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000020 : 0xbffff960`0016b5f1
Up to you to update this one, it's not gonna fix it anyway:
RTKVHD64.sys Fri May 22 21:04:20 2009
Realtek Audio (latest is Aug. 2010)
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\a\Minidump\D M P\101110-18891-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50 Debug session time: Mon Oct 11 11:21:40.495 2010 (GMT-5) System Uptime: 0 days 0:04:32.165 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {91, 0, fffffa8006bd5b60, 0} Probably caused by : win32k.sys ( win32k!xxxRealSleepThread+291 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by the operating system. The only supported way to extend a kernel mode stack is by using KeExpandKernelStackAndCallout. Arg2: 0000000000000000 Arg3: fffffa8006bd5b60 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0xc4_91 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: firefox.exe CURRENT_IRQL: 0 EXCEPTION_RECORD: fffff8800895f978 -- (.exr 0xfffff8800895f978) ExceptionAddress: fffff9600016b591 (win32k!xxxRealSleepThread+0x0000000000000291) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff8800895fa20 -- (.trap 0xfffff8800895fa20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=000000000004271f rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff9600016b591 rsp=fffff8800895fbb8 rbp=0000000000000000 r8=fffffa8006bf17b8 r9=0000000000000000 r10=fffffffffffffffd r11=0000000000000246 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc win32k!xxxRealSleepThread+0x291: fffff960`0016b591 c3 ret Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002d1624a to fffff80002cc1740 STACK_TEXT: fffff880`0895ea88 fffff800`02d1624a : 00000000`000000c4 00000000`00000091 00000000`00000000 fffffa80`06bd5b60 : nt!KeBugCheckEx fffff880`0895ea90 fffff800`02cee6b3 : fffff8a0`01bea020 fffff880`0895eb70 00000000`00000003 fffff800`02fb410a : nt! ?? ::FNODOBFM::`string'+0x4904 fffff880`0895ead0 fffff800`02cfb9ef : fffff880`0895f978 fffff880`0895f6e0 fffff880`0895fa20 00000000`00000001 : nt!RtlDispatchException+0x33 fffff880`0895f1b0 fffff800`02cc0d82 : fffff880`0895f978 00000000`000024ff fffff880`0895fa20 00000000`00000001 : nt!KiDispatchException+0x16f fffff880`0895f840 fffff800`02cbf68a : 00000000`ffffffff fffff880`00000001 00000000`000ceb10 fffffa80`06bd5c68 : nt!KiExceptionDispatch+0xc2 fffff880`0895fa20 fffff960`0016b591 : bffff960`0016b5f1 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a fffff880`0895fbb8 bffff960`0016b5f1 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!xxxRealSleepThread+0x291 fffff880`0895fbc0 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000020 : 0xbffff960`0016b5f1 STACK_COMMAND: kb FOLLOWUP_IP: win32k!xxxRealSleepThread+291 fffff960`0016b591 c3 ret SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: win32k!xxxRealSleepThread+291 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c483f FAILURE_BUCKET_ID: X64_0xc4_91_win32k!xxxRealSleepThread+291 BUCKET_ID: X64_0xc4_91_win32k!xxxRealSleepThread+291 Followup: MachineOwner bffff880`03ea5000 bffff880`03ec6000 raspptp raspptp.sys unavailable (00000000) bffff880`03f7d000 bffff880`03f7f000 USBD USBD.SYS unavailable (00000000) bffff880`05d82000 bffff880`05df3000 spsys spsys.sys unavailable (00000000) fffff800`00bb7000 fffff800`00bc1000 kdcom kdcom.dll Tue Jul 14 04:31:07 2009 (4A5BDFDB) fffff800`02c08000 fffff800`02c51000 hal hal.dll Tue Jul 14 04:27:36 2009 (4A5BDF08) fffff800`02c51000 fffff800`0322d000 nt ntkrnlmp.exe Sat Jun 19 07:16:41 2010 (4C1C44A9) fffff880`00c14000 fffff880`00c58000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 04:29:10 2009 (4A5BDF66) fffff880`00c58000 fffff880`00c6c000 PSHED PSHED.dll Tue Jul 14 04:32:23 2009 (4A5BE027) fffff880`00c6c000 fffff880`00cca000 CLFS CLFS.SYS Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00cca000 fffff880`00d8a000 CI CI.dll Tue Jul 14 04:32:13 2009 (4A5BE01D) fffff880`00d8a000 fffff880`00da4000 mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00da4000 fffff880`00dad000 atapi atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`00dad000 fffff880`00dd7000 ataport ataport.SYS Tue Jul 14 02:19:52 2009 (4A5BC118) fffff880`00dd7000 fffff880`00de2000 msahci msahci.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`00de2000 fffff880`00ded000 amdxata amdxata.sys Tue May 19 20:56:59 2009 (4A12F2EB) fffff880`00e00000 fffff880`00e15000 partmgr partmgr.sys Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`00e15000 fffff880`00e2a000 volmgr volmgr.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`00e2a000 fffff880`00e86000 volmgrx volmgrx.sys Tue Jul 14 02:20:33 2009 (4A5BC141) fffff880`00e86000 fffff880`00e8d000 pciide pciide.sys Tue Jul 14 02:19:49 2009 (4A5BC115) fffff880`00e8d000 fffff880`00e9d000 PCIIDEX PCIIDEX.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`00ea1000 fffff880`00f45000 Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F) fffff880`00f45000 fffff880`00f54000 WDFLDR WDFLDR.SYS Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`00f54000 fffff880`00fab000 ACPI ACPI.sys Tue Jul 14 02:19:34 2009 (4A5BC106) fffff880`00fab000 fffff880`00fb4000 WMILIB WMILIB.SYS Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`00fb4000 fffff880`00fbe000 msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE) fffff880`00fbe000 fffff880`00fcb000 vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB) fffff880`00fcb000 fffff880`00ffe000 pci pci.sys Tue Jul 14 02:19:51 2009 (4A5BC117) fffff880`01000000 fffff880`01073000 cng cng.sys Tue Jul 14 02:49:40 2009 (4A5BC814) fffff880`01073000 fffff880`010bf000 volsnap volsnap.sys Tue Jul 14 02:20:08 2009 (4A5BC128) fffff880`010bf000 fffff880`010e3000 rasl2tp rasl2tp.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`010e5000 fffff880`01131000 fltmgr fltmgr.sys Tue Jul 14 02:19:59 2009 (4A5BC11F) fffff880`01131000 fffff880`01145000 fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481) fffff880`01145000 fffff880`011a3000 msrpc msrpc.sys Tue Jul 14 02:21:32 2009 (4A5BC17C) fffff880`011a3000 fffff880`011dd000 rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A) fffff880`0120a000 fffff880`013ad000 Ntfs Ntfs.sys Tue Jul 14 02:20:47 2009 (4A5BC14F) fffff880`013ad000 fffff880`013c7000 ksecdd ksecdd.sys Tue Jul 14 02:20:54 2009 (4A5BC156) fffff880`013c7000 fffff880`013d8000 pcw pcw.sys Tue Jul 14 02:19:27 2009 (4A5BC0FF) fffff880`013d8000 fffff880`013e2000 Fs_Rec Fs_Rec.sys Tue Jul 14 02:19:45 2009 (4A5BC111) fffff880`013e2000 fffff880`013f8000 AgileVpn AgileVpn.sys Tue Jul 14 03:10:24 2009 (4A5BCCF0) fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164) fffff880`0144a000 fffff880`0145a000 vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E) fffff880`0145a000 fffff880`01462000 spldr spldr.sys Mon May 11 19:56:27 2009 (4A0858BB) fffff880`01462000 fffff880`01474000 mup mup.sys Tue Jul 14 02:23:45 2009 (4A5BC201) fffff880`01476000 fffff880`01568000 ndis ndis.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`01568000 fffff880`015c8000 NETIO NETIO.SYS Tue Jul 14 02:21:46 2009 (4A5BC18A) fffff880`015c8000 fffff880`015f3000 ksecpkg ksecpkg.sys Fri Dec 11 08:03:32 2009 (4B21E0B4) fffff880`015f3000 fffff880`015fc000 hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Mon Jun 14 06:39:04 2010 (4C15A458) fffff880`01800000 fffff880`01809000 RDPCDD RDPCDD.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`01809000 fffff880`01812000 rdpencdd rdpencdd.sys Tue Jul 14 03:16:34 2009 (4A5BCE62) fffff880`01812000 fffff880`0181b000 rdprefmp rdprefmp.sys Tue Jul 14 03:16:35 2009 (4A5BCE63) fffff880`0181b000 fffff880`01826000 Msfs Msfs.SYS Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`01826000 fffff880`01837000 Npfs Npfs.SYS Tue Jul 14 02:19:48 2009 (4A5BC114) fffff880`01837000 fffff880`01855000 tdx tdx.sys Tue Jul 14 02:21:15 2009 (4A5BC16B) fffff880`01855000 fffff880`01862000 TDI TDI.SYS Tue Jul 14 02:21:18 2009 (4A5BC16E) fffff880`01862000 fffff880`018a7000 netbt netbt.sys Tue Jul 14 02:21:28 2009 (4A5BC178) fffff880`018a7000 fffff880`018b7000 CompositeBus CompositeBus.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`018b7000 fffff880`018c3000 ndistapi ndistapi.sys Tue Jul 14 03:10:00 2009 (4A5BCCD8) fffff880`018cb000 fffff880`01905000 fvevol fvevol.sys Tue Jul 14 02:22:15 2009 (4A5BC1A7) fffff880`01905000 fffff880`0191b000 disk disk.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`0191b000 fffff880`0194b000 CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E) fffff880`01981000 fffff880`019ab000 cdrom cdrom.sys Tue Jul 14 02:19:54 2009 (4A5BC11A) fffff880`019ab000 fffff880`019b4000 Null Null.SYS Tue Jul 14 02:19:37 2009 (4A5BC109) fffff880`019b4000 fffff880`019bb000 Beep Beep.SYS Tue Jul 14 03:00:13 2009 (4A5BCA8D) fffff880`019bb000 fffff880`019c9000 vga vga.sys Tue Jul 14 02:38:47 2009 (4A5BC587) fffff880`019c9000 fffff880`019ee000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 02:38:51 2009 (4A5BC58B) fffff880`019ee000 fffff880`019fe000 watchdog watchdog.sys Tue Jul 14 02:37:35 2009 (4A5BC53F) fffff880`02c00000 fffff880`02c0b000 mssmbios mssmbios.sys Tue Jul 14 02:31:10 2009 (4A5BC3BE) fffff880`02c0b000 fffff880`02c1a000 discache discache.sys Tue Jul 14 02:37:18 2009 (4A5BC52E) fffff880`02c1d000 fffff880`02ca7000 afd afd.sys Tue Jul 14 02:21:40 2009 (4A5BC184) fffff880`02ca7000 fffff880`02cb0000 wfplwf wfplwf.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02cb0000 fffff880`02cd6000 pacer pacer.sys Tue Jul 14 03:09:41 2009 (4A5BCCC5) fffff880`02cd6000 fffff880`02cea000 vpcnfltr vpcnfltr.sys Thu Jul 23 01:20:17 2009 (4A6790A1) fffff880`02cea000 fffff880`02cf9000 netbios netbios.sys Tue Jul 14 03:09:26 2009 (4A5BCCB6) fffff880`02cf9000 fffff880`02d16000 serial serial.sys Tue Jul 14 03:00:40 2009 (4A5BCAA8) fffff880`02d16000 fffff880`02d31000 wanarp wanarp.sys Tue Jul 14 03:10:21 2009 (4A5BCCED) fffff880`02d31000 fffff880`02d86c00 vpcvmm vpcvmm.sys Thu Jul 23 01:20:22 2009 (4A6790A6) fffff880`02d87000 fffff880`02d9b000 termdd termdd.sys Tue Jul 14 03:16:36 2009 (4A5BCE64) fffff880`02d9b000 fffff880`02dec000 rdbss rdbss.sys Tue Jul 14 02:24:09 2009 (4A5BC219) fffff880`02dec000 fffff880`02df8000 nsiproxy nsiproxy.sys Tue Jul 14 02:21:02 2009 (4A5BC15E) fffff880`03a00000 fffff880`03a56000 USBPORT USBPORT.SYS Tue Jul 14 03:06:31 2009 (4A5BCC07) fffff880`03a56000 fffff880`03a7a000 HDAudBus HDAudBus.sys Tue Jul 14 03:06:13 2009 (4A5BCBF5) fffff880`03a7a000 fffff880`03a8c000 L1E62x64 L1E62x64.sys Mon Mar 29 05:08:44 2010 (4BB00BAC) fffff880`03a8c000 fffff880`03aca000 1394ohci 1394ohci.sys Tue Jul 14 03:07:12 2009 (4A5BCC30) fffff880`03aca000 fffff880`03ad7000 fdc fdc.sys Tue Jul 14 03:00:54 2009 (4A5BCAB6) fffff880`03ad7000 fffff880`03af5000 i8042prt i8042prt.sys Tue Jul 14 02:19:57 2009 (4A5BC11D) fffff880`03afd000 fffff880`03b80000 csc csc.sys Tue Jul 14 02:24:26 2009 (4A5BC22A) fffff880`03b80000 fffff880`03b9e000 dfsc dfsc.sys Tue Jul 14 02:23:44 2009 (4A5BC200) fffff880`03b9e000 fffff880`03baf000 blbdrive blbdrive.sys Tue Jul 14 02:35:59 2009 (4A5BC4DF) fffff880`03baf000 fffff880`03bd5000 tunnel tunnel.sys Tue Jul 14 03:09:37 2009 (4A5BCCC1) fffff880`03bd5000 fffff880`03beb000 intelppm intelppm.sys Tue Jul 14 02:19:25 2009 (4A5BC0FD) fffff880`03beb000 fffff880`03bfa000 kbdclass kbdclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`03e00000 fffff880`03e5a000 usbhub usbhub.sys Tue Jul 14 03:07:09 2009 (4A5BCC2D) fffff880`03e5b000 fffff880`03e8a000 ndiswan ndiswan.sys Tue Jul 14 03:10:11 2009 (4A5BCCE3) fffff880`03e8a000 fffff880`03ea5000 raspppoe raspppoe.sys Tue Jul 14 03:10:17 2009 (4A5BCCE9) fffff880`03ec6000 fffff880`03ee0000 rassstp rassstp.sys Tue Jul 14 03:10:25 2009 (4A5BCCF1) fffff880`03ee0000 fffff880`03eeb000 rdpbus rdpbus.sys Tue Jul 14 03:17:46 2009 (4A5BCEAA) fffff880`03eeb000 fffff880`03efa000 mouclass mouclass.sys Tue Jul 14 02:19:50 2009 (4A5BC116) fffff880`03efa000 fffff880`03efb480 swenum swenum.sys Tue Jul 14 03:00:18 2009 (4A5BCA92) fffff880`03efc000 fffff880`03f3f000 ks ks.sys Tue Jul 14 03:00:31 2009 (4A5BCA9F) fffff880`03f3f000 fffff880`03f51000 umbus umbus.sys Tue Jul 14 03:06:56 2009 (4A5BCC20) fffff880`03f51000 fffff880`03f6e000 vpcusb vpcusb.sys Thu Jul 23 01:20:23 2009 (4A6790A7) fffff880`03f6e000 fffff880`03f7d000 usbrpm usbrpm.sys Tue Jul 14 03:35:14 2009 (4A5BD2C2) fffff880`03f7f000 fffff880`03fbb000 vpchbus vpchbus.sys Thu Jul 23 01:20:23 2009 (4A6790A7) fffff880`03fbb000 fffff880`03fc6000 flpydisk flpydisk.sys Tue Jul 14 03:00:54 2009 (4A5BCAB6) fffff880`03fc6000 fffff880`03fdb000 NDProxy NDProxy.SYS Tue Jul 14 03:10:05 2009 (4A5BCCDD) fffff880`05028000 fffff880`051d4900 RTKVHD64 RTKVHD64.sys Fri May 22 21:04:20 2009 (4A16E924) fffff880`05200000 fffff880`05215000 LHidFilt LHidFilt.Sys Thu Mar 18 10:51:17 2010 (4BA1E985) fffff880`05215000 fffff880`05222000 mouhid mouhid.sys Tue Jul 14 03:00:20 2009 (4A5BCA94) fffff880`05222000 fffff880`05236000 LMouFilt LMouFilt.Sys Thu Mar 18 10:51:24 2010 (4BA1E98C) fffff880`05236000 fffff880`05259000 luafv luafv.sys Tue Jul 14 02:26:13 2009 (4A5BC295) fffff880`05259000 fffff880`0527a000 WudfPf WudfPf.sys Tue Jul 14 03:05:37 2009 (4A5BCBD1) fffff880`0527a000 fffff880`0528f000 lltdio lltdio.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`0528f000 fffff880`052a7000 rspndr rspndr.sys Tue Jul 14 03:08:50 2009 (4A5BCC92) fffff880`052db000 fffff880`05318000 portcls portcls.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`05318000 fffff880`0533a000 drmk drmk.sys Tue Jul 14 04:01:25 2009 (4A5BD8E5) fffff880`0533a000 fffff880`0533f200 ksthunk ksthunk.sys Tue Jul 14 03:00:19 2009 (4A5BCA93) fffff880`05340000 fffff880`0534c000 Dxapi Dxapi.sys Tue Jul 14 02:38:28 2009 (4A5BC574) fffff880`0534c000 fffff880`0535a000 crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD) fffff880`0535a000 fffff880`05366000 dump_dumpata dump_dumpata.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`05366000 fffff880`0536f000 dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113) fffff880`0536f000 fffff880`05382000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F) fffff880`05382000 fffff880`05390000 monitor monitor.sys Tue Jul 14 02:38:52 2009 (4A5BC58C) fffff880`05390000 fffff880`053ab000 USBSTOR USBSTOR.SYS Tue Jul 14 03:06:34 2009 (4A5BCC0A) fffff880`053ab000 fffff880`053c8000 usbccgp usbccgp.sys Tue Jul 14 03:06:45 2009 (4A5BCC15) fffff880`053c8000 fffff880`053d6000 hidusb hidusb.sys Tue Jul 14 03:06:22 2009 (4A5BCBFE) fffff880`053d6000 fffff880`053ef000 HIDCLASS HIDCLASS.SYS Tue Jul 14 03:06:21 2009 (4A5BCBFD) fffff880`053ef000 fffff880`053f7080 HIDPARSE HIDPARSE.SYS Tue Jul 14 03:06:17 2009 (4A5BCBF9) fffff880`0585e000 fffff880`05926000 HTTP HTTP.sys Tue Jul 14 02:22:16 2009 (4A5BC1A8) fffff880`05926000 fffff880`05944000 bowser bowser.sys Tue Jul 14 02:23:50 2009 (4A5BC206) fffff880`05944000 fffff880`0595c000 mpsdrv mpsdrv.sys Tue Jul 14 03:08:25 2009 (4A5BCC79) fffff880`0595c000 fffff880`05989000 mrxsmb mrxsmb.sys Sat Feb 27 09:52:19 2010 (4B88CF33) fffff880`05989000 fffff880`059d7000 mrxsmb10 mrxsmb10.sys Sat Feb 27 09:52:28 2010 (4B88CF3C) fffff880`059d7000 fffff880`059fa000 mrxsmb20 mrxsmb20.sys Sat Feb 27 09:52:26 2010 (4B88CF3A) fffff880`05c00000 fffff880`05c68000 srv2 srv2.sys Tue Jun 22 06:20:47 2010 (4C202C0F) fffff880`05c92000 fffff880`05d38000 peauth peauth.sys Tue Jul 14 04:01:19 2009 (4A5BD8DF) fffff880`05d38000 fffff880`05d43000 secdrv secdrv.SYS Wed Sep 13 16:18:38 2006 (4508052E) fffff880`05d43000 fffff880`05d70000 srvnet srvnet.sys Tue Jun 22 06:20:32 2010 (4C202C00) fffff880`05d70000 fffff880`05d82000 tcpipreg tcpipreg.sys Tue Jul 14 03:09:49 2009 (4A5BCCCD) fffff880`060a0000 fffff880`06136000 srv srv.sys Tue Jun 22 06:21:11 2010 (4C202C27) fffff880`06136000 fffff880`06140000 dgderdrv dgderdrv.sys Wed Jul 21 04:56:51 2010 (4C4653E3) fffff880`06140000 fffff880`06171000 WUDFRd WUDFRd.sys Tue Jul 14 03:06:06 2009 (4A5BCBEE) fffff880`06171000 fffff880`061a7000 fastfat fastfat.SYS Tue Jul 14 02:23:28 2009 (4A5BC1F0) fffff880`0fe00000 fffff880`0fe46000 dxgmms1 dxgmms1.sys Tue Jul 14 02:38:32 2009 (4A5BC578) fffff880`0fe46000 fffff880`0fe52000 serenum serenum.sys Tue Jul 14 03:00:33 2009 (4A5BCAA1) fffff880`0fe52000 fffff880`10ae3e00 nvlddmkm nvlddmkm.sys Sat Jul 10 00:15:58 2010 (4C37918E) fffff880`10ae4000 fffff880`10ae5180 nvBridge nvBridge.kmd Sat Jul 10 00:07:54 2010 (4C378FAA) fffff880`10ae6000 fffff880`10bda000 dxgkrnl dxgkrnl.sys Fri Oct 02 04:00:14 2009 (4AC5509E) fffff880`10bda000 fffff880`10be7000 usbuhci usbuhci.sys Tue Jul 14 03:06:27 2009 (4A5BCC03) fffff880`10be7000 fffff880`10bf8000 usbehci usbehci.sys Tue Jul 14 03:06:30 2009 (4A5BCC06) fffff880`10bf8000 fffff880`10c00000 ASACPI ASACPI.sys Thu May 14 04:25:17 2009 (4A0B72FD) fffff960`000a0000 fffff960`003af000 win32k win32k.sys Sat Jun 19 07:31:59 2010 (4C1C483F) fffff960`005a0000 fffff960`005aa000 TSDDD TSDDD.dll unavailable (00000000) fffff960`006f0000 fffff960`00717000 cdd cdd.dll Wed May 19 22:48:26 2010 (4BF4408A) fffff960`00810000 fffff960`00871000 ATMFD ATMFD.DLL Thu May 27 07:11:31 2010 (4BFDF0F3) Unloaded modules: fffff880`0194b000 fffff880`01959000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01959000 fffff880`01965000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01965000 fffff880`0196e000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0196e000 fffff880`01981000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Now that it started, it's been working since it crashed earlier.
I'll update the sound driver and run the HDDscan.
Will i need to post any report on the HDD scan?
Running the test now using
READ on my c:/ HDD.
I'll run memtest tonight through the night again, is there any specific test # that you want me to do?
I'm not sure if this information is useful:
I always get the BSOD when I do a first boot after having the computer unplugged from the power socket for several hours.
After I manage to boot back into windows, it seems to work fine and can run for the day.
I'll update the sound driver and run the HDDscan.
Will i need to post any report on the HDD scan?
Running the test now using
READ on my c:/ HDD.
I'll run memtest tonight through the night again, is there any specific test # that you want me to do?
I'm not sure if this information is useful:
I always get the BSOD when I do a first boot after having the computer unplugged from the power socket for several hours.
After I manage to boot back into windows, it seems to work fine and can run for the day.
Run SMART with HDD scan and when it's done see if it gives you any yellow/red warnings - save them.
So I select the drives and just click the S.M.A.R.T button right?
Sort of instant report generation.
I did this on all my internal and my 1 external HDD.
All green indicators. No yellow/red at all.
Sort of instant report generation.
I did this on all my internal and my 1 external HDD.
All green indicators. No yellow/red at all.
If you already did, skip it and proceed with the memtest.
Ok, I'll load memtest now and let it run. Thanks
Update: 2 passes no errors, I'd let it run for 12h at least today.
Btw, assuming memtest doesn't detect any errors, What course of action do we look to do next?
Update 1: Going for 5h + its 0 errors, Will let it continue.
Update: 2 passes no errors, I'd let it run for 12h at least today.
Btw, assuming memtest doesn't detect any errors, What course of action do we look to do next?
Update 1: Going for 5h + its 0 errors, Will let it continue.
Okay, I'm not sure if this is useful information.
But my RAM package says that the ram is supposed to be
4-4-4-12 , 2.2v
But memtest86 is showing 5-5-5-16
It is running at 400mhz (DDR800).
I stopped the memtest86 at 7 full passes to change the ram settings in BIOS.
I changed the ram to 4-4-4-12 and the voltage to 2.2, which is what the RAM is rated for.
I also increased the FSB termination voltage to 1.3, NB voltage to 1.3 as well. (These were in auto earlier, I read in the patriot forums that increasing these voltages with 4 DIMMS will help stabilise the system)
But now in memtest, it shows my FSB frequency to be 334mhz, it was 333mhz before.
I'll let memtest go thru the rest of the night or 12h. Should be done by lunch tomorrow.
But my RAM package says that the ram is supposed to be
4-4-4-12 , 2.2v
But memtest86 is showing 5-5-5-16
It is running at 400mhz (DDR800).
I stopped the memtest86 at 7 full passes to change the ram settings in BIOS.
I changed the ram to 4-4-4-12 and the voltage to 2.2, which is what the RAM is rated for.
I also increased the FSB termination voltage to 1.3, NB voltage to 1.3 as well. (These were in auto earlier, I read in the patriot forums that increasing these voltages with 4 DIMMS will help stabilise the system)
But now in memtest, it shows my FSB frequency to be 334mhz, it was 333mhz before.
I'll let memtest go thru the rest of the night or 12h. Should be done by lunch tomorrow.
Okay, BSOD again.
This time I was doing a search through a PDF file and I got BSOD.
Here is the dmp file and perfmon report.
The latest dmp file is dated 12 oct.
This time I was doing a search through a PDF file and I got BSOD.
Here is the dmp file and perfmon report.
The latest dmp file is dated 12 oct.
Well, I memtest while sleeping and came up with 6 errors.
I'll try replacing the ram later and run tests using the new ram chip.
1 error was in the 47mb area, the other 5 were in the 4000 mb area, same spot.
I'll try replacing the ram later and run tests using the new ram chip.
1 error was in the 47mb area, the other 5 were in the 4000 mb area, same spot.
You might want to test each RAM stick separately, one at a time to isolate the bad one. YOU should also test each RAM slot with a known good stick.
I'm actually thinking of changing it to a 2x2gb config from a 4x1gb that I am currently using now though.
I'll try and check the individual slots/chips to see which is the one giving me errors.
I'll try and check the individual slots/chips to see which is the one giving me errors.
Okay, I did extensive testing today.
Running 4 chips, I get tons of errors.
But running 1 chip at a time, I get 0 errors even with different slots.
What now?
How am I going to diagnose this problem?
Running 4 chips, I get tons of errors.
But running 1 chip at a time, I get 0 errors even with different slots.
What now?
How am I going to diagnose this problem? Sounds like I was right.
Same thing on my system with 4x2GB (two different kits of 2x2GB, each of which is fine on its own in either pair of coloured slots)
I haven't yet tried getting my system stable with 4 sticks, but what I'd try is the higher NB voltage with the 'stock' CL5 timings and default RAM voltage. (My logic says the looser timings should be easier on the NB)
Same thing on my system with 4x2GB (two different kits of 2x2GB, each of which is fine on its own in either pair of coloured slots)
I haven't yet tried getting my system stable with 4 sticks, but what I'd try is the higher NB voltage with the 'stock' CL5 timings and default RAM voltage. (My logic says the looser timings should be easier on the NB)
Hi Pirl,
Thanks for staying with me on this issue. And with the others as well.
I did try higher NB voltage -> it was @ 1.4v when the thing just died on me and memtest gave me tons of errors.
But after that, I was on looser CL5 timing, the stock is CL4, but I left the NB @ 1.4.
Then I did further tests using CL5 , nb @ 1.4v and did the single chip/single slot , double chip + double slot test. And went through them fine.
5-5-5-16, does this sound about right?
I had the DRAM volts at 2.2, which is what the ram is made for, should I decrease/increase this?
Now it's set to AUTO in bios.
I reverted all voltages back to AUTO and i managed to boot up into windows with 4 chips.
Thanks for staying with me on this issue. And with the others as well.
I did try higher NB voltage -> it was @ 1.4v when the thing just died on me and memtest gave me tons of errors.
But after that, I was on looser CL5 timing, the stock is CL4, but I left the NB @ 1.4.
Then I did further tests using CL5 , nb @ 1.4v and did the single chip/single slot , double chip + double slot test. And went through them fine.
5-5-5-16, does this sound about right?
I had the DRAM volts at 2.2, which is what the ram is made for, should I decrease/increase this?
Now it's set to AUTO in bios.
I reverted all voltages back to AUTO and i managed to boot up into windows with 4 chips.
5-5-5-18 1.8v is what mine is currently running at (set to auto with a kit rated at 4-4-4-12 2.1v)
However, I've only got two sticks at the moment (I need the stability for now, will tinker with four sticks in a couple of weeks - what I'm saying now is what I plan to try myself when I can)
Set the RAM to auto and bump the NB voltage +1.0, +1.5, +2.0 volts (as long as that's still under 1.6v)
If it's still crashing, 1.9v at CL5 with +1.0 NB, +1.5, +2.0.
If still then, do a bit more research.
I was able to boot and run windows for between 10 minutes and almost two days before it'd blue screen, so it's unfortunately not always quick to see if the changes make any real difference.
However, I've only got two sticks at the moment (I need the stability for now, will tinker with four sticks in a couple of weeks - what I'm saying now is what I plan to try myself when I can)
Set the RAM to auto and bump the NB voltage +1.0, +1.5, +2.0 volts (as long as that's still under 1.6v)
If it's still crashing, 1.9v at CL5 with +1.0 NB, +1.5, +2.0.
If still then, do a bit more research.
I was able to boot and run windows for between 10 minutes and almost two days before it'd blue screen, so it's unfortunately not always quick to see if the changes make any real difference.
You mean +0.1v NB right?
Because auto = 1.1v , if I add in +1 then it's above 1.6.
I'll try the suggestion out Pril, but for now I need to get some work done. :s
Because auto = 1.1v , if I add in +1 then it's above 1.6.
I'll try the suggestion out Pril, but for now I need to get some work done. :s
�� Quote: Originally Posted by lightice Okay, I did extensive testing today.
Running 4 chips, I get tons of errors.
But running 1 chip at a time, I get 0 errors even with different slots.
What now? How am I going to diagnose this problem?
Running 4 chips, I get tons of errors.
But running 1 chip at a time, I get 0 errors even with different slots.
What now?
How am I going to diagnose this problem? The funny thing is, that now when I run memtest with all chips, I don't get errors.
It's really weird, I really wonder what is going on.
And thanks Carl - I appreciate the help.
It's really weird, I really wonder what is going on.
And thanks Carl - I appreciate the help.
You are very welcome. Maybe the changes that you made solved the problem?
Nope, this happens intermittedly.
There is a chance it will occur again. It's like once the system starts running stable, it can go on for quite a while before anything happens.
But if I boot from cold/unplugged senario, it can freeze/bsod continuously.
There is a chance it will occur again. It's like once the system starts running stable, it can go on for quite a while before anything happens.
But if I boot from cold/unplugged senario, it can freeze/bsod continuously.
I see. We will wait for the hardware experts to come on line and take a look.
�� Quote: Originally Posted by lightice You mean +0.1v NB right?
Because auto = 1.1v , if I add in +1 then it's above 1.6.
I'll try the suggestion out Pril, but for now I need to get some work done. :s
Because auto = 1.1v , if I add in +1 then it's above 1.6.
I'll try the suggestion out Pril, but for now I need to get some work done. :s
I was thinking in +10 divisions (which I thought were 0.2v each rather than the 0.02v that they actually are.
�� Quote: Originally Posted by CarlTR6 I see. We will wait for the hardware experts to come on line and take a look.
�� Quote: Originally Posted by Pirl �� Quote: Originally Posted by lightice You mean +0.1v NB right?
Because auto = 1.1v , if I add in +1 then it's above 1.6.
I'll try the suggestion out Pril, but for now I need to get some work done. :s
Because auto = 1.1v , if I add in +1 then it's above 1.6.
I'll try the suggestion out Pril, but for now I need to get some work done. :s
I was thinking in +10 divisions (which I thought were 0.2v each rather than the 0.02v that they actually are.
�� Quote: Originally Posted by CarlTR6 I see. We will wait for the hardware experts to come on line and take a look.
Well, for a few days it was running fine, no crashes, no BSOD, startup went well no freezes, until I completed all my assignments. And today, when I switched it on, i got the same problem. Freeze (no BSOD) at windows.
Reboot, won't go to post.
After I switched everything off for a while, switched it back on, a message came out "Overclocking failed" Press F1 to enter Bios, F2 to reset to default.
The thing is, I never overclocked, Everything was set to auto. ??
Immediately I ran memtest and got a ton of errors -> 4 chips
Pulled out 2, running 2 chips on the yellow DIMMS and it's been 7h 39min, no errors.
DRAM timing is not the speced ones, it's now at 5-5-5-16 (auto)
Reboot, won't go to post.
After I switched everything off for a while, switched it back on, a message came out "Overclocking failed" Press F1 to enter Bios, F2 to reset to default.
The thing is, I never overclocked, Everything was set to auto. ??
Immediately I ran memtest and got a ton of errors -> 4 chips
Pulled out 2, running 2 chips on the yellow DIMMS and it's been 7h 39min, no errors.
DRAM timing is not the speced ones, it's now at 5-5-5-16 (auto)
Quote:
After I switched everything off for a while, switched it back on, a message came out "Overclocking failed" Press F1 to enter Bios, F2 to reset to default.
Quote:
Immediately I ran memtest and got a ton of errors -> 4 chips
Pulled out 2, running 2 chips on the yellow DIMMS and it's been 7h 39min, no errors.
DRAM timing is not the speced ones, it's now at 5-5-5-16 (auto)
Pulled out 2, running 2 chips on the yellow DIMMS and it's been 7h 39min, no errors.
DRAM timing is not the speced ones, it's now at 5-5-5-16 (auto)
Cybercore:
Actually I tested those 2 I pulled out a few days ago. I ran memtest extensively then and found no errors during the testing when running on 2 chips at 2 different slots. And various other combinations.
The motherboard can handle up to 16GB if I am not wrong. I'm only at 4GB.
It could be the RAM timing, but if that's the case it definiately points to a hardware fault because it's supposed to be running at 4-4-4-12 @ 2.2v.
Now it's auto @ 5-5-5-16 , not sure what voltage.
Actually I tested those 2 I pulled out a few days ago. I ran memtest extensively then and found no errors during the testing when running on 2 chips at 2 different slots. And various other combinations.
The motherboard can handle up to 16GB if I am not wrong. I'm only at 4GB.
It could be the RAM timing, but if that's the case it definiately points to a hardware fault because it's supposed to be running at 4-4-4-12 @ 2.2v.
Now it's auto @ 5-5-5-16 , not sure what voltage.
That's what I'm saying, you got 4 sticks - are you sure they are identical?
Yes, they are all patroit RAM, I purchased 2 identical kits at the same time.
When I was using the previous motherboard I never had such issues. (p5q pro before RMA first time)
Before the P5Q pro, it was in another motherboard, also no issues at all. Ran fine for more than a year without BSODs.
When I was using the previous motherboard I never had such issues. (p5q pro before RMA first time)
Before the P5Q pro, it was in another motherboard, also no issues at all. Ran fine for more than a year without BSODs.
Either sticks are bad, or they were somehow improperly installed that time it showed errors, or might be something with the motherboard - I'm viewing the first 7 pages, how about bios upgrade?
I had these problems using the latest bios, and I downgraded to 2nd latest one and still having the same issues.
I don't think they were improperly installed because it would run fine for a few days and these errors will then pop up.
The computer isn't moved and it's just located on a table top, so no one would kick it. Or even move it.
I'm stumped lol.
I don't think they were improperly installed because it would run fine for a few days and these errors will then pop up.
The computer isn't moved and it's just located on a table top, so no one would kick it. Or even move it.
I'm stumped lol.
Cybercore, I ran the computer for 14 days.
During these 14 days, if the computer was running fine for a few hours, it'd run well for a few days.
If I restarted it and it started BSOD/freezing, it'd continue freezing.
Yesterday I downgraded from the latest bios to one that was released sometime in dec 2008, I think it was 3rd or 4th latest version.
And I am running memtest, its been 17 hours now and no errors.
Previously, I think the 2 latest bios versions have problems.
Because even when I have not done anything to bios except move NB voltage to 1.2, it would give me an error at boot stating overclock failed.
And told me to press F1 to enter bios for setup, or F2 to set to default values.
Furthermore, once when I entered bios, I saw a smiley face, on AI.
Meaning the A became a smiley face. So I suspected that its probably a bios problem.
Now the memtest is still running, since I downgraded the bios, i will run it for 24h and report back.
During these 14 days, if the computer was running fine for a few hours, it'd run well for a few days.
If I restarted it and it started BSOD/freezing, it'd continue freezing.
Yesterday I downgraded from the latest bios to one that was released sometime in dec 2008, I think it was 3rd or 4th latest version.
And I am running memtest, its been 17 hours now and no errors.
Previously, I think the 2 latest bios versions have problems.
Because even when I have not done anything to bios except move NB voltage to 1.2, it would give me an error at boot stating overclock failed.
And told me to press F1 to enter bios for setup, or F2 to set to default values.
Furthermore, once when I entered bios, I saw a smiley face, on AI.
Meaning the A became a smiley face. So I suspected that its probably a bios problem.
Now the memtest is still running, since I downgraded the bios, i will run it for 24h and report back.
Memtest has been going on for longer than 24h and no errors. Could this really be a corrupted bios provided by ASUS?
I'll let it continue running over night and check again tomorrow morning. By that time it'd be close to 34h.
I'll let it continue running over night and check again tomorrow morning. By that time it'd be close to 34h.
36h passed on memtest, 40 full passes with 0 errors.
Well, the memtest doesn't say much, because win7 just froze again today.
And now I can't start the computer. It powers up, fan runs and nothing else. No post, no beep, no response on screen.
And now I can't start the computer. It powers up, fan runs and nothing else. No post, no beep, no response on screen.
Now I can't even run memtest without it crashing.
It has crashed 3 times
1) i got 'interrupt error' and the thing froze.
2) Instead of showing me what RAM i had installed, the lower portion of the screen turned into lines of smiley faces
3) The whole screen showed vertical coloured lines
It has crashed 3 times
1) i got 'interrupt error' and the thing froze.
2) Instead of showing me what RAM i had installed, the lower portion of the screen turned into lines of smiley faces
3) The whole screen showed vertical coloured lines
Không có nhận xét nào:
Đăng nhận xét