Windows Vista Vista 64 BSOD probably caused by ntkrnlmp.exe

I have had recent problems with Vista freezing up. It is not always while doing the same thing and anything exact I can pinpoint. Many times IE is open, but not sure if it is related. Not every time I get a BSOD, but the computer totally freezes and must do hard shutdown with power button. I did have a few BSODs which related to system file I found while Norton was doing inactive backbground scans. I stopped those scans and thought I had fixed my problem. However, the computer is still freezing with occasional BSOD. Sometimes the freezes occur while trying to awake computer from sleep mode. The most recent was related to ntskrnlmp.exe and here is the minidump file. Any help would be appreciated!!


Loading Dump File [C:\Windows\Minidump\Mini042311-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02609000 PsLoadedModuleList = 0xfffff800`027cddd0
Debug session time: Sat Apr 23 09:49:05.850 2011 (GMT-4)
System Uptime: 1 days 2:34:46.317
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 0, 0, fffffa600cea8230}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3335d )

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

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: 0000000000000001, (page was retrieved from disk)
Arg2: 0000000000000000, value found in stack where signature should be
Arg3: 0000000000000000, 0
Arg4: fffffa600cea8230, address of signature on kernel stack

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

BUGCHECK_STR: 0x77_1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800026c8ea7 to fffff80002663490

STACK_TEXT:
fffffa60`01940b78 fffff800`026c8ea7 : 00000000`00000077 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffffa60`01940b80 fffff800`026a2fad : fffffa80`06c79060 fffffa60`01940ca0 00000000`00000000 fffffa80`06c79060 : nt! ?? ::FNODOBFM::`string'+0x3335d
fffffa60`01940c80 fffff800`026a2c8b : fffff800`026a2850 fffffa80`03c8e3d0 00000000`00000000 00000000`00000080 : nt!MmInPageKernelStack+0x41
fffffa60`01940ce0 fffff800`026a28e4 : 00000000`00000000 00000000`00000080 00000000`00000000 00000000`00000000 : nt!KiInSwapKernelStacks+0x2b
fffffa60`01940d10 fffff800`0286df77 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KeSwapProcessOrStack+0x94
fffffa60`01940d50 fffff800`026a0636 : fffff800`0277c680 fffffa80`03ccb720 fffff800`02781b80 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffffa60`01940d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+3335d
fffff800`026c8ea7 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+3335d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4cb7275f

FAILURE_BUCKET_ID: X64_0x77_1_nt!_??_::FNODOBFM::_string_+3335d

BUCKET_ID: X64_0x77_1_nt!_??_::FNODOBFM::_string_+3335d

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

 

Just some points I would make...

Have you checked other dump debugs? If this is a one-off, it could lead us in the wrong direction. Check other dumps for anything "consistent ". As you mention, check "Probably caused by ", but also "Process Name" for anything repetitive in the reports. As you can guess, they won't be exactly the same each time, but you need to find anything that keeps getting reported repeatedly.

It is a mini-dump, you need to set it for a full dump (Help and Support should tell you how to make the settings).

If it doesn't "blue-screen" and just freezes, I check for a overheating problem first. Has the inside of the computer case been cleaned out regularly/recently? (Has dust built up in the cooling fins of heatsinks?). If it "freezes" you can check in Event Viewer to see if there were problems prior to the freeze.

The BSOD you have quoted is a "bad" one in my opinion. Lots of zeros. It talks about not being able to communicate with the SCSI controller (computers can see the SATA controller as "SCSI "). It talks about relating to the hard disk drive controller, but those zeros in the Arguments and Stack Text might lead me to check the RAM (Vista has a RAM test and take a look in my signature). The processes involved might lead me to suspect that the system just has "stopped" or frozen, but slowly enough to generate a dump file.

Matt

 

Thanks for the reply... I did some checking into the areas you mentioned. There were no Windows problems reported on the day of the BSOD. I did notice that Internet explorer had several problems however on different days. Several more recent ones were related to Flash10p or Flash10m.ocx. Then others previously were different; had several with seanote.dll_unloaded, and a couple with mshtml.dll.

I haven't had any BSODs since this last one, and not really any "freezes" either. I did the Vista memory test which came back fine. The most recent bsod before this one was Iastor.sys and I had many problems reported in vista with Norton background checks at that time... My computer would "freeze" during these scans and had to power down.

I disabled the norton background checks and the freezing has been much better since then! I'm not too sure if most of the freezing now is not related to Internet Explorer.. However, not sure if the BSOD was related. I also get BSOD a lot if I leave my SD card in my card reader too long, but this was not the case last time.

This is a laptop I am using and have chillmat running all the time with it. I will look into the temperature issue however. I'll find a program to read temps for me and update later if that is an issue. Thanks

 

If you suspect programs, I would uninstall them and get the most recent download. Some of those files appear to relate to Adobe Flash Player, so uninstall it in Control Panel -> Programs and Features, then get the latest version. You talk about Norton, after a while Norton can get very "patched ", I have often uninstalled and reinstalled it with the most recent version. Try using a different browser (like Firefox) to test if IE is the problem.

 

I haven't figured out what may be causing the problem... I had the exact same BSOD and dump file just a few minutes ago. Was just surfing on a website. I have 3 different temp monitors going right now which say 46,47,48 degrees on the CPU.... They have read 55 but drop and go up constantly, so not sure if heat is a problem.

Almost leaning toward backing up everything and doing a reformat...

 

Thanks Arie,
I looked over that site and I have vista so no dr Watson. Couldn't find any specific program dumps and no new information in windows problem reports. The last bsod had the exact dump as my original post so I did not repost it.. I haver had any more bsod since the last on.

I uninstalled norton and reverted ie back to version 8 and try to avoid it. "freezes" have slowed down but still happen but seem to most often be when the computer is possibly trying to go into or out of sleep mode

 

The main information in Arie's link should work. The reference to Dr Watson does relate to Win XP, but you won't have any dumps saved for Dr Watson (there are different places dumps can be saved).

The dump you posted did not report all the information that could be used to find a possible cause.

When you say "freeze" though, I think the system has come to a stop and the dumps are only partial anyway.

If you suspect Sleep or "stand-by ", try updating the chipset drivers at the computer manufacturer's website. I would still check for temperature problems. Those temperatures you quote are not great.

Matt