Random BSODs and Failed Launches

[tonylka10]

I have been getting random BSODs recently even after a fresh install of Windows 7. This can happen at any time, often when I am browsing or playing video games. It sometimes can even happen while the computer is idling.

The BSODs are really unexpected for the most part and don't happen under the same circumstance always.

 

[koolkat77]

Welcome to SevenForums.

Follow this:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Perform a System File Check:

1. Click on the start rb:
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Disk Check on your hard drive for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Please install all windows updates including SP-1

If this does not bring stability, test RAM.
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial: http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Let us know the results.

 

[tonylka10]

View attachment 253858

Here is my CBS

I don't currently have service pack 1 because I have been getting errors from windows update when tying to install SP1:
Code 90073701.

 

[koolkat77]

I'm requesting a friend to take a look at that.

What about SSD firmware and RAM test?

 

[NoelDP]

You have a couple of 'bad' files present.
While I catch up on the morning mail and craft a fix, please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your SkyDrive Public folder so I can take a look - post a link in your reply.

 

[NoelDP]

Once you have the CheckSUR report done......


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

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

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

 

[tonylka10]

I'm requesting a friend to take a look at that.

What about SSD firmware and RAM test?

I haven't had the time to get to those two things but I plan to. Thank you for your patience I have been busy lately. I'm completing the tasks Noel suggested so I can repair windows update.

 

[tonylka10]

You have a couple of 'bad' files present.
While I catch up on the morning mail and craft a fix, please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your SkyDrive Public folder so I can take a look - post a link in your reply.

https://skydrive.live.com/?cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21654&authkey=AM4w4obwGUIrAmQ#cid=74B6FF23D380B09B

 

[NoelDP]

You didn't share the file, so I can't see it.
If you attach it to a reply rather than uploading it to SkyDrive, it achieves the same object (My main forums are the MS ones, none of which accept file attachments - I forgot to amend the instructions for here. Sorry!)

 

[tonylka10]

Ok, sorry about that, I just shared it but I have also attached to my post.

 

[NoelDP]

The CheckSUR report found a large number of errors - 394 - and fixed all but these....

(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_bd3036d609e9d5f1 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_cd48131dd338388f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_78e52218b95dc04d HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_e9edab228ffde74c HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_b25a04b3f5f64bbe HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 microsoft-w..-deployment_31bf3856ad364e35_6.1.7600.16385_b1190aba12cf02aa HKLM\Components\CanonicalData\Deployments

I think the best thing to do is to run the tool again, and see if it can work out a way to fix those (while I try and work out what they mean )
Post the new CheckSUR.log file afterwards.

 

[tonylka10]

Here is my second CheckSUR

https://skydrive.live.com/?cid=74B6FF23D380B09B#cid=74B6FF23D380B09B&id=74B6FF23D380B09B!105

 

[NoelDP]

Your timing is perfect
I've just completed the fix for the remaining errors (assuming it works!)
Please follow these instructions EXACTLY - errors can be fatal!

Download the file tlkab.zip from my SkyDrive here....
Noel's SkyDrive

and save it (preferably to the desktop).
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new file regfix.reg in the same place

Create a new System Restore point for safety's sake!

Open an Elevated Command Prompt, and run the following command

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

(you should get a success message - leave the window open!)
now find the regfix.reg file, and right-click on it - select Merge
Accept the warnings.
You should get another success message

back in the Command Prompt window, run the following command

REG UNLOAD HKLM\COMPONENTS

Close the Command prompt window, and reboot

Now run another CheckSUR san, and post the new CheckSUR log file.

 

[tonylka10]

https://skydrive.live.com/?cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21654&authkey=AM4w4obwGUIrAmQ#cid=74B6FF23D380B09B&id=74B6FF23D380B09B%21105

 

[NoelDP]

Great! the CheckSUR is now clear.
Just to check that it hasn't exposed other problems, please run another SFC /scannow, and post the new CBS.log
If it comes back 'couldn't find any problems', then my job is done, and KoolKat can take you back over

Hopefully, the machine should run better anyhow.

 

[NoelDP]

... Oh - I forgot to mention - see if Windows Update behaves now

 

[tonylka10]

New CBS:

https://skydrive.live.com/?cid=74B6FF23D380B09B#cid=74B6FF23D380B09B&id=74B6FF23D380B09B!105

Windows update is still having problems though.

 

[NoelDP]

Heh - the repairs to the CheckSUR appear to have shaken something loose in the SFC....

2013-02-06 20:33:26, Info                  CSI    000009ff Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-ehome-font_31bf3856ad364e35_6.1.7600.16385_none_2ad6e90ee30ff985\WTVGOTHIC-S.ttc do not match actual file [l:30{15}]"WTVGOTHIC-S.ttc" :
  Found: {l:32 b:tS6Hw/E8qa4Cfb0TTMItxM45D09alD5jofCgvYojr84=} Expected: {l:32 b:dzS/rYReIjLpeofj7jo1l6q+cqg4X64ygEv2P/Dh6uo=}
2013-02-06 20:33:26, Info                  CSI    00000a00 [SR] Cannot repair member file [l:30{15}]"WTVGOTHIC-S.ttc" of Microsoft-Windows-ehome-font, 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
2013-02-06 20:33:26, Info                  CSI    00000a01 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-dxptasks-sync_31bf3856ad364e35_6.1.7600.16385_none_f4f399f5fbb26bc8\DxpTaskSync.dll do not match actual file [l:30{15}]"DxpTaskSync.dll" :
  Found: {l:32 b:jzATHWvin0Yx2BLyktB1sC8dOT32As+1jvZXO2bxMXE=} Expected: {l:32 b:KAtKkhINEyQMiNl/oncWeb3WWK27HRId82JKphWR6sY=}
2013-02-06 20:33:26, Info                  CSI    00000a02 [SR] Cannot repair member file [l:30{15}]"DxpTaskSync.dll" of Microsoft-Windows-DXPTasks-Sync, Version = 6.1.7600.16385, 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
2013-02-06 20:33:26, Info                  CSI    00000a03 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-ehome-font_31bf3856ad364e35_6.1.7600.16385_none_2ad6e90ee30ff985\WTVGOTHIC-S.ttc do not match actual file [l:30{15}]"WTVGOTHIC-S.ttc" :
  Found: {l:32 b:Kmhhr0oAV4t3GKKFBSHC+p3JHB4Dd8NX5lqeDwo76VA=} Expected: {l:32 b:dzS/rYReIjLpeofj7jo1l6q+cqg4X64ygEv2P/Dh6uo=}

I'll post a fix protocol later

 

[NoelDP]

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

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

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

 

[tonylka10]

https://skydrive.live.com/#cid=74B6FF23D380B09B&id=74B6FF23D380B09B!105

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-X694Y-26TPY-62HXF
Windows Product Key Hash: 3BkcibFo+Zn7pCfYBQGLlIg3hmU=
Windows Product ID: 00371-221-6087491-86673
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7600.2.00010100.0.0.048
ID: {AD277DDC-FF93-4899-B818-26D5EC727346}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7600.win7_gdr.120830-0334
TTS Error:
Validation Diagnostic:
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{AD277DDC-FF93-4899-B818-26D5EC727346}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-62HXF</PKey><PID>00371-221-6087491-86673</PID><PIDType>5</PIDType><SID>S-1-5-21-396230380-2319168695-1520334647</SID><SYSTEM><Manufacturer>To Be Filled By O.E.M.</Manufacturer><Model>To Be Filled By O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>P1.30</Version><SMBIOSVersion major="2" minor="7"/><Date>20120418000000.000000+000</Date></BIOS><HWID>03BA3607018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7600.16385

Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: 770bc271-8dc1-467d-b574-73cbacbeccd1
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00172-221-608749-00-1033-7600.0000-0112013
Installation ID: 012741599613201281313290882501822066182983794151307025
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: 62HXF
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 2/13/2013 5:25:41 PM

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 1:13:2013 06:16
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: OgAAAAIABAABAAIAAAAEAAAAAQABAAEAln0mUd3xdxYSwnTE6O3Cv7h+mCKweZC0PKXtX19QMEIucw==

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC ALASKA A M I
FACP ALASKA A M I
HPET ALASKA A M I
MCFG ALASKA A M I
ASF! INTEL HCG
SSDT Intel_ AoacTabl
AAFT ALASKA OEMAAFT
SSDT Intel_ AoacTabl
SSDT Intel_ AoacTabl
SSDT Intel_ AoacTabl
BGRT ALASKA A M I