Frequent and random of ntoskrnl.exe BSOD / wdf01000.sys

Similar Questions

• Ntoskrnl.exe BSOD at random

  I get a BSOD caused by ntoskrnl.exe or ntfs.sys, with a lot of different bugs 0x0f and 0x0A 0x01E. I used WhoCrashed to help me find what it was, but in no avai.

  Here at random, take a few minutes to a few hours.
  Here are the logs of WhoCrashed

  Thursday, November 10, 2011 2:48:45 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-26130-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
  Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Thursday, November 10, 2011 2:48:45 AM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x213D8)
  Verification of error code: 0 x 24 (0xFFFFF88009D8C348, 0xFFFFF88009D8BBB0, 0x1904FB, 0xFFFFF80002EE2EEA)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Thursday, November 10, 2011 2:18:09 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-19515-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0x212A3)
  Verification of error code: 0 x 24 (0xFFFFF88008DD4708, 0xFFFFF88008DD3F70, 0 x 190477, 0xFFFFF80002EA5C84)
  Error: NTFS_FILE_SYSTEM
  file path: C:\Windows\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Thursday, November 10, 2011 2:05:19 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-22682-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70590)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  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 control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, November 9, 2011 11:39:15 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-20638-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0xA (0xFFFFF880029ED988, 0xFFFFF80002D205F1, 0x2, 0x0)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, October 27, 2011 7:49:38 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110911-25162-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0xD1 (0xFFFFF8808327B1DA, 0xFFFFF880042A41EA, 0x2, 0 x 1)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, October 27, 2011 3:11:46 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\102611-21106-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0 x 70600)
  Bugcheck code: 0x3B (0xC0000005, 0x1, 0x0, 0xFFFFF88009B94300)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Let me know if I need to download the DPM

  Hello

  Doubt that its windows for millions would have the same questions.

  If you think that your Windows installation disc is damaged, try these as a test.

  This will give you a method to make and install from another disk as a test.

  Windows 7 Enterprise - 90 day trial
  http://TechNet.Microsoft.com/en-us/evalcenter/cc442495.aspx

  They will help make you the ERD that are bootable.

  If you need to repair disks - these help repair Windows not re-install.
  Often an ERD will help you when the recovery disk does not work.

  Download Windows 7 system recovery discs - charge now $9.75 for ISO
  images to make the discs.
  http://NeoSmart.net/blog/2009/Windows-7-system-repair-discs/

  How to create a Windows 7 - free system repair disc
  http://www.SevenForums.com/tutorials/2083-system-repair-disc-create.html

  ========================================

  These make it bootable Linux disks with many public services:

  Hiren Boot CD
  http://www.hirensbootcd.org/

  Rescue Kit Trinity
  http://trinityhome.org/home/index.php?wpid=1&front_id=12

  System Rescue CD
  http://www.SysRescCd.org/Main_Page

  Knoppix
  http://www.Knoppix.NET/

  Scan a Windows PC for viruses from a Ubuntu Live CD
  http://www.howtogeek.com/HOWTO/14434/scan-a-Windows-PC-for-viruses-from-a-Ubuntu-Live-CD/

  Use Ubuntu Live CD to backup files from your Windows computer dead
  http://www.howtogeek.com/HOWTO/Windows-Vista/use-Ubuntu-Live-CD-to-backup-files-from-your-dead-Windows-computer

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle="" -="" mark="" twain="" said="" it="">

• Serscan.sys ntoskrnl.exe BSOD

  I started having BSOD pointing to ntoskrnl.exe and serscan.sys. Before the accident, the system gets very insensitive. The Task Manager displays all the information Resource Monitor gets even worse. When I reboot I get BSOD. After a few resets the system up live. I scanned for malware and found nothing. Antivirus shows as well clean. HD Tune says Spin Retry count slightly exceeds threshold and an unknown attribute of a same drive on another more transferred sector Count. There is more than one drive, but HD Tune does not show health is probably that it is 2 TB. It would then be memory or maybe something else? BSOD SkyDrive here

  The accident was reported as being caused by DISK_HARDWARE_ERROR: a closer examination gives us a clue.

  Process of own fffffa800b83b380 Image: RapportService

  0: kd >! THREAD
  GetPointerFromAddress: unable to read from fffff800036ff000
  WIRE fffffa800a968640 Teb 13c8.1678 Cid: 00000000fff9e000 Win32Thread: 0000000000000000 PROCESSOR 0
  Borrow not identity
  GetUlongFromAddress: cannot read fffff8000363dbf0
  Owning process fffffa800b83b380 Image: RapportService
  Joint process s/o Image: n/a
  fffff78000000000: cannot get shared data
  Wait start TickCount 1985375

  You could do either of two things. Completely uninstall 'Trusteer report' and wait to see if the system crashes again, or you can force a crash by running the Driver Verifier, to help locate the faulty module, then post a link to the dump file here, resulting in the body of your next post.

  Driver Verifier - stalking a bad driver to behave.

  http://answers.Microsoft.com/en-us/Windows/wiki/windows_10-Update/Driver-Verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4B6D-95b3-c48669e4c983

• Caused by ntoskrnl.exe BSOD

  I get a lot of recent BSOD caused by + 59869 ntoskrnl.exe.  Doesanyone knows how to solve this problem?

  This is the dump: https://onedrive.live.com/redir?resid=A890DBFB04708DE%21107

  Hi Drew,

  Welcome to the Microsoft Community Forum.

  Based on my research by analyzing the time Mini dump file dump file gave the following result.

  PRIMAX Gaming Mouse

  STACK_COMMAND: kb

  FOLLOWUP_IP:

  NMgamingms + 1cbb

  fffff880'08512cbb

  SYMBOL_STACK_INDEX: 5

  SYMBOL_NAME: NMgamingms + 1cbb

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: NMgamingms

  Nom_image: NMgamingms.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 4a6976ec

  FAILURE_BUCKET_ID: X64_0x139_NMgamingms + 1cbb

  BUCKET_ID: X64_0x139_NMgamingms + 1cbb

  Follow-up: MachineOwner

  This file belongs to product Primax Gaming Mouse and was developed by the Primax Ltdcompany. This file description optical mouse USB Primax driver.

  I suggest updating the driver for your mouse in Device Manager and check if you are able to solve the problem.

  1. Press "Windows + R".
  2. Type devmgmt.msc
  3. Go with the mouse, right-click on it and click Update driver software

  I hope this helps. Write to us for assistance.

• How to fix "ntoskrnl.exe" BSOD since 64

  Once I updated for windows 7 64 I started having the BSOD and it's random, I would like to get help because I lost some files of work before and it's getting boring, it happened twice today.

  Minidump and sys info:

  https://onedrive.live.com/?CID=b25a6a01a3a51246&ID=B25A6A01A3A51246%21641&AuthKey=! AK0TCVMoFlBoCbk

  B

  Pilot verified and associated aswSnx.sys avast! Virtualization of ALWIL Software driver.  I remove it and use MSE in its place

  Avast can be a cause of BSOD.

  Please delete and replace by Microsoft Security Essentials at LEAST FOR TESTER
  http://files.avast.com/files/eng/aswclear5.exe

  http://www.Microsoft.com/security_essentials/

• Random BSOD and I do not know why.__Unable to load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32

  I don't know why this is happening, but I'm getting random BSOD now and then. I tried to point out my system to see if it generates a BSOD, but multitasking 3d and photoshop programs and what's not stress, then when I least expect, BANG! BSOD.
  The last of them, that I had now was in the middle of the night with almost no programs running. The system had worked for some time (one or two days), but nothing was he pointing out at the same time.

  What I think happened was: our microwave shorted out and caused a fuse to blow. But it was on another grid in our House (I hope I make myself clear, because I'm not used to talk about stuff like this in English!) so it should not affect my computer. But at the same time my microwave said "Thank you for everything!" my computer would BSOD. The thing is that my modem, my switch, my router and my NAS is connected to the electric network and my short circuted of switch. And my computer is connected to the switch cable.
  This effect possible that excess tension (or something) has short circuted my switch and 'jumped' power to the switch and on the cable and sending there is a shock to my computer? Or am I just paranoid? Laughing out loud

  I know that the controllers are pushed to the limit of the memory and therefor tolerate very little when it comes to electricity. I ran MemTest4.00 14 passes but I came with nothing. But memtest that tests memory, not the controllers, right? I am watching a fried motherboard?

  I did a windb, but I don't understand what he says. Could someone please translate this for me and give me your opinion?
  In addition, when you run windb, it's tell me am I wrong symbols. -What this means, and where can I get the symbols he wants? And what symbols?

  Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading dump file [C:\Windows\Minidump\Mini042910-01.dmp]
  The mini kernel dump file: only registers and the trace of the stack are available

  Symbol search path is: * invalid *.
  ****************************************************************************
  * Loading of the symbol may be unreliable without a symbol search path.           *
  * Use .symfix to get the debugger to choose a symbol path.                   *
  * After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
  ****************************************************************************
  Executable search path is:
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
  WARNING: Unable to verify timestamp for ntoskrnl.exe
  ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
  Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack2) MP (4 procs) free x 64
  Product: WinNt, suite: TerminalServer SingleUserTS
  Computer name:
  Kernel base = 0xfffff800 '02c4c000 PsLoadedModuleList = 0xfffff800' 02e10dd0
  The debugging session: 23:43:16.368 Thursday, April 29, 2010 (UTC + 02:00)
  System Uptime: 3 days 5:21:50.657
  *********************************************************************
  * Symbols cannot be loaded because the path is not initialized. *
  *                                                                   *
  * The symbol path can be defined: *.
  * using the _NT_SYMBOL_PATH environment variable.                 *
  * with the help of the there when you start the debugger argument. *.
  * using the .sympath and .sympath + *.
  *********************************************************************
  Cannot load the image \SystemRoot\system32\ntoskrnl.exe, 0n2 error Win32
  WARNING: Unable to verify timestamp for ntoskrnl.exe
  ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
  Loading the kernel symbols
  ...............................................................
  ................................................................
  ................................................
  Loading user symbols
  Loading unloaded module list
  ......
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Bugcheck A, {fffffa7fffffffea, 2, 0, fffff80002c5a95c}

  The kernel symbols are FALSE. Correct symbols to do the analysis.

  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  Probably caused by: ntoskrnl.exe (nt + e95c)

  Follow-up: MachineOwner
  ---------

  0: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  IRQL_NOT_LESS_OR_EQUAL (a)
  An attempt was made to access an address pageable (or completely invalid) to a
  application interrupt level (IRQL) that is too high.  It is usually
  caused by drivers using a wrong address.
  If a kernel debugger is available, download the stack trace.
  Arguments:
  Arg1: fffffa7fffffffea, memory referenced
  Arg2: 0000000000000002, IRQL
  Arg3: 0000000000000000, bit field:
  bit 0: value 0 = read operation, 1 = write operation
  bit 3: value 0 = not an enforcement operation, 1 = performance operation (only on chips that support this level of State)
  Arg4: fffff80002c5a95c, address memory

  Debugging information:
  ------------------

  The kernel symbols are FALSE. Correct symbols to do the analysis.

  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************
  *************************************************************************
  ***                                                                   ***
  ***                                                                   ***
  Your debugger is not using the appropriate symbols *.
  ***                                                                   ***
  In order for this command works correctly, your symbol path *.
  should point to .pdb files have the type information complete.      ***
  ***                                                                   ***
  Some (such as the public OS symbols) .pdb files are not *.
  contain the required information.  The contact group that *.
  you provided with these symbols, if you need this command for *.
  work.                                                          ***
  ***                                                                   ***
  Type referenced: nt! _KPRCB *.
  ***                                                                   ***
  *************************************************************************

  ADDITIONAL_DEBUG_TEXT:
  Use '! findthebuild' command to search for the generation of target information.
  If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.

  MODULE_NAME: nt

  FAULTING_MODULE: fffff80002c4c000 nt

  DEBUG_FLR_IMAGE_TIMESTAMP: 4b7d238f

  READ_ADDRESS: could not get nt! MmSpecialPoolStart
  Unable to get nt! MmSpecialPoolEnd
  Unable to get nt! MmPoolCodeStart
  Unable to get nt! MmPoolCodeEnd
  fffffa7fffffffea

  CURRENT_IRQL: 0

  FAULTING_IP:
  NT + e95c
  fffff800'02c5a95c?              ???

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

  BUGCHECK_STR: 0XA

  LAST_CONTROL_TRANSFER: from fffff80002ca626e to fffff80002ca64d0

  STACK_TEXT:
  fffffa60 '01bde688 fffff800' 02ca626e: 00000000' 0000000 a fffffa7f ' ffffffea 00000000'00000002 00000000'00000000: nt + 0x5a4d0
  fffffa60 '01bde690 00000000' 0000000-a: fffffa7f 'ffffffea 00000000'00000002 00000000'00000000 fffff800' 02c5a95c: nt + 0x5a26e
  fffffa60 '01bde698 fffffa7f' ffffffea: 00000000'00000002 00000000'00000000 fffff800 '02c5a95c fffffa60' 04dbf8b0: 0xa
  fffffa60 '01bde6a0 00000000' 00000002: 00000000 00000000' fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000' 00000000: 0xfffffa7f'ffffffea
  fffffa60'01bde6a8 00000000' 00000000: fffff800 '02c5a95c fffffa60' 04dbf8b0 00000000'00000000 00000000'00000000: 0 x 2

  STACK_COMMAND: .bugcheck; Ko

  FOLLOWUP_IP:
  NT + e95c
  fffff800'02c5a95c?              ???

  SYMBOL_NAME: nt + e95c

  FOLLOWUP_NAME: MachineOwner

  Nom_image: ntoskrnl.exe

  BUCKET_ID: WRONG_SYMBOLS

  Follow-up: MachineOwner
  ---------

  I'm grateful for any help I can get in that case.

  My system is: AMD 9950BE CPU, motherboard ASUS Crosshair II Formula, 4 x 2 giga OCZ 1066 mhz memory, Vista Ultimate 64 bit, ASUS 295GTX GPU

  Postal salvation,

  I think you're in luck. It chances are you are one of those rare cases where the BSOD may not be hardware related. In addition, it is actually pretty rare to have so many errors after a sfc... Wow. I think that alone has helped reduce the risk of an another BSOD and was good insurance against other problems.

  Do you have a chance to check the hard drive? Now, I would like to check the hard drive to see if there may be potential damage to the hard drive as well to help explain this number of errors (return to the material again).

  Here's how to new:

  http://Windows.Microsoft.com/en-us/Windows-Vista/check-your-hard-disk-for-errors

  I think that advice on the anti-virus scanning are also actually still relevant today. I have a scan of one of the two groups below as soon as you can and let us know the result if you can.

  virus/malware programs:

  Symantec:

  Works in Safe Mode and free:

  _ http://security.symantec.com/sscv6/WelcomePage.asp

  Trend Micro

  _ http://housecall.trendmicro.com/

  Ad-ware/spyware:

  Ad-aware

  http://www.lavasoftusa.com/

  Spybot Search and Destroy

  http://www.safer-networking.org/

  * It is an excellent versatile tool as it will both spyware and malware and has also a small footprint.

  See you soon,.

  Steve <> Microsoft Partner

• Blue screen error crash, caused by drivers: ntoskrnl.exe, Wdf01000.sys and tcpip.sys

  original title: Blue error screen, accident of death caused by drivers: ntoskrnl.exe, Wdf01000.sys and tcpip.sys

  I currently own an Aura of Alienware Dell, it's an amazing computer. The only problem is that I had a lot of problems, I was able to permanently fix all except this issue. I'll randomly crash blue screen, usually it doesn't happen often and it is normally not triggered by something specific, rarely it will crash at startup. I was able to download an application that can read the cache/dump blue screen crashes:

  34 accidents

  one was caused by Wdf01000.sys

  three was a result of tcpip.sys

  and all the rest of ntoskrnl.exe

  I don't know what caused it, I've had this computer for about a year now and I've never had this problem before. I don't remember an update of the cause, or by downloading any strange apps, downloads or viruses. (I had wiped my computer about 3 months ago)

  I don't know too much about software,

  Any help is appreciated.

  Hi bloo532,

  1. what application did you use to read dump files?

  2. did you of recent changes on the computer?

  It resembles that of the driver on the computer is causing the blue screen.

  Check if the problem persists in safe mode.

  Start your computer in safe mode

  http://Windows.Microsoft.com/en-us/Windows7/start-your-computer-in-safe-mode

  Restart the computer to return to normal mode

  Also make sure that all drivers are up to date on the computer.

  See the link below and try them the steps mentioned, check if it helps.

  Resolve stop (blue screen) error in Windows 7

  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

   

  If the previous step fails, then you will need to provide the minidump files.

  Use SkyDrive download collected files and after shot/screenshot.

  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  I hope this helps!

  Halima S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• Different random BSOD, ntoskrnl.exe

  Hello

  I am getting random BSOD in ntoskrnl.exe + 75c00
  Can occur at any time and not necessarily in charge. I tried testing my ram, hard drives to find errors & ran sfc/scannow without error.
  I downloaded the minidumps on skydrive @ https://skydrive.live.com/#cid=539E2424E35481DA&id=539E2424E35481DA%21105
  A big thank you to all those who can help.

  Brett

  Two different causes.  First and foremost your Kaspersky.  I would like to delete and replace it with MSE

  Kaspersky is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER.

  http://support.Kaspersky.com/downloads/utils/kavremover10.zip
  http://www.Microsoft.com/security_essentials/

  Second is related to keyscrambler.sys KeyScrambler keyboard driver.  I remove if not required or update to the latest if it is.

• BSOD of ntoskrnl.exe and other issues

  It is a new construction, new CPU/motherboard, etc, have a new video card. Three hard drives are in my system (1 SSD and HDD 2). I don't really know where to start to look at what may be the issue. I thought it was the video card, so I replaced it, but I still get similar questions.

  The BSOD is sporadic and the question doesn't seem to be the same thing every time, but ntoskrnl.exe has developed a couple of times. What are the possible problems that I might have?
  Here's what WhoCrashed said on the more recent accidents:
  Friday, February 8, 2013 4:59:24 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\020713-8751-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x33F79)
  Bugcheck code: 0xA (0xFFFFF88042F698C0, 0xFFFFF80002AD574F, 0x2, 0 x 1)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: Advanced Micro Devices, Inc..
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
  Google search: Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL

  Friday, February 8, 2013 4:59:24 AM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0xA (0xFFFFF88042F698C0, 0xFFFFF80002AD574F, 0x2, 0 x 1)
  Error: IRQL_NOT_LESS_OR_EQUAL
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, February 7, 2013 21:41:43 this computer crashed
  crash dump file: C:\Windows\Minidump\020713-8564-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)
  Verification of error code: 0 x 50 (0 x 8, 0xFFFFFFFFFFFFFFFF, 0xFFFFFFFFFFFFFFFF, 0x0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, February 5, 2013 11:53:09 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\020513-9063-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)

  
  Verification of error code: 0 x 50 (0 x 8, 0xFFFFF80006BC3FF6, 0xFFFFF80006BC3FF6, 0 x 2)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, January 30, 2013 3:26:32 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012913-9110-01.dmp
  This was probably caused by the following module: dxgkrnl.sys (dxgkrnl + 0 x 2333)
  Bugcheck code: 0xD1 (0xD, 0x301A460, 0x6FD35E33, 0x1)
  Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\dxgkrnl.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics Kernel
  Bug control description: This indicates that a kernel-mode driver attempted to access pageable memory with a high IRQL.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Monday, January 28, 2013 10:35:18 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012813-8314-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7EFC0)
  Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002AE3305, 0xFFFFF8800DEEA090, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Saturday, January 26, 2013 4:26:54 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012513-9500-01.dmp
  This was probably caused by the following module: hal.dll (hal + 0 x 5472)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\hal.dll
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: Hardware Abstraction Layer DLL
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Friday, January 25, 2013 05:35:47 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012413-11622-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x705C0)
  Bugcheck code: 0x3B (0xFFFFF80002A91846, 0xFFFFF8800CCB9600, 0xC0000096, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, January 23, 2013 05:06:04 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\012213-9328-01.dmp
  This was probably caused by the following module: pci.sys (pci + 0x25F1)
  Bugcheck code: 0xA (0 x 4722, 0xFFFFF80002ACEF85, 0 x 2, 0 x 1)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\drivers\pci.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Plug-and - Play PCI enumerator
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Dan you have 5 different causes there. May be an indication of Malware.
  To eliminate this possible cause, please download the free version of Malwarebytes.

  Update immediately.
  Do a full scan of the system
  Let us know the results at the end.
  
  http://www.Malwarebytes.org/products

• Frequent and unpredictable BSOD Ideapad S510p Touch 8.1 Windows 64 bit

  Help! My Ideapad S510p has recorded more than 10 BSOD during the last 2 weeks. It's totally random, not because of the mode to 'sleep' and is apparently caused by a failure in the ntoskrnl.exe and usbehci.sys.

  I tried looking for defective devices and disabled the bluetooth because it apparently didn't work.

  I also installed several new drivers.

  This has resolved nothing, and I am at a loss to know what to do entirely.

  Any help would be appreciated.

  I hope I can do something to solve it, because otherwise, I most certainly will get a new computer (not a Lenovo!) to replace this disappointment 4 - months old.

  In fact, I solved this problem myself after a while.

  I misled a system restore before the date where I started to encounter this error.

  So he came once more, I went into the 'PC Settings' menu and selected "update and recovery".

  He there had apparently updates to install, so I clicked on "More Details/information" and found that there are 3 related Intel drivers that have been listed, but for some reason, Windows 8 has not installed them automatically, so I checked each one and proceeded to install it and it was good sailing for me ever since.

  .

  A little tip for all of you who have experienced the problem, I've detailed in my previous post:

  Check what updates should be installed on your computer in the "PC settings" app thing and see if there are updates pilot-realted (as for your graphics card, in particular).

• BSOD, ntfs.sys and ntsokrnl.exe

  Hello, all.

  I have a user who has had multiple bluescreens than to the end. Initially, it started with the ntfs.sys driver crashing, but quickly turned to the subsequent accidents ntoskrnl. Started about a month apart, now much more frequent. I ran Dell startup diags, who spent all on board. I then updated / replaced every driver/chipset in the system and the BIOS. His current running Windows 7 Enterprise 64 bits in an environment of business and another user is to have what would be similar BSOD, but more specifically the ntfs.sys file. This is the discharge for the accidents. Any direction on where to take this would be greatly appreciated. Thank you!

  Thursday, March 5, 2015 18:55:01 this computer crashed
  crash dump file: C:\WINDOWS\Minidump\030515-11466-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7769A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF800047993D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Thursday, March 5, 2015 18:55:01 this computer crashed
  crash dump file: C:\WINDOWS\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x9F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF800047993D0)
  Error: DRIVER_POWER_STATE_FAILURE
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, March 3, 2015 11:52:00 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\030315-11216-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x7769A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039B4040, 0xFFFFF80000B9C3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, February 20, 2015 7:57:23 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\022015-11902-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x76E80)
  Bugcheck code: 0x9F (0x3, 0xFFFFFA8008B34060, 0xFFFFF80000B9C3D8, 0xFFFFFA8004BFDBD0)
  Error: DRIVER_POWER_STATE_FAILURE
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug check indicates that the driver is in an inconsistent or invalid power state.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, February 18, 2015 12:03:26 AM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\021715-8236-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x79D8A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039C8040, 0xFFFFF80000B9C3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, February 17, 2015 11:48:29 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\021715-10374-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x79D8A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039AB660, 0xFFFFF80000B9C3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Tuesday, January 13, 2015 18:26:12 GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\011315-20451-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x78A8A)
  Bug check code: 0x1000009F (0 x 4, 0 258, 0xFFFFFA80039B4660, 0xFFFFF8000478D3D0)
  Error: CUSTOM_ERROR
  file path: C:\WINDOWS\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  On Monday, December 8, 2014 6:39:14 PM GMT crashed your computer
  crash dump file: C:\WINDOWS\Minidump\120814-15459-01.dmp
  This was probably caused by the following module: ntfs.sys (Ntfs + 0 x 4211)
  Verification of error code: 0 x 24 (0xFFFFF880089ECCE8, 0xFFFFF880089EC540, 0x1904FB, 0xFFFFF880016D21D9)
  Error: NTFS_FILE_SYSTEM
  file path: C:\WINDOWS\system32\drivers\ntfs.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT file system driver
  Bug control description: This indicates there is a problem in the NTFS file system.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  The accident that produced this result is more than a month old, but I think that it always reflects exactly what the origins of the system to blue screen.

  1000009F error checking, {4, 258, fffffa80039b4660, fffff8000478d3d0}

  Failed to load image \SystemRoot\system32\DRIVERS\USA19Hx64.sys, 0n2 error Win32
  WARNING: unable to verify timestamp for USA19Hx64.sys
  ERROR: Module load completed but symbols can be loaded for USA19Hx64.sys
  WARNING: Unable to verify timestamp for win32k.sys
  ERROR: Module load completed but symbols can be loaded for win32k.sys
  Probably caused by: memory_corruption

  Follow-up: memory_corruption

  Loaded symbol image file: USA19Hx64.sys
  Image path: \SystemRoot\system32\DRIVERS\USA19Hx64.sys
  Image name: USA19Hx64.sys
  Timestamp: Thu Oct 30 15:52:45 2007 (47278B8D)

  USA19Hx64.sys, is a part of driver for Keyspan USB Serial Adapter ver: 3.7. Please update the driver, or uninstall the hardware/cable? If you can not.

  Keyspan® products.
  http://www.tripplite.com/LP/Keyspan/

  [Peripheral problem]

  Device PNP_Device_ID Error_Code
  Cisco Systems VPN Adapter for 64-bit Windows ROOT\NET\0000 this device is disabled.

• BSOD help (ntoskrnl.exe)

  I recently built a new computer for the first time and I am constantly a BSOD.  After consulting the minidump via the blue screen view files, it refers to the ntoskrnl.exe as the cause, but I suspect that maybe it's a corrupt driver (I could be wrong but).  Due to my lack of experience on this subject, however, I have no idea on how to identify the guilty and so need help.  As a result, I posted a link below containing the minidump files created by my computer and wish for some assistance on the interruption of information (any help would be greatly appreciated).

  http://www.mediafire.com/download/khtsg34cxn75t41/minidump.zip

  Thank you
  WildThing0079

  Great, thank you very much.

  We have various bug different controls:

  PFN_LIST_CORRUPT (4th)

  This indicates that the page frame number (PFN) list is corrupted.

  This error is usually caused by a driver passing a list of descriptor of bad memory. For example, the pilot could call MmUnlockPages twice with the same list. However, this bug control seems as frequently when there is a defective material, most often RAM or HARD disk.

  MEMORY_MANAGEMENT (1A)

  This indicates that an error occurred serious memory management.

  Error checking 1 a, {41287, 0, 0, 0}

  -1 setting of the bug check is 41287 indicating an illegal page fault occurred while now fixed synchronization of work.

  * Addition 41287, we have also the 1st parameter is 403 which indicates the table of page and NFPs are out of sync. It is probably a hardware error, although the device driver causing corruption is possible as well.

  PAGE_FAULT_IN_NONPAGED_AREA (50)

  This indicates that invalid system memory was referenced.

  Bug control 0 x 50 usually occurs after the installation of a faulty hardware or installation failure of material (usually associated with defective RAM, either main memory, L2 RAM or RAM video cache).

  Another common cause is a defective system service installation.

  Antivirus software can also cause this error, as a corrupted NTFS volume can do him.

  System_service_exception (3B)

  This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  
  This error has been linked to the excessive use of expanded memory and resulting from user mode graphics drivers enjambment and passing data incorrect of the kernel code.

  -----------------------

  1. AppleCharger.sys is listed and loaded, this is the driver GIGABYTE on / off Charge. See here for more information - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

  He is well known to cause BSOD, so please delete it as soon as POSSIBLE.

  2 even with gdrv.sys, which is the easy profit from Gigabyte - mobo utility power driver. Remove as soon as possible.

  3 remove and reinstall Kaspersky with temporary Microsoft Security Essentials for troubleshooting purposes:

  Kaspersky - remove http://support.Kaspersky.com/common/service.aspx?El=1464

  MSE - http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

  Kind regards

  Patrick

• BSOD on Windows 8 due to ntoskrnl.exe, DRIVER_POWER_STATE_FAILURE

  Greetings,

  My wife's computer has worked all fine until today where it restarted just randomly while it was idle, and then he did a check-up system and then it started to a black screen where nothing happened. My wife used the option Windows refresh to reset the drivers and all and then it worked fine again. After a short time however she started having a BSOD every 15 to 30 minutes or more.

  

  I used a program called Whocrashed to check dump files and it highlights the ntoskrnl.exe as guilty as possible or from what I understand, it could refer to a driver that works badly, but we know that one.
  Here is the link to the dump files:
  https://drive.Google.com/folderview?ID=0B2U-GIArNJ3YQ2p4T3Bhbkp4Sk0&USP=sharing
  If someone has an idea or can help us out, it would be greatly appreciated.
  Have a great day!

  TQ

  These have been associated with iaStorV.sys Matrix Storage Manager driver - ia32 of Intel Corporation.

  I would like to re - install the latest driver available.  Yours is 2 years and more

• BSOD - Server 2008 R2 - ntoskrnl.exe

  I had a problem recently with a BSOD that passes several times during the day. I newspapers DMP and used BlueScreenView to obtain some basic information (I know that it is also useful that it doesn't help) which seems to show that ntoskrnl.exe is at the origin of accidents. There are 6 Server, 1 is used by the LATTER and does not seem to have had this problem while the other 5 are part of a balanced load environment and have been seen this problem in some cases, 5 times a day. Here are the servers from RD.

  The servers were all working perfectly well until our company has purchased and installed a piece of software called screwdriver. This software seems to be the cause of accidents and I contacted their support in this regard. But while I'm waiting I think it is perhaps a good idea to ask if the DMP files might actually provide more information as to what specifically is causing accidents.

  For those who don't know, the screwdriver is a utility to help you with printing (printing from the Desktop server remotely to the workstation using the screwdriver driverless driver) and I wonder if there is a specific model of printer causing accidents or a driver side specific workstation or if its just one or a few users who cause accidents. Obviously BlueScreenView is not giving any information good but if the DMP file contains more information that might help I understand that it is worth looking into.

  The BSOD error is below:

  Signature of the problem:

  Problem event name: BlueScreen

  OS version: 6.1.7601.2.1.0.18.10

  Locale ID: 1033

  More information about the problem:

  BCCode: f4

  BCP1: 0000000000000003

  BCP2: FFFFFA801CCD9060

  BCP3: FFFFFA801CCD9340

  BCP4: FFFFF80001D85270

  OS version: 6_1_7601

  Service Pack: 1_0

  Product: 18_3

  Files helping to describe the problem:

  C:\Windows\Minidump\112414-48500-01.dmp

  C:\Users\***\AppData\Local\Temp\17\WER-2765148-0.SysData.XML

  Read our privacy statement online:

  http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409

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

  C:\Windows\system32\en-US\erofflps.txt

  Any help is appreciated.

  Thank you

  Ryan

  Ryan

  You should also put this on Technet and I will increase it there as well.

  http://social.technet.Microsoft.com/forums/en-us/home

  http://social.msdn.Microsoft.com/forums/en-us/home

• BSOD, BCCode f9, caused by ntoskrnl.exe, could you please help me with this?

  I get the BSOD with f9 code and I do not understand what is? Could you please advice what may cause this? I'm not sure,
  It happen when I stop or restart (15 minutes with him saying to stop) followed by BSOD (pilot State power failure).
  Once I'm back I can see that Windows has recovered from unexpected shutdown down. Using BlueScreenView tells me that ntoskrnl.exe is the cause.
  I was wondering if it has something to do with the USB Ports, because it won't work as a plug-and-Play (need to reboot USB is plugged).

  I reinstall all the USB drivers.

  My system:
  ASUS Z170A
  nVIDIA GTX 980ti

  850 M2 OF EVO 250 GB SSD

  Intel Core i7 - 4700 k
  32 GB of RAM (4 sticks 8 GB)
  Windows 7 64 bit

  All up to date.

  ==================================================
  Name of the file: ntoskrnl.exe
  Address of stack: ntoskrnl.exe + e23f0
  Address: Fffff800'0325e000
  Address: Fffff800'03844000
  Size: 0x005e6000
  Time stamp: 0x5708972e
  Time string: 09/04/2016 13:46:22
  Product name: Microsoft® Windows® Operating System
  File description: NT kernel & system
  File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
  Company: Microsoft Corporation
  Full path: C:\Windows\system32\ntoskrnl.exe
  ==================================================
  ==================================================
  Dump file: 081316-13447 - 01.dmp
  Crash time: 13/08/2016-12:46:05
  Bug Check String: DRIVER_POWER_STATE_FAILURE
  Bug check code: 0x0000009f
  Parameter 1: 00000000'00000003
  Parameter 2: fffffa80'1a0f1060
  Parameter 3: fffff800'052373 d 8
  Parameter 4: fffffa80'1f739c60
  Caused by the driver: ntoskrnl.exe
  Caused by the address: ntoskrnl.exe + 6f400
  File description: NT kernel & system
  Product name: Microsoft® Windows® Operating System
  Company: Microsoft Corporation
  File version: 6.1.7601.23418 (win7sp1_ldr.160408 - 2045)
  CPU: x 64
  Plant address: ntoskrnl.exe + 6f400
  Stack address 1:
  The stack address 2:
  Address 3 the battery:
  Computer name:
  Full path: C:\Windows\Minidump\081316-13447-01.dmp
  Number of processors: 8
  Main version: 15
  Minor Version: 7601
  Size of the dump file: 1 250 528
  Dump of file time: 13/08/2016-12:47
  ==================================================

  Hello

  There is a possibility that there is a problem with a driver on your PC. Here are a few things to try:
  • If you know which driver is causing the problem, update.
  • Make sure your hardware drivers are updated.

  Please keep us updated.

  Kind regards.