 | |
| |
| 30 Jun 2012 | #1 |
| | BSOD when playing games or watching flash videos Hi guys, basically my old 6870 card died because of numerous BSODs it had over the 6 months throunh flash videos and it killed it with artifacts. I have recently received a brand new XFX 6870 and have been using it over a month and its been happening again with flash videos as occasionally get BSOD randomly like 30 mins or even over an hour. which is pointing out Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\atikmpag.sys and Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\dxgkrnl.sys its even happened once last night on a game FIFA 12 which restarted and had this error Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe How will I be able to eliminate these problems? my system specs are below and I have built this system over 8 months and nothing is overclocked. cheers |
My System Specs | |
| 30 Jun 2012 | #2 |
| | I've even got it on the desktop when just running IE  the same error below On Sat 30/06/2012 11:03:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\063012-24788-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0xA (0xFFFFF680003BEFE8, 0x0, 0x0, 0xFFFFF800020CFB2B) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® 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 Sat 30/06/2012 11:03:20 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xA (0xFFFFF680003BEFE8, 0x0, 0x0, 0xFFFFF800020CFB2B) 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. |
| My System Specs |
| 30 Jun 2012 | #3 |
| | Hello GTO and welcome to Sevenforums. BSOD Analyse Memory Related or Driver related Looking at your bugcheck it's likely that a memory corruption event were there. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one. Memtest86+ - Advanced Memory Diagnostic Tool BSOD Summary Code: IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff6800003f618, memory referenced Arg2: 0000000000000000, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000207327b, address which referenced memory ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff6800003e738, memory referenced Arg2: 0000000000000000, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80001e6c27b, address which referenced memory ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ Frederik. |
| My System Specs |
| . |
| |
| 30 Jun 2012 | #4 |
| | HI thanks for replying, well after what you said I ran memtestX86 on USB, tested both RAM on the slots and to 7 passes and no errors. what should I do next?? Thanks |
| My System Specs |
| 30 Jun 2012 | #5 |
| | 
Quote: Originally Posted by GTO656  HI thanks for replying, well after what you said I ran memtestX86 on USB, tested both RAM on the slots and to 7 passes and no errors. what should I do next?? Thanks Quote: Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier. So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature). Then, here's the procedure: - Go to Start and type in "verifier" (without the quotes) and press Enter - Select "Create custom settings (for code developers)" and click "Next" - Select "Select individual settings from a full list" and click "Next" - Select everything EXCEPT FOR "IRP Logging", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next" ( "Special Pool" may be able to be used depending on amount of RAM and errors being seen. In situations with small amounts of RAM, DO NOT select it), - Select "Select driver names from a list" and click "Next" Then select all drivers NOT provided by Microsoft and click "Next" - Select "Finish" on the next page. Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part). Reboot into Windows (after the crash) and locate the memory dump file. If present, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page. Then, zip up the memory dump file(s) and upload them with your next post. If no dump files were generated, post back for further suggestions. If you can't get into Windows because it crashes too soon, try it in Safe Mode. If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. If that doesn't work, post back and we'll have to see about fixing the registry entry off-line: Code: Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Windows 7):
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel Frederik. |
| My System Specs |
| 15 Jul 2012 | #6 |
| | Sorry for the late post, I've received another error too yesterday: On Sat 14/07/2012 23:37:22 GMT your computer crashed crash dump file: C:\Windows\Minidump\071512-30326-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x423F9) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800020433F9, 0xFFFFF880009A99D8, 0xFFFFF880009A9230) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. 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 Sat 14/07/2012 23:37:22 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800020433F9, 0xFFFFF880009A99D8, 0xFFFFF880009A9230) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time |
| My System Specs |
| 22 Jul 2012 | #7 |
| | Hello, Are you able to upload the dumps? Also do the following- i) Make your way to ATI Drivers - Downloads and download the latest driver for your card, save it to your desktop for instance ii) Uninstall the Graphic driver you currently have and all its extensions (do not reboot yet) iii) Download Driver Sweeper iv) Get to safe mode (without network) and search for Driver Sweeper in your  v) Select all the ATI components and analyse them vi) Clean them, head into Windows without internet and install the driver you've downloaded previously Drivers to be aware of Code: AsIO.sys Mon Apr 6 09:21:08 2009 (49D9AD64) ASACPI.sys Thu May 14 03:25:17 2009 (4A0B72FD) athrx.sys Mon Oct 5 18:33:57 2009 (4ACA1FF5) amdiox64.sys Thu Feb 18 16:17:53 2010 (4B7D5A21) amdxata.sys Fri Mar 19 17:18:18 2010 (4BA3A3CA) ntk_PowerDVD_64.sys Tue Aug 3 11:04:12 2010 (4C57DB8C) 000.fcl Fri Nov 19 01:53:28 2010 (4CE5CA88) speedfan.sys Fri Mar 18 17:08:46 2011 (4D83838E) Rt64win7.sys Fri Jun 10 08:33:15 2011 (4DF1BAAB) AODDriver2.sys Wed Jun 15 10:38:35 2011 (4DF86F8B) cpuz135_x64.sys Wed Sep 21 10:23:41 2011 (4E799F0D) AtihdW76.sys Tue Oct 18 09:09:49 2011 (4E9D263D) aswFsBlk.SYS Mon Nov 28 18:51:52 2011 (4ED3CA38) aswMonFlt.sys Mon Nov 28 18:52:10 2011 (4ED3CA4A) aswTdi.SYS Mon Nov 28 18:52:18 2011 (4ED3CA52) aswRdr.SYS Mon Nov 28 18:52:20 2011 (4ED3CA54) aswSP.SYS Mon Nov 28 18:53:57 2011 (4ED3CAB5) aswSnx.SYS Mon Nov 28 18:54:05 2011 (4ED3CABD) atikmpag.sys Tue Dec 6 03:12:14 2011 (4EDD79FE) atikmdag.sys Tue Dec 6 03:52:23 2011 (4EDD8367) ASACPI.sys athrx.sys amdiox64.sys amdxata.sys ntk_PowerDVD_64.sys 000.fcl speedfan.sys Rt64win7.sys AODDriver2.sys cpuz135_x64.sys AtihdW76.sys aswFsBlk.SYS aswMonFlt.sys aswTdi.SYS aswRdr.SYS aswSP.SYS aswSnx.SYS atikmpag.sys atikmdag.sys Best Regards, Frederik. Last edited by FredeGail; 22 Jul 2012 at 08:14 AM.. |
| My System Specs |
 |
BSOD when playing games or watching flash videos problems?
| Thread Tools | |
| Similar help and support threads for: BSOD when playing games or watching flash videos | ||||
| Thread | Forum | |||
 BSOD while playing games or watching videos | BSOD Help and Support | |||
| BSOD when watching videos and playing games | BSOD Help and Support | |||
| BSOD while watching videos, playing games or music | BSOD Help and Support | |||
| Freezing or BSOD when playing games or watching flash videos | BSOD Help and Support | |||
| BSOD while playing games, browsing, watching videos.... please help | BSOD Help and Support | |||
All times are GMT -5. The time now is 08:01 AM.
