BSOD error 0x0000001e

djlethal · 08 Sep 2011

hi there, im having a BSOD problem with my laptop. i hope i have provided enough information

im running;

-windows 7 64-bit
-OEM version
-i just bought my asus n53sv in July 2011

i was unable to run the system health report. this was the error that i got,

Error:

An error occured while attempting to generate the report.

The wait for the report generation tool to finish has timed out.

anybody able to help? thanks

seth500 · 08 Sep 2011

Uninstall asus software such as it's updating service and just the general bloatware it not necessary and is causing errors in your event viewer..

90% of the minidumps point to ntkrnlmp.exe which is hardware errors and they are pointed towards memory so please follow this guide and tell us the results:

RAM - Test with Memtest86+

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\Windows_NT6_BSOD_jcgriff2(1)\Windows_NT6_BSOD_jcgriff2\083011-20514-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0304a000 PsLoadedModuleList = 0xfffff800`0328f670
Debug session time: Mon Aug 29 13:06:06.964 2011 (UTC - 6:00)
System Uptime: 0 days 0:00:23.900
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, 0, 8, 0}

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

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+3234613965636636
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f9100
 0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  lsass.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880086786a0 -- (.trap 0xfffff880086786a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007d09875 rbx=0000000000000000 rcx=fffff88008677730
rdx=fffff88008679000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff88008678830 rbp=0000000000000002
 r8=fffff88008679000  r9=ffffffffc0000005 r10=fffff88008678830
r11=fffff88008676ea0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
00000000`00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003112588 to fffff800030c6c40

STACK_TEXT:  
fffff880`08677e18 fffff800`03112588 : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff880`08677e20 fffff800`030c62c2 : fffff880`086785f8 fffff8a0`0124ae74 fffff880`086786a0 fffff8a0`0024ace0 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`086784c0 fffff800`030c4e3a : 00000000`00000008 00000000`00000000 00000000`00000000 fffff8a0`0124ae74 : nt!KiExceptionDispatch+0xc2
fffff880`086786a0 00000000`00000000 : fffffa80`07d09830 fffffa80`07d16c10 fffff880`00000000 fffff8a0`0024ace0 : nt!KiPageFault+0x23a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4977d
fffff800`03112588 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4977d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4977d

BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4977d

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