Hi. I built a new PC just under a year ago from individual parts that I bought (mostly new). It has been running fine with the very occasional lock-up and restart in games such as WoW and LOTRO. However, these random lock-ups have started to become more and more frequent over the last month and I have started to get random BSODs.
I recently did a format of my hard drives and re-installed Win 7, Office, GPU and sound card drivers, and LOTRO. I've still been getting the random lock-ups and random BSODs.
They generally only occur in a game, but I've had the odd one when just web surfing. Generally, the game will suddenly freeze and my monitor will display what looks like a scrambled image of random pixels and colours, and the sound stutters. This is sometimes then followed by a BSOD. Generally, when I restart Windows will boot as normal, although sometimes I get a BSOD or an error in the bios saying "overclocking has failed". I'm not actually overlocking anything, I've left everything as factory clocked. The only thing I changed in the bios to try and help the problem was to put the memory into ganged mode which hasn't helped.
I've followed the BSOD instructions and attached the zip file. Some more info:
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? win7 x64
- an OEM or full retail version? OEM (bought with the components that I then built myself) -
- What is the age of system (hardware)? just under 1 year (I built it last December)
- What is the age of OS installation (have you re-installed the OS?) Yes, re-installed about 3 days ago
Thanks very much in advance for any help you can give ! I've tried to diagnose the cause myself over the last week or so, taking the GPU out and the sound card out etc, but I've still not managed to find any root cause. I'm thinking it may be a RAM problem, but I've run memtest (not for very long though, just one pass) and the Win7 boot memory test and they displayed no errors.
I recently did a format of my hard drives and re-installed Win 7, Office, GPU and sound card drivers, and LOTRO. I've still been getting the random lock-ups and random BSODs.
They generally only occur in a game, but I've had the odd one when just web surfing. Generally, the game will suddenly freeze and my monitor will display what looks like a scrambled image of random pixels and colours, and the sound stutters. This is sometimes then followed by a BSOD. Generally, when I restart Windows will boot as normal, although sometimes I get a BSOD or an error in the bios saying "overclocking has failed". I'm not actually overlocking anything, I've left everything as factory clocked. The only thing I changed in the bios to try and help the problem was to put the memory into ganged mode which hasn't helped.
I've followed the BSOD instructions and attached the zip file. Some more info:
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? win7 x64
- an OEM or full retail version? OEM (bought with the components that I then built myself) -
- What is the age of system (hardware)? just under 1 year (I built it last December)
- What is the age of OS installation (have you re-installed the OS?) Yes, re-installed about 3 days ago
Thanks very much in advance for any help you can give ! I've tried to diagnose the cause myself over the last week or so, taking the GPU out and the sound card out etc, but I've still not managed to find any root cause. I'm thinking it may be a RAM problem, but I've run memtest (not for very long though, just one pass) and the Win7 boot memory test and they displayed no errors.
Welcome to the forum. I am sorry you are having problems.
Stop error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes - Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
The dump does not tell us very much and blames hardware as the cause.
Looking at your drivers, I found one that is almost guaranteed to cause crashes:
ASACPI.sys Sun Mar 27 22:30:36 2005
Out of date drivers can and do cause instability, memory corruption and crashes. I see the following out of date drivers on your system. Update these drivers.
After you update these drivers, especially ASACPI.sys, reboot and run your system. Let's see how it does. If you get another BSOD, upload the dump. If your system is running smoothly after a few days, update us and let us know.
Stop error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes - Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Code:
Kernel base = 0xfffff800`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50 Debug session time: Sun Oct 3 17:58:47.455 2010 (GMT-4) System Uptime: 0 days 1:50:50.218 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffffffffffff85, 1, fffff80002b7a890, 0} Could not read faulting driver name Probably caused by : hardware ( nt!AlpcpExposeAttributes+140 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffffffffffff85, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff80002b7a890, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab30e0 ffffffffffffff85 FAULTING_IP: nt!AlpcpExposeAttributes+140 fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800747f870 -- (.trap 0xfffff8800747f870) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80054afa60 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002b7a890 rsp=fffff8800747fa00 rbp=fffffa80054afa60 r8=0000000000000020 r9=00000000032aff00 r10=0000000000000000 r11=00000000032afd68 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!AlpcpExposeAttributes+0x140: fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl ds:fd40:ffffffff`ffffff85=?? Resetting default scope MISALIGNED_IP: nt!AlpcpExposeAttributes+140 fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl LAST_CONTROL_TRANSFER: from fffff800028fbf14 to fffff8000287b740 STACK_TEXT: fffff880`0747f708 fffff800`028fbf14 : 00000000`00000050 ffffffff`ffffff85 00000000`00000001 fffff880`0747f870 : nt!KeBugCheckEx fffff880`0747f710 fffff800`0287982e : 00000000`00000001 fffff8a0`0b3d0d00 00000001`00000000 fffff880`009e8180 : nt! ?? ::FNODOBFM::`string'+0x42837 fffff880`0747f870 fffff800`02b7a890 : 00000000`032afd00 fffffa80`00000010 fffffa80`0478ab01 00000000`032afd00 : nt!KiPageFault+0x16e fffff880`0747fa00 fffff800`02b7bbe2 : 00000000`00000000 00000000`0001bf01 00000000`032afd40 00000000`00000001 : nt!AlpcpExposeAttributes+0x140 fffff880`0747fa60 fffff800`02b7d006 : fffffa80`054afa60 00000000`00010000 00000000`00010000 fffffa80`054afa60 : nt!AlpcpReceiveMessage+0x3ef fffff880`0747fb00 fffff800`0287a993 : fffffa80`05c96b60 fffff880`0747fca0 00000000`032afc98 00000000`032afd88 : nt!NtAlpcSendWaitReceivePort+0x1e6 fffff880`0747fbb0 00000000`772205aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`032afc78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772205aa STACK_COMMAND: kb FOLLOWUP_IP: nt!AlpcpExposeAttributes+140 fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!AlpcpExposeAttributes+140 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner --------- 2: kd> lmtsmn start end module name fffff880`03e00000 fffff880`03e3e000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00f31000 fffff880`00f88000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02a00000 fffff880`02a8a000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04610000 fffff880`04626000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`03d8e000 fffff880`03da3000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00d90000 fffff880`00d9b000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`03fee000 fffff880`03ff6000 ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C) fffff880`06ddc000 fffff880`06de7000 asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5) fffff880`00cda000 fffff880`00ce3000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00d66000 fffff880`00d90000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`04641000 fffff880`04dfc000 atikmdag atikmdag.sys Wed Aug 25 21:47:22 2010 (4C75C7AA) fffff880`03da3000 fffff880`03ded000 atikmpag atikmpag.sys Wed Aug 25 21:20:56 2010 (4C75C178) fffff880`015eb000 fffff880`015f3000 AtiPcie AtiPcie.sys Tue May 05 11:00:22 2009 (4A005486) fffff880`02afd000 fffff880`02b04000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03d57000 fffff880`03d68000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`053a2000 fffff880`053c0000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`007c0000 fffff960`007e7000 cdd cdd.dll Wed May 19 15:48:26 2010 (4BF4408A) fffff880`02aca000 fffff880`02af4000 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`01000000 fffff880`01030000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d08000 fffff880`00d66000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01368000 fffff880`013db000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`04600000 fffff880`04610000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`05fd9000 fffff880`05fe7000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03d39000 fffff880`03d57000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03d2a000 fffff880`03d39000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`012c0000 fffff880`012d6000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`05f12000 fffff880`05f34000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`05ff3000 fffff880`05ffc000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05fe7000 fffff880`05ff3000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`05e00000 fffff880`05e13000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`0427c000 fffff880`04288000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`03e4d000 fffff880`03f41000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`03f41000 fffff880`03f87000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`00de7000 fffff880`00dfb000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`00d9b000 fffff880`00de7000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`013ec000 fffff880`013f6000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`01286000 fffff880`012c0000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`0142b000 fffff880`01475000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02de7000 fffff800`02e30000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`03f87000 fffff880`03fab000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`05e79000 fffff880`05ed5000 HdAudio HdAudio.sys Mon Jul 13 20:06:59 2009 (4A5BCC23) fffff880`05e40000 fffff880`05e59000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`05e59000 fffff880`05e61080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`05e32000 fffff880`05e40000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`052da000 fffff880`053a2000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`0148f000 fffff880`01498000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`04349000 fffff880`04358000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`05e62000 fffff880`05e70000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bcb000 fffff800`00bd5000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`04369000 fffff880`043ac000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9) fffff880`0134e000 fffff880`01368000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01400000 fffff880`0142b000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`05f34000 fffff880`05f39200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`043be000 fffff880`043d3000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04296000 fffff880`042b9000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00ce7000 fffff880`00cf4000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`04288000 fffff880`04296000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`04358000 fffff880`04367000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`0426f000 fffff880`0427c000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00cc0000 fffff880`00cda000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`053c0000 fffff880`053d8000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`05200000 fffff880`0522d000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`0522d000 fffff880`0527b000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`0527b000 fffff880`0529e000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`02b62000 fffff880`02b6d000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00f91000 fffff880`00f9b000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`012f0000 fffff880`0134e000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03d1f000 fffff880`03d2a000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`0147d000 fffff880`0148f000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01499000 fffff880`0158b000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`04626000 fffff880`04632000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`042c4000 fffff880`042f3000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0425a000 fffff880`0426f000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`02ab0000 fffff880`02abf000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02ba9000 fffff880`02bee000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`0158b000 fffff880`015eb000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02b6d000 fffff880`02b7e000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03d13000 fffff880`03d1f000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`0280b000 fffff800`02de7000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`0104e000 fffff880`011f1000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02af4000 fffff880`02afd000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`02a8a000 fffff880`02ab0000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00fdb000 fffff880`00ff0000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00f9b000 fffff880`00fce000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00e71000 fffff880`00e78000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00ff0000 fffff880`01000000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013db000 fffff880`013ec000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`06ad1000 fffff880`06b77000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`05ed5000 fffff880`05f12000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00cf4000 fffff880`00d08000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`03c56000 fffff880`03c7a000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`042f3000 fffff880`0430e000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`0430e000 fffff880`0432f000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`0432f000 fffff880`04349000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03cc2000 fffff880`03d13000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`02b47000 fffff880`02b50000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b50000 fffff880`02b59000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b59000 fffff880`02b62000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`0124c000 fffff880`01286000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`043d3000 fffff880`043eb000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`03fab000 fffff880`03fdd000 Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D) fffff880`06b77000 fffff880`06b82000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`01475000 fffff880`0147d000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`06cd5000 fffff880`06d6b000 srv srv.sys Mon Jun 21 23:21:11 2010 (4C202C27) fffff880`06a00000 fffff880`06a68000 srv2 srv2.sys Mon Jun 21 23:20:47 2010 (4C202C0F) fffff880`06b82000 fffff880`06baf000 srvnet srvnet.sys Mon Jun 21 23:20:32 2010 (4C202C00) fffff880`04367000 fffff880`04368480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`05f3a000 fffff880`05fd9000 t3 t3.sys Wed Jun 03 15:13:51 2009 (4A26CB6F) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`06baf000 fffff880`06bc1000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`02b9c000 fffff880`02ba9000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02b7e000 fffff880`02b9c000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03cae000 fffff880`03cc2000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`005f0000 fffff960`005fa000 TSDDD TSDDD.dll unavailable (00000000) fffff880`03d68000 fffff880`03d8e000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`043ac000 fffff880`043be000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`05e13000 fffff880`05e30000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15) fffff880`05e30000 fffff880`05e31f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`03fdd000 fffff880`03fee000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04200000 fffff880`0425a000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`03e3e000 fffff880`03e49000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`03c00000 fffff880`03c56000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00fce000 fffff880`00fdb000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02b04000 fffff880`02b12000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02b12000 fffff880`02b37000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00e00000 fffff880`00e15000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e15000 fffff880`00e71000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01200000 fffff880`0124c000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`03c93000 fffff880`03cae000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02b37000 fffff880`02b47000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00e7e000 fffff880`00f22000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f22000 fffff880`00f31000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02bee000 fffff880`02bf7000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00070000 fffff960`0037f000 win32k win32k.sys Sat Jun 19 00:31:59 2010 (4C1C483F) fffff880`03ff6000 fffff880`03fff000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00f88000 fffff880`00f91000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) Unloaded modules: fffff880`06d6b000 fffff880`06ddc000 spsys.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`012d6000 fffff880`012e4000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`015f3000 fffff880`015ff000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`012e4000 fffff880`012ed000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01030000 fffff880`01043000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Looking at your drivers, I found one that is almost guaranteed to cause crashes:
ASACPI.sys Sun Mar 27 22:30:36 2005
Quote:
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).
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).
Quote:
AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipset, Global Provider of Innovative Graphics, Processors and Media Solutions | AMD
Rt64win7.sys Thu Feb 26 04:04:13 2009 - Latest PCIe GBE (GigaBit Ethernet) drivers here: Realtek
Rt64win7.sys Thu Feb 26 04:04:13 2009 - Latest PCIe GBE (GigaBit Ethernet) drivers here: Realtek
Ok thanks, I will update those drivers as you suggest and then re-test my machine.
Thanks you for your prompt help.
Thanks you for your prompt help.
You are welcome. I am hoping for an update with good news. 
I've updated the
1) ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit
2) Rt64win7.sys Thu Feb 26 04:04:13 2009 - Latest PCIe GBE
drivers ok, but I can't find an update anywhere for the
3) AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipset, Global Provider of Innovative Graphics, Processors and Media Solutions | AMD
driver. I've searched for it on the above URL but it doesn't return any search results. Do you know where I can look for it ?
Thanks !
1) ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit
2) Rt64win7.sys Thu Feb 26 04:04:13 2009 - Latest PCIe GBE
drivers ok, but I can't find an update anywhere for the
3) AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipset, Global Provider of Innovative Graphics, Processors and Media Solutions | AMD
driver. I've searched for it on the above URL but it doesn't return any search results. Do you know where I can look for it ?
Thanks !
It can be the chipset driver, if you click the link above, I believe on the right of the screen there will be place for you to choose driver, try to choose the motherboard/chipset option and choose the one that corespond to what you have
Product name: ATI PCIE Driver
Description: ATI PCIE Driver for ATI PCIE chipset
Manufacturer: ATI Technologies Inc.
Product name: ATI PCIE Driver
Description: ATI PCIE Driver for ATI PCIE chipset
Manufacturer: ATI Technologies Inc.
It is a chipset driver. You will need the model of your motherboard to find it. Try this link and fill in the data: AMD Support Search. If you do not know your motherboard information, you can downloadSpeccy or CPUZ and get that information.
Hope this helps.
Hope this helps.
Thank you, Tuan. You type faster than I do.
Hi, thanks for the reply. I think my problem is getting worse ;o)
- While I was searching for the above driver file, my system locked up with a black screen.
- I restarted with the case reset switch, it gave a BSOD with "MEMORY_MANAGEMENT".
- I reset again, and it gave a BSOD with "Stop 0x0000007E" and "rdyboost.sys".
- I reset again, and it detected a mass-storage device (even though I haven't got one attached), and prompted me to select a device to boot from (1 of the 2 HDDs or the DVD), it then gave a BSOD with "BAD_SYSTEM_CONFIG_INFO".
- I reset again and it gave a BSOD with "BAD_SYSTEM_CONFIG_INFO".
- It then booted into Win7 but then locked up and I had to reset.
- I then booted into Win7 using repair mode, and it booted in ok but seemed to have rolled some changes back (it no longer showed my sound card in device manager, and I think my GPU driver had rolled back)
- I then had more lockups, and I couldn't get it to boot into Win 7 at all.
- I finally took out my sound card, and it has booted into Win 7 ok, long enough for me to type this !
I've also re-run Windows_NT6_BSOD_v3.03_jcgriff2 and the Perfmon report, I've zipped these up and attached them.
I hope you can help ! Thanks in advance.
(Note most of the components in my system are still under 1 years warranty, so if you think its faulty hardware, I could take it back to the store where I bought the components, and ask them to test it).
- While I was searching for the above driver file, my system locked up with a black screen.
- I restarted with the case reset switch, it gave a BSOD with "MEMORY_MANAGEMENT".
- I reset again, and it gave a BSOD with "Stop 0x0000007E" and "rdyboost.sys".
- I reset again, and it detected a mass-storage device (even though I haven't got one attached), and prompted me to select a device to boot from (1 of the 2 HDDs or the DVD), it then gave a BSOD with "BAD_SYSTEM_CONFIG_INFO".
- I reset again and it gave a BSOD with "BAD_SYSTEM_CONFIG_INFO".
- It then booted into Win7 but then locked up and I had to reset.
- I then booted into Win7 using repair mode, and it booted in ok but seemed to have rolled some changes back (it no longer showed my sound card in device manager, and I think my GPU driver had rolled back)
- I then had more lockups, and I couldn't get it to boot into Win 7 at all.
- I finally took out my sound card, and it has booted into Win 7 ok, long enough for me to type this !
I've also re-run Windows_NT6_BSOD_v3.03_jcgriff2 and the Perfmon report, I've zipped these up and attached them.
I hope you can help ! Thanks in advance.
(Note most of the components in my system are still under 1 years warranty, so if you think its faulty hardware, I could take it back to the store where I bought the components, and ask them to test it).
I've also tried to find the AtiPcie.sys driver using the links you posted above. My motherboard is the "ASUS Crosshair III Formula AMD 790FX (AM3) PCI-E DDR3", so the chipset is 790FX.
Using the AMD site, if I search on motherboard/ chipset drivers for the 790FX chipset, it doesn't find anything.
Looking on google, other people are saying the AMD 790FX chipset drivers are included in the ATI Catalyst driver pack which I downloaded and installed to update my GPU drivers. I have downloaded and installed the latest Catalyst driver pack (10.9), so I should have the most recent chipset drivers as well. Unless I have the wrong end of the stick ?
I've been on the ASUS website and searched for the latest drivers on there, I've downloaded and installed the latest Northbridge driver.
Thanks.
Using the AMD site, if I search on motherboard/ chipset drivers for the 790FX chipset, it doesn't find anything.
Looking on google, other people are saying the AMD 790FX chipset drivers are included in the ATI Catalyst driver pack which I downloaded and installed to update my GPU drivers. I have downloaded and installed the latest Catalyst driver pack (10.9), so I should have the most recent chipset drivers as well. Unless I have the wrong end of the stick ?
I've been on the ASUS website and searched for the latest drivers on there, I've downloaded and installed the latest Northbridge driver.
Thanks.
Some folks have found that uninstalling Catalyst worked for them. Maybe the latest version works better with Win 7.
[quote]
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes - Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
Error code 74, BAD_SYSTEM_CONFIG_INFO. Usual causes - System hive corruption, Missing registry keys/values
[/code]
Have you used a registry cleaner or any third party tuneup utility program?
I had not seen this driver showing up before: ASACPI.sys Sun Mar 27 22:30:36 2005.
While this driver is a big problem, I think you have other things going on. Try running SFC /SCANNOW:
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Your next step will be to do a repair install. Carefully read and follow this tutorial. You may opt to do a clean install. If you do, back up your data.
Repair Install
Clean Install Windows 7
Update that driver first and then try SFC. Let us know if you need help.
[quote]
Error code 50, PAGE_FAULT_IN_NONPAGED_AREA. Usual causes - Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
Error code 74, BAD_SYSTEM_CONFIG_INFO. Usual causes - System hive corruption, Missing registry keys/values
[/code]
Have you used a registry cleaner or any third party tuneup utility program?
I had not seen this driver showing up before: 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).
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Your next step will be to do a repair install. Carefully read and follow this tutorial. You may opt to do a clean install. If you do, back up your data.
Repair Install
Clean Install Windows 7
Update that driver first and then try SFC. Let us know if you need help.
Code:
Kernel base = 0xfffff800`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50 Debug session time: Sun Oct 3 17:58:47.455 2010 (GMT-4) System Uptime: 0 days 1:50:50.218 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffffffffffff85, 1, fffff80002b7a890, 0} Could not read faulting driver name Probably caused by : hardware ( nt!AlpcpExposeAttributes+140 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except, it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffffffffffff85, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff80002b7a890, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab30e0 ffffffffffffff85 FAULTING_IP: nt!AlpcpExposeAttributes+140 fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff8800747f870 -- (.trap 0xfffff8800747f870) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80054afa60 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002b7a890 rsp=fffff8800747fa00 rbp=fffffa80054afa60 r8=0000000000000020 r9=00000000032aff00 r10=0000000000000000 r11=00000000032afd68 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!AlpcpExposeAttributes+0x140: fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl ds:fd40:ffffffff`ffffff85=?? Resetting default scope MISALIGNED_IP: nt!AlpcpExposeAttributes+140 fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl LAST_CONTROL_TRANSFER: from fffff800028fbf14 to fffff8000287b740 STACK_TEXT: fffff880`0747f708 fffff800`028fbf14 : 00000000`00000050 ffffffff`ffffff85 00000000`00000001 fffff880`0747f870 : nt!KeBugCheckEx fffff880`0747f710 fffff800`0287982e : 00000000`00000001 fffff8a0`0b3d0d00 00000001`00000000 fffff880`009e8180 : nt! ?? ::FNODOBFM::`string'+0x42837 fffff880`0747f870 fffff800`02b7a890 : 00000000`032afd00 fffffa80`00000010 fffffa80`0478ab01 00000000`032afd00 : nt!KiPageFault+0x16e fffff880`0747fa00 fffff800`02b7bbe2 : 00000000`00000000 00000000`0001bf01 00000000`032afd40 00000000`00000001 : nt!AlpcpExposeAttributes+0x140 fffff880`0747fa60 fffff800`02b7d006 : fffffa80`054afa60 00000000`00010000 00000000`00010000 fffffa80`054afa60 : nt!AlpcpReceiveMessage+0x3ef fffff880`0747fb00 fffff800`0287a993 : fffffa80`05c96b60 fffff880`0747fca0 00000000`032afc98 00000000`032afd88 : nt!NtAlpcSendWaitReceivePort+0x1e6 fffff880`0747fbb0 00000000`772205aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`032afc78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772205aa STACK_COMMAND: kb FOLLOWUP_IP: nt!AlpcpExposeAttributes+140 fffff800`02b7a890 004885 add byte ptr [rax-7Bh],cl SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!AlpcpExposeAttributes+140 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner --------- Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a52e50 Debug session time: Mon Oct 4 17:10:33.097 2010 (GMT-4) System Uptime: 0 days 0:00:09.470 Loading Kernel Symbols ............................................................... ............... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 74, {2, fffff88003b87b20, 5, ffffffffc000014c} Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_SYSTEM_CONFIG_INFO (74) Can indicate that the SYSTEM hive loaded by the osloader/NTLDR was corrupt. This is unlikely, since the osloader will check a hive to make sure it isn't corrupt after loading it. It can also indicate that some critical registry keys and values are not present. (i.e. somebody used regedt32 to delete something that they shouldn't have) Booting from LastKnownGood may fix the problem, but if someone is persistent enough in mucking with the registry they will need to reinstall or use the Emergency Repair Disk. Arguments: Arg1: 0000000000000002, (reserved) Arg2: fffff88003b87b20, (reserved) Arg3: 0000000000000005, (reserved) Arg4: ffffffffc000014c, usually the NT status code. Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x74 PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d03cda to fffff80002885740 STACK_TEXT: fffff880`03b87a68 fffff800`02d03cda : 00000000`00000074 00000000`00000002 fffff880`03b87b20 00000000`00000005 : nt!KeBugCheckEx fffff880`03b87a70 fffff800`02b29c06 : 00000000`01d23e1b fffffa80`04efeb60 00000000`00000080 fffffa80`03af49e0 : nt!CmpLoadHiveThread+0x23a fffff880`03b87d40 fffff800`02863c26 : fffff800`029ffe80 fffffa80`04efeb60 fffffa80`04f00060 fffff880`01014bf0 : nt!PspSystemThreadStartup+0x5a fffff880`03b87d80 00000000`00000000 : fffff880`03b88000 fffff880`03b82000 fffff880`03b86ea0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!CmpLoadHiveThread+23a fffff800`02d03cda cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!CmpLoadHiveThread+23a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a Followup: MachineOwner --------- 3: kd> lmtsmn start end module name fffff880`00f57000 fffff880`00fae000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`02b6a000 fffff880`02bf4000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`03db0000 fffff880`03dc5000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00ff4000 fffff880`00fff000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`00e9a000 fffff880`00ea3000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00d6a000 fffff880`00d94000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`04604000 fffff880`04dbf000 atikmdag atikmdag.sys Wed Aug 25 21:47:22 2010 (4C75C7AA) fffff880`03c00000 fffff880`03c4a000 atikmpag atikmpag.sys Wed Aug 25 21:20:56 2010 (4C75C178) fffff880`01452000 fffff880`0145a000 AtiPcie AtiPcie.sys Tue May 05 11:00:22 2009 (4A005486) fffff880`02abe000 fffff880`02ac5000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`03d79000 fffff880`03d8a000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`02a8b000 fffff880`02ab5000 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`011a6000 fffff880`011d6000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00d0c000 fffff880`00d6a000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`012a5000 fffff880`01318000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`01216000 fffff880`01224000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`03d5b000 fffff880`03d79000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03d4c000 fffff880`03d5b000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`01200000 fffff880`01216000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01224000 fffff880`0122d000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`013f3000 fffff880`013ff000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`011d6000 fffff880`011e9000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`00de0000 fffff880`00df4000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`00d94000 fffff880`00de0000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`01329000 fffff880`01333000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`013b9000 fffff880`013f3000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`02df1000 fffff800`02e3a000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`015f1000 fffff880`015fa000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff800`00bc7000 fffff800`00bd1000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`0128b000 fffff880`012a5000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`015b4000 fffff880`015df000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`00ceb000 fffff880`00cf8000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`00cd0000 fffff880`00cea000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02b23000 fffff880`02b2e000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00fb7000 fffff880`00fc1000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`0122d000 fffff880`0128b000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03d41000 fffff880`03d4c000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`015df000 fffff880`015f1000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01462000 fffff880`01554000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`02a74000 fffff880`02a83000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`02a00000 fffff880`02a45000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`01554000 fffff880`015b4000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`02b2e000 fffff880`02b3f000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03d35000 fffff880`03d41000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`02815000 fffff800`02df1000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01003000 fffff880`011a6000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`02ab5000 fffff880`02abe000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`02a4e000 fffff880`02a74000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00e0d000 fffff880`00e22000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00fc1000 fffff880`00ff4000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00e93000 fffff880`00e9a000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00cc0000 fffff880`00cd0000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`01318000 fffff880`01329000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`00cf8000 fffff880`00d0c000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`03ce4000 fffff880`03d35000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`02b08000 fffff880`02b11000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b11000 fffff880`02b1a000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`02b1a000 fffff880`02b23000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`0137f000 fffff880`013b9000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`0144a000 fffff880`01452000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`02b5d000 fffff880`02b6a000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`02b3f000 fffff880`02b5d000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03cd0000 fffff880`03ce4000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff880`03d8a000 fffff880`03db0000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`00e00000 fffff880`00e0d000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`02ac5000 fffff880`02ad3000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`02ad3000 fffff880`02af8000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`00e22000 fffff880`00e37000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00e37000 fffff880`00e93000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01333000 fffff880`0137f000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`03cb5000 fffff880`03cd0000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`02af8000 fffff880`02b08000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00ea4000 fffff880`00f48000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f48000 fffff880`00f57000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`02a45000 fffff880`02a4e000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`00fae000 fffff880`00fb7000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) Ok thanks - I will update the ASACPI.sys driver and run SFC this evening, I'll let you know how I get on.
EDIT: Note I haven't used a registry cleaner or any third party tuneup utility program.
EDIT: Note I haven't used a registry cleaner or any third party tuneup utility program.
I hope that solves the problem. The error code 74 concerns me. I will be looking for your update. I am glad to know that you have not used a registry cleaner nor a tuneup utility.
Hi. I updated the ASACPI.sys driver and run SFC. SFC completed and it said that it found corrupt files and successfully repaired them. I ran the
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
command to pull all the "[SR]" log entries from the CBS.log file into a new log file, which is attached.
It contains a *lot* of files that were found to be corrupt and it repaired them. Any idea how so many files could have become corrupted ?
Thanks again !
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
command to pull all the "[SR]" log entries from the CBS.log file into a new log file, which is attached.
It contains a *lot* of files that were found to be corrupt and it repaired them. Any idea how so many files could have become corrupted ?
Thanks again !
That is a lot of files; but the good thing is SFC repaired them. A lot of things can cause file corruption from an unexpected power loss to a failing hard drive. You can test your drive using Check Disk.
Glad you got ASACPI.sys updated. Let's see how your system does now with ASACPI.sys updated and the files repaired.
Quote:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7).
Copy/paste the results into your next post.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7).
Copy/paste the results into your next post.
Hi there. I left my PC running all yesterday and last night whilst it was patching and updating LOTRO - since this takes a long time I left it overnight. This morning when I looked at all, the PC seemed to be still running (had power, fans going round, motheboard LEDs on ok EXCEPT for the HDD LED which was not flashing) but the monitor was showing a blank screen as though it had no signal, and the PC wouldn't wake up by pressing keys or moving the mouse.
I hit the case reset switch and booted into Win 7 safe mode ok, which it did, and told me that Windowns had suffered another BSOD (it also created file 100610-30232-01.dmp).
I've run the Windows_NT6_BSOD_v3.03_jcgriff2_ application and the Perfmon report, the results of these are zipped up and attached as usual.
I also ran SFC/ SCANNOW, it completed 100% and said that Windows Resource Protection did not find any integrity violations.
EDIT:
- Note I've not checked my HDDs yet, maybe that's something to do next ?
- For RAM since I have 2x2GB sticks, I was maybe going pull 1 of my RAM sticks out and put the remaining 1 in another empty motherboard slot, test, and then try with the other stick in on its own, and then test.
- I have 2 HDDs in my PC, an older 128GB drive with Win on it, and a newer 1TB drive for games, music, photos etc. If it's maybe a failing HDD, I was going to take the old 128GB drive out and do a clean install of Win 7 on the newer 1TB drive.
Please let me know your thoughts/ advice, and thanks again !
I hit the case reset switch and booted into Win 7 safe mode ok, which it did, and told me that Windowns had suffered another BSOD (it also created file 100610-30232-01.dmp).
I've run the Windows_NT6_BSOD_v3.03_jcgriff2_ application and the Perfmon report, the results of these are zipped up and attached as usual.
I also ran SFC/ SCANNOW, it completed 100% and said that Windows Resource Protection did not find any integrity violations.
EDIT:
- Note I've not checked my HDDs yet, maybe that's something to do next ?
- For RAM since I have 2x2GB sticks, I was maybe going pull 1 of my RAM sticks out and put the remaining 1 in another empty motherboard slot, test, and then try with the other stick in on its own, and then test.
- I have 2 HDDs in my PC, an older 128GB drive with Win on it, and a newer 1TB drive for games, music, photos etc. If it's maybe a failing HDD, I was going to take the old 128GB drive out and do a clean install of Win 7 on the newer 1TB drive.
Please let me know your thoughts/ advice, and thanks again !
Quote:
Error code 74, BAD_SYSTEM_CONFIG_INFO. Usual causes: System hive corruption, Missing registry keys/values.
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt. This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present. (i.e. somebody used regedt32 to delete something
that they shouldn't have) Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Error code D1, BAD_SYSTEM_CONFIG_INFO. Usually caused by a driver.
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt. This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present. (i.e. somebody used regedt32 to delete something
that they shouldn't have) Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Error code D1, BAD_SYSTEM_CONFIG_INFO. Usually caused by a driver.
Code:
Kernel base = 0xfffff800`02815000 PsLoadedModuleList = 0xfffff800`02a52e50 Debug session time: Mon Oct 4 17:10:33.097 2010 (GMT-4) System Uptime: 0 days 0:00:09.470 Loading Kernel Symbols ............................................................... ............... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 74, {2, fffff88003b87b20, 5, ffffffffc000014c} Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_SYSTEM_CONFIG_INFO (74) Can indicate that the SYSTEM hive loaded by the osloader/NTLDR was corrupt. This is unlikely, since the osloader will check a hive to make sure it isn't corrupt after loading it. It can also indicate that some critical registry keys and values are not present. (i.e. somebody used regedt32 to delete something that they shouldn't have) Booting from LastKnownGood may fix the problem, but if someone is persistent enough in mucking with the registry they will need to reinstall or use the Emergency Repair Disk. Arguments: Arg1: 0000000000000002, (reserved) Arg2: fffff88003b87b20, (reserved) Arg3: 0000000000000005, (reserved) Arg4: ffffffffc000014c, usually the NT status code. Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x74 PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d03cda to fffff80002885740 STACK_TEXT: fffff880`03b87a68 fffff800`02d03cda : 00000000`00000074 00000000`00000002 fffff880`03b87b20 00000000`00000005 : nt!KeBugCheckEx fffff880`03b87a70 fffff800`02b29c06 : 00000000`01d23e1b fffffa80`04efeb60 00000000`00000080 fffffa80`03af49e0 : nt!CmpLoadHiveThread+0x23a fffff880`03b87d40 fffff800`02863c26 : fffff800`029ffe80 fffffa80`04efeb60 fffffa80`04f00060 fffff880`01014bf0 : nt!PspSystemThreadStartup+0x5a fffff880`03b87d80 00000000`00000000 : fffff880`03b88000 fffff880`03b82000 fffff880`03b86ea0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!CmpLoadHiveThread+23a fffff800`02d03cda cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!CmpLoadHiveThread+23a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a BUCKET_ID: X64_0x74_nt!CmpLoadHiveThread+23a Followup: MachineOwner --------- Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. Loading unloaded module list ...Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. ......Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff80000c9b6e0, 2, 0, fffff880016e777b} Probably caused by : tcpip.sys ( tcpip!ConvertFieldToAddr+2b ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: fffff80000c9b6e0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff880016e777b, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aaf0e0 fffff80000c9b6e0 CURRENT_IRQL: 2 FAULTING_IP: tcpip!ConvertFieldToAddr+2b fffff880`016e777b 833800 cmp dword ptr [rax],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80000b9b200 -- (.trap 0xfffff80000b9b200) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffff80000c9b6e0 rbx=0000000000000000 rcx=000000000000000d rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880016e777b rsp=fffff80000b9b390 rbp=0000000000000000 r8=fffff80000b9b6e0 r9=000000000000c082 r10=0000000000000000 r11=00000000000000ff r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc tcpip!ConvertFieldToAddr+0x2b: fffff880`016e777b 833800 cmp dword ptr [rax],0 ds:fffff800`00c9b6e0=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002878469 to fffff80002878f00 STACK_TEXT: fffff800`00b9b0b8 fffff800`02878469 : 00000000`0000000a fffff800`00c9b6e0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`00b9b0c0 fffff800`028770e0 : 00000001`00000001 00000000`0000000d 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`00b9b200 fffff880`016e777b : 00000000`00000000 00000000`00000000 ffff0080`01cf30c1 00000000`00000000 : nt!KiPageFault+0x260 fffff800`00b9b390 fffff880`01700c1d : fffff800`00b9b6c8 fffff800`00b9b6e0 fffff800`00b9b850 fffff800`00b9b6d0 : tcpip!ConvertFieldToAddr+0x2b fffff800`00b9b3d0 fffff880`01700fbd : fffff800`00b9b820 00000000`00000000 00000000`00005000 fffff880`0588009a : tcpip!IndicateDropAudit+0x12d fffff800`00b9b620 fffff880`016915dc : fffffa80`05113ae0 00000000`00000006 fffffa80`04f221a0 fffff880`01495a39 : tcpip!ShimIndicateDiscardNoClassify+0x5d fffff800`00b9b670 fffff880`01632339 : fffffa80`04aac000 fffffa80`04ab0f00 00000000`00000014 fffff880`01494fbf : tcpip! ?? ::FNODOBFM::`string'+0xe597 fffff800`00b9ba40 fffff880`0163241d : fffffa80`04ab0f00 fffff800`00b9bce8 fffffa80`04aac000 fffff880`058800a2 : tcpip!InetInspectRespondDatagram+0x149 fffff800`00b9bbd0 fffff880`0167c4b0 : 00000000`00000000 fffffa80`04aac000 fffffa80`04949538 fffffa80`04949538 : tcpip!TcpDiscardReceive+0x6d fffff800`00b9bc20 fffff880`0167bc17 : fffff880`058800a2 fffffa80`04aac000 00000000`00000000 fffff880`0165f300 : tcpip!TcpMatchReceive+0x5e0 fffff800`00b9bd70 fffff880`0165e3c7 : fffffa80`04aac000 fffffa80`04ab5e30 fffffa80`04ab5000 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177 fffff800`00b9be20 fffff880`0165e499 : fffff800`00b9bfa0 fffff880`0176e9a0 fffff800`00b9bfb0 fffffa80`049217b0 : tcpip!IppDeliverListToProtocol+0x97 fffff800`00b9bee0 fffff880`0165e990 : fffffa80`04aac000 fffffa80`049e1860 00000000`00000000 fffff800`00b9bfa0 : tcpip!IppProcessDeliverList+0x59 fffff800`00b9bf50 fffff880`0165d821 : 00000000`0201a8c0 fffffa80`04aac000 fffff880`0176e9a0 00000000`05304301 : tcpip!IppReceiveHeaderBatch+0x231 fffff800`00b9c030 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!IpFlcReceivePackets+0x651 STACK_COMMAND: kb FOLLOWUP_IP: tcpip!ConvertFieldToAddr+2b fffff880`016e777b 833800 cmp dword ptr [rax],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: tcpip!ConvertFieldToAddr+2b FOLLOWUP_NAME: MachineOwner MODULE_NAME: tcpip IMAGE_NAME: tcpip.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc26e FAILURE_BUCKET_ID: X64_0xD1_tcpip!ConvertFieldToAddr+2b BUCKET_ID: X64_0xD1_tcpip!ConvertFieldToAddr+2b Followup: MachineOwner --------- You are running Windows Firewall which should not be a problem. Are you running Windows Defender or are you running Microsoft Security Essentials? If you are running Defender, download an install MSE. MSE will disable defender.
That said, the error code 74 troubles me. You posted earlier that you have not used a registry cleaner nor a tuneup utility. Have you edited the registry using regedit or any registry editor? The error code 74 dump implies there is something wrong with your registry.
At this point, I suggest a repair install: Repair Install
or a clean install: Clean Install Windows 7
Read these tutorials carefully and back up your data to another drive before attempting either method. If you have any questions, please post back. Let us know what you decide to do. If you would like, I can get another member of the team to take a look at this thread for a second opinion. That will certainly not hurt my feelings. Two or more sets of eyes are always better than one.
Hi there, thanks for the response.
I'm not using any antivirus at the moment.
I've not edited or changed the registry in anyway.
If it's easy, could you maybe ask another member of the team to have a look at this thread and the logs ? I trust you completely, so please don't think I mean anything bad by asking this, but I do like your suggestion of getting a second opinion, just to understand if there are any other things I should try or do
After that, I can try a repair install or a full install, no problem.
Do you think this could maybe be due to failing hardware, such as a HDD or motherboard ? Note the LAN port I am using is built into my motherboard, its not a separate card.
Thank you again !
I'm not using any antivirus at the moment.
I've not edited or changed the registry in anyway.
If it's easy, could you maybe ask another member of the team to have a look at this thread and the logs ? I trust you completely, so please don't think I mean anything bad by asking this, but I do like your suggestion of getting a second opinion, just to understand if there are any other things I should try or do
After that, I can try a repair install or a full install, no problem.
Do you think this could maybe be due to failing hardware, such as a HDD or motherboard ? Note the LAN port I am using is built into my motherboard, its not a separate card.
Thank you again !
That does not insult me at all. I ask for help from other team members frequently. We all want to help the OP as best we can. I have asked for help and that help will come.
Thank you !
First thing I notice, ASACPI has not been updated yet. Go here: ASUSTeK Computer Inc.-Support-
In the Utilities section, download the ATK0110 driver.
In one dump, tcpip.sys was blamed, the Windows TCP/IP driver. I see your Realtek network adapters are outdated. Please install these ones: Realtek
Your Soundblaster drivers are old too; no updates can be found however: Creative Worldwide Support
Hardware is blamed by one dump, but it doesn't say what component.
Try testing RAM with Memtest86, this time for longer. See this tutorial: RAM - Test with Memtest86+
You say you remove the GPU, and it didn't work? What GFX card did you use?
...Summary of the Dumps:
In the Utilities section, download the ATK0110 driver.
In one dump, tcpip.sys was blamed, the Windows TCP/IP driver. I see your Realtek network adapters are outdated. Please install these ones: Realtek
Your Soundblaster drivers are old too; no updates can be found however: Creative Worldwide Support
Hardware is blamed by one dump, but it doesn't say what component.
Try testing RAM with Memtest86, this time for longer. See this tutorial: RAM - Test with Memtest86+
You say you remove the GPU, and it didn't work? What GFX card did you use?
...Summary of the Dumps:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Tue Oct 5 21:34:44.814 2010 (UTC - 4:00) System Uptime: 0 days 7:00:34.562 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 BugCheck D1, {fffff80000c9b6e0, 2, 0, fffff880016e777b} Probably caused by : tcpip.sys ( tcpip!ConvertFieldToAddr+2b ) BUGCHECK_STR: 0xD1 PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Oct 4 17:10:33.097 2010 (UTC - 4:00) System Uptime: 0 days 0:00:09.470 BugCheck 74, {2, fffff88003b87b20, 5, ffffffffc000014c} Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+23a ) BUGCHECK_STR: 0x74 PROCESS_NAME: System �������������������������������������������������������������������������������������� Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Oct 3 17:58:47.455 2010 (UTC - 4:00) System Uptime: 0 days 1:50:50.218 BugCheck 50, {ffffffffffffff85, 1, fffff80002b7a890, 0} Probably caused by : hardware ( nt!AlpcpExposeAttributes+140 ) BUGCHECK_STR: 0x50 PROCESS_NAME: csrss.exe �������������������������������������������������������������������������������������� Thanks, some good extra things for me to try. I will try all of these and post back the results.
The other GPU I have is an nVidia 8800GT card, which I swopped in to test - I received a BSOD also with that card though, just when web surfing.
EDIT: these are the actions I've taken:
- updated my ATK0110/ ASACPI driver ok, this is the latest one from the ASUS website for my motherboard - this is version 1043.6.0.0 (05/05/2009)
- updated the LAN driver from the RealTek site, this is now version 7.26.902.2010 (02/09/2010).
- updated the soundblaster drivers from the creative site, this is now 6.10.0.209 (27/08/2009)
- ran memtest as instructed above via a boot CD: I left it running overnight for 9.5 hours and it did 9 passes with zero errors; the PC stayed up fine as well with no restarts or problems.
- ran CHKDSK on my HDD C: drive 128GB with Win 7 on:
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
83968 file records processed. File verification completed.
69 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
117926 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
83968 file SDs/SIDs processed. Cleaning up 291 unused index entries from index $SII of file 0x9.
Cleaning up 291 unused index entries from index $SDH of file 0x9.
Cleaning up 291 unused security descriptors.
Security descriptor verification completed.
16980 data files processed. CHKDSK is verifying Usn Journal...
33853616 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
83952 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
22128674 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
117210208 KB total disk space.
28460864 KB in 66208 files.
47760 KB in 16981 indexes.
0 KB in bad sectors.
186884 KB in use by the system.
65536 KB occupied by the log file.
88514700 KB available on disk.
4096 bytes in each allocation unit.
29302552 total allocation units on disk.
22128675 allocation units available on disk.
Internal Info:
00 48 01 00 01 45 01 00 1f 76 02 00 00 00 00 00 .H...E...v......
25 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 %...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
--------------------------------------------------------------------------
- ran CHKDSK on my HDD D: drive 1TB with media on and some games (LOTRO)
Checking file system on D:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
12800 file records processed. File verification completed.
1 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
13334 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
12800 file SDs/SIDs processed. Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
267 data files processed. CHKDSK is verifying file data (stage 4 of 5)...
12784 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
47345636 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
204697599 KB total disk space.
15229588 KB in 1494 files.
464 KB in 269 indexes.
0 KB in bad sectors.
84999 KB in use by the system.
65536 KB occupied by the log file.
189382548 KB available on disk.
4096 bytes in each allocation unit.
51174399 total allocation units on disk.
47345637 allocation units available on disk.
Internal Info:
00 32 00 00 ee 06 00 00 b8 09 00 00 00 00 00 00 .2..............
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
The other GPU I have is an nVidia 8800GT card, which I swopped in to test - I received a BSOD also with that card though, just when web surfing.
EDIT: these are the actions I've taken:
- updated my ATK0110/ ASACPI driver ok, this is the latest one from the ASUS website for my motherboard - this is version 1043.6.0.0 (05/05/2009)
- updated the LAN driver from the RealTek site, this is now version 7.26.902.2010 (02/09/2010).
- updated the soundblaster drivers from the creative site, this is now 6.10.0.209 (27/08/2009)
- ran memtest as instructed above via a boot CD: I left it running overnight for 9.5 hours and it did 9 passes with zero errors; the PC stayed up fine as well with no restarts or problems.
- ran CHKDSK on my HDD C: drive 128GB with Win 7 on:
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
83968 file records processed. File verification completed.
69 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
117926 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
83968 file SDs/SIDs processed. Cleaning up 291 unused index entries from index $SII of file 0x9.
Cleaning up 291 unused index entries from index $SDH of file 0x9.
Cleaning up 291 unused security descriptors.
Security descriptor verification completed.
16980 data files processed. CHKDSK is verifying Usn Journal...
33853616 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
83952 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
22128674 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
117210208 KB total disk space.
28460864 KB in 66208 files.
47760 KB in 16981 indexes.
0 KB in bad sectors.
186884 KB in use by the system.
65536 KB occupied by the log file.
88514700 KB available on disk.
4096 bytes in each allocation unit.
29302552 total allocation units on disk.
22128675 allocation units available on disk.
Internal Info:
00 48 01 00 01 45 01 00 1f 76 02 00 00 00 00 00 .H...E...v......
25 01 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 %...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
--------------------------------------------------------------------------
- ran CHKDSK on my HDD D: drive 1TB with media on and some games (LOTRO)
Checking file system on D:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
12800 file records processed. File verification completed.
1 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
13334 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
12800 file SDs/SIDs processed. Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
267 data files processed. CHKDSK is verifying file data (stage 4 of 5)...
12784 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
47345636 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.
204697599 KB total disk space.
15229588 KB in 1494 files.
464 KB in 269 indexes.
0 KB in bad sectors.
84999 KB in use by the system.
65536 KB occupied by the log file.
189382548 KB available on disk.
4096 bytes in each allocation unit.
51174399 total allocation units on disk.
47345637 allocation units available on disk.
Internal Info:
00 32 00 00 ee 06 00 00 b8 09 00 00 00 00 00 00 .2..............
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Hi there, I've performed the latest suggested tests, running memtest, CHKDSK and updating drivers. Results in my post above. Everything seems to be ok from the test results, but please check them and let me know.
I will carry on testing my system with some games and report back if I get any BSODs or lock-ups.
Thanks again.
I will carry on testing my system with some games and report back if I get any BSODs or lock-ups.
Thanks again.
Hi there. My PC has been sort of stable. I've left it running in Win 7 for a day or 2, and have had some games oh it, and I've had no problems.
I was running LOTRO (online game) for about 2 or 3 hours today, and it was stable - I decided to put my PC case side back on and move the tower case from on its side to standing upright under my desk as usual - when I did this, I had a BSOD with the error "an attempt was made to execute non-executable memory". I wonder if my RAM or another component may not be making a good connection, and moving the case caused this BSOD ?
I've attached the new mini dump and PerfmonReport files as usual.
Thanks.
I was running LOTRO (online game) for about 2 or 3 hours today, and it was stable - I decided to put my PC case side back on and move the tower case from on its side to standing upright under my desk as usual - when I did this, I had a BSOD with the error "an attempt was made to execute non-executable memory". I wonder if my RAM or another component may not be making a good connection, and moving the case caused this BSOD ?
I've attached the new mini dump and PerfmonReport files as usual.
Thanks.
No drivers seem to be the cause here.
Go ahead and stress your system more. Run Prime95, according to this tutorial: http://www.sevenforums.com/tutorials...t-prime95.html
Also, run the Blend test.
BSOD Summary:
Go ahead and stress your system more. Run Prime95, according to this tutorial: http://www.sevenforums.com/tutorials...t-prime95.html
Also, run the Blend test.
BSOD Summary:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Sun Oct 10 14:03:30.504 2010 (UTC - 4:00) System Uptime: 0 days 10:11:07.878 BugCheck FC, {fffff88003b3429e, 800000012f56b963, fffff88001f2ea60, 2} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42567 ) BUGCHECK_STR: 0xFC PROCESS_NAME: System �������������������������������������������������������������������������������������� Update on this:
- I've run Furmark today for 10 hours straight, no problems, PC stayed stable, GPU temp was constant at around 72 deg C.
- I've run Prime95 in stress test as instructed, I ran it for about an hour, seemed stable and ok so I stopped it after about an hour. Speedfan gives two temp read outs: 61 deg C (temp1), 73 deg C (core). PC Probe 2 gives the following: CPU 61, MB 30, NB 49, SB 45 (all deg C).
Any idea if these are too hot for my CPU or GPU (the CPU and GPU types are in my profile) ?
I guess I could buy a bigger/ better cooler for the CPU and use artic thermal paste ?
I should add that, following the last BSOD when I moved my case, I have reseated my 2 RAM sticks in the other two motherboard slots.
- I've run Furmark today for 10 hours straight, no problems, PC stayed stable, GPU temp was constant at around 72 deg C.
- I've run Prime95 in stress test as instructed, I ran it for about an hour, seemed stable and ok so I stopped it after about an hour. Speedfan gives two temp read outs: 61 deg C (temp1), 73 deg C (core). PC Probe 2 gives the following: CPU 61, MB 30, NB 49, SB 45 (all deg C).
Any idea if these are too hot for my CPU or GPU (the CPU and GPU types are in my profile) ?
I guess I could buy a bigger/ better cooler for the CPU and use artic thermal paste ?
I should add that, following the last BSOD when I moved my case, I have reseated my 2 RAM sticks in the other two motherboard slots.
Well, after 2 or 3 days of my PC being stable, I had a few lockups (freezes) and restarts in Win 7 today, and 3 BSODs with errors
MEMORY_MANAGEMENT
BUGCODE_USB_DRIVER
IRQL_NOT_LESS_OR_EQUAL
The problems seemed to start just after I put a CD in my DVD drive to install my monitor drivers (whether or not that was the trigger I'm not sure).
Win 7 generated a new mini dump file. I ran the usual program and I've zipped up the results and attached it.
Any help is most welcome !
Thanks.
MEMORY_MANAGEMENT
BUGCODE_USB_DRIVER
IRQL_NOT_LESS_OR_EQUAL
The problems seemed to start just after I put a CD in my DVD drive to install my monitor drivers (whether or not that was the trigger I'm not sure).
Win 7 generated a new mini dump file. I ran the usual program and I've zipped up the results and attached it.
Any help is most welcome !
Thanks.
Error code FE, BUGCODE_USB_DRIVER. Usually caused by a USB device driver.
Unfortunately, the dump file is partial corrupted and I did not get date stamps for most of the drivers.
Unfortunately I can't tell much from this dump other than it blames USB. As far as I can determine, all of your USB drivers are up to date. What do you have plugged into USB?
Unfortunately, the dump file is partial corrupted and I did not get date stamps for most of the drivers.
Code:
Kernel base = 0xfffff800`02867000 PsLoadedModuleList = 0xfffff800`02aa4e50 Debug session time: Wed Oct 13 17:22:44.495 2010 (GMT-4) System Uptime: 0 days 0:01:30.868 Loading Kernel Symbols .............................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FE, {5, fffffa8004f071a0, 10024398, fffffa80054c6f60} Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BUGCODE_USB_DRIVER (fe) USB Driver bugcheck, first parameter is USB bugcheck code. Arguments: Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is using a physical memory address that was not allocated by the USBport driver. Arg2: fffffa8004f071a0, Device extension pointer of the host controller Arg3: 0000000010024398, PCI Vendor,Product id for the controller Arg4: fffffa80054c6f60, Pointer to Endpoint data structure Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xFE PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800028e6a3a to fffff88003d957f2 STACK_TEXT: fffff800`00b9cc98 fffff800`028e6a3a : 00000000`002fd8f4 fffffa80`050335d8 fffff800`02a5fc40 00000000`00000002 : 0xfffff880`03d957f2 fffff800`00b9cca0 fffff800`028e16cc : fffff800`02a51e80 fffff800`00000000 00000000`00000000 fffff880`0130ac50 : nt!PoIdle+0x53a fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: nt!PoIdle+53a fffff800`028e6a3a 0fba2506fc17000f bt dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`02a66648)],0Fh SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!PoIdle+53a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0xFE_nt!PoIdle+53a BUCKET_ID: X64_0xFE_nt!PoIdle+53a Followup: MachineOwner --------- 0: kd> lmtsmn start end module name fffff880`00f44000 fffff880`00f9b000 ACPI ACPI.sys unavailable (00000000) fffff880`00c2a000 fffff880`00c35000 amdxata amdxata.sys unavailable (00000000) fffff880`00df6000 fffff880`00dff000 atapi atapi.sys unavailable (00000000) fffff880`00c00000 fffff880`00c2a000 ataport ataport.SYS unavailable (00000000) fffff880`0146b000 fffff880`01473000 AtiPcie AtiPcie.sys unavailable (00000000) fffff880`00d1c000 fffff880`00ddc000 CI CI.dll unavailable (00000000) fffff880`01000000 fffff880`01030000 CLASSPNP CLASSPNP.SYS unavailable (00000000) fffff880`00cbe000 fffff880`00d1c000 CLFS CLFS.SYS unavailable (00000000) fffff880`0127b000 fffff880`012ee000 cng cng.sys unavailable (00000000) fffff880`01455000 fffff880`0146b000 disk disk.sys unavailable (00000000) fffff880`00c81000 fffff880`00c95000 fileinfo fileinfo.sys unavailable (00000000) fffff880`00c35000 fffff880`00c81000 fltmgr fltmgr.sys unavailable (00000000) fffff880`012ff000 fffff880`01309000 Fs_Rec Fs_Rec.sys unavailable (00000000) fffff880`0141b000 fffff880`01455000 fvevol fvevol.sys unavailable (00000000) fffff880`01513000 fffff880`0155d000 fwpkclnt fwpkclnt.sys unavailable (00000000) fffff800`0281e000 fffff800`02867000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`01412000 fffff880`0141b000 hwpolicy hwpolicy.sys unavailable (00000000) fffff800`00bc4000 fffff800`00bce000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`01261000 fffff880`0127b000 ksecdd ksecdd.sys unavailable (00000000) fffff880`014e8000 fffff880`01513000 ksecpkg ksecpkg.sys unavailable (00000000) fffff880`00c9d000 fffff880`00caa000 mcupdate mcupdate.dll unavailable (00000000) fffff880`00ddc000 fffff880`00df6000 mountmgr mountmgr.sys unavailable (00000000) fffff880`00fa4000 fffff880`00fae000 msisadrv msisadrv.sys unavailable (00000000) fffff880`01203000 fffff880`01261000 msrpc msrpc.sys unavailable (00000000) fffff880`01400000 fffff880`01412000 mup mup.sys unavailable (00000000) fffff880`01309000 fffff880`013fb000 ndis ndis.sys unavailable (00000000) fffff880`01488000 fffff880`014e8000 NETIO NETIO.SYS unavailable (00000000) fffff800`02867000 fffff800`02e44000 nt ntkrnlmp.exe Mon Jul 13 19:40:48 2009 (4A5BC600) fffff880`0105c000 fffff880`011ff000 Ntfs Ntfs.sys unavailable (00000000) fffff880`00e00000 fffff880`00e15000 partmgr partmgr.sys unavailable (00000000) fffff880`00fae000 fffff880`00fe1000 pci pci.sys unavailable (00000000) fffff880`00e86000 fffff880`00e8d000 pciide pciide.sys unavailable (00000000) fffff880`00fee000 fffff880`00ffe000 PCIIDEX PCIIDEX.SYS unavailable (00000000) fffff880`012ee000 fffff880`012ff000 pcw pcw.sys unavailable (00000000) fffff880`00caa000 fffff880`00cbe000 PSHED PSHED.dll unavailable (00000000) fffff880`015b8000 fffff880`015f2000 rdyboost rdyboost.sys unavailable (00000000) fffff880`015b1000 fffff880`015b8000 speedfan speedfan.sys unavailable (00000000) fffff880`015a9000 fffff880`015b1000 spldr spldr.sys unavailable (00000000) fffff880`01600000 fffff880`017fd000 tcpip tcpip.sys unavailable (00000000) baac731c`f7bb12c0 baac731d`f328a91c Unknown_Module_baac731c_f7bb12c0 Unknown_Module_baac731c`f7bb12c0 unavailable (00000000) fffff880`00fe1000 fffff880`00fee000 vdrvroot vdrvroot.sys unavailable (00000000) fffff880`00e15000 fffff880`00e2a000 volmgr volmgr.sys unavailable (00000000) fffff880`00e2a000 fffff880`00e86000 volmgrx volmgrx.sys unavailable (00000000) fffff880`0155d000 fffff880`015a9000 volsnap volsnap.sys unavailable (00000000) fffff880`00e91000 fffff880`00f35000 Wdf01000 Wdf01000.sys unavailable (00000000) fffff880`00f35000 fffff880`00f44000 WDFLDR WDFLDR.SYS unavailable (00000000) fffff880`00f9b000 fffff880`00fa4000 WMILIB WMILIB.SYS unavailable (00000000) Hi there, the only thing I have plugged into USB is the wireless controller for my cordless keyboard and mouse. Following the BSODs last night I've now installed the software/ drivers for these, as well as the driver for my monitor.
Should I try attaching the zip file again ?
Should I try attaching the zip file again ?
I've run Prime95 as instructed above today for 13 hours. All 4 cores of my CPU were maxed out at 100%, CPU temp steady at 60 deg C, core temp steady at 72 deg C.
On each CPU core, approximately 555 test were completed, zero errors, zero warnings.
I also ran the Western Digital diagnostics program on both my HDDs, the C: drive from within windows, and the D: drive from a boot-CD. No errors or warnings were reported.
On each CPU core, approximately 555 test were completed, zero errors, zero warnings.
I also ran the Western Digital diagnostics program on both my HDDs, the C: drive from within windows, and the D: drive from a boot-CD. No errors or warnings were reported.
I've heard mice and keyboard drivers can insert their hooks all over the place, but all I can get out of that is that a bad mouse driver may cause BSODs.
Try using a different mouse.
Try using a different mouse.
Hey there. Over the last few weeks I have tested with just 1 RAM stick in at a time.
I put just 1 RAM stick in my PC and tested it for 1 week. I ran memtest for 24 hours or so and it did 20 passes with no errors. My system was also stable with no crashes or BSODs in games.
After that, I then swopped the RAM stick for the other one and tested my system for another week. I ran memtest for 24 hours or so, it did 20 passes with no errors, my system was stable with no problems.
After the 2nd week, I put both RAM sticks back in. I had no problems for a week and a half, but then today I suddenly had 2 BSODs in quick succession. I've attached the zip file as usual.
Any help would be great, thanks !
I put just 1 RAM stick in my PC and tested it for 1 week. I ran memtest for 24 hours or so and it did 20 passes with no errors. My system was also stable with no crashes or BSODs in games.
After that, I then swopped the RAM stick for the other one and tested my system for another week. I ran memtest for 24 hours or so, it did 20 passes with no errors, my system was stable with no problems.
After the 2nd week, I put both RAM sticks back in. I had no problems for a week and a half, but then today I suddenly had 2 BSODs in quick succession. I've attached the zip file as usual.
Any help would be great, thanks !
What is the make/model of your PSU?
You might try running Memtest on both sticks at the same time.
...Summary of the dumps
You might try running Memtest on both sticks at the same time.
...Summary of the dumps
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Debug session time: Mon Nov 15 05:03:00.581 2010 (UTC - 5:00) System Uptime: 0 days 0:02:12.329 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4 ��������������������������������������������������������������������������������������``
Hi there. My PSU is a Thermaltake 700W. I'll run memtest for 24 hours with both RAM sticks in.
It looks like the BSODs I had today were due to bad RAM, is that correct ?
EDIT: I just had another BSOD with the message "MEMORY_MANAGEMENT". This didn't write any debug information though - well, it didnt change the timestamp of today's mini dump file, so I'm guessing that means it hasn't written anything to that file.
It looks like the BSODs I had today were due to bad RAM, is that correct ?
EDIT: I just had another BSOD with the message "MEMORY_MANAGEMENT". This didn't write any debug information though - well, it didnt change the timestamp of today's mini dump file, so I'm guessing that means it hasn't written anything to that file.
The "memory_corruption" and "memory_management" often do point to bad RAM, so it may pay off to run a test.
Hi there,
I've just run memtest at bootup for 2 days solid with both RAM sticks in place. It did 42 passes and no errors.
Thanks.
I've just run memtest at bootup for 2 days solid with both RAM sticks in place. It did 42 passes and no errors.
Thanks.
Hello,
Try running a hard drive test, with SeaTools: | Seagate
Your hard drive is one of the older components in the system, so that may be the most likely to have problems.
Try running a hard drive test, with SeaTools: | Seagate
Your hard drive is one of the older components in the system, so that may be the most likely to have problems.
Hmmm I had a blue screen (IRQL_NOT_LESS_OR_EQUAL) and some lock ups tonight, although no mini dump files were created. I also had some strange graphical artefacts when in Win 7 desktop also - one of the lock ups was at the Win 7 startup screen, the PC froze and lots of red smears appeared on the background when it locked up. Does this suggest it could be my GPU, maybe the RAM on the GPU ?
It certainly is a possibility. Run Furmark following the instructions in this tutorial: Video Card - Stress Test with Furmark
Since you already changed the graphics card, that would make that possibility unlikely, but stranger things have happened.
Honestly, I suspect a motherboard problem.
-Furmark has been run: http://www.sevenforums.com/crashes-d...ml#post1009594
-Western Digital Data Lifeguard has been run: http://www.sevenforums.com/crashes-d...ml#post1013988
Prime95 has been run: http://www.sevenforums.com/crashes-d...ml#post1013988
Memtest86 has been run: http://www.sevenforums.com/crashes-d...ml#post1083163
-PSU is sufficient, although there is always that chance that a PSU will fail prematurely.
-Software has been all but eliminated.
I'd say motherboard is the most likely candidate here.
Honestly, I suspect a motherboard problem.
-Furmark has been run: http://www.sevenforums.com/crashes-d...ml#post1009594
-Western Digital Data Lifeguard has been run: http://www.sevenforums.com/crashes-d...ml#post1013988
Prime95 has been run: http://www.sevenforums.com/crashes-d...ml#post1013988
Memtest86 has been run: http://www.sevenforums.com/crashes-d...ml#post1083163
-PSU is sufficient, although there is always that chance that a PSU will fail prematurely.
-Software has been all but eliminated.
I'd say motherboard is the most likely candidate here.
I called up my PC shop today, where I bought the bits that I built the machine with. They told me to check the voltage setting on my RAM. It was set at 1.5 v by default, however my RAM sticks state it should be 1.65 v ! I've changed this now, and will keep monitoring things.
Please update us. I hope it works!
Hi there, well after a few days of my PC behaving, today I have had an instance where a game (Lord of the Rings Online) stopped working and crashed back to Win 7 desktop (although my PC stayed up in Windows ok). I then had another instance of this problem but this was followed straight away by my usual problem of the screen going fuzzy and a BSOD, which said "Video memory management has stopped working or encountered a problem (or something along those lines)".
I've attached the usual zip file with this BSOD in it (I think the previous mini dump file of 15th Nov is also included in this zip file, with the one dumped today on the 28th Nov).
I'm almost at the point of giving up and buying a whole new PC, ready built and tested - this sounds a bit extreme, but I just can't get to the bottom of what is wrong with my PC.
Thanks in advance for any help you can give.
I've attached the usual zip file with this BSOD in it (I think the previous mini dump file of 15th Nov is also included in this zip file, with the one dumped today on the 28th Nov).
I'm almost at the point of giving up and buying a whole new PC, ready built and tested - this sounds a bit extreme, but I just can't get to the bottom of what is wrong with my PC.
Thanks in advance for any help you can give.
I also had some more lock-ups and some BSODs later on this evening. In particular at one point, my PC wouldn't start up at the bios stage and was emitting a frequent bleeping noise until I re-started it.
Attached is an updated zip file with the new BSOD mini-dump files included.
Thanks !
Attached is an updated zip file with the new BSOD mini-dump files included.
Thanks !
Hi; I am sorry to hear you are still having problems. I went back through this thread and it looks like you have tested just about everything possible. The fact that you have four different error codes in four dumps leads me to suspect a hardware problem.
I have to agree with Jonathan. I think your motherboard may be at fault or possibly you power supply. Do you have access to another known good power supply you could try?
Quote:
Bugcheck A, VIDEO_MEMORY_MANAGEMENT_INTERNAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.
Bugcheck 10E, VIDEO_MEMORY_MANAGEMENT_INTERNAL. Usual causes: Video driver, ?Video memory
Bugcheck 4E, PFN_LIST_CORRUPT. Usual causes: Device driver, ?memory.
Bugcheck D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. Usually caused by a driver.
Bugcheck 10E, VIDEO_MEMORY_MANAGEMENT_INTERNAL. Usual causes: Video driver, ?Video memory
Bugcheck 4E, PFN_LIST_CORRUPT. Usual causes: Device driver, ?memory.
Bugcheck D1, DRIVER_IRQL_NOT_LESS_OR_EQUAL. Usually caused by a driver.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50 Debug session time: Mon Nov 15 05:03:00.581 2010 (GMT-5) System Uptime: 0 days 0:02:12.329 Loading Kernel Symbols ..............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Loading unloaded module list .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffffa7ff3ffffe0, 2, 1, fffff80002ad1e89} Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 ) Followup: MachineOwner --------- 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: fffffa7ff3ffffe0, 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: fffff80002ad1e89, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc10e0 fffffa7ff3ffffe0 CURRENT_IRQL: 2 FAULTING_IP: nt!MmZeroPageThread+3d4 fffff800`02ad1e89 f0410fba6d1000 lock bts dword ptr [r13+10h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880009a9a80 -- (.trap 0xfffff880009a9a80) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000006b rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ad1e89 rsp=fffff880009a9c10 rbp=00000000000000ff r8=0000000000000000 r9=0000058000000000 r10=0000000000000002 r11=fffff880009a9c08 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nt!MmZeroPageThread+0x3d4: fffff800`02ad1e89 f0410fba6d1000 lock bts dword ptr [r13+10h],0 ds:a410:00000000`00000010=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002a8a469 to fffff80002a8af00 STACK_TEXT: fffff880`009a9938 fffff800`02a8a469 : 00000000`0000000a fffffa7f`f3ffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`009a9940 fffff800`02a890e0 : 00000000`00000000 ffffffff`ffbfffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`009a9a80 fffff800`02ad1e89 : 00000000`000000ff 00000000`0000000f 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x260 fffff880`009a9c10 fffff800`02d2e166 : fffffa80`03b4a410 00000000`00000080 fffffa80`03b4a990 fffff800`02a69479 : nt!MmZeroPageThread+0x3d4 fffff880`009a9d40 fffff800`02a69486 : fffff800`02c03e80 fffffa80`03b4a410 fffff800`02c11c40 8b4c7024`7c8b4868 : nt!PspSystemThreadStartup+0x5a fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!MmZeroPageThread+3d4 fffff800`02ad1e89 f0410fba6d1000 lock bts dword ptr [r13+10h],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!MmZeroPageThread+3d4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4 BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4 Followup: MachineOwner --------- Debug session time: Sun Nov 28 12:34:49.728 2010 (GMT-5) System Uptime: 0 days 4:57:49.102 Loading Kernel Symbols ............................................................... .Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10E, {1f, fffff8a00d17ce50, 0, 3fe2a9} Probably caused by : watchdog.sys ( watchdog!WdLogEvent5+11b ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 000000000000001f, The subtype of the bugcheck: Arg2: fffff8a00d17ce50 Arg3: 0000000000000000 Arg4: 00000000003fe2a9 Debugging Details: ------------------ BUGCHECK_STR: 0x10e_1f CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff88002ae322f to fffff80002ac8f00 STACK_TEXT: fffff880`01f35878 fffff880`02ae322f : 00000000`0000010e 00000000`0000001f fffff8a0`0d17ce50 00000000`00000000 : nt!KeBugCheckEx fffff880`01f35880 fffff880`03f1c098 : fffff8a0`0d17ce50 fffff8a0`0d17ce50 00000000`003fe2a9 00000000`00000000 : watchdog!WdLogEvent5+0x11b fffff880`01f358d0 fffff8a0`0d17ce50 : fffff8a0`0d17ce50 00000000`003fe2a9 00000000`00000000 00000000`00000000 : 0xfffff880`03f1c098 fffff880`01f358d8 fffff8a0`0d17ce50 : 00000000`003fe2a9 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff8a0`0d17ce50 fffff880`01f358e0 00000000`003fe2a9 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05819000 : 0xfffff8a0`0d17ce50 fffff880`01f358e8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`05819000 fffff880`03f198af : 0x3fe2a9 STACK_COMMAND: kb FOLLOWUP_IP: watchdog!WdLogEvent5+11b fffff880`02ae322f cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: watchdog!WdLogEvent5+11b FOLLOWUP_NAME: MachineOwner MODULE_NAME: watchdog IMAGE_NAME: watchdog.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc53f FAILURE_BUCKET_ID: X64_0x10e_1f_watchdog!WdLogEvent5+11b BUCKET_ID: X64_0x10e_1f_watchdog!WdLogEvent5+11b Followup: MachineOwner --------- Debug session time: Sun Nov 28 16:29:58.498 2010 (GMT-5) System Uptime: 0 days 2:39:43.887 Loading Kernel Symbols ..............................................Unable to add module at ffffffff`ffffffff .Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 . Loading User Symbols Loading unloaded module list .Missing image name, possible paged-out or corrupt data. ...Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. ..Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. Missing image name, possible paged-out or corrupt data. .Missing image name, possible paged-out or corrupt data. . ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {7, 109094, 40a94, 0} Probably caused by : Unknown_Module_fffff880`00de6060 ( Unknown_Module_fffff880`00de6060>+2e1d792 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it Arg2: 0000000000109094, page frame number Arg3: 0000000000040a94, current share count Arg4: 0000000000000000, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 IP_MODULE_UNLOADED: Unknown_Module_fffff880`00de6060>+2e1d792 fffff880`03c037f2 ?? ??? LAST_CONTROL_TRANSFER: from fffff80002a9ca3a to fffff88003c037f2 STACK_TEXT: fffff800`00b9cc98 fffff800`02a9ca3a : 00000000`002fd8ea fffffa80`051cfdd8 fffff800`02c15c40 00000000`00000001 : <Unloaded_Unknown_Module_fffff880`00de6060>+0x2e1d792 fffff800`00b9cca0 fffff800`02a976cc : fffff800`02c07e80 fffff800`00000000 00000000`00000000 fffff880`01431c50 : nt!PoIdle+0x53a fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: Unknown_Module_fffff880`00de6060>+2e1d792 fffff880`03c037f2 ?? ??? SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: Unknown_Module_fffff880`00de6060>+2e1d792 FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module_fffff880`00de6060 IMAGE_NAME: Unknown_Module_fffff880`00de6060 DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x4E_7_Unknown_Module_fffff880_00de6060_+2e1d792 BUCKET_ID: X64_0x4E_7_Unknown_Module_fffff880_00de6060_+2e1d792 Followup: MachineOwner --------- Debug session time: Sun Nov 28 16:38:10.804 2010 (GMT-5) System Uptime: 0 days 0:00:26.194 Loading Kernel Symbols .............................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {200, 2, 1, fffff880009ce1e8} Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000200, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880009ce1e8, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbf0e0 0000000000000200 CURRENT_IRQL: 0 FAULTING_IP: +60e3952f00d0da0c fffff880`009ce1e8 ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System LAST_CONTROL_TRANSFER: from fffff80002a96a3a to fffff88003c5e7f2 STACK_TEXT: fffff800`00b9cc98 fffff800`02a96a3a : 00000000`002fd8f4 fffffa80`04f60a48 fffff800`02c0fc40 00000000`00000002 : 0xfffff880`03c5e7f2 fffff800`00b9cca0 fffff800`02a916cc : fffff800`02c01e80 fffff800`00000000 00000000`00000000 fffff880`014d5c50 : nt!PoIdle+0x53a fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c STACK_COMMAND: kb FOLLOWUP_IP: nt!PoIdle+53a fffff800`02a96a3a 0fba2506fc17000f bt dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`02c16648)],0Fh SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!PoIdle+53a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0xD1_nt!PoIdle+53a BUCKET_ID: X64_0xD1_nt!PoIdle+53a Followup: MachineOwner --------- Hi there, thanks for the response as ever. I don't have access to another PSU unfortunately. I do still have my old motherboard, so I could rebuild my PC using that with my old RAM etc. However, since that will take some time and this has been going on for 2 months now, I think I will let my local PC shop test it. If they can't find anything wrong with it, I will likely buy another pre-build and pre-tested PC.
I'll let you know if my local shop finds anything wrong with it.
Thanks once again !
p.s. Some of the BSODs posted above which happened last night were when I had swopped my old graphics card in, so at least that proves my graphics card is not likely to be at fault.
I'll let you know if my local shop finds anything wrong with it.
Thanks once again !
p.s. Some of the BSODs posted above which happened last night were when I had swopped my old graphics card in, so at least that proves my graphics card is not likely to be at fault.
I think that is a good decision. Be sure to let them know all that you have done and tried. They may help them narrow things down. Please let us know what they find. I hope they can solve it for you.
Không có nhận xét nào:
Đăng nhận xét