Solved System service exception BSOD playing Starcraft 2

[NoelDP]

I'll hold the fix until after the memory upgrade - there may be more to do anyhow by then.
Once you have it sorted....

Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

That'll also check the registry for problems with updates.

 

[JTMoney66]

Hello, I'm not sure what to do. I can't start Windows so I am limited to what I can do from the system recovery screen.

However, I did run the SURT recently and ive tried running SFC many many times before the BSOD was preventing me from loading Windows.
I replaced my RAM and tested with no errors.

 

[NoelDP]

Sorry - didn't see that you were now unable to boot to Windows

You maybe able to use the Offline SFC to help repair the OS - although I suspect that the Windows repair utility would have run it already...


Your best option in that case is to run the CHKDSK and SFC in offline mode from a Repair Environment boot.

Reboot the computer, and tap the F8 key until you get the advanced boot menu up - one option should be 'Repair your computer'. Pick that one.

Log into your normal account.
You'll get a set of options - pick the Command Prompt one.
At the command prompt, type DIR C:\
- if we're lucky this will bring up a listing of your normal C: drive contents, including the Program Files folder(s) and the Windows folder.
If not, try D:\ or E:\ (etc. until you get the right letter)
then type the following command

CHKDSK <drive>: /R

and wait for it to complete - it could take a few hours, depending on the size of the drive.

Once complete, type

sfc /scannow /OFFBOOTDIR=<drive>:\ /OFFWINDIR=<drive>:\Windows

where <drive> is the letter you found above.
(example - sfc /scannow /OFFBOOTDIR=P:\ /OFFWINDIR=P:\Windows)

Wait for the command to complete. (make a note of the response!).

Once it has, type EXIT and the pick the option to reboot.

 

[JTMoney66]

Alrighty, no worries. I am currently running the chkdsk on drive d where Windows is located. I think I tried running SFC before and I got a response stating "Windows resource protection could not perform the requested operation".

I do have the ability to copy log files via command prompt to an external drive and upload them using a laptop. I'll report back when the scans are done.

 

[JTMoney66]

The chkdsk completed and it stated "Windows has checked the file system and found no problems".

After running SFC I get this message: "Windows Resource Protection found corrupt files but was unable to fix some of them".

I need to go to sleep soon here. I'll check back whenever possible. I appreciate the help.

 

[NoelDP]

That was very quick! Ah- an SSD, so no wonder.
Please post the <drive>:\Windows\\Logs\CBS\CBS.log file (zipped!) when you can, and I'll see if there's anything new there to give us a clue.

 

[JTMoney66]

Here is CBS.zip.

 

[NoelDP]

Here's the Summary again...

 Line 4819: 2015-05-21 20:34:19, Info                  CSI    00000490 [SR] Beginning Verify and Repair transaction
 Line 4822: 2015-05-21 20:34:19, Info                  CSI    00000492 [SR] Cannot repair member file [l:28{14}]"Hydrangeas.jpg" of Microsoft-Windows-PhotoSamples, Version = 6.1.7600.16385, 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 4825: 2015-05-21 20:34:19, Info                  CSI    00000494 [SR] Cannot repair member file [l:22{11}]"ShvlRes.dll" of Microsoft-Windows-Shell-MultiplayerInboxGames-Spades, Version = 6.1.7600.16385, 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 4828: 2015-05-21 20:34:19, Info                  CSI    00000496 [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 4831: 2015-05-21 20:34:19, Info                  CSI    00000498 [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 4834: 2015-05-21 20:34:19, Info                  CSI    0000049a [SR] Cannot repair member file [l:22{11}]"mstscax.dll" of Microsoft-Windows-TerminalServices-ClientActiveXCore, Version = 7.2.7601.18585, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post the fix protocol in a few minutes.

 

[NoelDP]

I've uploaded a file - jt6aa.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:\jt6aa
hit the enter key - if you get a 'Not Found' error try
DIR D:\jt6aa
or
DIR E:\jt6aa



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



XCOPY <drive>:\jt6aa <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

 

[JTMoney66]

I've run the command, but I still get this persistent BSOD (process1_initialization_failed) stop 0x0000006b.

 

[NoelDP]

Did you run SFC /SCANNOW again? If do, please post the new CBS.log.

 

[JTMoney66]

"Windows Resource Protection found corrupt files but was unable to fix some of them."

Attached is the new CBS.zip

 

[NoelDP]

That's the same file you uploaded earlier - I need the new one from the CBS folder please

 

[JTMoney66]

I don't understand, that is the file here: D:\Windows\Logs\CBS\CBS.log but it says last modified on the 21st. It isn't saving the new ones?

 

[JTMoney66]

Ok, this should be the new one.

The weird thing is, when I copy from D:\Windows\Logs\CBS\CBS.log I got the old file (from before the BSODs)

When I copy from %windir%\Logs\CBS\CBS.log I got the latest version.

Please see attached.

 

[NoelDP]

That's because the %windir% almost certainly leads to C:\windows, rather than D:\Windows?

The CBS log is from after the SFC was run - please post the most recent CBSPersist file (zip it first - the forum doesn't accept CAB files)

 

[JTMoney66]

There is no windows directory in c:\ however. My windows drive used to be C: but it changed to D: for some reason. The old D: drive that I just used for storage is now my C: drive. Should there be a file named CBSpersist? The only cbs.log files I can find I have attached.

 

[NoelDP]

It's very unusual ( and not very easy) to get Windows 7 to install as the D: drive!

Yep, there's usually 5 CBSPersistxxxxxxxx.cab files in the CBS folder, along with a Filters.log and the CBS.log file

 

[JTMoney66]

This zip file has the latest CbsPersist file I could find (located in D:\Windows\Logs\CBS\) Apparently, %windir% in the recovery environment command prompt is referring to X:\Windows\ but in X:\Windows\Logs\CBS\ there are no CBSPersist cab files (only CBS.log). I had no idea I had an X drive.

 

[Boozad]

It's very unusual ( and not very easy) to get Windows 7 to install as the D: drive!

Indeed. I'm wondering how this happened. JTMoney66 could you post a screenshot of Disk Management please? Continue working with Noel please but this needs looking at.