ntoskrnl.exe driver Bsod

[UmbreFezz]

Hello everyone,
I have recently started to get this BSOD at least one time per day. I have no idea why. I know that the driver file, ntoskrnl.exe has something do with it because of bluescreenviewer. I'll post those in a minute.
I also know that this crash has something to do with memory transfers.(I think)
So I ran a mem test overnight, no errors return.

Here is my crash dump:
event id is 1033 i think. its always 1033 and it never changes even if the driver changes or parameters change.

BCC is 3b
011614-10342-01.dmp 1/16/2014 6:16:13 AM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`03101622 fffff880`09837c60 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\011614-10342-01.dmp 8 15 7601 292,368 1/16/2014 6:17:00 AM

my system specs:
amd fx8350 4.4 ghz
asus sabertooth 990fx r2.0
evga gtx 770
windows 7 home prem
8 gb g-skill 1866 running at 1600( cause I thought the ram was too fast for the voltage I had it at)


Honestly, any insight at this point I will be grateful for, as I receive this error quite frequently at startup, or just while running programs like skype and google chrome.

 

[HEXiT]

error 3b is related to the IEEE 1394 driver if you fire wire devices. normally its the driver that causes the error due to corruption.
there is a hotfix available.
http://support.microsoft.com/kb/980932
http://www.youtube.com/watch?v=dyfCWBC8KJU explains why you cant just install a new driver and why you have to use the supplied hotfix.

if you dont have any firewire devices attached and running then go into bios and disable ieee1394 device support.

i would also run a malware scan with a few decent anti malware apps like malware bytes and a good av. as drivers dont normally just become corrupt normally something has to corrupt them.

 

[johnbl]

The error indicated that a device driver has passed a invalid address to the windows kernel and windows kernel detected this and called a bugcheck.
The debug info is in your memory dump file C:\Windows\Minidump\011614-10342-01.dmp
if you post that file on a cloud service with guest access someone with a windows debugger can look at it and maybe determine what device driver caused the problem.

or you can just guess and just update a bunch of device drivers in the hope you find the correct one, both methods work.

 

[UmbreFezz]

error 3b is related to the IEEE 1394 driver if you fire wire devices. normally its the driver that causes the error due to corruption.
there is a hotfix available.
http://support.microsoft.com/kb/980932
http://www.youtube.com/watch?v=dyfCWBC8KJU explains why you cant just install a new driver and why you have to use the supplied hotfix.

if you dont have any firewire devices attached and running then go into bios and disable ieee1394 device support.

i would also run a malware scan with a few decent anti malware apps like malware bytes and a good av. as drivers dont normally just become corrupt normally something has to corrupt them.

Ummmm when I try to run the hotfix, It says this update is not applicable to your system. I will try to disable the device stuff and run a malware scan.

 

[UmbreFezz]

The error indicated that a device driver has passed a invalid address to the windows kernel and windows kernel detected this and called a bugcheck.
The debug info is in your memory dump file C:\Windows\Minidump\011614-10342-01.dmp
if you post that file on a cloud service with guest access someone with a windows debugger can look at it and maybe determine what device driver caused the problem.

or you can just guess and just update a bunch of device drivers in the hope you find the correct one, both methods work.

Here https://skydrive.live.com/redir?resid=8554AE42DA5F4AA2%21162

 

[UmbreFezz]

Also, I am getting this BSOD sometimes as well.... its the one i posted and this one most frequently. maybe they are related in some way.

011514-10296-01.dmp 1/15/2014 11:01:31 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75b90 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75b90 C:\Windows\Minidump\011514-10296-01.dmp 8 15 7601 292,640 1/15/2014 11:02:08 PM

 

[johnbl]

this one is not useful, all the numbers are incorrect. all zeros.

Also, I am getting this BSOD sometimes as well.... its the one i posted and this one most frequently. maybe they are related in some way.

011514-10296-01.dmp 1/15/2014 11:01:31 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75b90 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18247 (win7sp1_gdr.130828-1532) x64 ntoskrnl.exe+75b90 C:\Windows\Minidump\011514-10296-01.dmp 8 15 7601 292,640 1/15/2014 11:02:08 PM

 

[HEXiT]

go into bios and check to see if hpet (high precision event timer) is enabled. if its not enable it, save and quit.
http://en.wikipedia.org/wiki/High_Precision_Event_Timer

enabling it can resolve random bsods.

 

[johnbl]

problem:
BugCheck 3B, {c0000005, fffff80003101622, fffff88009837c60, 0}
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003101622, Address of the instruction which caused the bugcheck
Arg3: fffff88009837c60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.




Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 0:00:17.189


BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2104
BiosReleaseDate = 11/21/2013

BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = SABERTOOTH 990FX R2.0

Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4400MHz
Current Speed 4400MHz

memory: bank0: none
bank1: 4096MB 1600MHz part number F3-14900CL8-4GBXM
bank2: none
bank3: 4096MB 1600MHz part number F3-14900CL8-4GBXM

memory is G Skill Intl F3-14900CL8-4GBXM
---------------
This looks like a CPU issue, most likely due to overclocking. Disable overclocking and see if your issue goes away.
if you must overclock, check a overclocking guide to see what your CPU voltages should be with a 4400MHz clock.

other issues: you have overclocking drivers installed, after you get a stable overclock you want to remove as many of these special binaries
as you can, they are useful to finding a good overclock but tend to have issues if left in the system in the long term (memory corruption because of bugs in their drivers)

notes:
digital electronics: is based on binary, two values 1 or 0. the electronics uses voltages to represent this. when a value is changing from a 0 to a 1
the voltage is changing, this takes time make the change and become a stable value. For example a binary zero may mean a voltage of 0 to .3 volts while a binary 1 = .7 volts to 1 volt. the range between .3 and .7 is unknown if the CPU reads at this time you get "random" results
the time it takes the value to change state and be stable (0 to 1) is the setup and hold time. Now, if you overclock you increase the voltage to the CPU to lie to the electronics that your binary state is stable. The electronics is still designed to view over .7volts as a binary 1 but the increased voltage to the CPU really means that the unknown value states should also be increased to something like 0= 0 volts to .4 volts, unknown= .4 volts to .9 volts , and 1 = .9 volts to 1.3 volts. but the code in the CPU is not changed and a 1 binary is still at .7 V and over. (in this example)

sometimes overclocking is ok, sometimes not.

 

[UmbreFezz]

problem:
BugCheck 3B, {c0000005, fffff80003101622, fffff88009837c60, 0}
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003101622, Address of the instruction which caused the bugcheck
Arg3: fffff88009837c60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.




Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
System Uptime: 0 days 0:00:17.189


BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2104
BiosReleaseDate = 11/21/2013

BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = SABERTOOTH 990FX R2.0

Processor Version AMD FX(tm)-8350 Eight-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 4400MHz
Current Speed 4400MHz

memory: bank0: none
bank1: 4096MB 1600MHz part number F3-14900CL8-4GBXM
bank2: none
bank3: 4096MB 1600MHz part number F3-14900CL8-4GBXM

memory is G Skill Intl F3-14900CL8-4GBXM
---------------
This looks like a CPU issue, most likely due to overclocking. Disable overclocking and see if your issue goes away.
if you must overclock, check a overclocking guide to see what your CPU voltages should be with a 4400MHz clock.

other issues: you have overclocking drivers installed, after you get a stable overclock you want to remove as many of these special binaries
as you can, they are useful to finding a good overclock but tend to have issues if left in the system in the long term (memory corruption because of bugs in their drivers)

notes:
digital electronics: is based on binary, two values 1 or 0. the electronics uses voltages to represent this. when a value is changing from a 0 to a 1
the voltage is changing, this takes time make the change and become a stable value. For example a binary zero may mean a voltage of 0 to .3 volts while a binary 1 = .7 volts to 1 volt. the range between .3 and .7 is unknown if the CPU reads at this time you get "random" results
the time it takes the value to change state and be stable (0 to 1) is the setup and hold time. Now, if you overclock you increase the voltage to the CPU to lie to the electronics that your binary state is stable. The electronics is still designed to view over .7volts as a binary 1 but the increased voltage to the CPU really means that the unknown value states should also be increased to something like 0= 0 volts to .4 volts, unknown= .4 volts to .9 volts , and 1 = .9 volts to 1.3 volts. but the code in the CPU is not changed and a 1 binary is still at .7 V and over. (in this example)

sometimes overclocking is ok, sometimes not.

If i post my overclocking information, such as voltages, and stuff, like in a screenshot, would you evaluate them?
Oh, and I dont have any overclocking drivers.

 

[johnbl]

I really don't think you have a overclock issue but you should disable your overclock to make sure.
I think your issue is due to bugs in some old drivers you have installed and I would start by removing them if you don't need them or updating them.

for example:
various old asus drivers are out of date and are known to cause issues (forms of memory corruption)
AsUpIO.sys Mon Aug 02 19:47:59 2010
ASUSFILTER.sys Tue Sep 20 08:46:33 2011

I would also uninstall your AVAST antivirus until you get your system running correctly.
version is from Thu May 09 01:47:02 2013.

if i remember correctly one of your bugchecks was caused by windows not being able to get a lock and bugchecking. This could be caused by a bug in outdated AVAST drivers. (remove software,reboot and retest)
Edit: i would also remove \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys Thu May 03 12:56:17 2012
old apple itunes driver has issues