Solved Laptop crashed with Blue screen

[brummyfan]

Hi,
I got Blue screen and a crash, crash dump file created but I am unable to make anything of it, any help appreciated, Thanks.

 

[Arc]

Hi brummyfan.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff6800008a6e0, c66000000dedb847, fffff6800008b6e0}

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

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

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

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

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000307ebe6 to fffff800030d2bc0

STACK_TEXT:  
fffff880`09666668 fffff800`0307ebe6 : 00000000`0000001a 00000000`00000403 fffff680`0008a6e0 c6600000`0dedb847 : nt!KeBugCheckEx
fffff880`09666670 fffff800`03103e27 : fffff800`0324de00 fffff680`0008aef8 fffffa80`0c94ab30 fffff880`096668e8 : nt! ?? ::FNODOBFM::`string'+0x3211c
fffff880`09666820 fffff800`030bf3df : fffffa80`00000000 00000000`115dffff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`096669e0 fffff800`030d1e53 : ffffffff`ffffffff 00000000`0020dbf0 00000000`0020dbe8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`09666ae0 00000000`76da149a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020dbb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da149a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3211c
fffff800`0307ebe6 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3211c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3211c

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+3211c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_403_nt!_??_::fnodobfm::_string_+3211c

FAILURE_ID_HASH:  {bb27b598-7b95-8c3f-f3ab-762f6d4e2def}

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

 

[brummyfan]

Thanks Arc, I will follow the instructions and report back.

 

[brummyfan]

Hi Arc,
I have run memtest and found no errors in 8 passes, I have tried enabling Driver verifier and no crashes, so far the system looks stable and no crashes, I'll leave as it is and come back if I find any more problems, Thanks again for your timely help, much appreciated.

 

[Arc]

No problem mate.

Let us know for any further issue.