[RESOLVED] Windows 7 Blue screen of death

[Agent 0008]

Recently my system has started giving me a Windows 98 classic blue screen of death but instead of staying where I can read it my system shuts down. The last time it gave me a SYSTEM SERVICE EXTENSION error with Object GUID E7ff607e0-4395-11db-b0de-0800200c9a66 status 0x0000034 invalid object configuration.

What happens then is my system seems like it's running but all it does is throw my moniter into stand by. I have to repeated manually restart the system until it comes up again. It seemed like it started with and ASUS update for my graphic's card but I can't say for sure.

Running Windows 7 - 64 bit updated to the latest.
ASUS Motherboard M4A88TD-V EVO/USB3
ASUS Graphic's card EAH5670
AMD Phenom II x6 1090T Processor
G.Skill Ripjaws 16 gb ram DDR3 1333

[SuperSparks]

To stop it rebooting, go to Control Panel>System, then click "Advanced System settings" in the left-hand pane. In the System Properties dialog, click Settings under "Startup and Recovery", and then uncheck "Automatically restart". After that it will stay on the Blue Screen error which will be easier to troubleshoot.

BTW, it is "System_Service_Exception". There is a KB article here that may help:

http://support.microsoft.com/kb/980932

[Agent 0008]

It said the hotfix was noyt for me when I tried to run it.

[jdc2000]

Once you have Windows set to not reboot but to display the BSOD instead, you can use BlueScreenView to get more info on the error.

http://www.nirsoft.net/utils/blue_screen_view.html

[Agent 0008]

I hope I'm doing this right:

Item One:

Version=1
EventType=Office12ProofingTools
EventTime=129818318325939240
Consent=2
UploadTime=129818318325969242
ReportIdentifier=dad1b077-a105-11e1-a17c-20cf30ade0d4
Response.BucketId=2554096340
Response.BucketTable=5
Response.type=4
Response.CabId=1787338494
Sig[0].Name=Problem Signature 01
Sig[0].Value=OUTLOOK.EXE
Sig[1].Name=Problem Signature 02
Sig[1].Value=14.0.6109.5005
Sig[2].Name=Problem Signature 03
Sig[2].Value=msproof7.dll
Sig[3].Name=Problem Signature 04
Sig[3].Value=14.0.6015.1000
Sig[4].Name=Problem Signature 05
Sig[4].Value=1033
Sig[5].Name=Problem Signature 06
Sig[5].Value=IgnoreAll
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
Sec[0].Key=LCID
Sec[0].Value=1033
Sec[1].Key=No2nd
Sec[1].Value=2
State[0].Key=Transport.DoneStage1

Item Two:

Version=1
EventType=APPCRASH
EventTime=129822182383533695
ReportType=2
Consent=1
UploadTime=129822182383933696
ReportIdentifier=86955420-a489-11e1-8cdd-20cf30ade0d4
IntegratorReportIdentifier=8695541f-a489-11e1-8cdd-20cf30ade0d4
WOW64=1
Response.BucketId=2962063332
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=iexplore.exe
Sig[1].Name=Application Version
Sig[1].Value=9.0.8112.16421
Sig[2].Name=Application Timestamp
Sig[2].Value=4d76255d
Sig[3].Name=Fault Module Name
Sig[3].Value=Flash32_11_2_202_235.ocx
Sig[4].Name=Fault Module Version
Sig[4].Value=11.2.202.235
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4f9af5a5
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0026ecc2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033

[Train]

Are you overclocked?

[Agent 0008]

My wife says so!!

Yes, I ran the AMD Overdrive and allowed it to set the settings. Since I was able to get it up and going again I just re-ran AMD overdrive and allowed it to reset them.

[Train]

In my searches, overclocking seemed to be the biggest cause of that error. I would back it down a tab and keep tabs on things.

[SuperSparks]

I would strongly advise great caution when using any of those overclocking apps. They have a nasty tendency to increase Vcore (CPU voltage) to a large degree. Increasing Vcore is what can really kill a CPU

IMO, it's a lot better to manually overclock in the BIOS, and only go as far as is stable with the stock Vcore, or a very small increase only. I can regularly get up to 30% overclocks without ever touching the voltages, which is good enough for me

[Agent 0008]

The one thing I did noticed is the core unlocker was always disabled in the bios when it would come back up. So far re-running the clocking tool from AMD seems to have settled things down but I've been here before where everything looks good and then boom, back where I started. I'll keep you posted if it starts again or if it falls on it's face.

Thnaks everyone for your help so far (fingers crossed).

[Train]

Good LUCK!

[Agent 0008]

OK so far things have continued but have improved a bit. Instead of getting a blue screen and then locking up with my moniter in standby and having to manual reboot it now at least reboots and comes up on it's own. Since Overclock has been mentioned as the problem I have turned off the overclocking feature and will see if it will remain stable.

[SuperSparks]

That's a very good plan

If you still get problems, I would go to the next stage and go into the BIOS Setup, and go to "Load optimal defaults". That will make sure that the overclocking utility hasn't left any obscure settings tweaks in place.

[Agent 0008]

Well in a way it happened again, while I didn't get a blue screen I did have a crash.

Appcrash says the culprit is:

C:\Program Files\ATI Technologies\ATI.ACE\Fuel\Fuel.Service.exe

I see a few cxomplaints are being made about the AMD update Catalyst 12.4 which seem to start all my problems.

[SuperSparks]

Sometimes with graphics drivers you have to roll back to an earlier version to get one that's stable. I've had to do that with Nvidia drivers too