New
#11
Thanks for fast response!
My complete spec has been updated with SystemInfo.exe and here is my CPU-Z screenshot. I also get another BSOD yesterday, both on attachment.
Thanks for fast response!
My complete spec has been updated with SystemInfo.exe and here is my CPU-Z screenshot. I also get another BSOD yesterday, both on attachment.
Memory_Management 1A,.
We should wait for a reply from Britton30.
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41284, ff6001, 0, fffff70001080000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ac3 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000041284, A PTE or the working set list is corrupt. Arg2: 0000000000ff6001 Arg3: 0000000000000000 Arg4: fffff70001080000 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_41284 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: SystemInfo.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000311fa63 to fffff800030c8f00 STACK_TEXT: fffff880`07aac8e8 fffff800`0311fa63 : 00000000`0000001a 00000000`00041284 00000000`00ff6001 00000000`00000000 : nt!KeBugCheckEx fffff880`07aac8f0 fffff800`030f9c15 : fffff700`01080000 df100000`322f8867 00000000`20206f49 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4ac3 fffff880`07aac930 fffff800`0310ac4a : 00000000`00000000 00000000`00ffffff fffffa80`00000000 fffffa80`07dee390 : nt!MiDeleteVirtualAddresses+0x4cc fffff880`07aacaf0 fffff800`030c8153 : ffffffff`ffffffff 00000000`0015d518 00000000`0015d510 000007ff`00008000 : nt!NtFreeVirtualMemory+0x5ca fffff880`07aacbe0 00000000`7774009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0015d3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7774009a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+4ac3 fffff800`0311fa63 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4ac3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3 BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3 Followup: MachineOwner ---------
Attachment 246629
I suspect the RAM is not compatible with each other since they are different brands with differing specs. For a test, use your system normally with only one stick installed. If it is fine, try with the other RAM. If no BSODs or other issues, get a kit of matched RAM.
You should update to SP1 too.
Yeah, Driver Seewper was replaced by the less effective Driver Fusion. The link in my sig for Driver Sweeper is a direct download form SF if you would like to use it.
I'm not sureAnd I have another problem (low GPU usage) on this laptop, maybe both are related?
Did you try each RAM module in each slot for memtest for 7 passes? One slot may be bad. You should try the ASUS site for the GPU drivers, they may have a specific one for the lappy.
You should also get a matched set of RAM.
Yes it does show memory management 1A.
Please post the following report as well:Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {5003, fffff70001080000, 133e, 74246005} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+297b1 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY_MANAGEMENT (1a) # Any other values for parameter 1 must be individually examined. Arguments: Arg1: 0000000000005003, The subtype of the bugcheck. Arg2: fffff70001080000 Arg3: 000000000000133e Arg4: 0000000074246005 Debugging Details: ------------------ BUGCHECK_STR: 0x1a_5003 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: AvastSvc.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000313526c to fffff800030c5f00 STACK_TEXT: fffff880`05cf57a8 fffff800`0313526c : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000133e : nt!KeBugCheckEx fffff880`05cf57b0 fffff800`030f7f2b : 00000000`2e85b8c0 00000000`2e85b921 fffffa80`008b9110 0000000f`ffffffff : nt! ?? ::FNODOBFM::`string'+0x297b1 fffff880`05cf5840 fffff800`030ec599 : 00000000`00000000 00000000`2e85b8c0 00000000`1b17b867 fffffa80`06227ec8 : nt!MiResolveTransitionFault+0x33b fffff880`05cf58d0 fffff800`030e1d9e : 00000000`00000000 00000000`15811fa4 fffff680`000ac088 fffffa80`06227ec8 : nt!MiResolveProtoPteFault+0x419 fffff880`05cf5970 fffff800`030dff23 : ffffffff`ffffff00 00000000`15811fa4 00000000`00000002 00000000`00000000 : nt!MiDispatchFault+0x1de fffff880`05cf5a80 fffff800`030c3fee : 00000000`00000000 00000000`0003c3d4 00000000`00000001 00000000`fff80001 : nt!MmAccessFault+0x343 fffff880`05cf5be0 00000000`69bdeea3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e 00000000`09023000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x69bdeea3 STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+297b1 fffff800`0313526c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+297b1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+297b1 BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+297b1 Followup: MachineOwner ---------