wdf01000.sys blue screen error

[Ramprakash2191]

Hi All, 

I am often getting blue screen error with stope code 'wdf01000.sys'. I have attached the dump analysisi file along with this post. Kindly help me in resolving this issue.

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc. Primary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`1921c000 PsLoadedModuleList = 0xfffff801`19568660
Debug session time: Mon Nov 27 21:43:57.204 2017 (UTC - 5:00)
System Uptime: 0 days 22:35:59.994
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80aebcb94b9, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
Wdf01000!FxIoContext::ReleaseAndRestore+47549
fffff80a`ebcb94b9 0fb74e0a        movzx   ecx,word ptr [rsi+0Ah]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

BUGCHECK_STR:  0x1e_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  ffffa607168cc700 -- (.exr 0xffffa607168cc700)
ExceptionAddress: ffffa60716587730
   ExceptionCode: ebd04818
  ExceptionFlags: fffff80a
NumberParameters: 67610
   Parameter[0]: ffffa607168cc720
   Parameter[1]: ffffa607168cc720
   Parameter[2]: ffffa607168e1501
   Parameter[3]: 0000000000000000
   Parameter[4]: ffffa607168cc020
   Parameter[5]: ffffa607168d09c8
   Parameter[6]: ffffa607168d0aa8
   Parameter[7]: 0000000000000000
   Parameter[8]: ffffa607168cc020
   Parameter[9]: 0000000000000001
   Parameter[10]: 0000000000000000
   Parameter[11]: fffff80aebd04858
   Parameter[12]: 0000000000000000
   Parameter[13]: 0000000001010100
   Parameter[14]: 0000000000060000

LAST_CONTROL_TRANSFER:  from fffff801194170e6 to fffff80119388580

CONTEXT:  ffce8b480b7402c1 -- (.cxr 0xffce8b480b7402c1)
Unable to read context, Win32 error 0n30

STACK_TEXT:  
fffff801`1a638108 fffff801`194170e6 : 00000000`0000001e ffffffff`c0000005 fffff80a`ebcb94b9 00000000`00000000 : nt!KeBugCheckEx
fffff801`1a638110 fffff801`1938ea5d : fffff801`195a6000 fffff801`1921c000 000536a0`00889000 fffff801`00000000 : nt!KiFatalExceptionHandler+0x22
fffff801`1a638150 fffff801`19248244 : 00000000`00000000 fffff801`1a638280 00000000`00000000 ffffa607`161372b0 : nt!RtlpExecuteHandlerForException+0xd
fffff801`1a638180 fffff801`19246fe6 : fffff801`1a639058 fffff801`1a638da0 fffff801`1a639058 fffff801`1a639058 : nt!RtlDispatchException+0x404
fffff801`1a638870 fffff801`1939398e : ffffa607`168cc700 fffff80a`ebc6da96 ffffa607`168cc700 fffff801`1a638fa9 : nt!KiDispatchException+0x1f6
fffff801`1a638f20 fffff801`19391c34 : 00000000`00000000 fffff80a`ebd093e8 fffff80a`ebc709c0 fffff80a`ebc7020b : nt!KiExceptionDispatch+0xce
fffff801`1a639100 fffff80a`ebcb94b9 : 000059f8`ed75a1e8 ffffa607`168eec20 ffffa607`1d109020 fffff80a`ebc6c554 : nt!KiGeneralProtectionFault+0xf4
fffff801`1a639290 fffff80a`ebc70bf1 : ffffa607`1d109020 ffffa607`1f3e11b0 ffffa607`1f3e1190 ffffa607`1f3e1190 : Wdf01000!FxIoContext::ReleaseAndRestore+0x47549
fffff801`1a6392d0 fffff80a`ebc6b9b7 : ffffa607`1f3e1190 ffffa607`1d109020 ffffa607`1f3e11b0 00000000`00000000 : Wdf01000!FxRequestBase::Dispose+0x71
fffff801`1a639300 fffff80a`ebc642d9 : ffffa607`00000001 00000000`00000210 ffffa607`00000002 ffffa607`167bb010 : Wdf01000!FxObject::DeleteObject+0x3b7
fffff801`1a639390 fffff80a`f1487622 : ffffa607`168ef098 ffffa607`1f3e1190 ffffa607`1f3e1330 ffffa607`2003d010 : Wdf01000!imp_WdfObjectDelete+0x99
fffff801`1a639410 ffffa607`168ef098 : ffffa607`1f3e1190 ffffa607`1f3e1330 ffffa607`2003d010 ffffa607`1f3e1190 : SynTP+0x87622
fffff801`1a639418 ffffa607`1f3e1190 : ffffa607`1f3e1330 ffffa607`2003d010 ffffa607`1f3e1190 fffff80a`ebcb5733 : 0xffffa607`168ef098
fffff801`1a639420 ffffa607`1f3e1330 : ffffa607`2003d010 ffffa607`1f3e1190 fffff80a`ebcb5733 ffffa607`168f0750 : 0xffffa607`1f3e1190
fffff801`1a639428 ffffa607`2003d010 : ffffa607`1f3e1190 fffff80a`ebcb5733 ffffa607`168f0750 fffff80a`ebc712fe : 0xffffa607`1f3e1330
fffff801`1a639430 ffffa607`1f3e1190 : fffff80a`ebcb5733 ffffa607`168f0750 fffff80a`ebc712fe ffffa607`1f3e1190 : 0xffffa607`2003d010
fffff801`1a639438 fffff80a`ebcb5733 : ffffa607`168f0750 fffff80a`ebc712fe ffffa607`1f3e1190 00000000`00000000 : 0xffffa607`1f3e1190
fffff801`1a639440 ffffa607`2003d002 : fffff801`1a639588 fffff80a`ebc70b6f fffff801`1a6395a1 ffffa607`1a1d6980 : Wdf01000!FxIoTarget::FormatIoctlRequest+0x45483
fffff801`1a6394d0 fffff801`1a639588 : fffff80a`ebc70b6f fffff801`1a6395a1 ffffa607`1a1d6980 00000000`00000000 : 0xffffa607`2003d002
fffff801`1a6394d8 fffff80a`ebc70b6f : fffff801`1a6395a1 ffffa607`1a1d6980 00000000`00000000 00000000`00000001 : 0xfffff801`1a639588
fffff801`1a6394e0 fffff80a`ebc70a90 : ffffa607`1f3e1190 00000000`00000001 ffffa607`1f3e1190 ffffa607`1a1d6980 : Wdf01000!FxNonPagedObject::Lock+0x1f
fffff801`1a639510 fffff801`1932e8e8 : ffffa607`168e9e20 00000000`00000002 ffffa607`1a1d6980 00000000`00000005 : Wdf01000!FxIoTarget::_RequestCompletionRoutine+0xd0
fffff801`1a639580 fffff801`192884d7 : ffffa607`2003d010 fffff801`1a6396b0 00000000`00000000 ffffa607`2003d173 : nt!IopUnloadSafeCompletion+0x58
fffff801`1a6395b0 fffff80a`ebc6a0c2 : 00000000`00000038 ffffa607`2003d000 00000000`00000002 ffffa607`168cc700 : nt!IopfCompleteRequest+0x117
fffff801`1a6396e0 fffff80a`ebc6695b : ffffa607`00000001 fffff80a`00000000 ffffa607`16562a30 fffff80a`ebc63f28 : Wdf01000!FxRequest::CompleteInternal+0x242
fffff801`1a6397a0 fffff80a`f1662930 : ffffa607`168cc310 ffffa607`1a1d2020 00000000`00000000 00000000`00000025 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x9b
fffff801`1a639810 ffffa607`168cc310 : ffffa607`1a1d2020 00000000`00000000 00000000`00000025 fffff801`13b3d180 : Smb_driver_Intel+0x2930
fffff801`1a639818 ffffa607`1a1d2020 : 00000000`00000000 00000000`00000025 fffff801`13b3d180 fffff80a`f1661c7a : 0xffffa607`168cc310
fffff801`1a639820 00000000`00000000 : 00000000`00000025 fffff801`13b3d180 fffff80a`f1661c7a ffffa607`168cc310 : 0xffffa607`1a1d2020


FOLLOWUP_IP: 
Wdf01000!FxIoContext::ReleaseAndRestore+47549
fffff80a`ebcb94b9 0fb74e0a        movzx   ecx,word ptr [rsi+0Ah]

FAULTING_SOURCE_LINE:  minkernel\wdf\framework\shared\inc\private\km\fxiotargetkm.hpp

FAULTING_SOURCE_FILE:  minkernel\wdf\framework\shared\inc\private\km\fxiotargetkm.hpp

FAULTING_SOURCE_LINE_NUMBER:  130

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  Wdf01000!FxIoContext::ReleaseAndRestore+47549

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Wdf01000

IMAGE_NAME:  Wdf01000.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  26eee197

STACK_COMMAND:  .cxr 0xffce8b480b7402c1 ; kb

FAILURE_BUCKET_ID:  X64_0x1e_c0000005_Wdf01000!FxIoContext::ReleaseAndRestore+47549

BUCKET_ID:  OLD_IMAGE_Wdf01000.sys

Followup: MachineOwner
---------

This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)

Crash Code Links Loaded Module List Raw Stack Contents Dump Header Information Strings

[MKazi]

@Ramprakash2191

Thanks for reaching out to us on HP Support Forums. I came across your post and would like to assist.

I understand that you have an HP computer and it displays a blue screen error with stop code 'wdf01000.sys'. Not worry, I'll do my best to help you. 

For better clarity and to assist you better I would require more information regarding this:

• Please let me know the exact computer model no. This link will help you to find the model no: http://hp.care/2bygf7l.
• What version of Windows are you using?
• Did any software changes or updates take place on the computer?

Meanwhile, you may try to repair the Windows system files. 

Corrupt Windows system files can slow down the computer and cause other problems. System File Checker (SFC) is a utility in Windows that scans for corrupted system files. If SFC finds a problem, it tries to replace the problem files from a cached version on your computer.

If System File Checker cannot replace the corrupt files, use the Deployment Image Service and Management Tool (DISM). DISM checks the corrupted files, then downloads and replaces the files through Windows Update.

Use the following instructions to run System File Checker.

• In Windows, search for Command Prompt. In the search results, right-click Command Prompt, select Run as administrator, then click Yes.

• In Command Prompt, type sfc /scannow. Make sure to include the space between sfc and the forward slash /.

Figure : Running System File Checker

• Press Enter, then wait while System File Checker scans for corrupted files.

  When the scan completes, the results display on the screen.

  • If the file checker found and replaced any corrupted files, restart the computer, then check the performance.

  • If the file checker did not find any corrupted files or found corrupted files but could not replace them, then go to the next step.

• If System File Checker finds corrupted files but cannot replace them, use the Deployment Image Servicing and Management (DISM) tool. DISM checks the corrupted files, then downloads and replaces the files using Windows Update.

• In Windows, open a web browser.

• NOTE: You need to be connected to the Internet to use DISM.

• In Windows, search for Command Prompt. In the search results, right-click Command Prompt, select Run as administrator, then click Yes.

• In Command Prompt, type dism.exe /Online /Cleanup-image /Restorehealth. Make sure to include the space before each forward slash / in the command line.

  Press Enter, then wait while DISM works. This might take several minutes.

Figure : Running DISM

• If DISM finds corrupted files, it replaces them using Windows Update. If this occurs, after DISM is finished, restart your computer and see if the performance has improved.

I hope this information helps. Let me now. Cheers! 🙂

[Ramprakash2191]

Hi Kazi,

Below are my laoptop movdel and OS version details.

Kinldy let me know for any additional details.

The system randomly restarts showing the blue screen error. Not every time it shows the same 'wdf01000.sys' error.

Once it did show

"Stop Code KMODE EXCEPTION NOT HANDLED

What Failed: storport.sys'

"Stop Code KMODE EXCEPTION NOT HANDLED

What Failed: wdf01000.sys''

at time just  with "Stop Code KMODE EXCEPTION NOT HANDLED" error message.

I also have observed that this happens when a new software is installed or windows update is installed or even doing nothing by just watch movies for an hour or two.

Product Name: HP Pavilion 15-au062nr

Operating System: Windows 10 Home (10.0.15063.138)

Kinldy let me know whether this is related to any hardware failure. It has been 3 months since I bought this laptop but I am unable to use it  and running to the service center every week!!

Regards,

Ramprakash

[MKazi]

@Ramprakash2191

Hi Ramprakash,

Thank you for replying with the information. 

Let us run the hardware tests on the laptop by following the below steps:

• Power off the laptop.

• Turn on the laptop and immediately press Esc repeatedly, about once every second. When the menu appears, press the F2 key.

• On the main menu, click Component Tests.

Figure : Selecting Component Tests from the main menu

• The Component Tests menu displays. Your Component Tests menu might be different, depending on the components installed on your computer.

Figure : Sample list of Component Tests

• Please initiate a test one by one on the processor, system board, memory and the hard drive. 

If any of the tests fail then please contact out HP phone support team to explore the hardware service options for your laptop.  

You may perform a Microsoft Push Button Reset if the all the hardware tests pass. The push-button reset feature that repairs your computer by reinstalling the operating system. This can be done either while preserving your personal data and customizations, or removing all your personal data.

All the best! 🙂