BSOD caused by driver ntoskrnl.exe

Toggle sidebar Toggle sidebar
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
Hi,I have some crashes random...I don't know what's the cause,but blue screen viewer show this:

1st.
062514-16582-01.dmp
25/06/2014 20:19:35
IRQL_NOT_LESS_OR_EQUAL
0x0000000a
00000000`061b1998
00000000`00000002
00000000`00000000
fffff800`030c4f42
ntoskrnl.exe
ntoskrnl.exe+75bc0
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7601.18409 (win7sp1_gdr.140303-2144)
x64
ntoskrnl.exe+75bc0
C:\Windows\Minidump\062514-16582-01.dmp 6
15
7601
275.336
25/06/2014 20:20:18

2nd.
061914-24694-01.dmp 19/06/2014 12:23:24 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`0313276b ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\061914-24694-01.dmp 6 15 7601 275.336 19/06/2014 12:24:40


3rd.
061914-25646-01.dmp 19/06/2014 12:11:05 0x00000101 00000000`00000021 00000000`00000000 fffff880`02f65180 00000000`00000002 msahci.sys msahci.sys+4739 x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\061914-25646-01.dmp 6 15 7601 275.336 19/06/2014 12:13:14

4th.
061614-16021-01.dmp 16/06/2014 19:39:27 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 tcpip.sys tcpip.sys+16d9a0 x64 ntoskrnl.exe+75b90 C:\Windows\Minidump\061614-16021-01.dmp 6 15 7601 275.336 16/06/2014 19:40:07

5th.
061614-19344-01.dmp 16/06/2014 19:10:10 KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c000001d fffff880`086ab450 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\061614-19344-01.dmp 6 15 7601 275.336 16/06/2014 19:11:11

6th.
061614-16130-01.dmp 16/06/2014 18:22:29 DRIVER_OVERRAN_STACK_BUFFER 0x000000f7 00000000`039934a0 00002791`4ca60708 ffffd86e`b359f8f7 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\061614-16130-01.dmp 6 15 7601 275.336 16/06/2014 18:23:12



Can anyone help me?I had the same crashes with W 8.1 so I tried with W7 and they appears again...My pc is new,it have 4/5 month(assembled).I will give you every info you'll need.

PS:I had already tested my 2 ram (Corsair vengaence 1600 mhz) with memtest and they have pass 2 test(every one).I done a stress test to my GPU and it didn't show errors,already done scannow without errors...
 
Sort by date Sort by votes
O

onichikun

Distinguished
Nov 13, 2009
304
1
18,860
It is very likely this error is caused by an issue with a driver being loaded in your system. IRQL_NOT_LESS_OR_EQUAL basically means a program running in your operating systems kernel tried to access a service (such as memory paging) that is disabled at the current IRQL.

I would check your device managers, run windows update, and verify that you have proper drivers installed. Do you have any 3rd-party hardware installed? Gaming pads, cameras, etc. These devices could be causing this error, esp. if the wrong driver or a bad driver is installed.
 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
I have :
Lastest Catalyst of my GPU (R7 260X)
Haven't cameras
Gaming pads aren't plugged in
Etron USB3.0 Host controller
Microsoft.net framework 4.51
Realtek ethernet driver
Realtek High definition audio driver
Microsoft visual C++ Redistributable(2008 x 3,2010 x 2,2012 x 2)


Devices plugged in:
Audio speakers(Creative)
Mouse(Microsoft)
Wireless keyboard(Logitech)
 
Upvote 0 Downvote
Tcinator

Tcinator

Reputable
Jun 25, 2014
288
0
4,860
I'm seeing a few different bsod's here. I would recommend running tdsskiller available from Kaspersky for free. rootkits can last through installs and can cause these exact symptoms. if you can run hdd diags. that may be useful as well. My other recommendation would be to upload the minidumps for us to run through a debugger.
 
Upvote 0 Downvote
Tcinator

Tcinator

Reputable
Jun 25, 2014
288
0
4,860
So, you need to run a memory diagnostic run it for a good while. I know you said that you ran memtest. but that's what the logs are screaming. have you ran tdsskiller already? I may also suggest a BIOS update.
 
Upvote 0 Downvote
Tcinator

Tcinator

Reputable
Jun 25, 2014
288
0
4,860
Scratch that. I STRONGLY recommend a scan with tdsskiller.

This is straight from the .dmp:

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.
 
Upvote 0 Downvote
D

Decri

Reputable
Jun 25, 2014
23
0
4,510
Tdsskiller didn't found anything...So I will run memtest all this night.
Have I to run it with all the 2 RAM plugged in?Because I ran it before with 1 and after with the other 1

PS:I think it's impossible that I have a malware because this crashes appears with W 8.1 too..after W8.1 I had formatted my pc.
 
Upvote 0 Downvote
Tcinator

Tcinator

Reputable
Jun 25, 2014
288
0
4,860
The reason I had tdsskiller ran is because some rootkits can last between installs. you may try chipset drivers and bios updates. the bsod's range from tcpip to msahci to ntoskernal.... this is a bit strange. it may be a failing hard drive... it happens sometimes to new drive right at that 3-6 month period. So, hdd diags may be your next step.
 
Upvote 0 Downvote
Tcinator

Tcinator

Reputable
Jun 25, 2014
288
0
4,860
You are going to want to run memtest86+ over night. 5+ runs. and possibly prime95 just to beat up your rig. It is possible the motherboard has some defect, but ill pray its just a deep memory error that takes a while to surface. run memtest tonight and post in the am!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom