New
#11
Unfortunately, many times dumps do not point to a specific cause; so we have to use a process of eliminataion. That includes eliminating anything that is known to cause BSOD's.
Your latest dump is an error code A, IRQL_NOT_LESS_OR_EQUAL, usually caused by Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
The dump blames dxgmms1.sys which is a Direct X driver. While this is most likely not the real cause, it does give us a clue. It appears to be video card/driver problem.Code:Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x8283b000 PsLoadedModuleList = 0x82983810 Debug session time: Sat Aug 28 05:49:53.350 2010 (GMT-4) System Uptime: 0 days 1:52:58.129 Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {af672000, 0, 0, 828b2a3b} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+169 ) Followup: MachineOwner --------- 0: 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: af672000, memory referenced Arg2: 00000000, IRQL Arg3: 00000000, 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: 828b2a3b, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 829a3718 Unable to read MiSystemVaType memory at 82983160 af672000 CURRENT_IRQL: 0 FAULTING_IP: nt!MmProbeAndLockPages+4cc 828b2a3b 8a0f mov cl,byte ptr [edi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: 8a61b8d0 -- (.trap 0xffffffff8a61b8d0) ErrCode = 00000000 eax=00000000 ebx=007ffff8 ecx=8498a524 edx=00000000 esi=863fda48 edi=af672000 eip=828b2a3b esp=8a61b944 ebp=8a61b9ec iopl=0 nv up ei ng nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286 nt!MmProbeAndLockPages+0x4cc: 828b2a3b 8a0f mov cl,byte ptr [edi] ds:0023:af672000=?? Resetting default scope LAST_CONTROL_TRANSFER: from 828b2a3b to 8288182b STACK_TEXT: 8a61b8d0 828b2a3b badb0d00 00000000 00001000 nt!KiTrap0E+0x2cf 8a61b9ec 8e3a4daf 8498a500 00000000 00000002 nt!MmProbeAndLockPages+0x4cc 8a61ba40 8e3a5e13 882971d0 af670000 00008000 dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+0x169 8a61ba7c 8e3a798e 882971d0 86401000 882971d0 dxgmms1!VIDMM_SEGMENT::LockAllocationBackingStore+0x69 8a61ba94 8e396edb 882971d0 00000000 84b84ef8 dxgmms1!VIDMM_APERTURE_SEGMENT::CommitResource+0x17c 8a61bac0 8e3988b4 8507cc00 00000030 84b84df0 dxgmms1!VIDMM_GLOBAL::PageInAllocations+0x8f 8a61bbb8 8e3af93e ab27cb08 00000000 84b84ef8 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x95e 8a61bd18 8e3b022f 84b84720 868c35d0 8a61bd3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0 8a61bd28 8e3b04cc 84b84720 828773f1 863f2788 dxgmms1!VidSchiSubmitQueueCommand+0x61 8a61bd3c 8e3b0573 863f2788 00000000 863fda48 dxgmms1!VidSchiRun_PriorityTable+0x24 8a61bd50 82a496d3 863f2788 a92e1682 00000000 dxgmms1!VidSchiWorkerThread+0x7f 8a61bd90 828fb0f9 8e3b04f4 863f2788 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+169 8e3a4daf a138d0388e mov eax,dword ptr [dxgmms1!_imp__g_loggerInfo (8e38d038)] SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+169 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265 FAILURE_BUCKET_ID: 0xA_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+169 BUCKET_ID: 0xA_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+169 Followup: MachineOwner ---------
I also found two slightly out of date drivers on your system. I cannot say these are causing the problem; but Windows 7 does not like older drivers. I suggest that you try to update both of these through the Asus website. They are chipset drivers. If you need help, please ask.
L1E62x86.sys Thu Jun 11 02:39:12 2009 - Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20). Atheros, Wireless LAN, WLAN, 2.4/5-GHz, 802.11a/b/g, 802.11b/g, 802.11n, Radio-on-a-Chip, Overview, Networking, Products and Technology. Try to update this driver. I suggest you that you try to find an update through the Asus website.
viahduaa.sys Fri Mar 20 02:21:38 2009 - VIA High Definition Audio Driver, VIA Technologies, Inc. Try to update this one through the Asus website.
Your video drivers appear to be up to date. Open Device Manager and click on the little triangle to the left of Display adapters. Your display adapter should appear. Does it show a yellow error symbol? Right click on it and click on Properties. Does it say "This device is working properly? Click on the Driver tab. What is the date for your driver?
Go through this same procedure for your network adapters and post back with your results.
The display adapter ? Intel that one? I was wrongly click quit last time before i shut down the computer and it wasn't appear anymore when i turn on my computer. the Atheros driver, which shall I update? The driver problem which you specific to?
@Graphic device
It say the device working properly. Driver date is 4/21/2010
@The window update
Last few days my connection was broken >< then finally today I get my connection back =) SO I USE THE WINDOW UPDATE TO UPDATE THOSE DRIVER, WHICH IS IN THE LIST. but it seems like not working well...
Atheros - Network - Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller
Installation date: 8/30/2010 12:47 PM
Installation status: Successful
Update type: Optional
Atheros Network software update released in August, 2009
More information:
Winqual Help
Help and Support:
Select a Product Solution Center
------------------------------------------------------
Intel Corporation - Display - Mobile Intel(R) 4 Series Express Chipset Family
Installation date: 8/30/2010 12:48 PM
Installation status: Successful
Update type: Optional
Intel Corporation Display software update released in April, 2010
More information:
Winqual Help
Help and Support:
Select a Product Solution Center
---------------------------------------------------
ATK - Input - ATK0100 ACPI UTILITY
Installation date: 8/30/2010 12:48 PM
Installation status: Successful
Update type: Recommended
ATK Input software update released in December, 2006
More information:
Winqual Help
Help and Support:
Select a Product Solution Center
------------------------------------------------------
It is still continue BSOD after I updated =/
Last edited by Esther; 30 Aug 2010 at 08:59. Reason: Additional information
Your graphic drivers look good and are up to date. The error code of this latest dump is 8E, KERNEL_MODE_EXCEPTION_NOT_HANDLED. The usual causes are insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.
This is a hardware or hardware related error. Most commonly it is caused by a device driver. The dump file does not point to a specific cause; that means we have to troubleshoot by trial and error.Code:Kernel base = 0x8280c000 PsLoadedModuleList = 0x82954810 Debug session time: Mon Aug 30 09:40:10.435 2010 (GMT-4) System Uptime: 0 days 2:20:18.339 Loading Kernel Symbols ............................................................... ................................................................ .................. Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c000001d, 82851347, 84e47cc0, 0} Probably caused by : ntkrpamp.exe ( nt!KiTrap07+cf ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c000001d, The exception code that was not handled Arg2: 82851347, The address that the exception occurred at Arg3: 84e47cc0, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: nt!KiTrap07+cf 82851347 0fae29 xrstor [ecx] TRAP_FRAME: 84e47cc0 -- (.trap 0xffffffff84e47cc0) ErrCode = 00000000 eax=00000007 ebx=80010031 ecx=84e47dc0 edx=00000000 esi=029be000 edi=84bc9030 eip=82851347 esp=84e47d34 ebp=84e47d34 iopl=0 nv up di pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010006 nt!KiTrap07+0xcf: 82851347 0fae29 xrstor [ecx] Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 67eeedbd to 82851347 FAILED_INSTRUCTION_ADDRESS: nt!KiTrap07+cf 82851347 0fae29 xrstor [ecx] STACK_TEXT: 84e47d34 67eeedbd badb0d00 773464f4 00000000 nt!KiTrap07+0xcf WARNING: Frame IP not in any known module. Following frames may be wrong. 054bf8b4 00000000 00000000 00000000 00000000 0x67eeedbd STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap07+cf 82851347 0fae29 xrstor [ecx] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap07+cf FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac FAILURE_BUCKET_ID: 0x8E_BAD_IP_nt!KiTrap07+cf BUCKET_ID: 0x8E_BAD_IP_nt!KiTrap07+cf Followup: MachineOwner --------- 1: kd> lmtsmn start end module name 8848c000 884d4000 ACPI ACPI.sys Mon Jul 13 19:11:11 2009 (4A5BBF0F) 8d684000 8d6de000 afd afd.sys Mon Jul 13 19:12:34 2009 (4A5BBF62) 82e00000 82e12000 AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954) 885f0000 885f9000 amdxata amdxata.sys Tue May 19 13:57:35 2009 (4A12F30F) 93522000 9352b000 asyncmac asyncmac.sys Mon Jul 13 19:54:46 2009 (4A5BC946) 885c4000 885cd000 atapi atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 885cd000 885f0000 ataport ataport.SYS Mon Jul 13 19:11:18 2009 (4A5BBF16) 8d8a5000 8d9d2000 athr athr.sys Mon Oct 05 12:31:48 2009 (4ACA1F74) 8d800000 8d808000 ATKACPI ATKACPI.sys Thu Dec 14 02:11:57 2006 (4580F93D) 88533000 8853e000 BATTC BATTC.SYS Mon Jul 13 19:19:15 2009 (4A5BC0F3) 889e3000 889ea000 Beep Beep.SYS Mon Jul 13 19:45:00 2009 (4A5BC6FC) 8d7f1000 8d7ff000 blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8) 82e9e000 82ea6000 BOOTVID BOOTVID.dll Mon Jul 13 21:04:34 2009 (4A5BD9A2) 912b2000 912cb000 bowser bowser.sys Mon Jul 13 19:14:21 2009 (4A5BBFCD) 94600000 9461e000 cdd cdd.dll Mon Jul 13 21:04:18 2009 (4A5BD992) 88800000 8881f000 cdrom cdrom.sys Mon Jul 13 19:11:24 2009 (4A5BBF1C) 82ee8000 82f93000 CI CI.dll Mon Jul 13 21:09:28 2009 (4A5BDAC8) 88999000 889be000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18) 82ea6000 82ee8000 CLFS CLFS.SYS Mon Jul 13 19:11:10 2009 (4A5BBF0E) 8d9fa000 8d9fd700 CmBatt CmBatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6) 887a3000 88800000 cng cng.sys Mon Jul 13 19:32:55 2009 (4A5BC427) 8852b000 88533000 compbatt compbatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6) 88624000 88631000 CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716) 9378a000 93797000 crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E) 8d7d9000 8d7f1000 dfsc dfsc.sys Mon Jul 13 19:14:16 2009 (4A5BBFC8) 8d7cd000 8d7d9000 discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214) 88a00000 88a11000 disk disk.sys Mon Jul 13 19:11:28 2009 (4A5BBF20) 93767000 93780000 drmk drmk.sys Mon Jul 13 20:36:05 2009 (4A5BD2F5) 937a2000 937ab000 dump_atapi dump_atapi.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 93797000 937a2000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 937ab000 937bc000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F) 93780000 9378a000 Dxapi Dxapi.sys Mon Jul 13 19:25:25 2009 (4A5BC265) 8e4e9000 8e5a0000 dxgkrnl dxgkrnl.sys Thu Oct 01 20:48:33 2009 (4AC54DE1) 8e5a0000 8e5d9000 dxgmms1 dxgmms1.sys Mon Jul 13 19:25:25 2009 (4A5BC265) 9352b000 9359ab80 EagleNT EagleNT.sys Thu Mar 25 07:46:03 2010 (4BAB4CFB) 82fc7000 82fd8000 fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) 82f93000 82fc7000 fltmgr fltmgr.sys Mon Jul 13 19:11:13 2009 (4A5BBF11) 8860e000 88617000 Fs_Rec Fs_Rec.sys unavailable (00000000) 88967000 88999000 fvevol fvevol.sys Fri Sep 25 22:24:21 2009 (4ABD7B55) 88b6e000 88b9f000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43) 82c1c000 82c53000 hal halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07) 8d886000 8d8a5000 HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F) 937d2000 937e5000 HIDCLASS HIDCLASS.SYS Mon Jul 13 19:51:01 2009 (4A5BC865) 937e5000 937eb480 HIDPARSE HIDPARSE.SYS Mon Jul 13 19:50:59 2009 (4A5BC863) 937c7000 937d2000 hidusb hidusb.sys Mon Jul 13 19:51:04 2009 (4A5BC868) 9122d000 912b2000 HTTP HTTP.sys Mon Jul 13 19:12:53 2009 (4A5BBF75) 88bf6000 88bfe000 hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05) 8d9e2000 8d9fa000 i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B) 8dc0f000 8e4e9000 igdkmd32 igdkmd32.sys Wed Apr 21 14:09:56 2010 (4BCF3F74) 8d829000 8d83b000 intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07) 8dc00000 8dc0d000 kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 80ba2000 80baa000 kdcom kdcom.dll Mon Jul 13 21:08:58 2009 (4A5BDAAA) 928a6000 928da000 ks ks.sys Mon Jul 13 19:45:13 2009 (4A5BC709) 88790000 887a3000 ksecdd ksecdd.sys Mon Jul 13 19:11:56 2009 (4A5BBF3C) 88915000 8893a000 ksecpkg ksecpkg.sys Thu Dec 10 23:04:22 2009 (4B21C4C6) 8d9d2000 8d9e2000 L1E62x86 L1E62x86.sys Sun Aug 23 01:06:36 2009 (4A90CE5C) 92972000 92982000 lltdio lltdio.sys Mon Jul 13 19:53:18 2009 (4A5BC8EE) 9293d000 92958000 luafv luafv.sys Mon Jul 13 19:15:44 2009 (4A5BC020) 82e15000 82e8d000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21) 9359b000 935bb000 Mkd2kfNt Mkd2kfNt.sys Fri Oct 17 04:50:22 2008 (48F851CE) 937bc000 937c7000 monitor monitor.sys Mon Jul 13 19:25:58 2009 (4A5BC286) 88617000 88624000 mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13) 937ee000 937f9000 mouhid mouhid.sys Mon Jul 13 19:45:08 2009 (4A5BC704) 885ae000 885c4000 mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F) 82fd8000 82ffb000 MpFilter MpFilter.sys Sat Mar 20 00:03:26 2010 (4BA4490E) 934af000 934b7e00 MpNWMon MpNWMon.sys Sat Mar 20 00:03:24 2010 (4BA4490C) 912cb000 912dd000 mpsdrv mpsdrv.sys Mon Jul 13 19:52:52 2009 (4A5BC8D4) 912dd000 91300000 mrxsmb mrxsmb.sys Sat Feb 27 02:32:02 2010 (4B88CA72) 91300000 9133b000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85) 9133b000 91356000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B) 8d649000 8d654000 Msfs Msfs.SYS Mon Jul 13 19:11:26 2009 (4A5BBF1E) 884dd000 884e5000 msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D) 88765000 88790000 msrpc msrpc.sys unavailable (00000000) 8d7c3000 8d7cd000 mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) 88be6000 88bf6000 mup mup.sys Mon Jul 13 19:14:14 2009 (4A5BBFC6) 88820000 888d7000 ndis ndis.sys Mon Jul 13 19:12:24 2009 (4A5BBF58) 92831000 9283c000 ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930) 929c8000 929d8000 ndisuio ndisuio.sys Mon Jul 13 19:53:51 2009 (4A5BC90F) 9283c000 9285e000 ndiswan ndiswan.sys Mon Jul 13 19:54:34 2009 (4A5BC93A) 9292c000 9293d000 NDProxy NDProxy.SYS Mon Jul 13 19:54:27 2009 (4A5BC933) 8d747000 8d755000 netbios netbios.sys Mon Jul 13 19:53:54 2009 (4A5BC912) 8d6de000 8d710000 netbt netbt.sys Mon Jul 13 19:12:18 2009 (4A5BBF52) 888d7000 88915000 NETIO NETIO.SYS Mon Jul 13 19:12:35 2009 (4A5BBF63) 8d654000 8d662000 Npfs Npfs.SYS Mon Jul 13 19:11:31 2009 (4A5BBF23) 8d7b9000 8d7c3000 nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48) 8280c000 82c1c000 nt ntkrpamp.exe Fri Jun 18 23:55:24 2010 (4C1C3FAC) 88636000 88765000 Ntfs Ntfs.sys Mon Jul 13 19:12:05 2009 (4A5BBF45) 88a1e000 88a25000 Null Null.SYS unavailable (00000000) 92982000 929c8000 nwifi nwifi.sys Mon Jul 13 19:51:59 2009 (4A5BC89F) 8d717000 8d736000 pacer pacer.sys Mon Jul 13 19:53:58 2009 (4A5BC916) 8851a000 8852b000 partmgr partmgr.sys Mon Jul 13 19:11:35 2009 (4A5BBF27) 884e5000 8850f000 pci pci.sys Mon Jul 13 19:11:16 2009 (4A5BBF14) 88599000 885a0000 pciide pciide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17) 885a0000 885ae000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:11:15 2009 (4A5BBF13) 88600000 8860e000 pcw pcw.sys Mon Jul 13 19:11:10 2009 (4A5BBF0E) 91356000 913ed000 peauth peauth.sys Mon Jul 13 20:35:44 2009 (4A5BD2E0) 93738000 93767000 portcls portcls.sys Mon Jul 13 19:51:00 2009 (4A5BC864) 82e8d000 82e9e000 PSHED PSHED.dll Mon Jul 13 21:09:36 2009 (4A5BDAD0) 92819000 92831000 rasl2tp rasl2tp.sys Mon Jul 13 19:54:33 2009 (4A5BC939) 9285e000 92876000 raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D) 92876000 9288d000 raspptp raspptp.sys Mon Jul 13 19:54:47 2009 (4A5BC947) 9288d000 928a4000 rassstp rassstp.sys Mon Jul 13 19:54:57 2009 (4A5BC951) 8d778000 8d7b9000 rdbss rdbss.sys Mon Jul 13 19:14:26 2009 (4A5BBFD2) 8d631000 8d639000 RDPCDD RDPCDD.sys Mon Jul 13 20:01:40 2009 (4A5BCAE4) 8d639000 8d641000 rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3) 8d641000 8d649000 rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5) 8893a000 88967000 rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A) 929d8000 929eb000 rspndr rspndr.sys Mon Jul 13 19:53:20 2009 (4A5BC8F0) 913ed000 913f7000 secdrv secdrv.SYS Wed Sep 13 09:18:32 2006 (45080528) 88bde000 88be6000 spldr spldr.sys Mon May 11 12:13:47 2009 (4A084EBB) 9345e000 934af000 srv srv.sys Mon Jun 21 22:47:32 2010 (4C202444) 9340f000 9345e000 srv2 srv2.sys Mon Jun 21 22:47:19 2010 (4C202437) 91200000 91221000 srvnet srvnet.sys Mon Jun 21 22:47:09 2010 (4C20242D) 928a4000 928a5380 swenum swenum.sys Mon Jul 13 19:45:08 2009 (4A5BC704) 88a25000 88b6e000 tcpip tcpip.sys Sun Jun 13 23:36:59 2010 (4C15A3DB) 929eb000 929f8000 tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926) 8d679000 8d684000 TDI TDI.SYS Mon Jul 13 19:12:12 2009 (4A5BBF4C) 8d662000 8d679000 tdx tdx.sys Mon Jul 13 19:12:10 2009 (4A5BBF4A) 8d768000 8d778000 termdd termdd.sys Mon Jul 13 20:01:35 2009 (4A5BCADF) 949d0000 949d9000 TSDDD TSDDD.dll unavailable (00000000) 8d808000 8d829000 tunnel tunnel.sys Mon Jul 13 19:54:03 2009 (4A5BC91B) 928da000 928e8000 umbus umbus.sys Mon Jul 13 19:51:38 2009 (4A5BC88A) 93600000 93617000 usbccgp usbccgp.sys Mon Jul 13 19:51:31 2009 (4A5BC883) 937ec000 937ed700 USBD USBD.SYS Mon Jul 13 19:51:05 2009 (4A5BC869) 8e5e4000 8e5f3000 usbehci usbehci.sys Mon Jul 13 19:51:14 2009 (4A5BC872) 928e8000 9292c000 usbhub usbhub.sys Mon Jul 13 19:52:06 2009 (4A5BC8A6) 8d83b000 8d886000 USBPORT USBPORT.SYS Mon Jul 13 19:51:13 2009 (4A5BC871) 8e5d9000 8e5e4000 usbuhci usbuhci.sys Mon Jul 13 19:51:10 2009 (4A5BC86E) 93617000 9363ab00 usbvideo usbvideo.sys Mon Jul 13 19:51:51 2009 (4A5BC897) 8850f000 8851a000 vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B) 889ea000 889f6000 vga vga.sys Mon Jul 13 19:25:50 2009 (4A5BC27E) 9363f000 93738000 viahduaa viahduaa.sys Fri Mar 20 02:21:38 2009 (49C335F2) 8d603000 8d624000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D) 8853e000 8854e000 volmgr volmgr.sys Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8854e000 88599000 volmgrx volmgrx.sys unavailable (00000000) 88b9f000 88bde000 volsnap volsnap.sys Mon Jul 13 19:11:34 2009 (4A5BBF26) 8e5f3000 8e5fd000 vwifibus vwifibus.sys Mon Jul 13 19:52:02 2009 (4A5BC8A2) 8d736000 8d747000 vwififlt vwififlt.sys Mon Jul 13 19:52:03 2009 (4A5BC8A3) 8d755000 8d768000 wanarp wanarp.sys Mon Jul 13 19:55:02 2009 (4A5BC956) 8d624000 8d631000 watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A) 8840d000 8847e000 Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28) 8847e000 8848c000 WDFLDR WDFLDR.SYS Mon Jul 13 19:11:25 2009 (4A5BBF1D) 8d710000 8d717000 wfplwf wfplwf.sys Mon Jul 13 19:53:51 2009 (4A5BC90F) 94770000 949ba000 win32k win32k.sys Sat Jun 19 00:06:50 2010 (4C1C425A) 884d4000 884dd000 WMILIB WMILIB.SYS Mon Jul 13 19:11:22 2009 (4A5BBF1A) 92958000 92972000 WudfPf WudfPf.sys Mon Jul 13 19:50:13 2009 (4A5BC835) Unloaded modules: 934b8000 93522000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 91356000 9136e000 parport.sys Timestamp: unavailable (00000000) Checksum: 00000000 88a11000 88a1e000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 889be000 889c9000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 889c9000 889d2000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 889d2000 889e3000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000
I find two older drivers on your system that you need to try to update.
Mkd2kfNt.sys Fri Oct 17 04:50:22 2008 - MyKeyDefense Keyboard Filter Driver is a driver file from company AhnLab, Inc. belonging to product MyKeyDefense. This program is obsolete and is not going to run properly with Win 7. Windows XP, 2000, 98 are the operating systems this program is designed for. Uninstall it completely. It is not going to work with Win 7. Uninstall it through your Control Panel > Programs and Features.
viahduaa.sys Fri Mar 20 02:21:38 2009 - Lets ignore this one for the moment and take care of of MyKeyDefense.
When you have uninstalled MyKeyDefense, reboot and run you system. Let's see if you have another BSOD. If you, upload it and we will go from there.
Our next step in troubleshooting will be to enable Driver Verifier, if we need to. Keep in mind that troubleshooting is often a process of elimination.
This is just a note to help you with Windows 7. Windows 7 is a totally different operating system than XP. It is not an evolution of XP; but rather it is a totally new OS. Many programs written for XP simply will not run in Windows 7. The tricks we learned about XP do not apply to nor will they work with Windows 7. Win 7 is much advanced, more stable, and much safer than XP. However, Win 7 requires hardware and software that are designed to run with Win 7. Be very careful of advice about Win 7 from people who have little or no experience with it.
Be patient; I think we can get your system running smoothly. Post back after you have uninstalled MyKeyDefense. :)
I done remove the MyKeyDefense. It seems stable already, but yesterday when I start my computer, it tell me my computer was unable to start and it doing the system restore automatically. When finish the system restore, I realise my folder and data, which locate at Local Disk D was gone. Before i do the system restore,the dialog box tell me that it wont delete my personal data what.
I feel fairly sure that MyKeyDefese was causing most of your problems. I am glad to hear that your system is more stable now.
I do not know why your computer did not start. What other changes, if any, have you made? System restore is not supposed to touch user data; it is only supposed to to restore systems files and the registry. If you enabled Driver Verifier, turn it off. Can you still see your drive D: in Windows Explorer? If so, do you see any folders with the extension ".old" listed?
I understand. You really had no choice but to shut it down and restart. Unless the Asus recovery was used to restore your system rather than a Windows restore point, your data should be untouched. If the Ausus recovery was used, your system may be stored to the factory default.
since that day, whatever program i use, view photo, listening music, when i open the stuff it only will lag in maintain and then whole screen freeze..