Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

ATI Radeon graphics card failing?


  • Please log in to reply
23 replies to this topic

#1 Lumenne

Lumenne

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Vancovuer, BC
  • Local time:05:22 PM

Posted 28 January 2014 - 01:10 AM

ProBook 4720s Windows 7 Home Premium 64 bit

 

So I have been having screen pixilations (artifacts?), freezing, shutdown and BlueScreen. It is not temp related as I have been monitoring with software.

 

I have tried updating the driver made no difference, I reverted to an older driver no difference. This is happening 1-6 times a day and happens during normal web browsing.

 

I have tried to fix with Windows 7 troubleshooting but that couldn't complete.  This is what Windows is telling me AMD - Display Adapter - ATI Radeon Graphics Cards has stopped working.

Attached Files



BC AdBot (Login to Remove)

 


m

#2 Netghost56

Netghost56

  • Members
  • 973 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:07:22 PM

Posted 28 January 2014 - 10:30 AM

The bug only happens when Web Browsing? Have you tried letting the system idle and see if it happens? I would try both with and without a screensaver (assuming you use one).

 

What does your Event Viewer log say?



#3 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,001 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:22 PM

Posted 28 January 2014 - 11:23 AM

Does this happen in Safe Mode?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#4 Lumenne

Lumenne
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Vancovuer, BC
  • Local time:05:22 PM

Posted 29 January 2014 - 12:27 AM

Hi Guys thank you so much for replying.

 

So far it has not happened during safe mode but I have spent much time in safe mode yet so time will tell.

Has not happened during idle and I do not use a screen saver.

Here is a bit from my event log but honestly I don't know what I'm looking for.eventlog.jpg


Edited by Lumenne, 29 January 2014 - 12:38 AM.


#5 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:08:22 PM

Posted 29 January 2014 - 12:47 AM

Hello, if you could follow my directions below and post the speccy url into the forum, we will have a better idea of what is going on with your computer and what your computer's properties are.

 

 

  • Go to Piriform's website, and click the big download.png button.
  • Next, click Download from Piriform.com (the FileHippo link requires an extra click). Or if you want to use a portable version of Speccy (which doesn't require installation), click the builds page link and download the portable version.
  • You will now be asked where you want to save the file. The best place to put it is the Desktop, as it will be easy to find later.
  • After the file finishes downloading, you are ready to run Speccy. If you downloaded the installer, simply double-click on it and follow the prompts until installation is complete. If you downloaded the portable version, you will need to unzip it before use. Right-click the ZIP file and click Extract all. Click Next. Open up the extracted folder and double-click on Speccy.
  • Once inside Speccy, it will look similar to this (with your computer's specifications, of course):
    p22004369.gif
  • Now, at the top, click File > Publish Snapshot
  • You will see the following prompt:
    p22004371.gif
  • Click Yes > then Copy to Clipboard
    p22004372.gif
  • Now, once you are back in the forum topic you are posting in, click the p22004370.gif button. Right-click in the empty space of the Reply box and click Paste. Then, click Add Reply below the Reply box.
  • Congrats! You have just posted your specs!

Once you have posted your Speccy snapshot, it will be reviewed and a reply will be offered to you as soon as time permits.

Thank You For Choosing Bleeping Computer For computer related Help And Assistance

 

Bruce.


Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#6 Lumenne

Lumenne
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Vancovuer, BC
  • Local time:05:22 PM

Posted 29 January 2014 - 01:11 AM

http://speccy.piriform.com/results/0vT7SJkWQM1gXiOPLAlrq7P

 

Thank you so much for taking the time to help :)


Edited by Lumenne, 29 January 2014 - 01:12 AM.


#7 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:08:22 PM

Posted 29 January 2014 - 01:25 AM

No problem, allow me a few moments to look over the Speccy report and I most likely will have you run another program which will allow me to have a closer look at your system errors more accurately.

 

Bruce.


Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#8 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:08:22 PM

Posted 29 January 2014 - 01:44 AM

Please download VEW and save it to your Desktop: http://images.malwareremoval.com/vino/VEW.exe

 

Double-click VEW.exe (Vista, Windows 7 and Windows 8 users right click VEW.exe and choose Run As Administrator then under Select log to query, select:

Application

System

 

Under Select type to list, select:

Critical (Vista, Windows 7 and Windows 8 only)

Error

 

Click the radio button for Number of events

Type 20 in the 1 to 20 box

Then click the Run button.

Notepad will open with the output log.

 

In Notepad, click Edit > Select all then Edit > Copy

Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.

 

 

 

Next:

 

 

Download BlueScreenView 

No installation required. 

Double click on BlueScreenView.exe file to run the program. 

When scanning is done, go Edit>Select All

Go File>Save Selected Items, and save the report as BSOD.txt

Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

 

 

I'll probably need one more thing from you, but for now, we'll work with what you can provide from me in those two programs.


Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#9 Lumenne

Lumenne
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Vancovuer, BC
  • Local time:05:22 PM

Posted 29 January 2014 - 01:59 AM

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 28/01/2014 10:57:55 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 28/01/2014 7:07:56 AM
Type: Error Category: 0
Event: 512 Source: Microsoft-Windows-CAPI2
The Cryptographic Services service failed to initialize the VSS backup "System Writer" object.

Details:
Could not query the status of the EventSystem service.

System Error:
A system shutdown is in progress. .

Log: 'Application' Date/Time: 26/01/2014 8:31:42 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 26/01/2014 8:30:06 PM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 26/01/2014 6:11:43 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 26/01/2014 6:09:56 AM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 24/01/2014 10:44:39 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 24/01/2014 10:42:11 PM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 10/01/2014 9:40:01 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 10/01/2014 9:37:42 PM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 09/01/2014 6:59:56 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 09/01/2014 6:57:16 PM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 07/01/2014 5:12:24 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 07/01/2014 5:09:45 AM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 05/01/2014 9:27:12 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 05/01/2014 9:25:37 PM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 05/01/2014 8:33:58 PM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 05/01/2014 6:41:24 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program uDigital Theatre.exe version 3.0.16.160 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.  Process ID: 4e4  Start Time: 01cf0a45acb20a04  Termination Time: 11  Application Path: c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Theatre 3\uDigital Theatre.exe  Report Id: f60301e2-7638-11e3-9b2a-d9d5a1ff7bd8

Log: 'Application' Date/Time: 04/01/2014 7:47:46 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 04/01/2014 7:45:32 PM
Type: Error Category: 0
Event: 75 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe".Error in manifest or policy file "C:\Program Files (x86)\Skype\Toolbars\Internet Explorer\SkypeIEPluginBroker.exe" on line 2. Multiple requestedPrivileges elements are not allowed in manifest.

Log: 'Application' Date/Time: 03/01/2014 2:32:18 AM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest".Error in manifest or policy file "c:\Program Files (x86)\Arcsoft\TotalMedia Suite\TotalMedia Studio MV\CaptureModule.exe.Manifest" on line 3. The value "1, 2, 0, 17" of attribute "version" in element "assemblyIdentity" is invalid.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/01/2014 4:29:35 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 28/01/2014 4:22:01 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 28/01/2014 1:23:04 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 28/01/2014 1:14:15 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 27/01/2014 8:46:11 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 27/01/2014 5:40:57 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 27/01/2014 7:03:01 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 26/01/2014 7:20:48 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 26/01/2014 6:42:13 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 26/01/2014 5:05:14 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 25/01/2014 7:00:19 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 25/01/2014 6:50:17 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 24/01/2014 5:17:11 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/01/2014 3:12:55 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/01/2014 5:42:07 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/01/2014 5:39:41 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/01/2014 4:18:34 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/01/2014 4:09:42 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 03/01/2014 3:48:35 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 02/01/2014 10:05:36 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/01/2014 7:06:03 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:06:03 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:06:03 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:04:53 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:04:53 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:04:53 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:03:57 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:03:57 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:03:57 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:02:51 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:02:51 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 7:02:51 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 6:58:57 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 6:58:57 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 6:58:57 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 6:58:15 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 6:58:15 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 6:58:15 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.

Log: 'System' Date/Time: 28/01/2014 6:57:32 AM
Type: Error Category: 0
Event: 10005 Source: Microsoft-Windows-DistributedCOM
DCOM got error "1084" attempting to start the service wuauserv with arguments "" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334}

Log: 'System' Date/Time: 28/01/2014 6:56:49 AM
Type: Error Category: 0
Event: 7001 Source: Service Control Manager
The Computer Browser service depends on the Server service which failed to start because of the following error:  The dependency service or group failed to start.
 



#10 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:08:22 PM

Posted 29 January 2014 - 03:11 AM

Note sure if you seen the blue Screen View request I had for you in post number 8.

 

Looking at image number one that you posted in your opening post, I see BCC116. That means Bug Check Code 116.

 

That code is a video card issue known to plague both ATI and Nvidia video cards. It is called "Time Out Detection Recovery" or TDR.

 

 

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx

 

 

Now the link above brings us to this page:

 

Resolving stop (blue screen) errors in Windows 7

 

 

Quote from page linked to below: Stop errors (also sometimes called blue screen or black screen errors) can occur if a serious problem causes Windows 7 to shut down or restart unexpectedly. You might see a message that says, "Windows has been shut down to prevent damage to your computer."

These errors can be caused by both hardware and software issues, and it can be difficult to troubleshoot the problem. The following tools and methods can often help get Windows up and running again.

 

 

http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

 

I see you attempted system restore from start up recovery, that may not work if automatic updates are turned off.

 

System Restore is the easiest thing to try first. It can undo recent changes to your computer's system files that might have caused the problem. System Restore doesn't affect your personal files, such as e‑mail, documents, or photos. For more information, see What is System Restore?



To open System Restore

  1. Open System Restore by clicking the Start button 4f6cbd09-148c-4dd8-b1f2-48f232a2fd33_818. In the search box, type System Restore, and then, in the list of results, click System Restore.18abb370-ac1e-4b6b-b663-e028a75bf05b_48. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.

  2. Follow the instructions on your screen.

  3. Make sure system restore is turned on

Action center which is the white flag next to the system clock can take you there if you click on it, click recovery option and make sure system restore is active.

 

Bruce.


Edited by MrBruce1959, 29 January 2014 - 03:13 AM.

Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#11 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,001 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:04:22 PM

Posted 29 January 2014 - 11:24 AM

S.M.A.R.T. is a system which monitors the health of your hdd.   In the Speccy the hdd's S.M.A.R.T. is showing a warning.  This means that one or more of the parameters being monitored are failing.  The usual suggestion at this point is to backup all of your important data to removable media and then replace the hdd. 

 

The best way to determine the condition of the hdd is to run the manufacturers DOS diagnostic tool.  Your hdd is a Seagate, Seagate has a diagnostic tool called SeaTools for DOS.  I would suggest using this tool and run the long test for the most comprehensive results.

 

 

 
Please download SeaTool for DOS.
 
When the SeaTools for DOS website opens click on I Accept, then click on the Download button in step #4.
 
This download is a ISO image which you will need to burn to a CD in order to create a bootable disc with which to run the diagnostic tests.
 
To burn this ISO file to a CD or DVD please downlaod ImgBurn and install it.
 
Insert blank CD or DVD into your CD/DVD drive.
 
Open ImgBurn, and click on Write image file to disc.
 
ImgBurn1_zps715cb1c2.png
 
Click on the Browse for a file icon:
 
imgb1_zpsbb69e759.png
 
Right click on the Start orb startorb_zps06e1f985.png, then click on Downloads.  Scroll down to the SeaTools for DOS download and click on it.  This will load the ISO image, you will see the information listed as it is in the image below outlined in red.
 
imgb2_zps3f021ae7.png
 
Click on the blue arrow (also outlined in red) to start burning the bootable CD.
 
Once the disc is created load it in the CD/DVD drive and restart the computer.
 
Please note:  You may need to change the boot order in the BIOS so the CD/DVD-ROM is the first device in the boot order, and the hdd is the second device.
 
Please run the long test and include the results in your next post in this topic.

Edited by dc3, 29 January 2014 - 11:25 AM.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#12 Lumenne

Lumenne
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Vancovuer, BC
  • Local time:05:22 PM

Posted 29 January 2014 - 09:54 PM

MrBruce

 

Thank you once again, I have pasted the bluescreen view below.

 

==================================================
Dump File         : 012714-53009-01.dmp
Crash Time        : 27/01/2014 5:21:25 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`03d15010
Parameter 2       : fffff880`04042c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\012714-53009-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 383,120
Dump File Time    : 27/01/2014 5:23:39 PM
==================================================

==================================================
Dump File         : 012714-43274-01.dmp
Crash Time        : 26/01/2014 11:18:27 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`070dd010
Parameter 2       : fffff880`042b8c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\012714-43274-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 917,424
Dump File Time    : 27/01/2014 9:41:44 AM
==================================================

==================================================
Dump File         : 012614-43976-01.dmp
Crash Time        : 26/01/2014 11:20:05 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`096ad4e0
Parameter 2       : fffff880`04141c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\012614-43976-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,067,304
Dump File Time    : 26/01/2014 11:21:17 AM
==================================================

==================================================
Dump File         : 012614-53742-01.dmp
Crash Time        : 26/01/2014 10:40:50 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`0980f010
Parameter 2       : fffff880`04139c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\012614-53742-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,347,824
Dump File Time    : 26/01/2014 10:43:14 AM
==================================================

==================================================
Dump File         : 012514-50544-01.dmp
Crash Time        : 25/01/2014 10:57:27 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`04c3b010
Parameter 2       : fffff880`042f0c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\012514-50544-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,551,240
Dump File Time    : 25/01/2014 11:00:45 AM
==================================================

==================================================
Dump File         : 012514-50263-01.dmp
Crash Time        : 25/01/2014 10:48:07 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`08f43010
Parameter 2       : fffff880`0424cc58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\012514-50263-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 987,040
Dump File Time    : 25/01/2014 10:51:32 AM
==================================================

==================================================
Dump File         : 010814-49998-01.dmp
Crash Time        : 08/01/2014 6:42:15 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`04f95010
Parameter 2       : fffff880`04061c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010814-49998-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,133,688
Dump File Time    : 08/01/2014 7:13:40 PM
==================================================

==================================================
Dump File         : 010514-48235-01.dmp
Crash Time        : 05/01/2014 8:08:24 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`08a23010
Parameter 2       : fffff880`042c3c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010514-48235-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,497,296
Dump File Time    : 05/01/2014 8:10:12 PM
==================================================

==================================================
Dump File         : 010214-52041-01.dmp
Crash Time        : 02/01/2014 2:00:30 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`09b98010
Parameter 2       : fffff880`03c42c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010214-52041-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,704,696
Dump File Time    : 02/01/2014 2:02:30 PM
==================================================

==================================================
Dump File         : 010214-48999-01.dmp
Crash Time        : 02/01/2014 12:20:55 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`08ecf4e0
Parameter 2       : fffff880`04206c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010214-48999-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 555,744
Dump File Time    : 02/01/2014 12:22:41 AM
==================================================

==================================================
Dump File         : 010214-53274-01.dmp
Crash Time        : 02/01/2014 12:19:02 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`08eb3010
Parameter 2       : fffff880`04287c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010214-53274-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 555,744
Dump File Time    : 02/01/2014 12:20:46 AM
==================================================

==================================================
Dump File         : 010214-51792-01.dmp
Crash Time        : 02/01/2014 12:17:10 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`08e9e010
Parameter 2       : fffff880`02fa2c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010214-51792-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 555,752
Dump File Time    : 02/01/2014 12:18:54 AM
==================================================

==================================================
Dump File         : 010214-52104-01.dmp
Crash Time        : 02/01/2014 12:15:13 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`049b0010
Parameter 2       : fffff880`0420fc58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010214-52104-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 860,320
Dump File Time    : 02/01/2014 12:17:03 AM
==================================================

==================================================
Dump File         : 010214-49483-01.dmp
Crash Time        : 02/01/2014 12:01:52 AM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`095394e0
Parameter 2       : fffff880`00db8c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010214-49483-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 1,466,936
Dump File Time    : 02/01/2014 12:04:16 AM
==================================================

==================================================
Dump File         : 010114-42603-01.dmp
Crash Time        : 01/01/2014 10:59:22 PM
Bug Check String  :
Bug Check Code    : 0x00000116
Parameter 1       : fffffa80`047424e0
Parameter 2       : fffff880`043a9c58
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000002
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d140
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18228 (win7sp1_gdr.130731-2222)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\windows\Minidump\010114-42603-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 712,376
Dump File Time    : 01/01/2014 11:00:44 PM
==================================================
 



#13 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:08:22 PM

Posted 30 January 2014 - 01:55 AM

Not sure if you choose to run the tools dc3 asked you to run in post number 11. But it wouldn't hurt since the speccy did mention your hard drive was showing a warning status. 

 

I am curious if you went to the HP website and checked that all your drivers were current.

 

This link below is already set up to take you to the Windows 7 Home Premium 64 bit OS files.

 

http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/?sp4ts.oid=4145205&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D4058%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken

 

This link below should present the graphics driver at the top of the page. Try downloading that driver and install it.

 

CLICK FOR ATI GRAPHICS DRIVER

 

Hopefully that will stop the graphics errors.

 

Bruce.


Edited by MrBruce1959, 30 January 2014 - 02:04 AM.

Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#14 Lumenne

Lumenne
  • Topic Starter

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Vancovuer, BC
  • Local time:05:22 PM

Posted 03 February 2014 - 12:15 AM

A photo of the test Dc3 had me run

 

<a href="http://s1198.photobucket.com/user/shwanks/media/DSC03767.jpg.html" target="_blank"><img src="http://i1198.photobucket.com/albums/aa459/shwanks/DSC03767.jpg" border="0" alt=" photo DSC03767.jpg"/></a>

 

All my drivers are up to date

 

I was problem free for 3 days but it is worse now, 4 crashes in less than 2 hours and the last time I was not browsing, just idle with my desktop showing.



#15 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:08:22 PM

Posted 03 February 2014 - 02:59 AM

To the best of your knowledge, have you downloaded and installed or installed any programs just before this all started?

 

Please download MiniToolBox, save it to your desktop and run it.
Checkmark the following checkboxes:

  • List content of Hosts
  • List IP configuration
  • List Winsock Entries
  • List last 10 Event Viewer log
  • List Installed Programs
  • List Devices
  • List Users, Partitions and Memory size.
  • List Minidump Files
  • List Restore Points

Click Go The tool will scan your system and a copy of Result.txt will be saved in the same directory the tool is run. Such as your desktop.

Please post the results from result.txt in your next reply. I hope this time around something will jump out at me from those logs as to what might be causing this problem to happen.

 

Bruce.


Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users