Physical memory dumping

Question

Physical memory dumping

Anonymous

System Information (local)

Hi folks,

Whenever my HP ProBook 4540s resumes from standby, the systems crashes and performs a full boot rather than resuming from standby.

I have changed the ram but no use.It gives me blue screen error that is "Physical memory dumping"

computer name: HP

windows version: Windows 8 , 6.2, build: 9200

windows dir: C:\Windows

Hardware: HP ProBook 4540s, Hewlett-Packard, 17F6

CPU: GenuineIntel Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Intel586, level: 6

4 logical processors, active mask: 15

RAM: 4170641408 total

*** * Crash Dump Analysis*

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 6/25/2015 9:08:08 PM GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: Unknown (0xFFFFF8A000434728)

Bugcheck code: 0xA (0xFFFFF8A000434728, 0x2, 0x0, 0xFFFFF80172D7337F)

Error: IRQL_NOT_LESS_OR_EQUAL

Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

A third party driver was identified as the probable root cause of this system error.

Google query: IRQL_NOT_LESS_OR_EQUAL

On Thu 6/25/2015 5:31:31 PM GMT your computer crashed

crash dump file: C:\Windows\Minidump\062515-20515-01.dmp

This was probably caused by the following module: watchdog.sys (watchdog+0x255D)

Bugcheck code: 0x10E (0x1D, 0xFFFFFA8007A0A640, 0xFFFFF8A004E3C8D0, 0x0)

Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL

file path: C:\Windows\system32\drivers\watchdog.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Watchdog Driver

Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.

The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

*** * Conclusion*

2 crash dumps have been found and analyzed.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

3 additional answers

Answer 1

We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

If you have any questions about the procedure please ask

Answer 2

Who crashed is wrong more often than it is correct

This crash was related to a HD I/O error. I would go the the HD maker, download and run, their hd checking utility and run CHKDSK

CHKDSK /R

Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found any data available on that sector might be lost so as usual backup your data.

Run CHKDSK /R from an **elevated (Run as administrator) Command Prompt**.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/

*See "CHKDSK LogFile" below in order to check the results of the test.*CHKDSK LogFile:

Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).

Copy/paste the results into your next post.

Answer 3

Ok SIR, i have changed the settings so that it compiles up mini minidump file.

well i used "who crash" to analyze the MEMORY.DMP it displayed following:

here is the mindump file link:

https://onedrive.live.com/redir?resid=73821FB6DD7F6BC%21118

Crash dumps are enabled on your computer.

On Mon 7/6/2015 6:23:10 AM GMT your computer crashed

crash dump file: C:\Windows\Minidump\070615-20202-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0xDCD10)

Bugcheck code: 0x7A (0xFFFFFFFFC05AA428, 0xFFFFFFFFC0000185, 0x5BC918C0, 0xFFFFFFFFB5485B7C)

Error: KERNEL_DATA_INPAGE_ERROR

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 7/5/2015 4:51:49 AM GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: Unknown (0xFFFFFFFFC06000C8)

Bugcheck code: 0x7A (0xFFFFFFFFC06000C8, 0xFFFFFFFFC0000185, 0x2425E884, 0xFFFFFFFFC0019000)

Error: KERNEL_DATA_INPAGE_ERROR

Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.

A third party driver was identified as the probable root cause of this system error.

Google query: KERNEL_DATA_INPAGE_ERROR

Answer 4

This Dump file is corrupt and contains no useful information. Please change your settings as described in the wiki to a small dump. It will be faster for you to upload and for us to download

You need to update to windows 8.1

icrosoft (R) Windows Debugger Version 10.0.10158.9 AMD64

Loading Dump File [C:\Users\zigza\Desktop\MEMORY.DMP]

Kernel Summary Dump File: Kernel address space is available, User address space may not be available.

************************************************************************

WARNING: Dump file has inconsistent set-bit count. Data may be missing.

************************************************************************

WARNING: Whitespace at start of path element

Error: Empty Path.

Symbol search path is: srv*E:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

Unable to read PsLoadedModuleList

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

KdDebuggerData.KernBase < SystemRangeStart

Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x00000000 PsLoadedModuleList = 0x82b93810

Debug session time: Sun Jul 5 00:51:49.607 2015 (UTC - 4:00)

System Uptime: 0 days 0:59:14.544

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

Unable to read PsLoadedModuleList

**************************************************************************

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

**************************************************************************

KdDebuggerData.KernBase < SystemRangeStart

Loading Kernel Symbols

Unable to read PsLoadedModuleList

No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.

GetContextState failed, 0x80004002

CS descriptor lookup failed

GetContextState failed, 0x80004002

Unable to get program counter

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c06000c8, c0000185, 2425e884, c0019000}

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 1

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 2

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 3

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004002

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Unable to get current machine context, HRESULT 0x80004002

GetContextState failed, 0x80004002

Answer 5

Anonymous

https://onedrive.live.com/redir?resid=73821FB6DD7F6BC%21118

link to memory dump file

i have uploaded it on one-drive pl find solution.

0 comments

Share via

Physical memory dumping

3 additional answers