SYSTEM_SERVICE_EXCEPTION BSOD after PC rebuild

So everything went smooth until you tried to install IRST, correct?
You should have a system restore point you can go back to if the OS is buggy again.

• System Restore

Please upload an up to date version of the MSINFO32 file:

Start → Run → type MSINFO32 then hit Enter.
In MSINFO32 go to, File → Save → name it your user-name.
Once the file is saved right click it and choose Send to → Compressed (zipped) folder.

Attach the file in your next post.

Hey,

I did as you asked and I don't think it's the IRST driver!

After retrieving the MSINFO32 save from Safe Mode, called "Polygone - MSINFO32 before System Restore", I booted into Windows normally. After about 10 minutes of reaching the desktop, a "Windows Explorer has stopped working" error appeared shortly followed by SYSTEM_SERVICE_EXCEPTION BSOD with a driver reference. The crash dump is attached to this post.

I then ran System Restore from the Windows 7 installation disc and successfully took my PC back to before the Etron USB 3.0 driver was installed. This was the last driver installed before I ran the IRST install. Thinking that the errors were now all gone, I ran MSINFO32.exe. As its information was saving, another BSOD appeared. Its crash dumps are called SYSTEM_SERVICE_EXCEPTION 2! They're still happening! And I was so hopeful that we had found the cause!

I ran MSINFO32 from Safe Mode and its save is called: "Polygone - MSINFO32 after System Restore".

I installed the Etron USB 3.0 driver in the same boot-up as my attempted install of the IRST driver. Do you think that could be the culprit?

What do you make of all of this?

Please follow the Windows Update Posting Instructions and post the requested data - it'll give us something to chew on :) (I like a challenge!)

I'm glad you like a challenge because my PC is a never ending supply of errors!

I've tried to complete the tutorial that you posted but I've had problems!

Here's what has happened:

I downloaded the SURT on another PC and transferred it to a USB stick. I inserted this flash drive whilst my PC was booting into Safe Mode. Shortly after my PC auto-restarted. I was AFK at the time, so I'm not sure what happened. The next time, I was able to boot into Safe Mode successfully. My flash drive was still connected. As the SURT install was transferring from the flash drive to my PC, it auto-restarted. I don't know what happened as, again, I was AFK.

I booted into Safe Mode again. After reaching the desktop, I tried to run the installer. The error message below appeared when I did.

Windows Update Standalone Installer
Installer encountered an error: 0x8007000d

The data is invalid

Suspecting that the install did not download completely before my PC restarted, I downloaded it again from the USB stick. This is when I found that SURT wouldn't run in Safe Mode. I restarted my PC and booted up my PC normally. On reaching the desktop a CACHE_MANAGER BSOD flashed onscreen. The crash dumps are attached to this post. I then booted my PC normally again so as to find a stable boot that would allow me to run the SURT. Just before reaching the desktop, at around the "Welcome" and "Please wait..." stages of Windows starting up, the stop error message below appeared:

WerFault.exe - Application Error
The instruction at 0xf9108620 referenced memory at 0xf9132240. The memory could not be read.

A BSOD then appeared. Its attached to this post as "SF_24-11-2013 - 2 Maybe MEMORY_MANAGEMENT" as I didn't get a good look at the title before my PC auto-restarted. On the next attempt at booting up normally a stop error appeared with the title along the lines of: iusb3mon.exe. I didn't get a good look at the message as a MEMORY_MANAGEMENT BSOD appeared shortly afterwards. Its crash dumps are attached to this post as "SF_24-11-2013 - 3 MEMORY_MANAGEMENT".

On the fifth time I booted my PC normally in this session, it seemed fine when it reached the desktop. As such I started to run the SURT. Within the space of a minute or so, a PAGE_FAULT_IN_NON-PAGED_AREA BSOD appeared and my PC restarted. Like normal, I booted into Safe Mode to retrieve those crash dumps. As the SF_Diagnostic_Tool was retrieving the crash dumps, a SYSTEM_SERVICE_EXCEPTION BSOD appeared. My PC then restarted. This surprised me as I don't normally get blue-screens in Safe Mode.

I have been having trouble with the Seven Forums crash dump retrieval tool though. In this session of PC usage especially, when I run the tool after booting in to Safe Mode, it seems to stop retrieving parts of the crash dumps after a while. If I stop the tool running in Task Manager and delete the part file, the tool retrieves the crash dumps successfully on my next try. I have found though that a while after the second crash dump retrieval attempt, the first retrieval of the crash dumps starts up again. This is the first time that the SF_Diagnostic_Tool has ever generated a BSOD though.

Anyway, after my PC auto-restarted, I booted into Safe Mode again. I've attached to this post the part of the PAGE_FAULT BSOD that was collected by the Seven Forums tool. I was then able to successfully retrieve the SYSTEM_SERVICE_EXCEPTION BSOD that it had just generated.

As I couldn't find a stable boot, I decided to skip the SURT and run the "sfc /SCANNOW" utility. At 39% verification, the utility stopped and the message below was displayed:

Attachment 294867

I started the scan and this what appeared on-screen:

Attachment 294872

I stopped the "sfc /scannow" utility to see what you all thought of it. I've attached the Windows logs that you wanted.

Please let me know what you make of all of this!

SFC shows the following errors...

Code:

 Line 5654: 2013-11-24 14:27:02, Info                  CSI    00000409 [SR] Repairing 3 components
 Line 5655: 2013-11-24 14:27:02, Info                  CSI    0000040a [SR] Beginning Verify and Repair transaction
 Line 5658: 2013-11-24 14:27:02, Info                  CSI    0000040c [SR] Cannot repair member file [l:24{12}]"msgothic.ttc" of Microsoft-Windows-Font-TrueType-MSGothic, 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 5661: 2013-11-24 14:27:02, Info                  CSI    0000040e [SR] Cannot repair member file [l:18{9}]"unbcl.dll" of Microsoft-Windows-Setup-Component, Version = 6.1.7601.17514, 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 5664: 2013-11-24 14:27:02, Info                  CSI    00000410 [SR] Cannot repair member file [l:20{10}]"quartz.dll" of Microsoft-Windows-DirectShow-Core, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

There's also this error...

Code:

2013-11-24 14:20:00, Info                  CSI    0000013a [SR] Beginning Verify and Repair transaction
2013-11-24 14:20:03, Error                 CSI    0000013b@2013/11/24:14:20:03.153 (F) d:\w7rtm\base\wcp\cdf\cdf_cdfapi.cpp(936): Error STATUS_SXS_INVALID_ACTCTXDATA_FORMAT originated in function RtlCreateCdfEx expression: (null)
[gle=0x80004005]
2013-11-24 14:23:55, Info                  CSI    0000013c [SR] Verifying 100 (0x0000000000000064) components

Which I have to admit I have no understanding of.

I'll post a fix for the file errors later - if we're lucky it may fix the other error as well :)

I've uploaded a file - plgaa.zip - to my SkyDrive at Noel's SkyDrive
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:\plgaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\plgaa
or
DIR E:\plgaa

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

XCOPY <drive>:\plgaa <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 SkyDrive Public folder, and post a new link
Also run a new MGADiag report, and post the result.

The MGADiag doesn't tell us much because it was run an Safe Mode - doesn't matter, as I don't think it's likely to tell us that much more in normal mode.

The SFC log shows that it successfully replace the damaged font, and the other files were also successfully replaced.

There's no repeat of the error message since that original one, so it may have been a one-off, or we haven't hit the conditions which caused it - or we may have cured it.

I think I've done as much as I can for the moment - it's back to the BSOD guys :)

Ok, thanks for your help!

I managed to get MGADiag.exe to run in normal Windows mode. I'd rather be safe than sorry!

MGADiag.exe was ran after I used System Restore to make my PC back to before I installed a USB 3.0 hub controller. And your font fix! But I ran the font fix again and it successfully replaced the font. When I ran sfc /scannow again today it didn't find any integrity errors whereas it did last time. Do you think System Restore could have reversed the error?

I also retrieved a copy of the CBS.log file after the last sfc /scannow utility scan and it's attached to this document.

Here's a full list of what happened since my last post:

26.11.2013

After turning my PC on it hung after the POST screen. It lingered on a black screen with a white flashing underscore cursor where I normally hammer F8 to enter Safe Mode. I hadn't pressed anything since turning it on and my USB stick wasn't plugged in. I rebooted my PC manually. As it booted up normally, it reached the "Starting Windows" screen with the black background when it suddenly auto-restarted. It also auto-restarted when I tried to boot into Safe Mode after that last attempt.

I booted up my PC again and I ran Startup Repair from the prompt on the screen saying that my PC did not start successfully last time. I actually chose to use System Restore but Startup Repair said that it fixed the problem without loading it. I restarted the PC as prompted, so the changes could take effect. During this boot-up my PC got as far as the Windows "Welcome" screen where it hung. After 5 minutes of this a SYSTEM_SERVICE_EXCEPTION BSOD appeared. Its crash dump has the number 1 and is attached to this post.

I booted up my PC and entered the Repair Environment by pressing F8 after the POST screen. I followed the Repair My Computer option and started System Restore. I successfully restored my PC to 18.11.2013 before I first installed the Etron USB 3.0 Hub Controller. I restarted my PC as prompted and it booted up to the desktop. To test how stable the boot was I decided to wait for any errors and played around on Paint to see if any appeared. After a few minutes, Paint temporarily froze and the title bar said that it wasn't responding. A PAGE_FAULT_IN_NONPAGED_AREA BSOD then flashed onscreen.

I booted into Safe Mode as my PC auto-restarted and retrieved the blue-screen's crash dump. I ran the sfc /scannow utility and at 100% verification I was told:

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

I performed your plgaa file fix again and it said that it repaired the damaged font. I then restarted my PC and booted it up normally. After a minute at the desktop a SYSTEM_SERVICE_EXCEPTION blue-screen error appeared. I think a driver was named but it could have been that win32k.sys thing.

I have a copy of the CBS.log folder from this point if you want it, I haven't attached it to this post though.

27.11.2013

I booted my PC up normally. At the desktop, the boot seemed stable. I ran MGADiag.exe but it wouldn't let me copy the log to a .txt file. When I tried, the error message below appeared:

Attachment 295301

I rebooted my PC and on booting up normally, this boot also seemed stable. I ran MGADiag.exe again and this time the "Copy" button worked without generating an error. This is the text file that I mentioned at the start of this post.

I started my PC up normally again as I'd forgotten to run sfc /scannow since performing the plgaa fix. As it booted up, a BSOD appeared. Its crash dump is named "SF_27-11-2013 - 4 - fltmgr.sys BSOD" and is attached to this post.

When I booted up Windows normally again it successfully reached the desktop. I ran the sfc /scannow utility and at 100% verification I was told: Windows Resource Protection did not find any integrity violations. I ran the utility again to make sure there were no errors. During the scan another BSOD appeared. Its crash dump is named "SF_27-11-2013 - 5 - ntfs.sys BSOD". I also copied the CBS.log folder. This is the folder that I mentioned at the beginning of this post.

Could you please let me know what you make of all this?