Solved Had a random blue screen while playing team fotress 2

[M1GU31]

I was playing just fine,finished the round. Was going to change to a different map then when it was changing it just blue screened. Anyways was doing fine yesterday and the past week but got a blue screen just now. My question is what caused the blue screen and if it's a issue with like drivers or something then can you help me fix it? My temperatures were normal, I know since on my 2nd monitor I can see my temps for my video card and cpu. Cpu idle is 39-40c and load is about 46-50c. My gpu idle is 51c and the highest I've seen it under load was 70c but when i was playing tf2 it was around 67c.

Anyways here is the dump file that I got from using the app provided by forum in the bsod instructions. BTW made the folder into a zip file since it was just a folder.

EDIT: Was looking on the internet on how to check what caused my bsod. Saw a suggestion of checking with whocrashed and at the conclusion it says to do somthing with [FONT=Segoe UI, Arial]shareduserdata.sys and that it was most likely caused by a third party driver. Not sure what driver but i'm going to be uninstalling/reisntalling some drivers that I know of like video drivers. Also going to be running sfc /scannow to see if windows sees any issues and uninstalling tiny firewall since that's the last thing I remember installing and see what happens just running the default windows firewall. Could possibly be the beta amd video drivers i'm guessing.
[/FONT]

 

[Northernsoul55]

Hi,

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory

Firstly i notice you are running two AV's.
You have MSE and Panda Security installed, I would advise to uninstall Panda Security.
Also as stated uninstall Tiny Firewall and enable Windows Firewall.

I also notice you have a driver installed known to cause BSOD'S:

ASACPI ASACPI.sys Thu Jul 16 04:31:29 2009
Refers to: Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities

Please uninstall the Asus Utility, if the program is no longer on your system, manually remove:

C:\windows\system32\drivers and locate the ASACPI.sys driver, right click to delete, reboot.

You guessed it, your ATI drivers are causing issues:

ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Dated: Tue Mar 19 01:29:26 2013
ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Dated: Tue Mar 19 02:47:22 2013

Also related to ATI is this driver: AtiPcie.sys
Dated: Mon Aug 24 09:25:26 2009
Refers to: ATI PCIE Driver for ATI PCIE chipset or
ATI PCI Express (3GIO) Filter
Found in ATI video drivers (Intel chipset)

There maybe newer drivers available for Video and Chipset:
:ar: http://support.amd.com/us/Pages/AMDSupportHub.aspx
If no new drivers are available for your ATI Video drivers perhaps
rolling them back to the previous version may help.

Stop message 0x0000007F Descriptive text: UNEXPECTED_KERNEL_MODE_TRAP
Usual cause: There is a hardware or software problem. This is usually caused by a hardware failure.

From your 27/3/2013 logs you experienced a STOP 0x7F BSOD.
I would recommend running some hardware tests:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight

Run chkdsk /f/r in an elevated command prompt.
Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
At the command prompt please type: chkdsk /f/r
(Note: there is a space between chkdsk and /f/r)
:ar: http://www.sevenforums.com/tutorials/433-disk-check.html

Also please run malwarebytes (to eliminate that as a possible cause):

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

:ar: http://www.malwarebytes.org/lp/malware_lp/?gclid=CLuo8ryGnbYCFeXKtAodqx8A7A
Did you run SFC? What was the outcome?

Post back any results/observations.
Cheers
Dave

 

[M1GU31]

Thank you for the response. I have update my video card and chipset drivers just now by rolling back my video drivers to the latest stable release instead of running beta drivers and updating my chipset drivers to a newer version. Removed the asus driver by going to the folder since I didn't have the utitlly installed anymore then rebooted. Did a malwarbytes scan and no malicious software was found so my system seems to be clean. Ran sfc /scannow , says Verification 100% complete, windows resource protection found corrupt files but was unable to fix some them. Now going to run a chkdsk in a bit after a I reboot and will post back here the results. Will run memtest probably tonight like you suggested and post back the result.


:UPDATE

Well Just ran chkdsk, the ending result said my volume was clean. Now just need to run memtest which I will do later this afternoon.

 

[Northernsoul55]

Thanks for your feedback.

As SFC was unable to fix some of your errors.
We need to see which files windows couldnt repair, may have a bearing on your issue:

Open the Start Menu>Type in search cmd
Right click cmd at top and Run as Administrator.
In the elevated command prompt, copy and paste the command below, and press Enter.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt

Then close the command prompt and upload the sfcdetails.txt file from your desktop.

Cheers
Dave

 

[M1GU31]

Got the sfc /scannow result now and memtest. Apparently one of my ram sticks is bad :shock: , one passes and the other fails. Funny thing is there only like 3 weeks old since I just bought them from corsair on amazon. Going to have to see if I can get a replacement for the bad one or if i have to send both back in.

 

[Northernsoul55]

Well at least thats some progress and you found the BSOD cause I suspect.
Agreed...very annoying when you just bought something then it stops working a week or so later.
Let me know how it goes with the memory replacement and if it stops the BSOD'S when replaced.

I have asked another member (Tom982) to look at your SFC logs (Im not too good at those things )

Cheers

Dave

 

[tom982]

Hi M1GU31,

Would you mind uploading your full CBS log please:

C:\Windows\Logs\CBS\CBS.log

Zip it up and attach it to your next post.

Though sfcdetails.txt shows the scale of the corruption on your computer, it doesn't actually include any of the details required to fix this

Tom

 

[M1GU31]

Tried uploading but forum says I exceed the forums limit of 2.0Mb for this file type. Says mine is 3.37MB

I hope it's ok if I upload it to dropbox.
https://www.dropbox.com/s/glbc35xiv0atn56/CBS.log

EDIT:
Eh just noticed I forgot to zip it probably why it was to big anyways already uploaded to drop box so I hope that's fine.

 

[tom982]

Hi M1GU31,

No worries, Dropbox is just as good.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFixScript.zip, and save this to your Desktop. Ensure that this file is named SFCFixScript.zip - do not rename it.
   
   https://dl.dropbox.com/u/16537616/SFCFix/Scripts/M1GU31/SFCFixScript.zip
   
   
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.zip.
5. Drag the file SFCFixScript.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a files should be created on your Desktop: SFCFix.txt.
8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Tom

 

[M1GU31]

Tom can you reupload the 2nd file, it won't allow me to download my browser keeps saying it's a phishing site according to OpenDNS Why idk.

 

[tom982]

That's weird, I use OpenDNS as well but it didn't give me any problems. I've attached it to this post

Tom

 

[M1GU31]

SFCFix version 1.4.0.0 by niemiro.
Start time: 2013-04-10 23:09:13.407
Using .zip script file at C:\Users\Miguel\Desktop\SFCFixScript.zip




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
Successfully took permissions for file or folder C:\Windows\SysWOW64\fdeploy.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll
Successfully took permissions for file or folder C:\Windows\SysWOW64\gpedit.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll
Successfully took permissions for file or folder C:\Windows\SysWOW64\gptext.dll
Successfully took permissions for file or folder C:\Windows\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll
Successfully took permissions for file or folder C:\Windows\SysWOW64\fde.dll

Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\fdeploy.dll to \\?\C:\Windows\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll.
Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\fdeploy.dll to \\?\C:\Windows\SysWOW64\fdeploy.dll.
Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\gpedit.dll to \\?\C:\Windows\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll.
Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\gpedit.dll to \\?\C:\Windows\SysWOW64\gpedit.dll.
Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\gptext.dll to \\?\C:\Windows\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll.
Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\gptext.dll to \\?\C:\Windows\SysWOW64\gptext.dll.
Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\fde.dll to \\?\C:\Windows\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll.
Successfully copied file \\?\C:\Users\Miguel\AppData\Local\niemiro\Archive\fde.dll to \\?\C:\Windows\SysWOW64\fde.dll.


Successfully restored ownership for C:\Windows\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
Successfully restored permissions on C:\Windows\WinSxS\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
Successfully restored ownership for C:\Windows\SysWOW64\fdeploy.dll
Successfully restored permissions on C:\Windows\SysWOW64\fdeploy.dll
Successfully restored ownership for C:\Windows\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll
Successfully restored permissions on C:\Windows\WinSxS\x86_microsoft-windows-g..policy-admin-gpedit_31bf3856ad364e35_6.1.7600.16385_none_ce0882b8c63afdf6\gpedit.dll
Successfully restored ownership for C:\Windows\SysWOW64\gpedit.dll
Successfully restored permissions on C:\Windows\SysWOW64\gpedit.dll
Successfully restored ownership for C:\Windows\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll
Successfully restored permissions on C:\Windows\WinSxS\x86_microsoft-windows-grouppolicy-gptext_31bf3856ad364e35_6.1.7600.16385_none_372622adf05a6587\gptext.dll
Successfully restored ownership for C:\Windows\SysWOW64\gptext.dll
Successfully restored permissions on C:\Windows\SysWOW64\gptext.dll
Successfully restored ownership for C:\Windows\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll
Successfully restored permissions on C:\Windows\WinSxS\x86_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_aa136561b9ed4ae4\fde.dll
Successfully restored ownership for C:\Windows\SysWOW64\fde.dll
Successfully restored permissions on C:\Windows\SysWOW64\fde.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 1.4.0.0 by niemiro has completed.
Currently storing 8 datablocks.
Finish time: 2013-04-10 23:09:14.291
----------------------EOF-----------------------

 

[tom982]

Looking good! Let's see what SFC thinks of things now:

SFC Scan

1. Click on the Start
   
   button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   sfc /scannow
   
   Wait for this to finish before you continue
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
   
   
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

 

[M1GU31]

Here is the log.

 

[tom982]

Here is the log.

Thanks, but that's the wrong log, can you re-read my instructions please

http://www.sevenforums.com/bsod-hel...e-playing-team-fotress-2-a-2.html#post2360381

 

[M1GU31]

Had to redo the copy to desktop, not sure why i uploaded the other one by accident. Made it a zip since the file was too big.

 

[tom982]

No problem.

2013-04-11 10:43:38, Info                  CSI    000002f5 [SR] Repairing 0 components
2013-04-11 10:43:38, Info                  CSI    000002f6 [SR] Beginning Verify and Repair transaction
2013-04-11 10:43:38, Info                  CSI    000002f7 Repair results created:
POQ 126 starts:
 
POQ 126 ends.
2013-04-11 10:43:38, Info                  CSI    000002f8 [SR] Repair complete

Everything has been fixed so you're all good to go!

 

[Northernsoul55]

@Tom982....many thanks m8

@M1GU31....Has replacing the RAM stopped your BSOD'S?

Any feedback would be appreciated.

Cheers

Dave

 

[M1GU31]

@Tom982....many thanks m8

@M1GU31....Has replacing the RAM stopped your BSOD'S?

Any feedback would be appreciated.

Cheers

Dave

Using my old set of 2Gbx2 and the bsod have stopped. Sent the other pair to corsair in the mail waiting for my new ram sticks. As of now I say this thread is solved, if I have issues again I will let you know. Hopefully the new pair of ram sticks are good when they get here, barely shipped the bad sticks today and on there way to corsair.

 

[Northernsoul55]

Good news and thanks for the feedback.
Cheers

Dave