BSOD, crashing

[Hoopster81]

Hey guys,

I've got a real frustrating problem. I've been getting the following message in the blue screen of death on a daily basis for the last few days.

A problem has been detected and Windows has been shut down to prevent damage to your computer.

DRIVER_IRQL_NOT_LESS_OR_EQUAL

It then recommends:
-checking newly installed software/hardware
-disabling BIOS memory options such as caching or shadowing

Finally, the last line is

Techincal Information:
*** STOP: 0x000000D1 (0x00760065, 0x00000002, 0x00000008, 0x00760065)



I did some research on the web, and some people suggested that this error was a sign of failing hardware. I ran Memtest86 - results were normal. The HD had been making weird noises for awhile, so I just replaced it to see if that was the problem. No dice.

I can't think of any new software I installed that coincided with the appearance of this problem, but I do install new software all the time. There is no common software/program that is running when this crashes as far as I know.

I got this computer back in April from Dell. It is a Dimension E510. I think Dell has a 12-month policy for returns. Would this qualify? I'd rather fix it myself, but I have no idea where to turn.

Any help would be greatly appreciated.

Thanks

 

[imported_nocturne]

Check the guide in my sig. The first outlines basic bsod debugging, and dclive's guide tells you how to debug your dump files.

 

[Hoopster81]

TY

The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error. Possible Resolutions: Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

I did recently purchase Norton Ghost. I can't remember if it was before the BSODs or after. The program was not updated, but it is now. I hope this is the answer.

 

[Hoopster81]

Well, after not crashing for a couple days, I just got the blue screen. I downloaded WinDbg and did File->Open Crash Dump, pointed it to the right file, but it didn't seem to work right. Does anyone have any ideas of what I need to do?


edit: The MEMORY.dmp file is almost 200MB. Is this normal?


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


Loading Dump File [C:\WINDOWS\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 ntkrpamp.exe -
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Nov 20 18:49:00.484 2006 (GMT-5)
System Uptime: 0 days 1:44:32.191
*********************************************************************
* 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 ntkrpamp.exe -
Loading Kernel Symbols
.................................................................................................................................
Loading User Symbols

Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {2, 2, 1, 894ec31c}

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

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command 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 : ntkrpamp.exe ( nt!Kei386EoiHelper+2834 )

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

 

[n7]

I have no idea what the .dmp files mean really, but BSODs are often caused by bad RAM.

Try running Memtest for a while to see if it can even pass that.

 

[Hoopster81]

Originally posted by: n7
I have no idea what the .dmp files mean really, but BSODs are often caused by bad RAM.

Try running Memtest for a while to see if it can even pass that.

Already did that. See OP.

On the crash screen, now it mentons "portcls.sys" under the Stop error.

But can anyone tell me why WinDbg isn't reading my dump file?