BSOD problems while gaming, and after that

Hi, since some days i have experimenting some BSOD some are 0x03b, some are 0x07b and have seen some 0x04a, and IRQL NOT LESS OR EQUAL. the majority of them appear while i play some games, can be League Of Legends, Hearthstone or World Of Warcraft. After the BSOD i have some trouble initializing windows an then some more BSOD appear, needing to restart several times.

Then i turn off the pc for a minute or two and can enter normally, sometimes even the BSOD appear when normally browsing the web but thats weird and just happen ocassionally, any tips on this?.

have run memtest to see if it was the ram and didnt get errors, same with chkdsk and sfc, so im running out on ideas of what could be

my pc especifications are

CPU: AMD Phenom II X4 925 2,8 Ghz
Motherboard: ASUSM4A78LT-M-LE
BIOS: American Megatrends Inc. 0803 , 23/07/2012
Total memory: 16.00 GB Usable: 16.00GB
HDD: Hitachi HDS721010KLA330 ATA device
Graphics card: NVIDIA GeForce GTX 660
OS: Microsoft Windows 7 Ultimate 64-bit Service Pack 1

attach the zip with the last 2 errors and other usefull information (run ccleaner by mistake), anything would be of big help

PD: and btw sorry for my english its not my native languaje

Attachment 308921

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 04/03/2014 01:13:36 a.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030314-27471-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D4348B, 0xFFFFF880028F8720, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.



On Tue 04/03/2014 01:13:36 a.m. 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: 0x3B (0xC0000005, 0xFFFFF80002D4348B, 0xFFFFF880028F8720, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.

the report from whocrashed, dont know if it can be usefull

bump
any suggestions?

Maybe you can start by removing Avast and install Microsoft Essentials.
Update the graphic card to latest driver.
Check the Memory Dimms soket for correct positions in the sokets or remove from soket them into the correct position (read in manual of motherboard).
Modify the paging file of the system manually...make a custom paging file. (Initial size = size of RAM and Maximum = 1.3x RAM (go to System>advanced system settings > advanced> performance >settings >advanced >virtual memory>change) restart.
Update the motherboard drivers.

1 done
2 already updated at 334.89 whql
3 checked
4 done
5 already updated with latest bios from asus page

now i have to wait if it crashes again

updated atk 0110 driver, i had the 2005 version, got the 2009 one, the BSOD are less frequent but still appearing

new dumps Attachment 309032

Demonmanu said:

updated atk 0110 driver, i had the 2005 version, got the 2009 one, the BSOD are less frequent but still appearing

new dumps Attachment 309032

I know that that driver is for AWAY system mode (another mode of Standby or Hibernate Mode) but if you updated that driver it is most likely that is not the issue. Can you replay with the bugchek numer in the error from the event witha copy >paste ?

these are the latest ones

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 05/03/2014 04:44:35 p.m. GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFA801B091010)
Bugcheck code: 0xA (0xFFFFFA801B091010, 0x2, 0x1, 0xFFFFF80002B4FCB6)
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.
Google query: IRQL_NOT_LESS_OR_EQUAL



On Wed 05/03/2014 04:31:30 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030514-18579-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 that cannot be identified at this time.



On Wed 05/03/2014 03:13:53 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030514-24102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A7E62D, 0xFFFFF8800AA37E20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 that cannot be identified at this time.



On Wed 05/03/2014 03:02:20 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030514-29608-01.dmp
This was probably caused by the following module: ???????
.sys (Unloaded_???????
+0x1C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000B9A490, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program 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.
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: ???????
.sys .
Google query: ???????
.sys KMODE_EXCEPTION_NOT_HANDLED



On Wed 05/03/2014 02:59:19 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030514-24804-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF6FC00069E08, 0x2, 0x0, 0xFFFFF80002AD889A)
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 that cannot be identified at this time.



On Wed 05/03/2014 02:38:43 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030514-24258-01.dmp
This was probably caused by the following module: unknown_module_fffff880`021fec20.sys (Unloaded_Unknown_Module_fffff880`021fec20+0x1F24BD2)
Bugcheck code: 0x24 (0x190477, 0xFFFFF880046F54D8, 0xFFFFF880046F4D30, 0xFFFFF8800122849E)
Error: NTFS_FILE_SYSTEM
Bug check description: This indicates a problem occurred in the NTFS file system.
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_module_fffff880`021fec20.sys .
Google query: unknown_module_fffff880`021fec20.sys NTFS_FILE_SYSTEM



On Tue 04/03/2014 10:17:07 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-36613-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880031A80F8, 0xFFFFF880031A7950, 0xFFFFF80002AC1AC5)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 04/03/2014 09:37:06 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-22963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002AD3AC5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 that cannot be identified at this time.



On Tue 04/03/2014 06:49:59 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-25006-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D344F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 04/03/2014 06:02:16 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\030414-36831-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000100.sys (Unloaded_Unknown_Module_00000000`00000100+0x29B92E)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88005D4CD28, 0xFFFFF88005D4C580, 0xFFFFF880012F6E29)
Error: NTFS_FILE_SYSTEM
Bug check description: This indicates a problem occurred in the NTFS file system.
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_module_00000000`00000100.sys .
Google query: unknown_module_00000000`00000100.sys NTFS_FILE_SYSTEM

hi, can u post you system configuration here?

what type of graphic card you have can u paste a link?