BSOD

[wrightsnake]

Is Vista Home Premium 32 bit. Original OS, OEM. Hardware is a Sony Vaio, 4 years old. The only thing that I think could have caused the issue is Microsoft Silverlight automatically updating. It's the only software that has recently changed, and the computer hasn't been used since Silverlight self-updated. Computer loads up as normal but bluescreens shortly after it reaches the desktop.

I got an error message, 'The system cannot find the path specified' when trying to run the System Health Report, hence no report in the .zip file.

Thanks for any assistance.

 

[richc46]

Welcome
Usually these reports just give little clues. Your reports are clear, it is a registry problem.

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

Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff.zip\Windows_NT6_BSOD_jcgriff2\Mini051912-04.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 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.22777.x86fre.vistasp1_ldr.101014-0432
Machine Name:
Kernel base = 0x8520d000 PsLoadedModuleList = 0x85325c70
Debug session time: Sat May 19 07:43:44.596 2012 (GMT-4)
System Uptime: 0 days 0:02:24.335
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 51, {1, 8d623800, 4597000, 368}
Probably caused by : ntkrpamp.exe ( nt!HvpSetRangeProtection+40 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry.  If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000001, (reserved)
Arg2: 8d623800, (reserved)
Arg3: 04597000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000368, depends on where Windows bugchecked, may be return code of
 HvCheckHive if the hive is corrupt.
Debugging Details:
------------------

CUSTOMER_CRASH_COUNT:  4
DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT
BUGCHECK_STR:  0x51
PROCESS_NAME:  services.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 853fdd3e to 852da561
STACK_TEXT:  
a290a94c 853fdd3e 00000051 00000001 8d623800 nt!KeBugCheckEx+0x1e
a290a994 853f8743 04597000 3311e000 00000004 nt!HvpSetRangeProtection+0x40
a290a9c8 853f7652 8d623800 00361e3c 37353136 nt!HvMarkDirty+0x43b
a290a9f0 8537f387 00361e40 00000000 a09cf95c nt!HvMarkCellDirty+0x22b
a290aa40 8537f1d5 00000001 019cf95c 8d623800 nt!CmpMarkKeyValuesDirty+0x10f
a290aa58 8537ebc5 8d623800 02c2a958 a6dda21c nt!CmpFreeKeyValues+0x15
a290aac4 8537e99c 8d623800 a6dda21c 8d623800 nt!CmpSyncKeyValues+0x3d
a290ab10 8537f994 c1039000 8d623800 8d623800 nt!CmpCopySyncTree2+0x1e9
a290ab34 8537f8ea 8d623800 000001d0 8d623800 nt!CmpCopySyncTree+0x3d
a290aca4 8537f46d 0001003d a290ad48 8537f3f2 nt!CmpSaveBootControlSet+0x2ae
a290acc0 85264bba 0000003f a290ad58 85262e65 nt!NtInitializeRegistry+0x7b
a290acc0 85262e65 0000003f a290ad58 85262e65 nt!KiFastCallEntry+0x12a
a290ad3c 8537f419 0000003f 000df794 8537f3f2 nt!ZwInitializeRegistry+0x11
a290ad58 85264bba 0000003f 000df7d0 774c96f4 nt!NtInitializeRegistry+0x27
a290ad58 774c96f4 0000003f 000df7d0 774c96f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
000df7d0 00000000 00000000 00000000 00000000 0x774c96f4

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!HvpSetRangeProtection+40
853fdd3e cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt!HvpSetRangeProtection+40
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4cb716c2
FAILURE_BUCKET_ID:  0x51_nt!HvpSetRangeProtection+40
BUCKET_ID:  0x51_nt!HvpSetRangeProtection+40
Followup: MachineOwner
---------

Use system restore to go back to the point that you did not have a problem. Use safe mode if needed to get to restore.

 

[zigzag3143]

Is Vista Home Premium 32 bit. Original OS, OEM. Hardware is a Sony Vaio, 4 years old. The only thing that I think could have caused the issue is Microsoft Silverlight automatically updating. It's the only software that has recently changed, and the computer hasn't been used since Silverlight self-updated. Computer loads up as normal but bluescreens shortly after it reaches the desktop.

I got an error message, 'The system cannot find the path specified' when trying to run the System Health Report, hence no report in the .zip file.

Thanks for any assistance.

Just passing by not subscribing.

You have a 12 year old driver loaded on the system Related to DMICall.sys Sony DMI Call service driver. From 2000 (before vista was released)>

If your hardware is <5 years old you probably dont even need it. Check with the mfr.