Hi,
So far today I have been getting many BSODs and have traced the problem down to the ntoskrnl.exe. I have tried to find fixes for it but have had no luck. I found one but it wouldn't work since I was running a 64 bit system. I am on Windows Vista Ultimate 64bit. Here are my specs.
AMD athlon 4000+ 64 2.6ghz
Asus M2A-VM motherboard
CORSAIR XMS2 4GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model TWIN2X2048-6400C5DHX

Under I will post my minidump
Thanks for any help its appreciated

Loading Dump File [C:\Windows\Minidump\Mini021808-29.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Vista Kernel Version 6000 UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`01999e90
Debug session time: Mon Feb 18 17:20:45.180 2008 (GMT-5)
System Uptime: 0 days 0:07:16.836
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
........................................................................... .........................................................
Loading User Symbols
Loading unloaded module list
......
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff800018506be}

***** 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 : ntoskrnl.exe ( nt+4e250 )

Followup: MachineOwner

Though significant the probable cause of ntoskrnl.exe is too general for specific answers.

However, it what you posted there is listed the 0x7F error and hardware failures are the most common cause and, of these, memory hardware failures are the most common.

I suggest you run MemTest for a minimum of 7 passes. if you have any errors you have corrupted memory that will need to be replaced. I also suggest that if you do get errors you then run the test individually to see what stick(s) are needing tobe replaced.

One other thing, a number of people who have come here recently have had RAM issues not because their memory was bad but because their memory timings/voltage was causing instability.

If you are overclocking your RAM you may want to first easing off of your timings and see if stability returns.

Ran memory test and it said it was fine. How could I tell if voltage ect was causing anything???

If you haven't overclocked then I would say your motherboard has automatically set the voltage and timing.

Speaking of motherboards, ASUS make great mobos but they are picky about RAM. I suggest going to ASUS' website, look up your motherboard and see what memory is recommended for your board.

If you can, attach your minidumps to your next posting. The most recent first.

ataport.SYS is newest error. I tried fix voltage setting still gets BSOD but in safe mode I never get it.

Attached Files

MiniDump.zip (97.2 KB, 1 views)

Now it keeps crashing more and more can't find a fix for it

ataport.sys errors and Vista have been causing many people headaches. It is part of the Vista OS and it has to do with controlling your SATA optical drive.

Here is a link from MS on how to fix it. Let us know if it works.

http://support.microsoft.com/kb/928253

I sent in a request for the hotfix do u think that could be the thing causing all my problems???

That is what your minidumps are reporting and if you google that driver with Vista you'll see many people having issues with it.

Please keep us informed of how it goes.

The hotfix decreased my BSOD's big time but I am still getting them here is my minidumps since i installed the fix thanks for the help by the way.

Attached Files

Minidump.zip (94.8 KB, 4 views)

You have several different error codes. Some are pointing to device drivers while others lean towards hardware. Try the following:

1. Run chkdsk.

2. Run a harddrive diagnostics.

3. When you ran MemTest did you run it for a minimum of 7 passes?

4. Are you running the onboard video or had disabled that in the BIOS and are running a PCI-e video card?

5. Try updating your chipset drivers.

6. Did you build this and if so did you install the Ant-virus that came with the motherboard?

7. What security software are you running?

I built this computer and since I installed the hotfix I rarely get any BSOD's I didn't install the anti virus and am not running any at the time I ran 7 passes all passed umm i ran the chkdsk and it made my explorer crash. I am running a 2600XT PCIe not using onboard but since the hotfix it is alot more stable.