Memory Crash Dump (BSOD, Product 768_1)

I am at a loss as to how to resolve this issue. I have run memory checks, even re-seated the RAM cards, but to no avail.

When trying to shut down the computer, I encounter a BSOD with a memory crash dump that soon goes to a login screen. I am unable to shutdown, except via Safe Mode.

I have perused some older posts but there seems to be unique reasons for the problems, like specific drivers.

The key that I have seen, is that you experts have been able to open the dmp file and peer into the reason (driver) causing the problem. Can you kindly do the same for my case?

I have attached a copy of the latest (today) dmp file in zip format.

Thank you for your help.

How can I read a .dmp file that persistently happens on my computer while trying to shutdown?
I'd like to sift through its contents to determine what the problem may be.

Any help would be great.

Thanks.

Jonathan_King said:

This should show you enough to get you started: https://www.sevenforums.com/crash-loc...ing-tools.html

I want to learn and, in time, also give back to the group, so will eagerly do this, for myself first. I will kindly ask for your assistance or to help me interpret the results. Much thanks!

There is a great feeling about knowing what to do when confronted with a problem that initially seems insurmountable. I installed the Debugging Tools for Windows, and did my first dump analysis on my own issue. And, I believe that I identified the problem, but would like your opinion.

The short version of the analysis is:

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


Loading Dump File [I:\040510-20233-01 - Copy.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`0324ae50
Debug session time: Mon Apr 5 19:50:27.137 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:51.339
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\system32\DRIVERS\ndasfs.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ndasfs.sys
*** ERROR: Module load completed but symbols could not be loaded for ndasfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8000308e4e0, fffff880043d25a8, fffff880043d1e00}

Probably caused by : ndasfs.sys ( ndasfs+517de )

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

It shows a problem with the driver for NDAS, my attached external HD unit, that I use as a network and backup hard drive.




I will disable the unit, and its driver and then perform the shutdown sequence that resulted in the memory dump and BSOD, to determine if that was the cause.


Is this a correct analysis, Jonathan? Am I interpreting this properly (even if it states that the symbols could not be loaded for ndasfs.sys)?





PS: Jonathan, Thanks for pointing out the "secret" MS tool that apparently the email tech support people at HP don't know about, 'cause they were really hopeless with 5 days of trying to get them to figure it out. Absolutely useless.



And, this is THE best forum of people, devotees and all-around nice guys to help out with seemingly "insurmountable" problems. So, am "paying forward" to help someone's problem: next!

Thanks in large part to the expert devotees of this Windows Seven Forum, my problem has been fixed. This group is even quoted and hyperlinked in the Microsoft Answers website. Now how good is that? That's very complimentary.

With your guidance, Jonathan, I was able to help myself to an analysis that lead to the fix. For future sufferers of the same issue, the driver needs to be updated from Ximeta's website ( Download Center - NDAS Software for Windows ), for the network/USB NDAS hard drive.

If you run into problems, I will gladly assist.

In the course of this analysis, I came across another tool that I will recommend on the page in this forum that you led me to initially, Jonathan, and that will help users with another tool.

You guys did what HP could not even come close to do!!!