F5F Stay Refreshed Power Users Overclocking Assistance with 0x3b crash, SYSTEM_SERVICE_EXCEPTION at ntoskrnl.exe+80640

Assistance with 0x3b crash, SYSTEM_SERVICE_EXCEPTION at ntoskrnl.exe+80640

Assistance with 0x3b crash, SYSTEM_SERVICE_EXCEPTION at ntoskrnl.exe+80640

Pages (2): 1 2 Next
W
William_Burke
Junior Member
5
11-10-2016, 11:10 AM
#1
[strike]Can't find it, turns out this one driver is the cause of every single problem I've been having (Bluescreens and crashes, which resulted in the death of my 2TB drive) for the past six months or so. Want to disable it, but can't find an option for it in the BIOS.
So, would any of you happen to know where the option is? Thanks![/strike]
Ignore all that, I am dumb and was misinformed.
Still getting BSODS and it's making getting work done really damn difficult. It doesn't even take stress to crash anymore. Just random bluescreens.
This is the crash I got before starting this topic.
W
William_Burke
11-10-2016, 11:10 AM #1

[strike]Can't find it, turns out this one driver is the cause of every single problem I've been having (Bluescreens and crashes, which resulted in the death of my 2TB drive) for the past six months or so. Want to disable it, but can't find an option for it in the BIOS.
So, would any of you happen to know where the option is? Thanks![/strike]
Ignore all that, I am dumb and was misinformed.
Still getting BSODS and it's making getting work done really damn difficult. It doesn't even take stress to crash anymore. Just random bluescreens.
This is the crash I got before starting this topic.

R
reddwarf1234
Member
219
11-14-2016, 02:50 AM
#2
Typically in the chipset or integrated peripherals part, everything depends on the BIOS, but whether it's the root of your issues isn't clear. You might try disabling it in Device Manager if it's not listed in the BIOS.
R
reddwarf1234
11-14-2016, 02:50 AM #2

Typically in the chipset or integrated peripherals part, everything depends on the BIOS, but whether it's the root of your issues isn't clear. You might try disabling it in Device Manager if it's not listed in the BIOS.

C
CatBuggz
Member
248
11-14-2016, 02:59 AM
#3
Hello... That is a "firewire" connection... I Don't see your MB hardware spec'd with it. B /
1) What is the exact model of your MB?
2) What else do you have with hardware/parts?
C
CatBuggz
11-14-2016, 02:59 AM #3

Hello... That is a "firewire" connection... I Don't see your MB hardware spec'd with it. B /
1) What is the exact model of your MB?
2) What else do you have with hardware/parts?

S
SmolDom
Junior Member
26
11-19-2016, 03:13 AM
#4
mcnumpty23 :
usually in chipset or integrated peripherals section all depends on the bios
though whether its the cause of your problems or not is another matter
could just disable it in device manager if cant find it in the bios
Oh it's definitely the cause of my problems. The driver for it keeps causing bluescreens and I finally got one that stayed up long enough to write a crash dump. Got a 0x3b code and it specified ntoskrnl.exe. There's supposed to be a hotfix for it, but for some reason it's unavailable for my system.
Thank you! I'll look for the chipset section.
S
SmolDom
11-19-2016, 03:13 AM #4

mcnumpty23 :
usually in chipset or integrated peripherals section all depends on the bios
though whether its the cause of your problems or not is another matter
could just disable it in device manager if cant find it in the bios
Oh it's definitely the cause of my problems. The driver for it keeps causing bluescreens and I finally got one that stayed up long enough to write a crash dump. Got a 0x3b code and it specified ntoskrnl.exe. There's supposed to be a hotfix for it, but for some reason it's unavailable for my system.
Thank you! I'll look for the chipset section.

X
xDomx
Junior Member
7
11-19-2016, 04:32 AM
#5
I personally think the killer network was likely dealing with a lot of memory leaks, and I can't recall the solution at this moment. Also, does the board actually support FireWire?
X
xDomx
11-19-2016, 04:32 AM #5

I personally think the killer network was likely dealing with a lot of memory leaks, and I can't recall the solution at this moment. Also, does the board actually support FireWire?

S
SamaMonster
Member
178
11-24-2016, 03:03 PM
#6
mcnumpty23 :
personally i would suspect the killer network been a lot of memory leak issues and stuff with it--cant remember the fix for that right at this moment gone brain dead
and as some one else asked does that board actually have firewire?
Board does not have firewire, I'm just dumb.
Something is causing a 0x3b BSOD, but I can't find out what. The driver responsible is ntoskrnl.exe.
S
SamaMonster
11-24-2016, 03:03 PM #6

mcnumpty23 :
personally i would suspect the killer network been a lot of memory leak issues and stuff with it--cant remember the fix for that right at this moment gone brain dead
and as some one else asked does that board actually have firewire?
Board does not have firewire, I'm just dumb.
Something is causing a 0x3b BSOD, but I can't find out what. The driver responsible is ntoskrnl.exe.

I
Imagodie
Junior Member
16
12-10-2016, 12:36 PM
#7
Hello... This appears to be the NT OS Kernel. I recommend the OS should be "re-freshed" or re-installed (compiled) B.
I
Imagodie
12-10-2016, 12:36 PM #7

Hello... This appears to be the NT OS Kernel. I recommend the OS should be "re-freshed" or re-installed (compiled) B.

K
KIRO_HD
Member
216
12-11-2016, 06:02 AM
#8
Hello... That is your NT OS Kernel... I would recommend the OS be "re-freshed" or re-installed (compiled) B / It's a completely fresh setup. It was functioning on my previous installation too, but I just installed this OS yesterday.
Update, by the way. It crashed while I was looking up more details about the 0x3b crash.
K
KIRO_HD
12-11-2016, 06:02 AM #8

Hello... That is your NT OS Kernel... I would recommend the OS be "re-freshed" or re-installed (compiled) B / It's a completely fresh setup. It was functioning on my previous installation too, but I just installed this OS yesterday.
Update, by the way. It crashed while I was looking up more details about the 0x3b crash.

J
JEFF_JEFFERSON
Senior Member
627
12-12-2016, 06:18 AM
#9
Hello... 3) Can you share a screenshot of your Control Panel-Device manager? Are there any RED or yellow indicators for any connected hardware devices?
4) Is this issue occurring after the fresh installation?
5) Does it happen after a fresh install, followed by MB driver installation?
6) Is this happening after a fresh installation, MB driver installation, and subsequent Windows updates?
J
JEFF_JEFFERSON
12-12-2016, 06:18 AM #9

Hello... 3) Can you share a screenshot of your Control Panel-Device manager? Are there any RED or yellow indicators for any connected hardware devices?
4) Is this issue occurring after the fresh installation?
5) Does it happen after a fresh install, followed by MB driver installation?
6) Is this happening after a fresh installation, MB driver installation, and subsequent Windows updates?

M
Mario_512
Member
163
12-12-2016, 08:08 AM
#10
Hello... 3) Could you share an image of your Control Panel-Device manager? Are there any red or yellow indicators for any connected hardware devices?
4) Is this issue occurring after the fresh installation?
5) Does it happen after the fresh install and MB driver installation?
6) Is this happening after the fresh install, MB driver installation, and Windows updates?
Yes (to posting, no to any yellow or red icons), yes, yes, and yes.
M
Mario_512
12-12-2016, 08:08 AM #10

Hello... 3) Could you share an image of your Control Panel-Device manager? Are there any red or yellow indicators for any connected hardware devices?
4) Is this issue occurring after the fresh installation?
5) Does it happen after the fresh install and MB driver installation?
6) Is this happening after the fresh install, MB driver installation, and Windows updates?
Yes (to posting, no to any yellow or red icons), yes, yes, and yes.

Pages (2): 1 2 Next