Sign in with
Sign up | Sign in
Your question
Solved

Several BSOD errors (Windows 8.1)

Tags:
  • Blue Screen
  • Minidump
  • Windows 8.1
  • Computers
  • Windows 8
  • 0x0000001e
  • KMODE_EXCEPTION_NOT_HANDLED
Last response: in Windows 8
Share
February 15, 2014 7:52:17 AM

My computer has been crashing somewhat inconsistently. It seems to happen 1-2 times a day, but I can't isolate a cause. It doesn't happen during a particular task. This computer is just over a month old, and it has been happening ever since I built it. I should also mention that there appears to be a problem with either my memory or the motherboard as well, because I cannot use my RAM in dual channel mode (will not POST if either of the sticks is in B1 or B2). It has been a pain.

Specs:
Windows 8.1
ASRock B85 Pro4 Motherboard
Intel i5 4570 - BX80646I54570
Powercolor R9 270x - 2GBD5-PPDHE
2x4GB Team Dark DDR3 1600MHz RAM - TXD38192M1600HC9DC-D
Western Digital 1TB - WD10EZEX
RAIDMAX 535W PSU - RX-535AP
SAMSUNG DVD Burner - SH-224DB/BEBE
Razer Abyssus Mouse
Logitech G105 Keyboard

Link to the minidump files: https://www.dropbox.com/s/3v6wvyk8r2tts2d/Minidumps.rar

I'm not quite sure how to interpret these files. I downloaded NirSoft BlueScreenView, but it seems that the crashes are being caused by several different drivers (if I'm reading the report correctly), and Googling hasn't yielded very consistent answers.

All of the crashes are "KMODE_EXCEPTION_NOT_HANDLED" with bug check code "0x0000001e." Drivers and addresses reported as causes (for those who don't want to download the minidumps):
Crash 1: Caused by driver: Wdf01000.sys ; Caused by address: Wdf01000.sys + 844c ; Crash address: None given
Crash 2: Caused by driver: Wdf01000.sys ; Caused by address: Wdf01000.sys + 844c ; Crash address: ntoskrnl.exe+14dca0
Crash 3: Caused by driver: Wdf01000.sys ; Caused by address: Wdf01000.sys + 844c ; Crash address: ntoskrnl.exe+14dca0
Crash 4: Caused by driver: dxgmms1.sys ; Caused by address: dxgmms1.sys + c26b ; Crash address: ntoskrnl.exe+14dca0
Crash 5: Caused by driver: Ndu.sys ; Caused by address: Ndu.sys + a49b ; Crash address: ntoskrnl.exe+14dca0
Crash 6: Caused by driver: hal.dll ; Caused by address: hal.dll + 6627 ; Crash address: ntoskrnl.exe+14dca0

I'd really appreciate any help that you're willing to give. Thank you so much.

More about : bsod errors windows

a b * Windows 8
February 16, 2014 7:42:40 PM

edit: you will also want to get a update for your intel ethernet driver
directly from intel: https://downloadcenter.intel.com/detail_desc.aspx?Dwnld...
it has various fixes from the version you currently have from last march.

the windows debugger did not like your copy of win32k.sys that you had in memory. I don't know why but I would suggest that you check your copy on your disk for corruption using the system file checker
(Windows key+x+a) to run cmd.exe as a admin
then
sfc.exe /scannow (this will check your windows core files for corruption and fix them if it can)
if that command find a error it can not fix
then run
dism.exe /online /check-image /restorehealth (this will get a clean copy for any corrupted file)


you might also want to update your chipset drivers directly from intel
https://downloadcenter.intel.com/SearchResult.aspx?lang...

I mention this because your intel usb dirver is kind of old (2012) and your razor device and your logitech device both depend on it to work correctly.

---------------
all the memory dumps had the same root cause: the razer abyssus driver.
I would look for a update from the manufacture. If i could not get one I would look for a update to my usb driver or maybe change the USB mode for the hardware in the BIOS. (just a guess, the razer support people should know about this problem)

here it the exception code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

not too useful for you but you might google it with the razer driver name of Abyssus.sys to find a fix or updated file.

I did not try to figure out if the error code is correct, sometimes it is just corruption that cause some routine to complain and spit out a error. (still a problem with the driver though)

(it might even be related to the limit windows 8.1 put on using polling intervals to grab excess system resources, that can be fixed with a registry setting but the razor support will know if that is the case)


memory dump: 012314-16968-01.dmp
BugCheck 1E, {ffffffffc0000047, fffff80069355bf4, ffffd0002019b0d0, fffff80069211627}
KMODE_EXCEPTION_NOT_HANDLED (1e)


you need to remove or update this driver: Abyssus.sys
Razer Abyssus
http://www.razersupport.com/index.php?_m=downloads&_a=v...


2: kd> lmvm Abyssus
start end module name
fffff800`02fdd000 fffff800`02fea000 Abyssus T (no symbols)
Loaded symbol image file: Abyssus.sys
Image path: \SystemRoot\system32\drivers\Abyssus.sys
Image name: Abyssus.sys
Timestamp: Tue Jan 08 21:31:18 2013
m
0
l
February 18, 2014 7:32:02 PM

johnbl said:
edit: you will also want to get a update for your intel ethernet driver
directly from intel: https://downloadcenter.intel.com/detail_desc.aspx?Dwnld...
it has various fixes from the version you currently have from last march.

the windows debugger did not like your copy of win32k.sys that you had in memory. I don't know why but I would suggest that you check your copy on your disk for corruption using the system file checker
(Windows key+x+a) to run cmd.exe as a admin
then
sfc.exe /scannow (this will check your windows core files for corruption and fix them if it can)
if that command find a error it can not fix
then run
dism.exe /online /check-image /restorehealth (this will get a clean copy for any corrupted file)


you might also want to update your chipset drivers directly from intel
https://downloadcenter.intel.com/SearchResult.aspx?lang...

I mention this because your intel usb dirver is kind of old (2012) and your razor device and your logitech device both depend on it to work correctly.

---------------
all the memory dumps had the same root cause: the razer abyssus driver.
I would look for a update from the manufacture. If i could not get one I would look for a update to my usb driver or maybe change the USB mode for the hardware in the BIOS. (just a guess, the razer support people should know about this problem)

here it the exception code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

not too useful for you but you might google it with the razer driver name of Abyssus.sys to find a fix or updated file.

I did not try to figure out if the error code is correct, sometimes it is just corruption that cause some routine to complain and spit out a error. (still a problem with the driver though)

(it might even be related to the limit windows 8.1 put on using polling intervals to grab excess system resources, that can be fixed with a registry setting but the razor support will know if that is the case)


memory dump: 012314-16968-01.dmp
BugCheck 1E, {ffffffffc0000047, fffff80069355bf4, ffffd0002019b0d0, fffff80069211627}
KMODE_EXCEPTION_NOT_HANDLED (1e)


you need to remove or update this driver: Abyssus.sys
Razer Abyssus
http://www.razersupport.com/index.php?_m=downloads&_a=v...


2: kd> lmvm Abyssus
start end module name
fffff800`02fdd000 fffff800`02fea000 Abyssus T (no symbols)
Loaded symbol image file: Abyssus.sys
Image path: \SystemRoot\system32\drivers\Abyssus.sys
Image name: Abyssus.sys
Timestamp: Tue Jan 08 21:31:18 2013


Thanks for your help. I could have sworn I updated those drivers right after I put the computer together, but I suppose I didn't. Hopefully that'll stop the abyssus driver from causing crashes, since that driver is fully updated.

The scan came back with no errors. I'm going to run memtest86. I have a feeling that'll reveal one of my problems.
m
0
l

Best solution

a b * Windows 8
February 18, 2014 8:10:30 PM

the razer people have been claiming that they are going to come out with fixed drivers "soon" they were not there a few days ago but who knows.
also, if you do have a mouse that has high polling frequency windows 8.1 puts a cap on how many times a second the device can poll itself to 200 times a second. Some drivers try 1000 or 8000 times a second and just eat up the system resources. If you have one of these devices you now have to make a registry setting for your game to allow the device to exceed 200 queries per second. That way your mouse only screws up the system while you are playing the game. I think you can google "windows 8.1 mouse polling registry setting" to find how to set it if you need to. You can even set it to run at the higher polling rate on everything in windows if you want.

mahtale said:
johnbl said:
edit: you will also want to get a update for your intel ethernet driver
directly from intel: https://downloadcenter.intel.com/detail_desc.aspx?Dwnld...
it has various fixes from the version you currently have from last march.

the windows debugger did not like your copy of win32k.sys that you had in memory. I don't know why but I would suggest that you check your copy on your disk for corruption using the system file checker
(Windows key+x+a) to run cmd.exe as a admin
then
sfc.exe /scannow (this will check your windows core files for corruption and fix them if it can)
if that command find a error it can not fix
then run
dism.exe /online /check-image /restorehealth (this will get a clean copy for any corrupted file)


you might also want to update your chipset drivers directly from intel
https://downloadcenter.intel.com/SearchResult.aspx?lang...

I mention this because your intel usb dirver is kind of old (2012) and your razor device and your logitech device both depend on it to work correctly.

---------------
all the memory dumps had the same root cause: the razer abyssus driver.
I would look for a update from the manufacture. If i could not get one I would look for a update to my usb driver or maybe change the USB mode for the hardware in the BIOS. (just a guess, the razer support people should know about this problem)

here it the exception code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

not too useful for you but you might google it with the razer driver name of Abyssus.sys to find a fix or updated file.

I did not try to figure out if the error code is correct, sometimes it is just corruption that cause some routine to complain and spit out a error. (still a problem with the driver though)

(it might even be related to the limit windows 8.1 put on using polling intervals to grab excess system resources, that can be fixed with a registry setting but the razor support will know if that is the case)


memory dump: 012314-16968-01.dmp
BugCheck 1E, {ffffffffc0000047, fffff80069355bf4, ffffd0002019b0d0, fffff80069211627}
KMODE_EXCEPTION_NOT_HANDLED (1e)


you need to remove or update this driver: Abyssus.sys
Razer Abyssus
http://www.razersupport.com/index.php?_m=downloads&_a=v...


2: kd> lmvm Abyssus
start end module name
fffff800`02fdd000 fffff800`02fea000 Abyssus T (no symbols)
Loaded symbol image file: Abyssus.sys
Image path: \SystemRoot\system32\drivers\Abyssus.sys
Image name: Abyssus.sys
Timestamp: Tue Jan 08 21:31:18 2013


Thanks for your help. I could have sworn I updated those drivers right after I put the computer together, but I suppose I didn't. Hopefully that'll stop the abyssus driver from causing crashes, since that driver is fully updated.

The scan came back with no errors. I'm going to run memtest86. I have a feeling that'll reveal one of my problems.


Share
!