Random BSOD on ASUS notebook K50IJ

djkelsey · 30 Jan 2012

ASUS notebook K50IJ just over 1 year old with original OS (7 Home Premium 64 bit SP1). Daughter's college pc.
I am having very random BSOD's, sometimes more frequent than others. Had 2 today while trying to diagnose.
Steps taken so far:

chkdsk.....OK
memtest86+ for 2 hours.....OK
Ccleaner.....basic and registry clean
Malwarebytes full scan.....OK

I tried to run Windows Memory Diagnostics Tool, but it wanted me to insert a system disk on restart due to not finding the right files.
The only other issue that I can see is my Action Center has an hourglass sign and says "backup in progress". My daughter started this after the first BSOD and then it crashed again and was not able to finish the backup.
TIA for your time.

writhziden · 30 Jan 2012

Code:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\djkelsey\Windows_NT6_BSOD_jcgriff2\013012-27362-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c1d000 PsLoadedModuleList = 0xfffff800`02e62670
Debug session time: Mon Jan 30 15:54:00.226 2012 (GMT-7)
System Uptime: 0 days 0:10:22.990
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 80, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46485 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000080
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880094857f0 -- (.trap 0xfffff880094857f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000039b90008 rbx=0000000000000000 rcx=fffffa8003c01760
rdx=0000000000000081 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c91b65 rsp=fffff88009485980 rbp=fffff88009485a00
 r8=0000000000000080  r9=fffff6800000b198 r10=fffffa8003c01760
r11=fffff88009485be0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02c91b65 498b08          mov     rcx,qword ptr [r8] ds:b168:00000000`00000080=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c2cd7e to fffff80002c99c40

STACK_TEXT:  
fffff880`09485688 fffff800`02c2cd7e : 00000000`0000001a 00000000`00041287 00000000`00000080 00000000`00000000 : nt!KeBugCheckEx
fffff880`09485690 fffff800`02c97d6e : 00000000`00000000 00000000`00000080 fffffa80`044d0c00 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x46485
fffff880`094857f0 fffff800`02c91b65 : 00000000`00000002 fffff800`02caa44d 80000000`118f5867 fffff880`09485a00 : nt!KiPageFault+0x16e
fffff880`09485980 fffff800`02caa44d : 80000000`118f5867 fffff880`09485a00 fffff700`01080000 fffffa80`03fafa68 : nt!ExpInterlockedPopEntrySListFault16
fffff880`09485990 fffff800`02ca719e : 00000000`00000001 00000000`0163312e fffff880`09485be0 fffff680`0000b198 : nt!MiResolveDemandZeroFault+0x14d
fffff880`09485a80 fffff800`02c97d6e : 00000000`00000001 00000000`0163312e fffffa80`04508001 00000000`01600a50 : nt!MmAccessFault+0x5de
fffff880`09485be0 00000000`77b4676f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`02a0c960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b4676f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+46485
fffff800`02c2cd7e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+46485

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485

Followup: MachineOwner
---------

Possible causes are Memory problems... Drivers...

If you are overclocking any hardware, please stop.
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).
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.