Jump to content

Various blue screens


TheAkreian

Recommended Posts

Kevin recently helped me with a malware infection and told me to refer to that page for better assistance.

 

It finally created a minidump this time.

 

https://forums.malwarebytes.org/index.php?showtopic=139797&page=3

 

I am currently uninstalling recent games.

 

 

Heres a VEW

 

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 08/01/2014 4:30:50 AM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 08/01/2014 5:46:27 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.
 
Log: 'Application' Date/Time: 08/01/2014 5:44:42 AM
Type: Error Category: 0
Event: 9 Source: SideBySide
Activation context generation failed for "C:\Program Files\WinZip\adxloader.dll.Manifest".Error in manifest or policy file "C:\Program Files\WinZip\adxloader.dll.Manifest" on line 2. The manifest file root element must be assembly.
 
Log: 'Application' Date/Time: 07/01/2014 3:10:47 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll".Error in manifest or policy file "c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll" on line 3. The value "MAJOR_VERSION.MINOR_VERSION.BUILD_NUMBER_MAJOR.BUILD_NUMBER_MINOR" of attribute "version" in element "assemblyIdentity" is invalid.
 
Log: 'Application' Date/Time: 07/01/2014 3:09:34 AM
Type: Error Category: 0
Event: 9 Source: SideBySide
Activation context generation failed for "C:\Program Files\WinZip\adxloader.dll.Manifest".Error in manifest or policy file "C:\Program Files\WinZip\adxloader.dll.Manifest" on line 2. The manifest file root element must be assembly.
 
Log: 'Application' Date/Time: 06/01/2014 1:56:30 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Users\Akillease\Desktop\esetsmartinstaller_enu.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
 
Log: 'Application' Date/Time: 06/01/2014 1:56:27 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Users\Akillease\Desktop\esetsmartinstaller_enu.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
 
Log: 'Application' Date/Time: 06/01/2014 1:56:27 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Users\Akillease\Desktop\esetsmartinstaller_enu.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
 
Log: 'Application' Date/Time: 06/01/2014 1:50:13 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Users\Akillease\Desktop\esetsmartinstaller_enu.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
 
Log: 'Application' Date/Time: 06/01/2014 1:34:47 PM
Type: Error Category: 0
Event: 80 Source: SideBySide
Activation context generation failed for "C:\Users\Akillease\Desktop\esetsmartinstaller_enu.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest.
 
Log: 'Application' Date/Time: 06/01/2014 10:31:10 AM
Type: Error Category: 0
Event: 1 Source: Chrome
The event description cannot be found.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/01/2014 9:17:40 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The SBSD Security Center Service service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 08/01/2014 9:17:38 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The SecureUpdate service failed to start due to the following error:  The system cannot find the path specified.
 
Log: 'System' Date/Time: 08/01/2014 9:17:29 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The atksgt service failed to start due to the following error:  This driver has been blocked from loading
 
Log: 'System' Date/Time: 08/01/2014 9:17:29 AM
Type: Error Category: 0
Event: 875 Source: Application Popup
Driver atksgt.sys has been blocked from loading.
 
Log: 'System' Date/Time: 08/01/2014 9:17:27 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The SAS Core Service service failed to start due to the following error:  The system cannot find the file specified.
 
Log: 'System' Date/Time: 08/01/2014 9:16:50 AM
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000041284, 0xfffff704401b4001, 0x0000000000013df4, 0xfffff70001080000). A dump was saved in: C:\Windows\Minidump\010814-25381-01.dmp. Report Id: 010814-25381-01.
 
Log: 'System' Date/Time: 08/01/2014 9:16:50 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 3:57:06 AM on ?1/?8/?2014 was unexpected.
 
Log: 'System' Date/Time: 08/01/2014 5:55:25 AM
Type: Error Category: 0
Event: 5 Source: Microsoft-Windows-Kernel-General
{Registry Hive Recovered} Registry hive (file): '\??\Volume{7dc86ea2-6863-11e1-9389-806e6f6e6963}\System Volume Information\SPP\SppCbsHiveStore\{cd42efe1-f6f1-427c-b004-033192c625a4}{1FF5F51C-1A9E-4031-B3E4-A86718C6EC0A}' was corrupted and it has been recovered. Some data might have been lost.
 
Log: 'System' Date/Time: 08/01/2014 4:44:56 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Steam Client Service service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion.
 
Log: 'System' Date/Time: 08/01/2014 4:44:56 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect.
 
The minidump is attached as .rar
 
 
 
Thanks for your time, 
 
Sean

010814-25381-01.rar

Link to post
Share on other sites

  • Root Admin

It looks like it is probably due to a bad memory module.  I would recommend that you download memtest and burn the ISO to disk and then boot from it and do a test, if it passes then do another full test

 

memtest.org

memtest86+-5.01.iso.zip

 

Windows 7: RAM - Test with Memtest86+

 

Link to post
Share on other sites

Hi im finally able to be here posting.  More blue screens happened.  It's strange, sometimes my computer will run for hours, other times, minutes.

 

I do not have a disc to burn the iso to, unfortunately.

 

Here are the new crash reports.

 

the most recent was System service exception, not sure if it wrote it or not

3Minidumps.rar

Link to post
Share on other sites

  • Root Admin

If you follow the links you can build the disk with a USB stick too.

 

All of those dumps point to some type of error reading or write memory.  It's very likely that you may have a bad stick of RAM - or something else going on that mimics a memory issue.

 

Again I would highly advise you to fully test your system memory to confirm it's not bad.

Link to post
Share on other sites

Hi:

Until AdvancedSetup or the experts return/arrive...

 

Im on my phone. I wasnt able to get memtest to run. I get crashes like bad pool caller irql not less or equal . Something like that.

Did you create the ISO on the USB stick?

(You can't just run the zip file from the stick.)

Might want to re-check the instructions?

The tutorials at sevenforums.com are generally quite excellent.

Just take your time with the steps.

 

Would factory restoring fix this problem?

No, not if you have a bad RAM stick.

"Factory restore" just sets the system (OS, drivers, programs) back to how the computer was when it left the factory.

It does not have any effect on a bad memory module.

I'm just a home user, but I would really try to follow AdvancedSetup's advice.

If you have bad RAM, then the entire system is vulnerable to total failure until it's replaced.

I'm sure the staff and experts will have additional advice.

Cheers,

daledoc1

Link to post
Share on other sites

Yes I want to. As of now my computer wont even start.

 

Hmm, well unfortunately that can happen with bad RAM.

BSOD is usually caused by hardware or driver problems (or sometimes bad rootkit infections, but you excluded that already).

If you're unable to run the memtest because the system won't boot at all, there may be few options.

 

Please wait for one of the staff or expert members to advise you.

I have a feeling it's going to entail a recommendation that you take the computer to a local, trustworthy, "mom and pop" computer shop (not a big box electronics store) for help.

 

Thanks for your patience,

 

daledoc1

Link to post
Share on other sites

  • Root Admin

Great, glad you got it sorted out.  If you've had severe crashes you may want to run a full disk check to ensure your data integrity is good.

 

From and elevated Admin command prompt you can run the following then press Y and the Enter key and reboot to let it run and check the disk.

 

 

CHKDSK C: /R

 

Cheers

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.