Event 41 kernel power 63

mediator

New Member
Hi,

My computer freezes randomly. The error in event viewer is "event 41 kernel power 63". I had tried windbg. I am neither a developer, nor an expert. I am new to this forum. Below is the code generated from whatever little analysis I could do.

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


Loading Dump File [C:\Apps\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.23569.amd64fre.win7sp1_ldr.161007-0600
Machine Name:
Kernel base = 0xfffff800`03656000 PsLoadedModuleList = 0xfffff800`03898730
Debug session time: Sat Nov 26 22:08:54.071 2016 (UTC + 5:30)
System Uptime: 0 days 21:12:13.945
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
.....................Page 1d3664 not present in the dump file. Type ".hh dbgerr004" for details
...........Page 1d16a4 not present in the dump file. Type ".hh dbgerr004" for details
............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.........

************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffffa8009b685f4, fffff880207cbb40, 0}

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for em018_64.dat -
*** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : em018_64.dat ( em018_64+225f4 )

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


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffffa8009b685f4, Address of the instruction which caused the bugcheck
Arg3: fffff880207cbb40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\ntoskrnl.exe\57F7B8335e6000\ntoskrnl.exe
The system cannot find the file specified.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80003656000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5829848c

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

FAULTING_IP:
em018_64+225f4
fffffa80`09b685f4 6642394c3818 cmp word ptr [rax+r15+18h],cx

CONTEXT: fffff880207cbb40 -- (.cxr 0xfffff880207cbb40;r)
rax=ffffffffb9b6bc9a rbx=000000001aaebda2 rcx=000000000000020b
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000061073000
rip=fffffa8009b685f4 rsp=fffff880207cc520 rbp=00000000000f3000
r8=0000000000000000 r9=0000000000000000 r10=0000000061080000
r11=0000000000000000 r12=fffff880207cc5b0 r13=fffffa801147fa08
r14=00000000000f3000 r15=0000000060f80000
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210283
em018_64+0x225f4:
fffffa80`09b685f4 6642394c3818 cmp word ptr [rax+r15+18h],cx ds:002b:00000000`1aaebcb2=????
Last set context:
rax=ffffffffb9b6bc9a rbx=000000001aaebda2 rcx=000000000000020b
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000061073000
rip=fffffa8009b685f4 rsp=fffff880207cc520 rbp=00000000000f3000
r8=0000000000000000 r9=0000000000000000 r10=0000000061080000
r11=0000000000000000 r12=fffff880207cc5b0 r13=fffffa801147fa08
r14=00000000000f3000 r15=0000000060f80000
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210283
em018_64+0x225f4:
fffffa80`09b685f4 6642394c3818 cmp word ptr [rax+r15+18h],cx ds:002b:00000000`1aaebcb2=????
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffffa8009b644b5 to fffffa8009b685f4

STACK_TEXT:
fffff880`207cc520 fffffa80`09b644b5 : fffffa80`0781e600 00000000`00000000 fffffa80`0781e6f8 00000000`00000000 : em018_64+0x225f4
fffff880`207cc590 fffffa80`09b6410d : fffffa80`5f7f20e8 fffffa80`1147fa08 fffff880`207cc858 fffffa80`0781e6f8 : em018_64+0x1e4b5
fffff880`207cc600 fffffa80`09b6e79c : fffffa80`09a674b8 fffff800`03879bc0 fffff880`207cc858 fffffa80`0781e6f8 : em018_64+0x1e10d
fffff880`207cc670 fffff880`0472c935 : 00000000`00000001 fffffa80`09a674b8 fffff800`03879bc0 fffff8a0`0036e4e0 : em018_64+0x2879c
fffff880`207cc6d0 fffff800`039ebcb8 : 00000000`00000000 00000000`00000001 fffff800`03879bc0 00000000`00000000 : ehdrv+0x1c935
fffff880`207cc700 fffff800`039eb9f2 : fffffa80`0781e6a0 fffffa80`111e2d28 fffffa80`078acd20 00000000`00000001 : nt!FsRtlReleaseFile+0x1468
fffff880`207cc760 fffff800`039e7ba7 : fffffa80`078acce0 fffffa80`111e2b10 fffff880`207cca10 fffff880`207cca08 : nt!FsRtlReleaseFile+0x11a2
fffff880`207cc8b0 fffff800`039e7eae : ffffe46b`00000004 fffffa80`111e2b10 fffff880`207cca10 00000000`00000021 : nt!ObCheckObjectAccess+0x25f7
fffff880`207cc9a0 fffff800`036c5693 : 00000000`000007ac fffffa80`1107eb50 00000000`0025e008 00000000`00000001 : nt!NtMapViewOfSection+0x2be
fffff880`207cca70 00000000`76dbbfba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x3a23
00000000`0025dfe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76dbbfba


FOLLOWUP_IP:
em018_64+225f4
fffffa80`09b685f4 6642394c3818 cmp word ptr [rax+r15+18h],cx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: em018_64+225f4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: em018_64

IMAGE_NAME: em018_64.dat

STACK_COMMAND: .cxr 0xfffff880207cbb40 ; kb

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

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

I'd be grateful, if anyone can help me out.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi Mediator,
it's best if we have the actual dump files in order to debug. If you use the application in this thread it will collect the data for you. All you need to do is zip it up (unless it already is) and post:
How to ask for help with a BSOD problem

I did have a quick look at your posted details and that dump file is blaming Eset AV. Try either updating it or removing to test.
 

mediator

New Member
Hi Kemical,

The dump file is about 1 GB. I tried the application from this forum. But the dump file is not found in "C:\Windows\Minidump" or "C:\Windows". I had a hunch regarding Eset. I will remove this. Thanks for confirming. Let me know where else I can find the created minidump file created with W7F Diagnostic Tool.

Thank you.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi,
if there isn't an actual dump file then you may have to change settings so they are produced.
Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

If however you do have dump files but the application didn't pick them up make sure your running it as administrator. If it still won't find them but you know where they are you can always zip them up and post.
 

mediator

New Member
Hi Kemical,

I tried your fix for dump file. But I have given "C:\Apps" as the directory. But there is no memory dump in that location also. I ran that application as admin only.

Also, the crash appears, whenever I try to put laptop into sleep mode. It works fine in hibernate mode.

Thank you.
 
Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi,
sorry I didn't realise you had posted back, must have missed the prompt... Odd. Anyhoo, dump files are usually found in the Minidump folder located in the main Windows folder.
Why not have a quick look inside the folder yourself?

If you cannot find any dump files then you will just have to wait until you bsod again. (making sure your settings match the parameters I outlined above)

Where is the dump file you copied and pasted from?

Send that if you have it.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffffa8009b685f4, fffff880207cbb40, 0}

Page 1d3664 not present in the dump file. Type ".hh dbgerr004" for details
Page 1d3664 not present in the dump file. Type ".hh dbgerr004" for details
Page 1d16a4 not present in the dump file. Type ".hh dbgerr004" for details
Page 1d16a4 not present in the dump file. Type ".hh dbgerr004" for details
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for em018_64.dat -
*** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
Probably caused by : em018_64.dat ( em018_64+225f4 )

Followup:     MachineOwner

Code:
FAILURE_ID_HASH_STRING:  km:x64_0x3b_'em018_64'+225f4

Debugger error dbgerr004 displays the message "Page 'number' not present in dump file." This error indicates that the debugger needed a memory page that was not included in the dump file being debugged.

Hi,
Bugcheck 3B This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. GPU drivers are often the main culprit but we see from the above probable cause is:
em018_64.dat Mon Nov 14 09:31:56 2016: ESET Smart Security. I think you have already removed this application so just monitor the situation.

Looking over your system drivers they could do with updating. I checked your support page over at Dell and there are later drivers to be had. They are a couple of years later but some like the chipset drivers improve performance:
Enhancements
- Enhanced WHQL, Intel PV
- BIOS new release ME FW 1164
- Enhanced performance
Ref:
Intel Management Engine Interface Driver Driver Details | Dell UK

Support for XPS 15 L502X
Support for XPS 15 L502X | Dell UK


Post any new dump files
 

mediator

New Member
Hi Kemical,

Thank you so much for looking into this.

I had done a drivers update last week through Dell's System Detect. It updated the necessary drivers, and also the BIOS. The driver (R292317) you showed is in my download's folder. So I believe it was updated as well. I am running without an antivirus right now. So lets see as I'm monitoring the situation. But the system gives BSOD and crashes whenever I close the lid or activate 'Sleep' mode. I'm using hibernate as an alternative.

Thank you.
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
. I am running without an antivirus right now
Hmm... That's not really advisable. You at least want something and to that end try running something like MSE as it's very stable.
system gives BSOD and crashes whenever I close the lid or activate 'Sleep' mode. I'm using hibernate as an alternative.
Is it possible for you to post a dump file from the associated blue screen?
 

mediator

New Member
Hi,

I'll be installing AV after a week may be. Till then I don't want to install anything so as to zero in to the problem.

I tried sleep mode again, and it crashed without creating any dumps. So I have uploaded a capture of BSOD.

Thank you so much.
 

Attachments

  • DSC_0569[1].JPG
    DSC_0569[1].JPG
    2.6 MB · Views: 322

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi,

I'll be installing AV after a week may be. Till then I don't want to install anything so as to zero in to the problem.

I tried sleep mode again, and it crashed without creating any dumps. So I have uploaded a capture of BSOD.

Thank you so much.
Can you post the actual dump file please. As I said before we need to see the original dump files so we can debug them.
 

mediator

New Member
The dump file I shared earlier is the only file that has been created so far. I have tried to reproduce BSOD using Sleep, but it doesn't create any dump file. What to do? If it gets created, then I'd gladly share.
 

mediator

New Member
I did. But it just does not create any dumps. It fails. The problem is in sleep mode. I have also found that my HDD has developed a few bad sectors. Can that be a cause of the problem?

I may get a new SSD for my L502x system. What do you suggest, which SSD should I get?
 
Last edited:

kemical

Windows Forum Admin
Staff member
Premium Supporter
Hi,
there can be a number of reasons for no dump file creation and a failing HDD is a prime candidate. I'm not saying your hard drive is actually failing but it is a possibility.

Try running a chkdsk making sure whichever method you use from the guide that you search for and repair broken sectors:
How to Fix Hard Drive Problems with Chkdsk in Windows 7, 8, and 10

If the chkdsk fails to run or can't repair, then run Seatools for Windows as this will check if it's a viable drive:
How to use SeaTools for Windows

What do you suggest, which SSD should I get?
A good all round SSD is the Samsung 850 I use a 500GB model for my main drive and they are extremely fast.
 

mediator

New Member
Hi Kemical,

I did run chkdsk. It did repair a few bad sectors. But anyways, I have Linux installed too for many years. I'll do some analysis there as well. Everything runs fine there though. But lets see.

You have been of tremendous help. Thank you so much. :)
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Your very welcome. It might be an idea to run Seatools anyway as this will give you a definite pass or fail. In any case please let me know how you get on.. :)
 

mediator

New Member
Sure. I'll give Seatools a shot as well. Is there any setting you want me to run it on? Also, how do you evaluate "Seagate ST1000LM014 1TB Laptop Solid State Hybrid Drive"? Its been 2-3 days that I uninstalled ESET. I have not received any random BSODs. But yes, if I do sleep mode, then its confirmed that I'll get a BSOD.

I'll be running Seatools tomorrow when I'm out for work.

Thank you!!!
 

kemical

Windows Forum Admin
Staff member
Premium Supporter
Sure. I'll give Seatools a shot as well. Is there any setting you want me to run it on?
Not really just click start.
how do you evaluate "Seagate ST1000LM014 1TB Laptop Solid State Hybrid Drive
Do you mean what do I think of Seagates 1TB Hybrid drive? I've never used one to be honest but Seagate is a brand you can usually trust.
 
Top