Blue Screen of Death

Toggle sidebar Toggle sidebar
S

SirRudeGamer

Reputable
Nov 28, 2015
22
0
4,510
Hi,

I have been receiving BSOD's for a while and I would like to get it fixed. The BSOD's usually occur when I watch YouTube videos on Chrome or play Skyrim but half the time happen randomly. It can take up to two hours of starting my computer.
Here are the few latest minidumps: https://onedrive.live.com/redir?resid=7C659656EC616A17!390&authkey=!ACMe_BfbjbcXPzk&ithint=folder%2c (You will have to copy and paste the entire link into your browser, its not detecting the full link)

They all seem to be caused by ntoskrnl.exe but thats all I can really tell from Blue Screen View.

Any help is appreciated, thanks
 
Solution
Colif
So the motherboard has no codes or anything written on it? think we need to work out what it is. it could be the cause.

The bios is a start but without knowing the features of the board, it must be hard to keep up to date.
Sort by date Sort by votes


Ok, thank you :)
 
Upvote 0 Downvote


It didn't work 🙁
 
Upvote 0 Downvote


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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 18-Mar-16 10:46:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031916-22093-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltpPerformPreCallbacks+0x167)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018E666B97, 0xFFFFD0014C0FE368, 0xFFFFD0014C0FDB80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 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 Fri 18-Mar-16 10:46:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltpPerformPreCallbacks+0x167)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8018E666B97, 0xFFFFD0014C0FE368, 0xFFFFD0014C0FDB80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 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 Fri 18-Mar-16 10:26:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031816-15734-01.dmp
This was probably caused by the following module: hal.dll (hal!KeQueryPerformanceCounter+0x68)
Bugcheck code: 0xA (0xFFFFF80400052D98, 0xFF, 0x0, 0xFFFFF8035640F1C8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Thu 17-Mar-16 11:16:01 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031816-19765-01.dmp
This was probably caused by the following module: ndis.sys (ndis!ndisInterruptDpc+0x14B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80017756E4B, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
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 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 Thu 17-Mar-16 11:25:54 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031716-15937-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF8010035F28A, 0xFF, 0x0, 0xFFFFF80148032001)
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 that cannot be identified at this time.



On Thu 17-Mar-16 7:50:12 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031716-28265-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF8020D400BB4, 0xFF, 0x0, 0xFFFFF8022169D001)
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 that cannot be identified at this time.



On Mon 14-Mar-16 3:58:57 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031416-19937-01.dmp
This was probably caused by the following module: win32k.sys (win32k!NtUserQueryWindow+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960494D1AF0, 0xFFFFD00020E93210, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Multi-User Win32 Driver
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 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 Sat 12-Mar-16 11:29:18 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031216-17250-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF8030035F307, 0xFF, 0x17, 0xFFFFF80383294001)
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 that cannot be identified at this time.



On Fri 11-Mar-16 8:39:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031216-42171-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF8010EA68AB2, 0x2, 0x0, 0xFFFFF80135FCC609)
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 that cannot be identified at this time.



On Fri 11-Mar-16 11:31:46 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031116-45562-01.dmp
This was probably caused by the following module: hal.dll (hal!KeQueryPerformanceCounter+0x68)
Bugcheck code: 0xA (0xFFFFF80300052D98, 0xFF, 0x0, 0xFFFFF802707D81C8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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.





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

18 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has 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:

rt64.sys


That's what the WhoCrashed analysis came up with
 
Upvote 0 Downvote
ouch, that is a lot in a short period.

I can't find anything on rt64.sys but what I would do first is go look at the web site for the motherboard in your pc and make sure you have all the latest drivers installed. Most bsod caused by drivers so its just a matter of finding the right one.
 
Upvote 0 Downvote


That's going to be tricky as even CPU-Z can't even find out the OEM for my motherboard and it's not anywhere on the actual motherboard. As far as I can tell all my drivers are up to date but I'll see what I can find
 
Upvote 0 Downvote
No name motherboard, makes it hard to update bios too I imagine. I had thought about suggesting that you do that too.

CPU Z keeps getting deleted by windows 10 malicious software tool. You could try Sandra Lite, it is slightly more indepth: http://www.sisoftware.eu/download-buy/ and is at least free. AIDA64 is another option but no free version.

I wish there was a all system driver updater that didn't try to install the wrong drivers, or wasn't full of malware.
 
Upvote 0 Downvote


I do know what my BIOS is. I could always try updating it to see if that fixes it
 
Upvote 0 Downvote
So the motherboard has no codes or anything written on it? think we need to work out what it is. it could be the cause.

The bios is a start but without knowing the features of the board, it must be hard to keep up to date.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom