Solved BSOD while playing games. Multiple Error codes

[Kharma]

Hello,

I am getting Multiple BSOD (about once a day) that happen at seemingly random times. I am uncertain of how best to troubleshoot this issue and would appreciate any help you may provide.

I have attached the ZIP file per the posting instructions. If I can provide any additional information please let me know.

 

[essenbe]

Hello, Kharma. I will try to help you. I read your last 5 or 6 dump files and other information. I notice you are getting a lot of errors from LOL client and Chrome. If you are running an older version or a Beta version, I would suggest you updating Chrome to the latest stable version which is, 42.0.2311.152 I believe. Your dump files were all over the place and one said Memory Corruption. The fact that all the others were different causes and stop codes is indicative of memory problems.

[COLOR=#303942][COLOR=#303942]Use !analyze -v to get detailed debugging information.[/COLOR]
[COLOR=#303942]BugCheck 3B, {c0000005, fffff8000311f68c, fffff880103b1e50, 0}[/COLOR]
[COLOR=#303942]Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )[/COLOR]
[COLOR=#303942]Followup: MachineOwner[/COLOR]
[/COLOR]

Some of the others were

fffff880`0d318718  fffff880`04265e09*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: [COLOR=red]Module load completed but symbols could not be loaded for mv91xx.sys[/COLOR]
 mv91xx+0x39e09
 
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80202c75a0, fffff80007a243d8, fffffa80213d7590}
*** WARNING:[COLOR=red] Unable to verify timestamp for asmthub3.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.sys
 
fffff800`07a24558  fffff880`089cc340Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: [COLOR=red]Module load completed but symbols could not be loaded for nvlddmkm.sys[/COLOR]
 nvlddmkm+0x18a340
fffff800`07a242c0  fffff880`042a2c70Unable to load image iaStorA.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** [COLOR=red]ERROR: Module load completed but symbols could not be loaded for iaStorA.sys[/COLOR]
 iaStorA+0x2ff5c70

Based on you system specs, this is going to be difficult for you, but I believe necessary. Running memtest86+ with 32GB of ram, I suspect will take anout 40 hours. 8 GB takes 9.5-10 and my 16GB takes around 20 hours, so I would expect your 32 GB would take around 40. Trust me I know what I;m asking you to do, but I do feel it is necessary. Ram is one of the worst problems to have, especially for debugging. When it throws a fault, the debugger will blame whatever driver it sees as most in use. That is why you see all of the different components listed, which are probably not the cause.


Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes all in the same session or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes in the same session to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[Kharma]

The sfc /scannow command was run 4 times (3 restarts) and I am still getting the following error located in (log.png).

I have also attached the log file to this response.

 

[essenbe]

I've requested someone else to look at the CBS files.

 

[NoelDP]

Here's the Summary from the SFC scan...

 Line 3621: 2015-05-19 20:36:34, Info                  CSI    0000035d [SR] Repairing 2 components
 Line 3622: 2015-05-19 20:36:34, Info                  CSI    0000035e [SR] Beginning Verify and Repair transaction
 Line 3625: 2015-05-19 20:36:34, Info                  CSI    00000360 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3628: 2015-05-19 20:36:34, Info                  CSI    00000362 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3629: 2015-05-19 20:36:35, Info                  CSI    00000363 [SR] Cannot repair member file [l:24{12}]"certutil.exe" of Microsoft-Windows-CertUtil, Version = 6.1.7601.18151, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

Ill post a fix protocol later.

 

[NoelDP]

I've uploaded a file - khaaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\khaaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\khaaa
or
DIR E:\khaaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\khaaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[Kharma]

Newest CBS File Attached.

Still failing to complete.

 

[NoelDP]

Odd - it repaired two fo the files, but not the third.

 Line 9894: 2015-05-20 20:38:50, Info                  CSI    0000034d [SR] Repairing 1 components
 Line 9895: 2015-05-20 20:38:50, Info                  CSI    0000034e [SR] Beginning Verify and Repair transaction
 Line 9896: 2015-05-20 20:38:50, Info                  CSI    0000034f [SR] Cannot repair member file [l:24{12}]"certutil.exe" of Microsoft-Windows-CertUtil, Version = 6.1.7601.18151, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

I'll have to check, and upload another fix later.

 

[NoelDP]

There's no apparent reason that the file shouldn't be present and correct.

Please open an Elevated Command Prompt, and run the following commands.

DIR C:\khaaa /S
DIR C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7601.18151_none_b75e12ea91c1f49b
ICACLS C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7601.18151_none_b75e12ea91c1f49b /T
 
.

post the results. (the first one may take a couple of minutes to complete - be patient )


Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[Kharma]

Output is below:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DIR C:\khaaa /S
Volume in drive C is SSD
Volume Serial Number is 361E-BC72

Directory of C:\khaaa

05/20/2015 09:34 AM <DIR> .
05/20/2015 09:34 AM <DIR> ..
05/20/2015 09:34 AM <DIR> amd64_microsoft-windows-u..ed-telemetry-c
lient_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda
05/20/2015 09:32 AM <DIR> x86_microsoft-windows-certutil_31bf3856ad
364e35_6.1.7601.18151_none_b75e12ea91c1f49b
0 File(s) 0 bytes

Directory of C:\khaaa\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad
364e35_6.1.7601.18839_none_fe0845bb1d97efda

05/20/2015 09:34 AM <DIR> .
05/20/2015 09:34 AM <DIR> ..
04/27/2015 12:23 PM 1,254,400 diagtrack.dll
01/23/2015 04:26 PM 660 telemetry.asm-windowsdefault.json
01/23/2015 04:26 PM 955 utc.app.json
04/27/2015 11:06 AM 36,864 utcresources.dll
4 File(s) 1,292,879 bytes

Directory of C:\khaaa\x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7601.
18151_none_b75e12ea91c1f49b

05/20/2015 09:32 AM <DIR> .
05/20/2015 09:32 AM <DIR> ..
05/12/2013 08:08 PM 43,008 certenc.dll
05/12/2013 08:08 PM 903,168 certutil.exe
2 File(s) 946,176 bytes

Total Files Listed:
6 File(s) 2,239,055 bytes
8 Dir(s) 26,099,695,616 bytes free

C:\Windows\system32>DIR C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf385
6ad364e35_6.1.7601.18151_none_b75e12ea91c1f49b
Volume in drive C is SSD
Volume Serial Number is 361E-BC72

Directory of C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf3856ad364e35_
6.1.7601.18151_none_b75e12ea91c1f49b

05/20/2015 09:32 AM <DIR> .
05/20/2015 09:32 AM <DIR> ..
05/12/2013 08:08 PM 43,008 certenc.dll
05/12/2013 08:08 PM 903,168 certutil.exe
2 File(s) 946,176 bytes
2 Dir(s) 26,099,695,616 bytes free

C:\Windows\system32>ICACLS C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf
3856ad364e35_6.1.7601.18151_none_b75e12ea91c1f49b /T
C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7601.18151
_none_b75e12ea91c1f49b NT SERVICE\TrustedInstallerI)(OI)(CI)(F)

BUILTIN\AdministratorsI)(OI)(CI)(RX)

NT AUTHORITY\SYSTEMI)(OI)(CI)(RX)

BUILTIN\UsersI)(OI)(CI)(RX)

C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7601.18151
_none_b75e12ea91c1f49b\certenc.dll NT SERVICE\TrustedInstallerF)

BUILTIN\AdministratorsRX)

NT AUTHORITY\SYSTEMRX)

BUILTIN\UsersRX)

C:\Windows\winsxs\x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7601.18151
_none_b75e12ea91c1f49b\certutil.exe NT SERVICE\TrustedInstallerF)

BUILTIN\AdministratorsRX)

NT AUTHORITY\SYSTEMRX)

BUILTIN\UsersRX)

Successfully processed 3 files; Failed processing 0 files

C:\Windows\system32>^A

C:\Windows\system32>DIR C:\khaaa /S
Volume in drive C is SSD
Volume Serial Number is 361E-BC72

Directory of C:\khaaa

05/20/2015 09:34 AM <DIR> .
05/20/2015 09:34 AM <DIR> ..
05/20/2015 09:34 AM <DIR> amd64_microsoft-windows-u..ed-telemetry-c
lient_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda
05/20/2015 09:32 AM <DIR> x86_microsoft-windows-certutil_31bf3856ad
364e35_6.1.7601.18151_none_b75e12ea91c1f49b
0 File(s) 0 bytes

Directory of C:\khaaa\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad
364e35_6.1.7601.18839_none_fe0845bb1d97efda

05/20/2015 09:34 AM <DIR> .
05/20/2015 09:34 AM <DIR> ..
04/27/2015 12:23 PM 1,254,400 diagtrack.dll
01/23/2015 04:26 PM 660 telemetry.asm-windowsdefault.json
01/23/2015 04:26 PM 955 utc.app.json
04/27/2015 11:06 AM 36,864 utcresources.dll
4 File(s) 1,292,879 bytes

Directory of C:\khaaa\x86_microsoft-windows-certutil_31bf3856ad364e35_6.1.7601.
18151_none_b75e12ea91c1f49b

05/20/2015 09:32 AM <DIR> .
05/20/2015 09:32 AM <DIR> ..
05/12/2013 08:08 PM 43,008 certenc.dll
05/12/2013 08:08 PM 903,168 certutil.exe
2 File(s) 946,176 bytes

Total Files Listed:
6 File(s) 2,239,055 bytes
8 Dir(s) 26,099,036,160 bytes free

C:\Windows\system32>

 

[NoelDP]

That's rather confusing!
The file is definitely present, and appears to be OK - but Windows/SFC is not apparently seeing it. All permissions are as expected, and there are no obvious problems.

I can only think that there's a registry problem.

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

 

[Kharma]

Posted here:

https://www.dropbox.com/s/vtlmmnvapsf88vj/COMPONENTS.zip?dl=0

 

[NoelDP]

Gotcha!
The problem is a missing entry in the registry...


I've uploaded a file - khaab.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the saved file and select Extract all...
Save it to the default location
This should create a file khaab.reg

right-click on the file, and select Merge
Accept the warnings, - you should then get a 'Success' message.
Close all windows, and reboot.

Run CheckSUR again, and post the new log.

 

[Kharma]

I am getting an error messages that says "Cannot import C:\Windows\khaab.reg: Error accessing the registry.".

 

[NoelDP]

OK - this should help...

Open an Elevated Command Prompt, and run the following command

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS

Then try the registry merge again - it should work now.

 

[Kharma]

File attached with results from latest SFC /scannow

 

[NoelDP]

Here's the new summary...

2015-05-22 13:01:22, Info                  CSI    00000352 [SR] Repairing 1 components
2015-05-22 13:01:22, Info                  CSI    00000353 [SR] Beginning Verify and Repair transaction
2015-05-22 13:01:22, Info                  CSI    00000354 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
  Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
2015-05-22 13:01:22, Info                  CSI    00000355 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

So we solved one problem, and another has reared its head.


SFCFix Script

Warning: this fix is specific to the above corruptions only, do not run these fixes if you do not have these corrupt files.

• Download SFCFix.exe (by niemiro) and save this to your Desktop.
• Download SFCFix.zip from the below link, and save this to your Desktop. Ensure that this file is named SFCFix.zip – do not rename it.
• download this version: SFCFix(x64version)
• Save any open documents and close all open windows.
• On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.

• Drag the file SFCFix.zip onto the file SFCFix.exe and release it.

• SFCFix will now process the script.
• Upon completion, a file should be created on your Desktop: SFCFix.txt.

• Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please – put tags around the log to break up the text.

SFC /SCANNOW

• Right click on the Start button
• Click on Command prompt (Admin) => Press Yes on the prompt
• Inside the Command Prompt windows copy and paste the following command SFC /SCANNOW

 

[Kharma]

Output from FSCFix:

------------------------------------------------------------------------------------------
SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-23 09:00:11.018
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\kharma\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll

The file \\?\C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll is in use and must be replaced over a reboot.
Successfully copied file C:\Users\kharma\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json.
Successfully copied file C:\Users\kharma\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json.
Successfully copied file C:\Users\kharma\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll to C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll.

Successfully pended file for replace over reboot: \\?\C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll

Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.asm-windowsdefault.json
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utcresources.dll
PowerCopy:: directive completed successfully.

Reboot:: directive completed successfully.

PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.

PostRebootRestorePermissions::
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\diagtrack.dll
PostRebootRestorePermissions:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2015-05-23 09:02:08.269
----------------------EOF-----------------------

------------------------------------------------------------------------------------------

Output from SFC SCANNOW:

------------------------------------------------------------------------------------------

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>SFC /SCANNOW

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

 

[NoelDP]

Lookin' good!

So - how is the system behaving now?

 

[Kharma]

Right now it is working pretty well. Haven't had a blue screen since the last fix (which has only been half a day). I will wait a few more days and if nothing new happens I will go ahead and mark this as solved. Otherwise I will update this with any issues.