Windows 7 Blue Screen when watching video's

[ZoloK]

Hello i just started getting blue screen when im watching videos online, and no this is not all video's.
Some work fine, others i will crash.
Now i know im supposed to upload the mini dump but for some reason i dont have permission to upload it ?

Ive been looking around on the net for quite awhile and tried out quite a few things with no luck

Anyways heres the analysis from windbg.


Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\080414-8720-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532
Machine Name:
Kernel base = 0xfffff800`0345b000 PsLoadedModuleList = 0xfffff800`03697e70
Debug session time: Mon Aug 4 21:28:16.226 2014 (UTC + 2:00)
System Uptime: 0 days 0:05:46.552
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800ff2cdbb, fffff88003c77328, fffff88003c76b90}

Probably caused by : atikmdag.sys ( atikmdag+c7dbb )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800ff2cdbb, The address that the exception occurred at
Arg3: fffff88003c77328, Exception Record Address
Arg4: fffff88003c76b90, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
atikmdag+c7dbb
fffff880`0ff2cdbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

EXCEPTION_RECORD: fffff88003c77328 -- (.exr 0xfffff88003c77328)
ExceptionAddress: fffff8800ff2cdbb (atikmdag+0x00000000000c7dbb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8

CONTEXT: fffff88003c76b90 -- (.cxr 0xfffff88003c76b90;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000003c0000 rdi=0000000000000002
rip=fffff8800ff2cdbb rsp=fffff88003c77560 rbp=fffffa80078fe960
r8=0000000000000002 r9=000000f418120000 r10=0000000000000000
r11=fffff88003c77790 r12=fffffa80067272c0 r13=fffffa8007a0ff00
r14=fffffa80068d6010 r15=fffff8800fe65000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc7dbb:
fffff880`0ff2cdbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=00000000003c0000 rdi=0000000000000002
rip=fffff8800ff2cdbb rsp=fffff88003c77560 rbp=fffffa80078fe960
r8=0000000000000002 r9=000000f418120000 r10=0000000000000000
r11=fffff88003c77790 r12=fffffa80067272c0 r13=fffffa8007a0ff00
r14=fffffa80068d6010 r15=fffff8800fe65000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc7dbb:
fffff880`0ff2cdbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000000000006a8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800037020e0
GetUlongFromAddress: unable to read from fffff80003702198
00000000000006a8 Nonpaged pool

FOLLOWUP_IP:
atikmdag+c7dbb
fffff880`0ff2cdbb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]

BUGCHECK_STR: 0x7E

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800ff2cdbb

STACK_TEXT:
fffff880`03c77560 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffffa80`068d6010 : atikmdag+0xc7dbb


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+c7dbb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53508a3c

STACK_COMMAND: .cxr 0xfffff88003c76b90 ; kb

FAILURE_BUCKET_ID: X64_0x7E_atikmdag+c7dbb

BUCKET_ID: X64_0x7E_atikmdag+c7dbb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x7e_atikmdag+c7dbb

FAILURE_ID_HASH: {1bce3716-c561-7934-01c3-535369bb657c}

Followup: MachineOwner
---------

 

[kemical]

Hi Zolok,
we need to see your actual dump files in order to debug them. Please read the thread found here and post the results:
Link Removed

Just to add, the above is blaming the GPU driver so may need updating but if that doesn't help follow the instructions given in the thread linked and we will read your dump files for you.


Oh and i also moved your thread to the correct section.

 

[ZoloK]

thank you for the link and moving my post, here is a link to the file's that you asked for Link Removed
the screenshots are included in the folder.
and yes i tried updating my gpu driver more than once.

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800fef7dbb, fffff88003e3e328, fffff88003e3db90}

Probably caused by : atikmdag.sys ( atikmdag+c7dbb )

Followup: MachineOwner

Hi,
all your dump files are the same and is probably caused by either a driver, out of date Bios or system software.
Your missing Service Pack 1 which is critical for the smooth operation of windows. Please download and install SP1 here:
Link Removed
If you encounter issues when installing you might need the update readiness tool:
Link Removed

BiosVersion = 0805
BiosReleaseDate = 05/07/2012
You have Bios updates pending. At least 9 updates have been released since the version number above:
Link Removed

Please run the Intel driver update utility:
Link Removed

RTCore64.sys Wed May 25 07:39:12 2005: RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7) uninstall to test.

Post any new dump files.

 

[ZoloK]

So i finaly got the damn bios updated, anyways i wanted to ask real quick and this may be a silly question but, in the link you provided to get service pack 1, do i download every single file ? including the Iso file even ? what should i do with the iso file ? mount it ?

Nevermind, i figured it out, ill return once im done with it all

 

[ZoloK]

ok so i have done everything you mentioned, i assume you are gonna leave this post open so i can report back within a day or two if this has not fixed the issue.
so far thank you for your time though

Sincerely ZoloK

 

[kemical]

Hi ZoloK,
yup just post back if need be and good luck with the updates..

 

[ZoloK]

For anyone who might watch post due to same issues.
case NOT solved.
I am assuming this is faulty hardware as i am still crashing after doing everything i was told.

 

[kemical]

Hi Zolok,
we don't close threads and we work with the user until a solution has been found. Please post any new dump files and keep us updated. Sometimes it will take a while to actually track down the issue and threads running into multiple pages is not uncommon.
Please post any new dump files following the same procedure as above.

 

[ZoloK]

Hello again, so ive had 3 new blue screens since last time i posted, while they do seem more frequent, ive also not been doing what caused them, as much as before.
So here are the dump files again.
Link Removed

PS: you may notice that i still have the program installed which you asked me to uninstall, this is because i still blue screened after uninstalling it, so i decided to get it back again, as its very usefull for my fan.

again thank you for your time, sincerely zolok

 

[kemical]

Hi Zolok,
unfortunately no dump files were present are you sure they were bsods? Make sure your settings are set like this:

Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK and apply to exit the dialogs, then reboot for the changes to take effect.

Other reasons for no dump file can be no page file or one that is lower than 200MB. Sometimes users with SSDs will remove their pagefile.

You did right with the app you re-installed as i only mentioned to uninstall to test.

Let me know about your dump files and I'll debug asap.

 

[ZoloK]

thats weird im 100% sure they were blue screens as i saw the atikmdag error pop up everytime on the bluescreen.
But now that you mention the paging file, i did change it previously, tho it should be on 12000 so that shouldnt be an issue ?
i tried looking back in the post and changed settings as explained in the first link about auto restart being turned off, so i guess we'll have to see from here on. I'll be back

ZoloK

 

[kemical]

It might be worth just double checking your pagefile in case the changes you made didn't take or something similar?

 

[ZoloK]

im pretty sure everything is ok ?
Link Removed
screenshot of the pagefile settings.

 

[kemical]

These parameters must be correct for a dump file to be produced:

- Page file must be on OS drive
- Page file base allocation size must be > than installed physical RAM
- Windows Error Reporting (WER) system service should be set to MANUAL
- Set page file to system managed, OS drive

If your system complies with the above then try running a chkdsk just to make sure your storage is ok.
Link Removed

 

[ZoloK]

so everything is correct according to your info and i ran the chkdsk aswell, still no minidump files...
this is weird, but right now im typing to you as i noticed a new issue, im not sure how to describe this other than the pc shutting down randomly by itself.
Basicly my screens randomly go black and says theres no connections, you know like when your PC is turned off but you turn your screen on.
BUT after screen goes black, pc kinda freezes i think ? coz keyboard and mouse is still full light, but no sound, no picture, just black screen.
this has no specific trigger as far as i can tell, it just happends randomly.

 

[kemical]

Hey Zolok,
first try downloading and running Malwarebytes:
https://www.malwarebytes.org/

Run a System file check which will look for and if possible repair corruption. Find command prompt and right click on it, choose properties and then run as admin. Type:
sfc /scannow
Press enter and await results.

Test your CPU using Intels daignostic test:
Link Removed

Test your GPU by running Furmark:
http://www.ozone3d.net/benchmarks/fur/
Test the cards memory:
Link Removed

If after making the above changes you still get the bsod then you need to test your RAM.
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/

To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Try and run the test overnight if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

Lastly check the event viewer and see if the freezes have been logged and as what or why.