black screen / maybe bsod

when trying to watch a link on facebook or go watch movies on youtube or something like that or a random game i play the computer screen will go black and restart after a minute or so then when restarted says windows recovered from a error search for solution when click for solution window closes and doesnt reappear my crash boot log all look the same saying this Welcome to WhoCrashed (HOME EDITION) v 3.06 System Information (local) ——————————————————————————– computer name: JOSHSCOMP windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: AuthenticAMD AMD Phenom™ II X6 1075T Processor AMD586, level: 16 6 logical processors, active mask: 63 RAM: 8587370496 total VM: 2147352576, free: 1913323520 Crash Dump Analysis ——————————————————————————– Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 7/20/2012 9:21:23 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\072012-19156-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032A0756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. 24 similar crashes with same numbers and file links and names except the crash dump file when looking for the specified file path [C:\Windows\system32\ntoskrnl.exe] with see hidden items on it is not in there my computer specs are as follows windows 7 home premium service pack 1 amd phenom™ II x6 1075t processor 3.00 GHz installed memory 9RAM0: 8.00GB system type 64bit operating system

Hi advento,
Welcome to WTT

Please download WhoCrashed (scroll down to Crash Analysis Tool) to your desktop.
http://www.resplendence.com/downloads


1) Click on the file you just downloaded and run it.
2) Put a tick in Accept then click on Next
3) Tick Don't create a start menu folder / click Next
4) Tick Create a Desktop Icon / click on Install / tick Launch Whocrashed / click Finish
5) Click Analyze

It will want to download the Debugger and install it / Yes

WhoCrashed will create report /.scroll down to see it
Copy and paste it into your next reply.

Cheers,
Lee

——————————————————————————– System Information (local) ——————————————————————————– computer name: JOSHSCOMP windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: AuthenticAMD AMD Phenom™ II X6 1075T Processor AMD586, level: 16 6 logical processors, active mask: 63 RAM: 8587370496 total VM: 2147352576, free: 1918402560 ——————————————————————————– Crash Dump Analysis ——————————————————————————– Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sat 7/21/2012 8:01:30 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\072112-16863-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032E1756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 7/20/2012 9:21:23 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\072012-19156-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032A0756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Fri 7/20/2012 3:02:47 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071912-38719-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF80003287756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 7/19/2012 1:40:56 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071812-17284-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032DB756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Wed 7/18/2012 12:19:39 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071712-16458-01.dmp This was probably caused by the following module: Unknown (0xFFFFF880073E06E4) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032D7756) Error: IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown . Google query: Unknown IRQL_NOT_LESS_OR_EQUAL On Tue 7/17/2012 12:42:55 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\071712-16224-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032A1756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 7/12/2012 2:14:34 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\071112-19000-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF8000329F756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/9/2012 11:57:53 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070912-19593-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032D7756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/9/2012 8:16:31 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070912-20716-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032D9756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/9/2012 7:59:04 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070912-25818-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032D5756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/9/2012 7:55:30 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070912-24772-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF80003291756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Mon 7/9/2012 7:20:39 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070912-18220-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032D3756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 7/8/2012 10:41:06 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070812-22947-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032D9756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 7/8/2012 9:06:03 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070812-20217-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032CF756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sun 7/8/2012 4:29:49 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070812-17846-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x0, 0xFFFFF800032CF756) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. ——————————————————————————– Conclusion ——————————————————————————– 37 crash dumps have been found and analyzed. Only 15 are included in this report. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.) aswsp.sys (avast! self protection module, AVAST Software) unknown If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

It looks like you have a corrupt video driver causing problems.

Downloaded the latest Windows updates. If Microsoft update does not include a video driver as a download option, go to ATI support to download the latest video driver for your computer.

If you are not sure of which video driver you need, please let us know your computer model and version. I can then supply a link to the correct driver.

I notice you have Avast anti-virus installed. There may also be a problem there, but lets first see if a new video driver fixes the computer problem. If you have more than one anti-virus program installed, remove them as they will cause conflicts with Avast.

It might be a good idea to check your computer temps too. Download and install this small program: SpeedFan.. Make no adjustments to the program, just run it as is.

The temps we need are HD0, CPU, MB and GPU.

Cheers,
Lee

Description A problem with your video hardware caused Windows to stop working correctly. Problem signature Problem Event Name: LiveKernelEvent OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Files that help describe the problem WD-20120721-0131.dmp sysdata.xml WERInternalMetadata.xml View a temporary copy of these files Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer. Extra information about the problem BCCode: 117 BCP1: FFFFFA80076174E0 BCP2: FFFFF88002D99250 BCP3: 0000000000000000 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 i found this error report while brousing thru google help i have taken 2 sticks out each time and restart computer and tried to see if it was ram peieces still does it i have completly reset all internet settings and plugins its automatically scheduled defrag weekly but when i watch a video that is on my hard drive it does not crash just video games or online videos still working on trying to get the speedfan application to work at this time

and at this time the the radeon hd 6800 series driver is up to date with the AMD VISION Engine Control center with default settings but also as i stated i have tried to stress the graphics card and played 3 movies similtaniously for ten minutes that are on my hard drive and it executed without a problem but watching the cat bloopers movie on youtube it crashes my computer after just 45 seconds

and the fan speeds are as follows fan 1 3184 rpm gpu fan 2516 rpm TEMPS.. temp 1 41c temp 2 43c temp 3 45c hdo 41c hd1 44c gpu 40c core 33c also the whocrash did not prompt me to install a debugger just the ability to read the crash reports

i have tried to stress the graphics card and played 3 movies similtaniously for ten minutes that are on my hard drive and it executed without a problem but watching the cat bloopers movie on youtube it crashes my computer after just 45 seconds

So your PC works fine now except for watching "Cat bloopers" on youtube which crashes your pc.

I can't analyze particular youtube videos as there is often all sorts of glitches there and possibly even videos that may crash a pc.
I'd suggest avoiding "cat bloopers" if it's causing "pc bloopers"

Were you able to watch the same videos (cat bloopers) previously without your PC crashing? If so, have you made any hardware or significant software changes recently? You could try rolling back your video driver to the previous version, especially if it was not causing problems.

Cheers,
Lee

Added PS: You have not overclocked your video card by any chance have you?

no i have not overclocked anything as it said it may damage my computer and i saw no reason to try.. The computer crashes at any imbedded video on a webpage being facebook youtube or anywhere else i have looked and when i play games mainly (mmorpg games) that are saved on my harddrive it crashes as well.. but when i look at pictures or movies that are saved on my harddrive i have no problem at all.. when it does crash sometimes it will go straight black and sometimes it will look like the picture i added.. and i dont believe i made any hardware changes and i bought the computer last february from newegg.com a little over a year ago… the computer does work besides the crashing on embedded videos and gaming crashes which is what i mostly used this for.. the last graphics driver update i did was 6/11/12 which was 2 weeks after the computer started crashing

If it is embedded video that you are having problems with, I suspect a flash problem, Try un-installing your flash player and installing a fresh version. Are you using Firefox by any chance?

no im not using firefox just regular IE8 i have deleted adobe flash and all adobe products and java as well.. restarted and reinstalled still doing the same problem will play video somewhere between 30seconds to 2 minutes then will still crash video games crash when started

he last graphics driver update i did was 6/11/12

I will take that to mean 11.6.12 (?) Which was fairly recent and a major software change.

If you have a restore point before that date, do a system restore.
If not, please roll-back the video driver to the last version and see how that goes.

Cheers,
Lee

might be worth turning off hardware acceleration in the flash settings and see if that makes a difference.

might be worth turning off hardware acceleration in the flash settings and see if that makes a difference.

wow im amazed that seems to work with the online imbedded videos… im gonna try one of my mmorpg games but dunno how i would turn off a hardware accelerator if there is one on those

im gonna try one of my mmorpg games

As well as "turning off hardware acceleration", for any flash games you have had problems with you should disable ActiveX filtering. You can find out how to do that here.