BSOD several times a day

Hikapoo

Honorable
Dec 15, 2013
7
0
10,510
I have a home built win 8 pc which tends to get BSOD alot, I have run a memtest and did not get any errors after 3 passes. I have tried to update and reinstall drivers but nothing seems to work, sometimes I can go for hours without crashing, but especially when I'm on youtube I get alot of shockwave flash crashes and thereafter a BSOD.

My dumpfiles suggest that they are software problems, but I do believe it can be related to hardware.

I'll list my dump files down here, maybe someone could help me pinpoint the problem, because the dumpfiles can certainly not...



System Information (local)
--------------------------------------------------------------------------------

windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., RAMPAGE IV EXTREME
CPU: GenuineIntel Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 34295222272 total
VM: 2147352576, free: 1903484928




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 05.02.2014 22:06:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-25046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xFC (0xFFFFE00003400FC0, 0x80000008048009E3, 0xFFFFD00024F50BA0, 0x4)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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.02.2014 22:06:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x11E6)
Bugcheck code: 0xFC (0xFFFFE00003400FC0, 0x80000008048009E3, 0xFFFFD00024F50BA0, 0x4)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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 Wed 05.02.2014 21:50:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-25359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF800632BEB76)
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.02.2014 14:40:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-25437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0xFFFFF6008033A828, 0x0, 0x1, 0xFFFFF80281EDA209)
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.02.2014 14:21:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-25515-01.dmp
This was probably caused by the following module: iastora.sys (iaStorA+0x68822)
Bugcheck code: 0x7F (0x8, 0xFFFFD00020A482B0, 0x20A6A7E0, 0xFFFFF80000934822)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\iastora.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation).
Google query: Intel Corporation UNEXPECTED_KERNEL_MODE_TRAP



On Wed 05.02.2014 01:31:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xF7 (0x12BB6DE13459, 0x12BB6D293459, 0xFFFFED4492D6CBA6, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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.02.2014 00:15:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-14578-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x324B7)
Bugcheck code: 0x24 (0xB500190637, 0xFFFFD00026CD5EA8, 0xFFFFD00026CD56B0, 0xFFFFF80000C83854)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: NTFS-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.02.2014 23:07:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020514-14500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFFFFFC985800C, 0x1, 0xFFFFF80320AAF872, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.02.2014 21:12:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020414-15031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF8013EAB1B76)
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 Tue 04.02.2014 19:09:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020414-14781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80073F1A87E, 0xFFFFD00026904D20, 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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

51 crash dumps have been found and analyzed. Only 10 are included in this report. 5 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:

verifierext.sys (Driver Verifier Extension, Microsoft Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 334.67 , NVIDIA Corporation)
iastora.sys (Intel Rapid Storage Technology driver - x64, Intel Corporation)
samsungrapiddiskfltr.sys
rtkvhd64.sys


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.




 

molokaidiver

Honorable
May 15, 2013
3
0
10,510
Instead of doing a memory test, try process of elimination. If i'm correct, it looks like you're running 4 gigs of RAM? If it's x2 2gb sticks, try taking out one and run your computer then...if the problem continues, try the other stick...if the problem continues, try switching slots...if all that fails, try finding spare ram that you know works and install it into your computer. if you're still encountering errors, then the fault lies somewhere else...possibly bad board. Not really a solution but suggestions hoping to be solutions. Hope this helps.
 
It looks like a driver issue.
Make sure you have also installed all available Windows hotfixes.
Have you installed the following drivers?

Intel(R) Rapid Storage Technology Driver Software V12.8.0.1016 for Windows 7/8/8.1 32bit & 64bit.(WHQL)
Intel Rapid Storage Technology enterprise driver software V3.6.0.1093 for Windows Vista/7/8 32bit & 64bit.(WHQL)
Asmedia SATA Controller Driver V1.3.4.0 for Windows XP/Vista/7/8 32bit & 64bit.(WHQL)
Asmedia AHCI Driver V1.3.4.0 for Windows 8 32bit & 64bit.(WHQL)
Intel X79 chipset V9.3.2.1015 for Windows 8 32&64bit.
Intel(R) Chipset Software Installation Utility V9.3.2.1015 for Windows XP/Vista/7/8/8.1 32bit & 64bit.(WHQL)

https://www.asus.com/au/ROG_ROG/RAMPAGE_IV_EXTREME/#support
 

Hikapoo

Honorable
Dec 15, 2013
7
0
10,510


I'm actually running x4 8gb, which makes 32 gb ram, I will try to run the sticks seperatly and see if it finds anything.
 

Hikapoo

Honorable
Dec 15, 2013
7
0
10,510


I have downloaded all the drivers now, I'll report back if i get more BSoD, though it did seem like everything was mostly up to date. I'll also try to update the motherboard whenever I get a hold of a usb drive.
 

Hikapoo

Honorable
Dec 15, 2013
7
0
10,510


I have downloaded all the drivers now, I'll report back if i get more BSoD, though it did seem like everything was mostly up to date. I'll also try to update the motherboard whenever I get a hold of a usb drive.
 


The motherboard bios can be updated from within Windows, you don't need to boot from a USB device.
 
-run malwarebytes to confirm you do not have malware
- remove these two drivers:
Asus Smart Doctor/iTracker 2
C:\Windows\system32\drivers\IOMap64.sys Thu Feb 04 17:55:34 2010

SystemRoot\system32\DRIVERS\nvoclk64.sys Tue Sep 15 14:59:25 2009

I suspect that one of these drivers is corrupting your stack and windows caught it and called a bugcheck on the assumption it was a hacking attempt.
I would also update these two drivers if you can locate a update
\SystemRoot\System32\drivers\HECIx64.sys Mon Dec 17 11:32:21 2012


\SystemRoot\system32\DRIVERS\e1c64x64.sys Wed Aug 21 03:09:36 2013
(this one is a intel lan driver, you want to update this because of a driver memory leak, unrelated to this problem)






problem:
BugCheck F7, {12bb6de13459, 12bb6d293459, ffffed4492d6cba6, 0}DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer. This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned. This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.

machine:
Processor Version Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz
Processor Voltage 8ah - 1.0V
Manufacturer ASUSTeK COMPUTER INC.
Product RAMPAGE IV EXTREME
Version Rev 1.xx
BIOS Release Date 08/29/2013






 

Hikapoo

Honorable
Dec 15, 2013
7
0
10,510
So I've downloaded and updated all the drivers I could, and now it seems I only get BSods when I watch something flash related. I will get several errors where shockwaves flash crashes, and then a BSod. I've also checked the ram, they all work on the left side but when I test them out on the right side the monitor wont show anything for some reason, I don't know if this is suppose to happen or that it may be defect, I got a Rampage Extreme IV motherboard, and use the ram on the red sockets.