BSOD when playing games or watching flash videos

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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Cheers,
Frederik.

GTO656 said:

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

Let's do some Driver Verifier.

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/Win7 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, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Best Regards,
Frederik.

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)

AsIO.sys
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.