I just ran CHKDSK twice last night. I did not receive any errors. Also, I checked my connections to my SATA cord and they appear fine. I am starting to think that this is driver issue or something related to my graphic card.
I will soon post a list of processes running on my computer. Maybe that will help me discover the issue.
Thanks for the suggestions. Keep them coming.
You're missing these devices:
I have no clue what the first one is for - you'll have to check in Device Manager for that.Code:Null ROOT\LEGACY_NULL\0000 This device is not present, is not working properly, or does not have all its drivers installed. Not Available ACPI\AWY0001\2&DABA3FF&1 The drivers for this device are not installed.
The second one is the AMD Away drivers for your CPU
Is this a clean install, or did you upgrade from within Vista? It looks like a clean install (to me) due to the absence of any Dell stuff in the Program Groups section of MSINFO32
Please do the following to install the Vista version of this driver:
Also, after this is done, check in Device Manager to see if the other device is now detected.Compatibilty Mode Driver Installation
1 - Download the latest driver from the manufacturer's website ( Drivers and Downloads ).
2 - Uninstall the current drivers using the Control Panel...Programs and features...Uninstall a program applet. Then verify that the driver/device has been removed in Device Manager
3 - Right click on freshly downloaded driver installation file and select "Properties"
4 - Select the Compatibility tab - and do the following:
- Click on the "Change settings for all users" button
- Click on the box to select "Run this program in compatibility mode for" and then select Windows Vista Service Pack 1
- Click on the box to select "Run as administrator"
- Click on OK to exit all the dialogs
5 - Right click on the driver installation file and select "Run as administrator"
6 - Let it install and see if that stops the BSOD's.
The MSINFO32 file also shows a STOP 0x7F error on 12/26/09 at 12:14 AM
More info on the error here: BSOD Index
Please zip up the contents of the C:\Windows\Minidump folder - and then upload/attach the .zip file with your next post.
Placing the blame on the Windows kernel (ntkrnlpa.exe) is probably not correct. If it was, you'd be likely to be having a lot more problems other than the occasional BSOD.
The incorrect symbols message can be cause by the symbol path being incorrect (info on that in para E here: WinDbg Analysis Report ) or by a version of Windows that isn't supported by the Microsoft Symbol Server.
USASMA,
Yes, I did a clean install of Windows 7 Ultimate a while ago. I believe I installed all of the correct drivers for my dell machine.
I checked the Device Manager as you suggested and found the AMD Away Mode Driver not found. It lists the driver as an unknown device. This maybe the source of the problem.
There is another issue that I recently discovered. The AMD Away Mode Driver you sent was only capable for Windows XP & Windows Vista machines. I have windows 7 running on my pc so this file is no use to me. I am currently searching the right driver for my machine. If you find it before I do please post as soon as possible.
Lastly, I have noticed that my PC is running perfectly while in Safe Mode. I have not encountered a BSOD or a freeze of any kind while in this mode.
Well even though the driver is for XP or Vista I will follow your steps and let you know what happens. Thanks again.
Well I believe I have solved the AMD Away Mode driver. I followed your instructions and was able to get the driver loaded onto my PC. My device manager no longer shows an "unknown device" in the menus.
New MSINFO32
Attachment 43810
At this point there has not been a freeze for the past 2 hours!!!! But...the CPU now randomly shuts down (without the blue screen). This has happen twice in the last 30 minutes. I specifically checked the Startup & Recovery option and made sure that a system failure will NOT force an automatic restart.
Hopefully this "new" problem does not persist.
Never mind...the cpu just froze up a couple minutes ago. I had to physically shut it down again.
IS THERE NO END TO THIS MADNESS?
Did you install the Vista driver using the compatibility mode instructions in my last post?
Still waiting for the BSOD files I mentioned in my last post.
The unknown device is still present in the Problem Devices section of the MSINFO32 report. Dunno if it's got anything to do with your problems. Please check Device Manager for any problem devices present.
Yes, I followed your instructions and the Away Mode Driver is installed properly.
However, after looking at the hidden devices on the device manager I finally found the NULL driver and Security Processor Loader driver are not present or are not loaded properly.
I am not sure if this is the root of the problem or my graphics card. Remember in safe mode I do not encounter a freeze, a BSOD or a random reboot.
The reason I have not posted a minidump is because I have not experienced a BSOD today. Also, I accidently deleted the minidump from yesterday's experience. If I do see another BSOD, I will be sure to post the minidump asap.
Security Processor Loader is a very important component (spldr.sys). As I understand it, it's an important part of the OS. Please run SFC.EXE /SCANNOW from an elevated (Run as administrator) Command Prompt.
Keep an eye on it to see if it finds errors - if so, we'll need the CBS.log file.
If we start finding more OS errors, you may want to start considering a wipe of your hard drive with KillDisk or DBAN and then a clean install of Windows.
No error occurred while running SFC.EXE. I performed it twice just to make sure.
In last couple minutes I did receive another BSOD. I managed to capture the small dump.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
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 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a37000 PsLoadedModuleList = 0x82b7f810
Debug session time: Sat Dec 26 23:35:04.852 2009 (GMT-6)
System Uptime: 0 days 0:09:25.834
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
WARNING: Process directory table base AEB2E400 doesn't match CR3 00185000
*********************************************************************
* 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
PEB is paged out (Peb.Ldr = 7ffde00c). Type ".hh dbgerr001" for details
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 801de000, 0, 0}
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntkrpamp.exe ( nt!Kei386EoiHelper+17d4 )
Followup: MachineOwner
Quote