Multiple BSOD with Vista

[ribabe8]

Hello, I am new to this,I am looking for some help, I keep getting the BSOD constantly. I am using Windows Vista. I am enclosing a copy of the last .dmp file. I keep getting the BSOD either saying, MEMORY_MANAGEMENT, PAGE_FAULT_IN NON_PAGED_ERROR or KERNEL_STACK_IN_PAGE_ERROR.

Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini020709-01.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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sat Feb 7 18:30:11.916 2009 (GMT-5)
System Uptime: 0 days 0:20:55.639
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
...
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 00000000, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: 8240dc90, address of signature on kernel stack
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: 81c00000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b550
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
BUGCHECK_STR: 0x77_1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81ccccb9 to 81cd8781
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
826abcb4 81ccccb9 00000077 00000001 00000000 nt+0xd8781
826abd38 81cccd15 833623e8 826abd58 00000000 nt+0xcccb9
826abd6c 81cb3a57 83362458 00000000 826abdc0 nt+0xccd15
826abd7c 81e25556 00000000 826a0680 00000000 nt+0xb3a57
826abdc0 81c915fe 81cb39d4 00000000 00000000 nt+0x225556
00000000 00000000 00000000 00000000 00000000 nt+0x915fe

STACK_COMMAND: kb
FOLLOWUP_IP:
nt+d8781
81cd8781 8be5 mov esp,ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+d8781
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------



If someone can help, I would greatly appreciate it.

Thanks

 

[Route44]

0x00000077: KERNEL_STACK_INPAGE_ERROR
A page of kernel data requested from the pagefile could not be found or read into memory. This message also can indicate disk hardware failure, disk data corruption, or possible virus infection.

Since your errors could be caused by several things try the following standard diagnostic steps:

A. Run Memtest on your RAM.

1. Go to www.memtest.org and download the latest ISO version. It is free and perfectly safe.

2. Burn to a CD.

3. Place CD in your drive and reboot with CD in drive. The test will take over.

4. Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

5. If you have errors you have corrupted memory and it needs to be replaced.

6. Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


B. Scan for Infections.


C. Run a full harddrive diagnostics on your harddrive. You'll find a free utility from your harddrive manufacturer's website to do this. Seagate's SeaTools will work with many brands.


D. Run ChkDsk.


*** Get back to us with your results.

 

[ribabe8]

Hello, thanks for your response. I have already done a full Norton Anti - Virus scan and that came back fine. I have done the CHKDSK and have already defragged the memory and the registry. When I went to defrag the hard drive, that is the last time I got the BSOD saying KERNEL_STACK_INPAGE_ERROR. I have downloaded the memtest, I am going to do that later. By any chance, do you know what "ntkrnlpa.exe" does, I saw that show up alot in all the .dmp files. Thanks for your help.

 

[Route44]

That is a core Windows driver and does many critical functions. By the way, nice proactive diagnostic work. I am not certain but my suspicion at this moment is that it might be your harddrive. I would back up all of your essential information as soon as possible. Better to be cautious than sorry.

 

[ribabe8]

Hello, since yesterday I have ran memtest for 6 passes and there were no errors. I also downloaded the harddrive diagnostic from Western Digital. I have tried it 3 times, it gets halfway through & the computer reboots itself, there is no BSOD it just reboots. Could it be that the problem is the harddrive?

Thanks

 

[Route44]

Hello, since yesterday I have ran memtest for 6 passes and there were no errors. I also downloaded the harddrive diagnostic from Western Digital. I have tried it 3 times, it gets halfway through & the computer reboots itself, there is no BSOD it just reboots. Could it be that the problem is the harddrive?

Thanks

Yes, it could very well be. What harddrive tests did you run? The reason I ask is because I strongly suggest you go to the Storage and Networking forum here and tell them what has happened when you attempted to diagnose your disk three times and how it rebooted.

Ask them for advice. And as I said before, I would A.S.A.P. back up all of your important stuff because if the harddrive is failing and it crashes data retrieval is very expensive.

 

[ribabe8]

Hello, the test I had ran was the Western Digital Data LifeGuard Diagnostic - DLGDIAG for Windows - Version 1.09b. I have a Western Digital Scorpio Bloe 160 gb harddrive.

Thanks

 

[Route44]

Okay, then look at my previous post and take that advice. Back up your information onto CD/DVD and then go to the Storage and Network forum and post there that you've attempted to run a harddrive diagnostics on three separate occassions and the outcome.

It sounds like your harddrive is failing.

 

[ribabe8]

Hello, I have already posted a thread in the Storage & Networking Forum about the harddrive. I'll see if I can back this up by cd or dvd, but it might not work, I was burning dvd's when this all started to happen & I stopped doing that because of the BSOD's.

Thanks

 

[Route44]

Okay, then if CD/DVD burns don't work try backing up with flash drives.

 

[ribabe8]

Hello, I just got a response from Storage & Networking forum and they also said that it is a bad harddrive. I am going to get flash drives today to back up all my files. I have a 40 gb external harddrive but when my dog was a puppy he chewed up the usb cable and I can't find the cable for the external harddrive.

Thanks