Windows 7 freezes [CRASHDUMP included]

Hi all

Last night, I experience a big freeze. all of a suddenly happened.

no drivers or updates where installed over the last few days.

What happens is, the whole screen froze, cannot do anything at all, only way is to manually reboot.


I check out the crash dumps, it turns out to be a hard drive fault?
but everything runs fine in safe mode, I've just backup some documents and important stuff, and not a single freeze. it been running in safe mode for at least 2 hours so far. but since last night freeze, when I restart it after a freeze, another freeze would occur within 20 minutes after logging in normally.

Code:

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


Loading Dump File [C:\Users\JohnLaptop\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c50000 PsLoadedModuleList = 0xfffff800`02e8de50
Debug session time: Thu Apr  8 02:24:42.094 2010 (UTC + 1:00)
System Uptime: 0 days 18:03:41.185
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols

Loading unloaded module list
........
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc500690e0, ffffffffc0000185, 1f2bb4880, fffff8a00d21c000}

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

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

2: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc500690e0, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000001f2bb4880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00d21c000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d35438 to fffff80002cc1f00

STACK_TEXT:  
fffff880`031fc7f8 fffff800`02d35438 : 00000000`0000007a fffff6fc`500690e0 ffffffff`c0000185 00000001`f2bb4880 : nt!KeBugCheckEx
fffff880`031fc800 fffff800`02cb3d8b : fffffa80`07b0ece0 fffff880`031fc970 fffff800`02e4cb40 fffffa80`06a253c0 : nt! ?? ::FNODOBFM::`string'+0x34cde
fffff880`031fc8e0 fffff800`02cdcda4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000080 : nt!MiIssueHardFault+0x28b
fffff880`031fc9b0 fffff800`02cabfc4 : 00000000`00000000 fffffa80`0736e880 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`031fcb10 fffff800`02faff13 : fffffa80`0736e800 00000000`00000000 00000000`00080081 fffffa80`00080081 : nt!MiDeleteSegmentPages+0xd0
fffff880`031fcbc0 fffff800`02de7f6b : fffffa80`0736e808 00000000`00000001 00000000`00000000 002e004b`00000631 : nt!MiSegmentDelete+0x7b
fffff880`031fcc00 fffff800`02de85dd : 00000000`00000000 00000000`00000080 fffffa80`06a05040 00000000`00000012 : nt!MiProcessDereferenceList+0x23b
fffff880`031fccc0 fffff800`02f65166 : 00000000`00000020 00440042`004b000a 002e004c`00430059 0001004c`004c0044 : nt!MiDereferenceSegmentThread+0x10d
fffff880`031fcd40 fffff800`02ca0486 : fffff880`02f64180 fffffa80`06a253c0 fffff880`02f6efc0 00000000`00005000 : nt!PspSystemThreadStartup+0x5a
fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc550 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34cde
fffff800`02d35438 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34cde

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde

BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde

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

Would appreciate some input. :)

ttran said:

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Start your own thread in the "Crashes and Debugging" section of the forum and attach the ZIP archive to your post using the "paperclip" (file attachments) button.

attached the minidump :)

Tews said:

Better yet, read this, and be sure to run the tool as administrator... Blue Screen of Death (BSOD) Posting Instructions

Thanks, I'll give that a go once I can get to it. freezing atm

Tews said:

Better yet, read this, and be sure to run the tool as administrator... Blue Screen of Death (BSOD) Posting Instructions

attached the whole lot.

Tews said:

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. Please enable driver verifer using these instructions..

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc500690e0, ffffffffc0000185, 1f2bb4880, fffff8a00d21c000}

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

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

So it a not a hardware failure?

anyway i did what you said, then reboot.

"Windows failed to start....."

and the startup repair window is currently attempting to repair it as I'm writing this.

sinbin said:

shame hear that hope you sort it out!

im sure i will

failed to repair

reboot, log on.

BSOD!!! x2

i guess it normal, base on what you said.(really dont know why windows itself attempted to repair the start up in the first place)


btw, when do these BSOD stops/? this is my 3rd one, and it so fast, cant read it in time.

5th BSOD, 6th reboot, it now hanging/or frozen on the windows logo "Starting Windows" etc

edit: @tews, how many BSOD is suppose to show? now already my 10th one :/

ttran said:

Just same stuff

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

trying this now

also for some reason, I got no restore points , I tried to do that last night, where the last time I remember I had 3 restore point.

ok update:

turn off Driver Verifier in safe mode

4 new minidumps

Code:

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


Loading Dump File [F:\dumps\Minidump\072910-18501-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`03057e50
Debug session time: Thu Jul 29 11:38:50.510 2010 (UTC + 1:00)
System Uptime: 0 days 0:00:15.242
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {6, 103, fffff9800d68ce10, 0}

Unable to load image \SystemRoot\system32\DRIVERS\nvoclk64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvoclk64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvoclk64.sys
Probably caused by : nvoclk64.sys ( nvoclk64+b264 )

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

1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status
Arg2: 0000000000000103, the status
Arg3: fffff9800d68ce10, the IRP
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc9_6

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  6

IRP_ADDRESS:  fffff9800d68ce10

DEVICE_OBJECT: fffffa800901d690

DRIVER_OBJECT: fffffa800901ec70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000332a0c2 to fffff80002e8a600

STACK_TEXT:  
fffff880`031af528 fffff800`0332a0c2 : 00000000`000000c9 00000000`00000006 00000000`00000103 fffff980`0d68ce10 : nt!KeBugCheckEx
fffff880`031af530 fffff880`0424e264 : fffff880`031af640 00000000`00000000 00000000`00000103 fffff980`0d68ce10 : nt!IovCompleteRequest+0xc2
fffff880`031af600 fffff880`031af640 : 00000000`00000000 00000000`00000103 fffff980`0d68ce10 00000000`00000000 : nvoclk64+0xb264
fffff880`031af608 00000000`00000000 : 00000000`00000103 fffff980`0d68ce10 00000000`00000000 00000000`00000002 : 0xfffff880`031af640


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvoclk64+b264
fffff880`0424e264 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nvoclk64+b264

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvoclk64

IMAGE_NAME:  nvoclk64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ab00e3d

FAILURE_BUCKET_ID:  X64_0xc9_6_VRF_nvoclk64+b264

BUCKET_ID:  X64_0xc9_6_VRF_nvoclk64+b264

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