STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,



Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Code:

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp5_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\Mini111510-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x81e1b000 PsLoadedModuleList = 0x81f32c70
Debug session time: Mon Nov 15 12:59:21.974 2010 (GMT-5)
System Uptime: 0 days 0:09:29.678
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000006, 820f704f, b5f36930, b5f3662c}
Probably caused by : hardware_disk
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000006, The exception code that was not handled
Arg2: 820f704f, The address that the exception occurred at
Arg3: b5f36930, Exception Record Address
Arg4: b5f3662c, Context Record Address
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
FAULTING_IP: 
nt!ExGetNextWakeTime+1f6
820f704f 668b13          mov     dx,word ptr [ebx]
EXCEPTION_RECORD:  b5f36930 -- (.exr 0xffffffffb5f36930)
ExceptionAddress: 820f704f (nt!ExGetNextWakeTime+0x000001f6)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 00000000
   Parameter[1]: 08900000
   Parameter[2]: c0000185
Inpage operation failed at 08900000, due to I/O error c0000185
CONTEXT:  b5f3662c -- (.cxr 0xffffffffb5f3662c)
eax=b6dadc54 ebx=08900000 ecx=0000004d edx=00000000 esi=0858cd46 edi=0858cef3
eip=820f704f esp=b5f369f8 ebp=08581060 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!ExGetNextWakeTime+0x1f6:
820f704f 668b13          mov     dx,word ptr [ebx]        ds:0023:08900000=????
Resetting default scope
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
EXCEPTION_PARAMETER1:  00000000
EXCEPTION_PARAMETER2:  08900000
EXCEPTION_PARAMETER3:  c0000185
IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
BUGCHECK_STR:  0x7E
EXCEPTION_STR:  0xc0000006_c0000185
FOLLOWUP_IP: 
+1f6
08900000 ??              ???
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware_disk
IMAGE_NAME:  hardware_disk
DEBUG_FLR_IMAGE_TIMESTAMP:  0
STACK_COMMAND:  kb
FAILURE_BUCKET_ID:  0x7E_IMAGE_hardware_disk
BUCKET_ID:  0x7E_IMAGE_hardware_disk
Followup: MachineOwner
---------

A quick review indicates that it is hard drive problem. Make sure that you have enough space on your hard drive. Check the hard drive. If all are negative defrag.

Test Hard Drive www.carrona.org/hddiag.html or this test Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

Well,
You have to understand my position, I cant see or touch the computer. All I have is the information from the dump report and what you tell me.
The report indicates hard drive
You gave me the results of several tests and some say fail.
The HD tests are not always definitive.
Taking everything into account, I think that you should back up your stuff and get ready to buy a new HD.
If you do get another BSOD, post and I will check it again. You have given me several already and most of them give the HD as the cause.
You, now, have the benefit of all that I know.

IM sorry you must have that key to reinstall. I assume you did not back it up.

Rich,
If this is a preinstalled OS there are two keys. One key is on the body of the computer. That is the key that should be used. The other key can be seen with software like Magic JellyBean, but this key number will not work. It is a special volume key number that the Manufactuer used to actually install the OS. It will not work. I know this form much experience at the Forum.