Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD - wdf01000.sys - PLEASE HELP!

12 Jul 2019   #1

Windows 7 Ultimate Service Pack 1 64 bit
BSOD - wdf01000.sys - PLEASE HELP!

My computer doesn't shut down and barley turns back on!
When I hit shut down the shut down windows appears but freezes for a few seconds and then BSOD appears (Attached photo).

When BSOD appears, shutdown button doesn't work and I have to unplug the computer!
When I put back the plug, it takes about 20 clicks on the turn on button for the computer to respond!

Couldn't find an answer anywherer.

after computer comes on it reads:
"Windows has recovered from an unexoected shutdown".

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 1037

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000003
BCP2: 0000000000000002
BCP3: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:

Read our privacy statement online:
Windows 7 Privacy Statement

If the online privacy statement is not available, please read our privacy statement offline:

Attached Thumbnails
BSOD - wdf01000.sys - PLEASE HELP!-whatsapp-image-2019-07-12-13.29.18.jpeg  
My System SpecsSystem Spec
12 Jul 2019   #2

Windows 8.1 Enterprise x64

My System SpecsSystem Spec
14 Jul 2019   #3

Windows 7 Ultimate Service Pack 1 64 bit

Thank you for the clarification regarding the post process,
Here's the zip file acording to the instructions.

Attached Files
File Type: zip (1.96 MB, 1 views)
My System SpecsSystem Spec

14 Jul 2019   #4

Windows 8.1 Enterprise x64

1. Run Driver Verifier Manager
2. Select "Create custom settings (for code developers)"
3. Select all standard settings and 2 additional settings ("Force pending I/O request" and "IRP Logging")
4. Select "Select driver names from a list"
5. Select all drivers except Microsoft drivers
6. Reboot computer
My System SpecsSystem Spec
17 Jul 2019   #5

Windows 7 Ultimate Service Pack 1 64 bit
Thank you - a new problem!

Thank you for the response.
I followed your instructions, for some reason it caused a new BSOD error.
Attached is a screen shot and again a new zip file with all the info as incstruced.
Also my computer became super slow since i ran Driver Verifier Manager... PLEASE HELP!!!

Attached Thumbnails
BSOD - wdf01000.sys - PLEASE HELP!-whatsapp-image-2019-07-12-13.29.18.jpeg  
Attached Files
File Type: zip (114.1 KB, 1 views)
My System SpecsSystem Spec
17 Jul 2019   #6

Windows 8.1 Enterprise x64

BSoD's causes the mafw.sys driver
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [F:\071019-77204-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*
Symbol search path is: SRV*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24441.amd64fre.win7sp1_ldr.190418-1735
Machine Name:
Kernel base = 0xfffff800`0340e000 PsLoadedModuleList = 0xfffff800`03647c90
Debug session time: Wed Jul 10 13:25:51.649 2019 (UTC + 2:00)
System Uptime: 0 days 0:53:55.414
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
For analysis of this file, run !analyze -v
0: kd> !analyze
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck D1, {3, 2, 0, fffff88000e554a1}

*** WARNING: Unable to verify timestamp for mafw.sys
GetUlongPtrFromAddress: unable to read from fffff800036ab300
Probably caused by : mafw.sys ( mafw+d62e )

Followup:     MachineOwner

0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arg1: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000e554a1, address which referenced memory

Debugging Details:








BUILD_VERSION_STRING:  7601.24441.amd64fre.win7sp1_ldr.190418-1735





BUGCHECK_P4: fffff88000e554a1

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036ab100
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800036ab2f0
GetUlongPtrFromAddress: unable to read from fffff800036ab4a8
GetPointerFromAddress: unable to read from fffff800036ab0d8


fffff880`00e554a1 4c3910          cmp     qword ptr [rax],r10


CPU_MHZ: cf0

CPU_VENDOR:  GenuineIntel









ANALYSIS_SESSION_TIME:  07-17-2019 13:49:20.0925

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

TRAP_FRAME:  fffff80000b9e500 -- (.trap 0xfffff80000b9e500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa80171530b8
rdx=fffffa8017153010 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000e554a1 rsp=fffff80000b9e698 rbp=fffff80000b9e770
 r8=fffffa800dc10868  r9=0000000000000000 r10=fffffa80115138f8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff880`00e554a1 4c3910          cmp     qword ptr [rax],r10 ds:00000000`00000003=????????????????
Resetting default scope


STACK_OVERFLOW: Stack Limit: fffff80000b9efb0. Use (kF) and (!stackusage) to investigate stack usage.

LAST_CONTROL_TRANSFER:  from fffff800034afe69 to fffff800034a1aa0

fffff800`00b9e3b8 fffff800`034afe69 : 00000000`0000000a 00000000`00000003 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9e3c0 fffff800`034adc88 : 00000000`00000000 00000000`00000003 fffffa80`0cbe1000 fffffa80`0dc10800 : nt!KiBugCheckDispatch+0x69
fffff800`00b9e500 fffff880`00e554a1 : fffff880`00e4e539 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x448
fffff800`00b9e698 fffff880`00e4e539 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff800`035e768e : Wdf01000!FxIrpQueue::InsertIrpInQueue+0x61
fffff800`00b9e6a0 fffff880`00e89adc : fffffa80`11513850 fffff880`00e4ff62 00000000`00000000 00000000`00000000 : Wdf01000!FxRequest::InsertTailIrpQueue+0x85
fffff800`00b9e6e0 fffff880`00e4e0ef : fffffa80`11513850 fffff800`00b9e770 fffffa80`17153002 00000000`00000005 : Wdf01000!FxIoQueue::InsertNewRequestLocked+0x34
fffff800`00b9e730 fffff880`00e592fb : fffffa80`100cc5c0 fffffa80`0dc10802 fffffa80`0dc10800 fffffa80`0dc10800 : Wdf01000!FxIoQueue::DispatchEvents+0x55f
fffff800`00b9e7b0 fffff880`00e4f51a : fffffa80`100cc502 fffffa80`0dc10800 fffffa80`17153010 fffff800`00b9e890 : Wdf01000!FxIoQueue::QueueRequest+0x2ab
fffff800`00b9e820 fffff880`00e4b79a : fffffa80`0dc10800 fffffa80`17153010 fffffa80`0ce1e000 fffffa80`17153010 : Wdf01000!FxPkgIo::Dispatch+0x4da
fffff800`00b9e890 fffff880`00e4b866 : fffffa80`17153010 fffffa80`0ce1e000 fffffa80`10ba79d0 fffffa80`1033e2c0 : Wdf01000!FxDevice::Dispatch+0x19a
fffff800`00b9e8d0 fffff880`077bb62e : fffffa80`13316602 fffffa80`0ce1e000 fffffa80`133165a0 fffffa80`133166f0 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff800`00b9e910 fffffa80`13316602 : fffffa80`0ce1e000 fffffa80`133165a0 fffffa80`133166f0 00000000`00000000 : mafw+0xd62e
fffff800`00b9e918 fffffa80`0ce1e000 : fffffa80`133165a0 fffffa80`133166f0 00000000`00000000 fffffa80`10476a40 : 0xfffffa80`13316602
fffff800`00b9e920 fffffa80`133165a0 : fffffa80`133166f0 00000000`00000000 fffffa80`10476a40 00000000`00000000 : 0xfffffa80`0ce1e000
fffff800`00b9e928 fffffa80`133166f0 : 00000000`00000000 fffffa80`10476a40 00000000`00000000 00000000`00000001 : 0xfffffa80`133165a0
fffff800`00b9e930 00000000`00000000 : fffffa80`10476a40 00000000`00000000 00000000`00000001 00000000`00000000 : 0xfffffa80`133166f0

THREAD_SHA1_HASH_MOD_FUNC:  1d53ccd977bf7691d5116f07cba17ed56a54e054

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3d5251130f378689572f7eca8e776e158e6cced1

THREAD_SHA1_HASH_MOD:  5a24e45f89be3fa31d970f6de32dd403b512a109

fffff880`077bb62e ??              ???


SYMBOL_NAME:  mafw+d62e

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  mafw.sys


STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_0xD1_mafw+d62e

BUCKET_ID:  X64_0xD1_mafw+d62e

PRIMARY_PROBLEM_CLASS:  X64_0xD1_mafw+d62e

TARGET_TIME:  2019-07-10T11:25:51.000Z

OSBUILD:  7601







OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS



OSBUILD_TIMESTAMP:  2019-04-19 04:08:54


BUILDLAB_STR:  win7sp1_ldr

BUILDOSVER_STR:  6.1.7601.24441.amd64fre.win7sp1_ldr.190418-1735



FAILURE_ID_HASH_STRING:  km:x64_0xd1_mafw+d62e

FAILURE_ID_HASH:  {c2e9db89-aff9-c269-6d3f-9a02e8c761f0}

Followup:     MachineOwner

0: kd> .load pde
 PDE v11.3 - Copyright 2017 Andrew Richards
0: kd> !dpx
Start memory scan  : 0xfffff80000b9e3b8 ($csp)
End memory scan    : 0xfffff80000b9f000 (Kernel Stack Base)

               rax : 0xfffff80000b9e4c0 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
               rbx : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
               rsp : 0xfffff80000b9e3b8 : 0xfffff800034afe69 : nt!KiBugCheckDispatch+0x69
               rsi : 0xfffff80000b9e7c0 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e3b8 : 0xfffff800034afe69 : nt!KiBugCheckDispatch+0x69
0xfffff80000b9e3e0 : 0xfffff88000e554a1 : Wdf01000!FxIrpQueue::InsertIrpInQueue+0x61
0xfffff80000b9e4c0 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e4d0 : 0xfffff80000b9e7c0 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e4f8 : 0xfffff800034adc88 : nt!KiPageFault+0x448
0xfffff80000b9e500 : 0x0000000000000000 :  Trap @ fffff80000b9e500
0xfffff80000b9e518 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
0xfffff80000b9e608 : 0xfffff8800558a5cc : ks!KspTransferKsIrp+0x54
0xfffff80000b9e628 : 0xfffff800035e846d : nt!ExFreePoolWithTag+0x22d
0xfffff80000b9e630 : 0xfffff800034a3c99 : nt!KiIsrLinkage+0x328
0xfffff80000b9e638 : 0xfffff800035f2180 : nt!KiInitialPCR+0x180
0xfffff80000b9e668 : 0xfffff88000e554a1 : Wdf01000!FxIrpQueue::InsertIrpInQueue+0x61
0xfffff80000b9e680 : 0xfffff80000b9e698 : 0xfffff88000e4e539 : Wdf01000!FxRequest::InsertTailIrpQueue+0x85
0xfffff80000b9e698 : 0xfffff88000e4e539 : Wdf01000!FxRequest::InsertTailIrpQueue+0x85
0xfffff80000b9e6b8 : 0xfffff800035e768e : nt!ExAllocatePoolWithTag+0xfe
0xfffff80000b9e6d8 : 0xfffff88000e89adc : Wdf01000!FxIoQueue::InsertNewRequestLocked+0x34
0xfffff80000b9e6e0 : 0xfffffa8011513850 :  dt Wdf01000!FxIoQueue
0xfffff80000b9e6e8 : 0xfffff88000e4ff62 : Wdf01000!FxIoQueue::CanThreadDispatchEventsLocked+0x8a
0xfffff80000b9e728 : 0xfffff88000e4e0ef : Wdf01000!FxIoQueue::DispatchEvents+0x55f
0xfffff80000b9e730 : 0xfffffa8011513850 :  dt Wdf01000!FxIoQueue
0xfffff80000b9e750 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e758 : 0xfffff88000e558d3 : Wdf01000!FxRequest::FxRequest+0x33
0xfffff80000b9e790 : 0xfffffa8011513850 :  dt Wdf01000!FxIoQueue
0xfffff80000b9e7a8 : 0xfffff88000e592fb : Wdf01000!FxIoQueue::QueueRequest+0x2ab
0xfffff80000b9e7c0 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e7c8 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e7d8 : 0xfffff88000e4e539 : Wdf01000!FxRequest::InsertTailIrpQueue+0x85
0xfffff80000b9e808 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e810 : 0xfffffa8011513850 :  dt Wdf01000!FxIoQueue
0xfffff80000b9e818 : 0xfffff88000e4f51a : Wdf01000!FxPkgIo::Dispatch+0x4da
0xfffff80000b9e828 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e838 : 0xfffff80000b9e890 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e858 : 0xfffff80003608888 : nt!NonPagedPoolDescriptor+0x8
0xfffff80000b9e888 : 0xfffff88000e4b79a : Wdf01000!FxDevice::Dispatch+0x19a
0xfffff80000b9e890 : 0xfffffa800dc10800 :  dt Wdf01000!FxRequestFromLookaside
0xfffff80000b9e8c8 : 0xfffff88000e4b866 : Wdf01000!FxDevice::DispatchWithLock+0xa6
*** WARNING: Unable to verify timestamp for mafw.sys
0xfffff80000b9ea08 : 0xfffff88000e4b866 : Wdf01000!FxDevice::DispatchWithLock+0xa6
0xfffff80000b9eab8 : 0xfffff8801081c23c : 1394ohci!IsochRx::WdfEvtNotificationDpc+0x2d8
0xfffff80000b9eb20 : 0xfffff8000361e7b8 : nt!ExWorkerQueue+0x18
0xfffff80000b9eb48 : 0xfffff88000eb579f : Wdf01000!FxDpc::FxDpcThunk+0xd7
0xfffff80000b9eb88 : 0xfffff80003457d2c : nt!KiRetireDpcList+0x1bc
0xfffff80000b9eb90 : 0xfffff800035f2180 : nt!KiInitialPCR+0x180
0xfffff80000b9ebd8 : 0xfffff800034a4495 : nt!SwapContext_PatchXRstor+0x98
0xfffff80000b9ebf8 : 0xfffff8000361e7b8 : nt!ExWorkerQueue+0x18
0xfffff80000b9ec20 : 0xfffff800036021c0 : nt!KiInitialThread
0xfffff80000b9ec30 : 0xfffff800035f2180 : nt!KiInitialPCR+0x180
0xfffff80000b9ec38 : 0xfffff800034a501a : nt!KiIdleLoop+0x5a
0xfffff80000b9ec40 : 0xfffff800035f2180 : nt!KiInitialPCR+0x180
0xfffff80000b9ec48 : 0xfffff800036021c0 : nt!KiInitialThread
0xfffff80000b9ec58 : 0xfffff88000eb56c8 : Wdf01000!FxDpc::FxDpcThunk

0: kd> !verifier

Verify Flags Level 0x00000000

    [X] (0x00000000) Automatic Checks
    [ ] (0x00000001) Special pool
    [ ] (0x00000002) Force IRQL checking
    [ ] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [ ] (0x00000100) Security checks
    [ ] (0x00000800) Miscellaneous checks

    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging

    [X] Indicates flag is enabled

Summary of All Verifier Statistics

  RaiseIrqls           0x0
  AcquireSpinLocks     0x0
  Synch Executions     0x0
  Trims                0x0

  Pool Allocations Attempted             0x0
  Pool Allocations Succeeded             0x0
  Pool Allocations Succeeded SpecialPool 0x0
  Pool Allocations With NO TAG           0x0
  Pool Allocations Failed                0x0

  Current paged pool allocations         0x0 for 00000000 bytes
  Peak paged pool allocations            0x0 for 00000000 bytes
  Current nonpaged pool allocations      0x0 for 00000000 bytes
  Peak nonpaged pool allocations         0x0 for 00000000 bytes

0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff880`186a8000 fffff880`19b8c000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Jul  3 01:19:59 2019 (5D1C652F)
    CheckSum:         0148878C
    ImageSize:        014E4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
0: kd> lmvm mafw
Browse full module list
start             end                 module name
fffff880`077ae000 fffff880`077e9000   mafw     T (no symbols)           
    Loaded symbol image file: mafw.sys
    Image path: \SystemRoot\system32\DRIVERS\mafw.sys
    Image name: mafw.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Jul 29 14:26:58 2009 (4A70BEA2)
    CheckSum:         000390C0
    ImageSize:        0003B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
M-Audio FireWire driver (M-Audio)
My System SpecsSystem Spec
19 Jul 2019   #7

Windows 7 Ultimate Service Pack 1 64 bit
no update for m-audio firewire

Hello again, thank you so much for your help!
Unfortunatelly, there is no updates available for the device M-audio firewire 410, I have the latest installed on my machine.


Any other ideas?

Attached Images
BSOD - wdf01000.sys - PLEASE HELP!-capture.png 
My System SpecsSystem Spec
19 Jul 2019   #8

Windows 8.1 Enterprise x64

I looked for a moment and found such a fix:
Just in case anyone ever has the same problem, I appear to have fixed it by using the following method (found here: 404 Error Page...)

Click Start

Then click on Control Panel

Click on Device Manager

Note: If you don’t see Device Manager listed, click on View By: Category on the top right side of the
Control Panel Window.
Then Click on Large Icons
You should now have a list of items in the Control Panel and click on Device Manager.

Under the Device Manager, look down the list for IEEE 1394 Bus Host Controllers and Double Click on it.

It should display something like - 1394 OHCI Compliant Host Controller

Note: If it has the word (Legacy) behind it, you are already setup and you can just exit out.

Next, double click on the 1394 OHCI Compliant Host Controller

A window will popup saying 1394 OHCI Compliant Host Controller Properties

Click on the Driver Tab

Then look down in the widow and click on Update Driver

Then select - Browse my computer for driver software

Next select - Let me pick from a list of device drivers on my computer

It will bring up a list of drivers.

Click on 1394 OHCI Compliant Host Controller (Legacy)

NOTE: It is important that you select the one with (Legacy) after it, just like shown above.

Then click Next

Once it installs the 1394 OHCI Compliant Host Controller (Legacy),
it will say Windows has successfully updated your driver software.

Click on the Close button and exit out of all of the other windows.

Then Reboot your computer.
Source: Firewire 410, Win764bit, bluescreen on shutdown
My System SpecsSystem Spec
19 Jul 2019   #9

Windows 7 Ultimate Service Pack 1 64 bit

Thank you for that,
Did the repair and now I have the 1394 controller (Legacy),
but pc sound is gone and my M-AUDIO is on "other devices"...
Should I re-install the drivers? will it reverse the Legacy?

Attached Images
BSOD - wdf01000.sys - PLEASE HELP!-capture2.png 
My System SpecsSystem Spec
19 Jul 2019   #10

Windows 8.1 Enterprise x64

Reinstall M-Audio drivers
My System SpecsSystem Spec

 BSOD - wdf01000.sys - PLEASE HELP!

Thread Tools

Similar help and support threads
Thread Forum
wdf01000.sys bsod windows 7 help!
Experiencing BSOD when pressing 'Ctrl+alt+delete' to access the passwordscreen. Personally cant find out much details from windbg. Can someone help please. Thanks!
BSOD Help and Support
BSOD Playing GTA IV Better DS3/Wdf01000.sys
Hey guys first post here :) Everytime i play GTA IV i get this BSOD But i dont think its GTA but then again my other games run fine 1 time NFS world BSOD, the DMP file bellow says something about the Better DS3 Microsoft (R) Windows Debugger Version 6.12.0002.633 Copyright (c) Microsoft...
BSOD Help and Support
BSOD WDF01000.sys
I have attached a zip of my minidump folder. Getting random BSOD's. Appears to happen when PC is sitting idle for the most part. Started shortly after Win 7 Pro 64-bit install. This is from an HP 6560b laptop. It seemed that windbg only shows wdf01000.sys as the problem, but I'm not sure if my...
BSOD Help and Support
BSOD Wdf01000.sys
Hello, just got a bluescreen and i couldnt get back into windows untill i removed one of my RAM`s. I tryed the startup repair system restore before doing that but i was getting bluescreen everytime before or after windows was loading. Tho i only see only one event, the others might have been lost...
BSOD Help and Support
BSOD, Driver Wdf01000.sys
Trying to help my father-in-law who is getting a BSOD on his very new laptop. We've barely used the thing, so I'm not getting it. Attached is the SF dump file info. I am intermediate level computer knowledge, so bear with me. It starts in safe mode. Thanks for any help.
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 21:01.
Twitter Facebook