Hi . .back again, been continuing the review and diagnostics . . Have replaced all my RAM with new sticks and shut down / removed all Marvell drivers
I've been watching Event Viewer like a hawk to see what is happening . . as follows is a highlight form the last week and a new Crash dump from and hour ago, there is never any Warning / Error / Critical logged prior to one of these crashes (after boot up). Ironically this time I was actually looking as Event Viewer and wiaitng for the logs to load, thats when it crashed . . someone has a sense of humour.
This is the BSOD message regards the dump attached before
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c3e0630, 0xfffffa800c3e0910, 0xfffff800041d88b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021812-18876-01.
These are errors seen over the last few days . . . none of which happened before the crash as noted above . . .
------------- 1
An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\??\GLOBALROOT\Device\HarddiskVolumeShadowCopy13\ Users\default\ntuser.dat'.
------------- 2
Volume Shadow Copy Error: An error 0x00000000c000014d was encountered while Registry Writer was preparing the registry for a shadow copy. Check the Application and System event logs for any related errors.
Operation:
OnFreeze event
Freeze Event
Context:
Execution Context: Registry Writer
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {5f9fce2d-391f-43c1-9df0-96c6c4016397}
------------- 3
The content source <csc://{S-1-5-21-3823838570-2202061524-1894531514-1001}/> cannot be accessed.
Context: Application, SystemIndex Catalog
Details:
The URL was already processed during this update. If you received this message while processing alerts, then the alerts are redundant, or else Modify should be used instead of Add. (HRESULT : 0x80040d0d) (0x80040d0d)
------------- 4
The content source <mapi://{S-1-5-21-3823838570-2202061524-1894531514-1001}/> cannot be accessed.
Context: Application, SystemIndex Catalog
Details:
A server error occurred. Check that the server is available. (HRESULT : 0x80041206) (0x80041206)
------------- 5
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3823838570-2202061524-1894531514-1001:
Process 5840 (\Device\HarddiskVolume2\Windows\System32\msiexec. exe) has opened key \REGISTRY\USER\S-1-5-21-3823838570-2202061524-1894531514-1001\Software\Microsoft\Windows\CurrentVersion\Exp lorer
------------- 6
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
DETAIL -
1 user registry handles leaked from \Registry\User\S-1-5-21-3823838570-2202061524-1894531514-1001:
Process 1668 (\Device\HarddiskVolume4\Windows\System32\svchost. exe) has opened key \REGISTRY\USER\S-1-5-21-3823838570-2202061524-1894531514-1001
------------- 7
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
Freeze Event
Context:
Execution Context: Writer
Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Name: Registry Writer
Writer Instance ID: {5f9fce2d-391f-43c1-9df0-96c6c4016397}
Command Line: C:\Windows\system32\vssvc.exe
Process ID: 5616
------------- 8
BITS has encountered an error communicating with an Internet Gateway Device. Please check that the device is functioning properly. BITS will not attempt to use this device until the next system reboot. Error code: 0x80040501.
All other BSODs logs since fresh install last weekend
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c1977d0, 0xfffffa800c197ab0, 0xfffff800031978b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021812-21543-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c489480, 0xfffffa800c489760, 0xfffff8000318d8b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021712-20576-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c4a2060, 0xfffffa800c4a2340, 0xfffff8000318a8b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021712-18720-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa80075fb8c0, 0xfffffa80075fbba0, 0xfffff800031828b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021412-19515-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa8007b78b30, 0xfffffa8007b78e10, 0xfffff800031dc8b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021212-18938-01.
