Solved BSOD Idle (wdf01000.sys) and (ntoskrnl.exe ) W8.1

Kezen · Jul 3, 2014

Hi everyone !
This is my first thread here so bear with me, today I got my first BSOD in more than a decade and WhoCrashed told me this :

On Thu 03/07/2014 11:06:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070314-63187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80037B1C375, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 03/07/2014 11:06:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x18FC)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80037B1C375, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l’infrastructure de pilotes en mode noyau
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.

I recently added 8gb of RAM to my Gigabyte Z87 UD3H motherboard and I believe this is where the problem stems from as this board apparently does not like its 4 slots to be occupied. I removed 2 of them so I'm currently running 8gb of Corsair Vengeance ram.
Rest of my PC :
I7 4770K stock
GTX 770 MSI Gaming

I also had a "Wininit 1015" issue with the Issass which I thought was fixed in W8. Not sure if it has anything to do with everything above though.

Ran a virus scan, nothing.

I attached the information you guys need. I hope you will be able to pinpoint what caused all this, if my little theory proves incorrect.
I should add that the second BSOD occured when while I was running a SFC /SCANNOW and it crashed when I reached 100% precisely.

blueelvis · Jul 4, 2014

Hi Kezen & Welcome To the Forums ^_^,

Seems like you are a fan of NVIDIA

Anyways, I have analyzed your dump file and a summary has been provided below :-

Code:

**************************Thu Jul  3 16:36:13.047 2014 (UTC + 5:30)**************************
*** WARNING: Unable to verify timestamp for win32k.sys
 
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
 
Probably caused by : cdrom.sys ( cdrom! ?? ::FNODOBFM::`string'+420 )
 
BugCheck 1E, {ffffffffc0000005, fffff80037b1c375, 0, ffffffffffffffff}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
 
BUGCHECK_STR:  0x1E_c0000005_R
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0x1E_c0000005_R_cdrom!_??_::FNODOBFM::_string_
 
MaxSpeed:     3500
 
CurrentSpeed: 3500
 
  BIOS Version                  F5
 
  BIOS Release Date             05/16/2013
 
  Manufacturer                  Gigabyte Technology Co., Ltd.
 
  Product Name                  Z87X-UD3H
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Below is a list of 3rd party drivers which I found on your system :-

Code:

**************************Thu Jul  3 16:36:13.047 2014 (UTC + 5:30)**************************
HECIx64.sys                 Tue Dec 18 01:02:21 2012 (50CF7345)
mvxxmm.sys                  Thu Jan 24 13:13:49 2013 (5100E635)
mvs91xx.sys                 Thu Jan 24 13:14:05 2013 (5100E645)
RTKVHD64.sys                Tue Feb 26 18:08:48 2013 (512CACD8)
e1i63x64.sys                Wed Mar 20 13:07:29 2013 (51496739)
RTL8192su.sys               Thu Mar 28 13:11:32 2013 (5153F42C)
rikvm_38F51D56.sys          Mon Jun 17 09:35:56 2013 (51BE8B24)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
avkmgr.sys                  Mon Sep 16 16:44:23 2013 (5236E80F)
mbam.sys                    Wed Oct 30 21:41:45 2013 (52712FC1)
nvhda64v.sys                Thu Nov 28 19:08:09 2013 (52974741)
iwdbus.sys                  Wed Dec 18 04:17:38 2013 (52B0D48A)
avgntflt.sys                Thu Mar 13 22:19:28 2014 (5321E198)
avipbb.sys                  Thu Mar 20 13:16:51 2014 (532A9CEB)
MBAMSwissArmy.sys           Fri Mar 21 03:42:35 2014 (532B67D3)
iaStorA.sys                 Fri Apr  4 04:30:05 2014 (533DE7F5)
dump_iaStorA.sys            Fri Apr  4 04:30:05 2014 (533DE7F5)
nvlddmkm.sys                Tue May 20 04:38:44 2014 (537A8EFC)

Kezen · Jul 4, 2014

Thanks for your response.

Neither Avira nor Malwarebytes are even remotely likely to be responsible for the system stability issues. Those are well made, reliable apps. I've been using them for years and never encountered significant problems.

Ever since I removed two of my RAM sticks I'm no longer experiencing ANY issues. This, sadly, confirms that my mainboard really does not like 4 sticks of RAM. 2x4 is my safest option for the time being.

I think I can call that clase closed. Thanks for you help.

blueelvis · Jul 5, 2014

Hi,

Glad to see that you have resolved it. Unfortunately, in many cases of Dump Analysis, before we proceed further we need to make sure that some of the software are not colliding with each other and hence the suggested removal.

Also, did you run Memtest to make sure if the board is faulty or not?

Kezen · Jul 5, 2014

blueelvis said:
Hi,

Glad to see that you have resolved it. Unfortunately, in many cases of Dump Analysis, before we proceed further we need to make sure that some of the software are not colliding with each other and hence the suggested removal.

Also, did you run Memtest to make sure if the board is faulty or not?

That's unnecessary in my case as I didn't find anything in the Event Logger that could suggest my RAM is faulty, such as WHEA-logger or a BSOD bugcheck ending with 0x124 (hardware related errors).
I read countless accounts of BSODs with the same codes as mine with the Z87 UD3H. As long as you go easy on it (2 slots and not 4) it's fine.

Again, nothing of note to report since I switched from 4 slots to 2 slots so I think I'm good.

You can close this case. If I run into issues again I'll be back.
Thanks for everything.

blueelvis · Jul 5, 2014

Kezen said:
blueelvis said:

Hi,

Glad to see that you have resolved it. Unfortunately, in many cases of Dump Analysis, before we proceed further we need to make sure that some of the software are not colliding with each other and hence the suggested removal.

Also, did you run Memtest to make sure if the board is faulty or not?

Click to expand...

That's unnecessary in my case as I didn't find anything in the Event Logger that could suggest my RAM is faulty, such as WHEA-logger or a BSOD bugcheck ending with 0x124 (hardware related errors).
I read countless accounts of BSODs with the same codes as mine with the Z87 UD3H. As long as you go easy on it (2 slots and not 4) it's fine.

Again, nothing of note to report since I switched from 4 slots to 2 slots so I think I'm good.
You can close this case. If I run into issues again I'll be back.
Thanks for everything.

Hi Kezen!

Thanks for providing with the information, I will keep this in mind. Also, I noticed that you have an older version of BIOS as opposed to the currently available BIOS versions on the Gigabyte site. Visit this link :-

GIGABYTE - Motherboard - Socket 1150 - GA-Z87X-UD3H (rev. 1.x)

You may try upgrading your BIOS and see if the issue still persists or not. In case the issue is still not resolved, I would pass this information to the Gigabyte team and wait for their reply about the actual problem.
^_^

Kezen · Jul 7, 2014

blueelvis said:
Kezen said:

blueelvis said:

Hi,

You may try upgrading your BIOS and see if the issue still persists or not. In case the issue is still not resolved, I would pass this information to the Gigabyte team and wait for their reply about the actual problem.
^_^

Click to expand...

Thanks for the tip, unfortunately neither BIOS update truly fix the 4 slots issue so I'm stuck until I can afford 2x8GB of high quality ram.

You can close this thread and again a big thanks to anyone involved at Eightforums.net.
You guys are doing a great job. :thumb:

Click to expand...

blueelvis · Jul 7, 2014

Thanks mate for your kind words. I will send a mail to Gigabyte regarding this thread and let's see what happens ^_^.

Please mark this thread as solved ^_^.

Solved BSOD Idle (wdf01000.sys) and (ntoskrnl.exe ) W8.1

Kezen

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Kezen

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Kezen

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Kezen

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One