New
#11
Possible outdated drivers:ASACPI.sysCode:ASACPI fffff880`04295000 fffff880`0429d000 Sun Mar 27 20:30:36 2005 (42476c4c) 00003c77 ASACPI.sys ctac32k fffff880`04b1f000 fffff880`04bcd000 Wed Jul 02 02:38:22 2008 (486b3e7e) 00095082 ctac32k.sys yk62x64 fffff880`0fe00000 fffff880`0fe63000 Mon Feb 23 08:02:27 2009 (49a2ba83) 0006049b yk62x64.sys NuidFltr fffff880`057f3000 fffff880`057fc000 Fri May 08 02:53:31 2009 (4a03f30b) 0000559d NuidFltr.sys GEARAspiWDM fffff880`0742a000 fffff880`07437000 Mon May 18 06:17:04 2009 (4a1151c0) 000159b4 GEARAspiWDM.sys
ctac32k.sys
yk62x64.sys
NuidFltr.sys
GEARAspiWDM.sys
This appears to be related to your memory or data corruption. I do note your .nfo file is corrupted, so you may have corruption of data on your system.Code:Loading Dump File [D:\Kingston\BSODDmpFiles\symetric\022612-49951-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e70 Debug session time: Sun Feb 26 07:36:12.384 2012 (UTC - 7:00) System Uptime: 0 days 13:26:02.008 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 34, {50830, fffff880083ab768, fffff880083aafd0, fffff8000303146b} Probably caused by : ntkrnlmp.exe ( nt!PfCheckDeprioritizeFile+16b ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CACHE_MANAGER (34) See the comment for FAT_FILE_SYSTEM (0x23) Arguments: Arg1: 0000000000050830 Arg2: fffff880083ab768 Arg3: fffff880083aafd0 Arg4: fffff8000303146b Debugging Details: ------------------ EXCEPTION_RECORD: fffff880083ab768 -- (.exr 0xfffff880083ab768) ExceptionAddress: fffff8000303146b (nt!PfCheckDeprioritizeFile+0x000000000000016b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880083aafd0 -- (.cxr 0xfffff880083aafd0) rax=005c006500630069 rbx=0000000000000001 rcx=007600650044005c rdx=0f505c3adea72267 rsi=fffff8a013055140 rdi=0000000000000000 rip=fffff8000303146b rsp=fffff880083ab9a0 rbp=0000000000000000 r8=0000000000004000 r9=fffff8a013055140 r10=ffffffffffffffff r11=fffff80002e17c30 r12=0000000000000001 r13=00000000031b6478 r14=0000000000000000 r15=0000000000000011 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!PfCheckDeprioritizeFile+0x16b: fffff800`0303146b 488b4108 mov rax,qword ptr [rcx+8] ds:002b:00760065`00440064=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eae0e0 ffffffffffffffff FOLLOWUP_IP: nt!PfCheckDeprioritizeFile+16b fffff800`0303146b 488b4108 mov rax,qword ptr [rcx+8] FAULTING_IP: nt!PfCheckDeprioritizeFile+16b fffff800`0303146b 488b4108 mov rax,qword ptr [rcx+8] BUGCHECK_STR: 0x34 LAST_CONTROL_TRANSFER: from fffff80002fac5fe to fffff8000303146b STACK_TEXT: fffff880`083ab9a0 fffff800`02fac5fe : fffffa80`0ae0c910 fffff8a0`13055140 00000000`00000000 00000000`00000000 : nt!PfCheckDeprioritizeFile+0x16b fffff880`083aba10 fffff800`02c8f3b7 : 00000000`00000000 fffffa80`0be70920 00000000`00000000 00000000`00100000 : nt! ?? ::NNGAKEGL::`string'+0x18c56 fffff880`083aba50 fffff800`02c66144 : 00000000`00000001 fffffa80`0bf56940 fffffa80`0ae0c900 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7 fffff880`083abae0 fffff800`02c69bdc : fffffa80`0ae0c910 00000000`00000000 fffffa80`0ae0c910 fffffa80`07af8900 : nt!CcDeleteSharedCacheMap+0x140 fffff880`083abb50 fffff800`02c6a3ec : 00000000`10000000 fffff880`083abc58 00000000`00000000 00000000`00000000 : nt!CcWriteBehind+0x5bc fffff880`083abc00 fffff800`02c837e1 : fffffa80`06a20ee0 fffff880`01253270 fffff800`02e7d160 fffff880`00000000 : nt!CcWorkerThread+0x1c8 fffff880`083abcb0 fffff800`02f166fa : 00000000`00000000 fffffa80`07af89b0 00000000`00000080 fffffa80`06a06040 : nt!ExpWorkerThread+0x111 fffff880`083abd40 fffff800`02c54b46 : fffff880`02f64180 fffffa80`07af89b0 fffffa80`06a16040 fffff880`0125e534 : nt!PspSystemThreadStartup+0x5a fffff880`083abd80 00000000`00000000 : fffff880`083ac000 fffff880`083a6000 fffff880`083aad20 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!PfCheckDeprioritizeFile+16b FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aa44 STACK_COMMAND: .cxr 0xfffff880083aafd0 ; kb FAILURE_BUCKET_ID: X64_0x34_nt!PfCheckDeprioritizeFile+16b BUCKET_ID: X64_0x34_nt!PfCheckDeprioritizeFile+16b Followup: MachineOwner ---------
Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.
- If you are overclocking any hardware, please stop.
- Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:
- Going to the Asus motherboard support site
When you reach the website:- Scroll down the page and click Utilities
- Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
- Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
- Download and install the driver.
- After installation is complete, verify that it installed correctly.
- Click Start Menu
- Click My Computer
- Go to C:\WIndows\System32\drivers\
- Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
Thanks to JMH and zigzag3143 for the above information.
You may not have to proceed with the following steps after this because your system may be stable after updating, but I do still recommend at the very least installing all Windows updates. I also recommend making sure the first four drivers in the list above are updated (ASACPI is the first, so this should already be done).
The fifth driver may be part of iTunes and therefore cannot be updated, so do not worry about it unless you continue to have crashes, in which case you may want to uninstall iTunes with the steps in Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7 to test.
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
- Install all Windows updates. I notice you do not have Service Pack 1 installed yet. Update to Service Pack 1 (SP1)
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 (KB947821) [August 2011]Links to Service Pack 1 (SP1) and preparation for SP1 courtesy of JMH
Download Details - Microsoft Download Center - System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [August 2011]
Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center
Service Pack 1 Download site
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.