BSoD 0x9f error code

In recent weeks, my computer started showing a BSoD, titled State pilot failure, whenever I stop, and sometimes, when I restart.  The computer hangs on the closing down of the screen for at least ten minutes, until appears the BSoD, where making me one forced to close.  After having extensively searched through Microsoft' forums and topics of support I still have not found a solution.  I ran Debugging Tools for Windows to open a dump file, and it revealed an error code 0x9f with an ntoskrnl.exe image name.  She led me to believe that my ntoskrnl.exe is corrupted or out of date, but I know that it is not recommended to replace this program unless that busy on a Microsoft OS disc.  I bought my PC from Future Shop, so it isn't an OS disc.

Some of the solutions related to this error message, he said that the problem was possibly linked to attached USB devices.  The only USB device I connected is an OCZ Eclipse Laser Mouse.

The BSoD has a side effect that if she interrupts a reboot of the system that is required to complete the system configuration, it leaves such configurations what.

My PC specs are:
Manufacturer: gateway
Model: FX6800 - 03 h
OS: Windows Vista Home Premium 64-bit
SP: Service Pack 2
Processor: Intel Core i7 920

Here is the report of the bucket.  I'm totally familiar with this program then please let me know what I can do to provide more information if required.

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

Loading dump file [C:\Windows\Minidump\Mini091909-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 (8 procs) free x 64
Product: WinNt, suite: TerminalServer personal TerminalServer
Computer name:
Kernel base = 0xfffff800 '02663000 PsLoadedModuleList = 0xfffff800' 02827dd0
The debugging session: Fri Sep 17 23:57:05.741 2009 (GMT-7)
System Uptime: 0 days 4:13:43.191
*********************************************************************
* 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 1000009F, {4, 258, fffffa80078fa040, 0}

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 *.
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 + *.
*********************************************************************
*********************************************************************
* 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 + *.
*********************************************************************
Probably caused by: ntoskrnl.exe (nt + 5cc7f)

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

0: kd > nt! _KPRCB
^ Syntax error in ' nt! _KPRCB'
0: kd > referenced: nt! _KPRCB
^ Bad registry error in ' referenced: nt! _KPRCB'
0: kd > nt! _KPRCB
^ Syntax error in ' nt! _KPRCB'
0: kd > y
^ Syntax error in '-y'
0: kd > _NT_SYMBOL_PATH
^ Syntax error in "_NT_SYMBOL_PATH.
0: kd >! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, the change in diet has expired waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, the time-out in seconds.
Arg3: fffffa80078fa040, the thread that currently holds the lock of Pnp.
Arg4: 0000000000000000

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 *.
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 + *.

*********************************************************************
*********************************************************************
* 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 + *.
*********************************************************************

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: fffff80002663000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: fffffa80078fa040

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0X9F

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff800026bfc7f

STACK_TEXT:
fffffa60'01daf510 00000001' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000001: nt + 0x5cc7f
fffffa60 '01daf518 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000001 fffff800'026c3c9b: 0x1

STACK_COMMAND: .thread 0xfffffa80078fa040; Ko

FOLLOWUP_IP:
NT + 5cc7f
fffff800'026bfc7f 488d8c2400010000 lea rcx, [rsp + 100 h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt + 5cc7f

FOLLOWUP_NAME: MachineOwner

Nom_image: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

0: kd >! findthebuild
FindTheBuild service not found
0: kd >! findthebuild s; .reload
Use:! findthebuild [e |-Y] [PEI | s |-r] [-l

]
-E - disables exepath update
Y - disables friendly update
-l - hide local sets for the railways (must be last).
' *' define first sympath hiding in the local cache.
Pei - adds sympath and exepath discovery railroads
-r - sets of paths like sympath and exepath discovery
s - adds sympath and exepath discovery railroads
-t--detects the code paths for this trial version
*********************************************************************
* 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 + *.
*********************************************************************
0: kd > lmvm nt
start end module name
fffff800 ' 02663000 fffff800' 02b7b000 nt T (no symbol)
Loaded symbol image file: ntoskrnl.exe
Image path: \SystemRoot\system32\ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Fri Apr 10 21:58:39 2009 (49E0237F)
CheckSum: 00487B 94
ImageSize: 00518000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Any help would be greatly appreciated.  Thank you for your time.

Hello

It's a bad driver more likely. Have you added all the other new features or updated drivers just before that
has started? Look in the Windows updates too to see if new drivers have been added at this time there. Use the utility
below to read the minidump.

Here are a few ways to possibly fix the blue screen issue. If you could give the info from the blue screen that would be
Help. Such as ITC and 4 others entered at the bottom left. And any other information such as STOP error
codes and info like IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples:

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format:

Stop: 0 x 00000000 (oxoooooooo oxoooooooo oxoooooooo oxooooooooo)
Tcpip.sys - address blocking 0 x 0 00000000 000000000 DateStamp 0 x 000000000

It is an excellent tool for displaying the blue screen error information

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the
information on all accidents of a table - free
http://www.NirSoft.NET/utils/blue_screen_view.html

BlueScreens many are caused by old or damaged drivers, video drivers in particular, but there are other causes.

You can follow these steps in the Safe Mode if necessary or the command prompt Vista DVD or Options of recovery if your
system installed by the manufacturer.

This tells you how to access the System Recovery Options and/or a Vista DVD
http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

You can try a system restore to a point before the problem started when one exists.

How to make a Vista system restore
http://www.Vistax64.com/tutorials/76905-System-Restore-how.html

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

Start - type this in the search box-> find COMMAND at the top and RIGHT CLICK – RUN AS ADMIN

Enter this at the command prompt - sfc/scannow

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log
http://support.Microsoft.com/kb/928228

The log can give you the answer if there is a corrupted driver. (Says not all possible driver problems).

Also run CheckDisk, so we cannot exclude as much as possible of the corruption.
How to run the check disk at startup in Vista
http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

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

Often drivers up-to-date will help, usually video, sound, network card (NIC), WiFi, 3rd party keyboard and
smile, as well as of other major device drivers.

Look at the sites of the manufacturer for drivers - and the manufacturer of the device manually.
http://pcsupport.about.com/od/driverssupport/HT/driverdlmfgr.htm

How to install a device driver in Vista Device Manager
http://www.Vistax64.com/tutorials/193584-Device-Manager-install-driver.html

How to disable automatic driver Installation in Windows Vista - drivers
http://www.AddictiveTips.com/Windows-Tips/how-to-disable-automatic-driver-installation-in-Windows-Vista/
http://TechNet.Microsoft.com/en-us/library/cc730606 (WS.10) .aspx

------------------------------------------------------------------
How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly
http://support.Microsoft.com/kb/958233

Troubleshooting, STOP error blue screen Vista
http://www.chicagotech.NET/Vista/vistabluescreen.htm

Understanding and decoding BSOD (blue screen of death) Messages
http://www.Taranfx.com/blog/?p=692

Windows - troubleshooting blue screen errors
http://KB.wisc.edu/page.php?id=7033

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

In some cases, it may be necessary.

The Options or Vista recovery disk Startup Repair

How to do a startup repair
http://www.Vistax64.com/tutorials/91467-startup-repair.html

This tells you how to access the System Recovery Options and/or a Vista DVD
http://windowshelp.Microsoft.com/Windows/en-us/help/326b756b-1601-435e-99D0-1585439470351033.mspx

I hope this helps.

Rob - bicycle - Mark Twain said it is good.

Tags: Windows

Similar Questions

  • BSOD with error code Bugcheck: 0xD1

    Original title: the dreaded BSOD.

    Hi, finally bite the bullet and ask for help.

    Establish an office a few years back who worked perfectly without any problem, a couple of years, I decided it was time to upgrade and replaced the motherboard, RAM and graphics card with a clean install of Windows 7. He ran very well with some heavy for a week or two games and then the first BSOD came, nothing thought and turned down my graphics settings and tried to play again and then he started blue screening 5 minutes of any game. After many graphics driver reinstall (with driver sweeper), memtest runs and HD check blue screens have continued and I finally gave up on it.

    Fast forward 2 years, I made another attempt on the desktop, 10 hours of updates Windows and updates of pilot followed a complete with MSE analysis and I booted up Fallout New Vegas, the game ran perfectly for 2 days and then blue screens started.

    Help please!

    Processor: AMD Phenom II x 4 955

    RAM: 2x2gb Crucial

    Mobo: Asus M4A785TD-V Evo

    OS: Windows 7 64-bit

    PSU: Corsair CX500

    GPU: Gigabyte Nvidia GTX460

    No overclocking

    Information System

    Minidumps

    DriverView

    WhoCrashed reports

    Friday, April 18, 2014 11:18:08 GMT crashed your computer
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0xAA2A)
    Bugcheck code: 0xD1 (24, 0 x 2, 0 x 0 x 0, 0xFFFFF88004172A2A)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    Description: DirectX Graphics MMS
    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.

    Thursday, April 17, 2014 22:38:20 GMT crashed your computer
    crash dump file: C:\Windows\Minidump\041714-27861-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FABB05, 0xFFFFF88007EB6E30, 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.

    Thursday, April 17, 2014 22:09:37 GMT crashed your computer
    crash dump file: C:\Windows\Minidump\041714-68921-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
    Verification of error code: 0 x 50 (1, 0xFFFFF80002E86E49, 0xFFFFF88006C3D000, 0 x 0 x 0)
    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.

    Thank you!

    I would remove the stick that failed and operate the system for a few days.

    Kind regards

    Patrick

  • Pavilion g6: BSOD BUGCODE_USB_DRIVER error

    I have a HP Pavilion g6-1b60us running Windows 7.  Recently, I've been doing the BSOD with error code BUGCODE_USB_DRIVER at least once a day, sometimes several times a day. I tried updating the drivers, but am still affected by the same problem. Your help would be greatly appreciated!

    Hi there @reCATcha1 

    Welcome to the Forums of HP Support! It's a good place to find the help you need, so many other users, the HP experts and other members of the support staff.

    I understand that you have found an error on blue screen BUGCODE_USB_DRIVER. I'm happy to help you.

    Have you tried to scan your system for what as malware, viruses etc?  If you do not I would recommend doing this first and as a result, clean your system.

    If you know approximately when the problem started, you can try to do a system restore to a point before it all started.

    Using Microsoft System Restore (Windows 7)

    Otherwise, I recommend you back up the contents of your hard drive and then look at the system recovery, I would start with just the drivers, and if it does not help, then a factory restore.

    Performing a recovery of system HP (Windows 7)
    Troubleshooting problems of recovery HP System (Windows 7)

  • Windows 7 BSOD and receiver code error BCCode: 9f

    Original title: Windows 7 BSOD
     
    Hey guys I just built my first system and it was a lot. I used the trial version of Windows 8 64-bit for about a week I had to wait for my windows 7 to arrive. Windows 8 everything went fine with no problems. Then I installed windows 7 and ever since then, every time I leave my system alone for an hour or two, I'll be back to see that it crashed because of this error message below. Can I use my computer all day, video, editing, etc, but when I close all and leave for an hour, I'll be back to see that I have broke down. I try to leave it overnight to install my steam on games but crashes after about an hour.
    Any help would be great.
    Error message:
    Signature of the problem:
    Problem event name: BlueScreen
    OS version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033
    More information about the problem:
    BCCode: 9f
    BCP1: 0000000000000003
    BCP2: FFFFFA80070A4A10
    BCP3: FFFFF800047C43D8
    BCP4: FFFFFA80097AB010
    OS version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
    Files helping to describe the problem:
    C:\Windows\Minidump\122112-20077-01.dmp
    C:\Users\Ryan\AppData\Local\Temp\WER-58203-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
    Data sheet:
    Intel i5 3570 k @3.4 ghz
    Cooler Master Hyper 212 Evo
    Z77 UD5H Gigabyte motherboard
    EVGA Gtx 670 FTW
    Corsair Vengeance 8 GB 1600
    Corsair HX 750w PSU
    Seagate Barracuda 7200 rpm 1 TB
    Cooler Master Storm Stryker
    Edit: I thought it might have something to do with memory, so I ran Memtest 86 + 4 hours and had no error: P

    Hello

    Thanks for posting your query in Microsoft Community!

    According to the description, you are receiving BSOD (Blue Screen of Death) and receive the error code BCCode: 9f.

    To help you to propose measures to solve the problem, I would appreciate if you could answer the following question:

    Did you do changes on the computer before the show?

    I suggest to follow the steps of the items listed below and check if it works.

    Error message when you try to resume a Windows 7 or Windows Server 2008 R2 to Hibernate computer-based: "Stop 0x0000009F"

    http://support.Microsoft.com/kb/977186

     

    Stop error when you upgrade a computer that is running Windows 7 or Windows Server 2008 R2 standby or into hibernation, or when you restart the computer: "0x9F".

    http://support.Microsoft.com/kb/975599

     

    stop "0x0000009F" error message when a computer enters and fate of putting into hibernation in Windows 7 or Windows Server 2008 R2

    http://support.Microsoft.com/kb/981848

    Hope this information helps. For any other corresponding Windows help, do not hesitate to contact us and we will be happy to help you.

  • Where in the event error Codes BSOD Windows XP store Viewer

    As the title States where Windows XP Professional SP3 with 0 x 86 stores the error logs when a blue screen happens? I can not find I checked in the system log, but could not yet identify the BSOD error codes. I activated to connect with these error codes when it occurs.

    Can someone tell me where to find the error codes to stop Windows (BSOD)? Also, if you can describe what the entry will look like it should help.

    Thank you

    Victor

    VM

    You have several questions.

    1 - this one accident was linked to Redlight. sys with description BufferZone Kernel Module is a driver file of the BufferZone belonging to BufferZone product company.  That needs to be removed (at least for testing)

    2 - cumon

    Associated cumon.sys driver filter system provider (R) Win 7 kit Windows DDK CRCMon (it's a minor issue)

    3 - cmuda.sys related to cmuda.sys C-Media Audio Driver (WDM). YOURS IS 2002

    How to find drivers:


    -Google search for the name of the driver
    -compare Google results with what is installed on your system to determine on what device/program, it belongs to
    -Visit the web site of the manufacturer of the hardware or program to get the latest drivers (do not use Windows Update or Device Manager Update Driver function).
    s ' there is difficult to locate them, post back with questions, and someone will try and help you find the right program

    The most common drivers are listed on this page: driver reference

    http://www.carrona.org/dvrref.php

    http://SysNative.com/drivers/

    -Driver manufacturer links are on this page: http://www.carrona.org

  • BSOD error codes and stop after windows update

    Hi all.  I have a computer dell laptop, inspiron e1505. 2 days ago, he did a system update and then restarts are not at all. If I start windows normally or start with the last known good configuration I get the BSOD and stop error codes, 0x0000007e, 0 x 80000003, 0x805c370c, 0xf79e02b4, 0xf79dffb0.
    If I try to any safe mode, it begins to go through a list of drivers then stops briefly and goes to a blue screen Uni with no writing at all.   It's beyond what I know how to fix.  Thanks for your time

    Kb971486 uninstalled by using the recovery console, works again.

  • Windows Vista SP2, random BSOD with error checking code 0 x 19

    Hi all

    I have seemingly random crashes on my old laptop 3 years recently - BSOD with error checking code 0 x 0000019 (0x00000020, 0xe92f4780, 0xe92f48d0, 0x0a2a0440), and BlueScreenView says that accidents are caused by ntkrnlpa.exe and Ntfs.sys. I have absolutely no idea why it happened--unusual does update, none of the material changes & software installations. The system hangs especially after maybe one or two days after starting with some sleep & wake ups inbetween and the only accidents while there are prominent running shows - namely, all the accidents that happened while I was running Firefox. Seconds before the BSoD (shell & all) system simply freezes and does not respond to ctrl + alt + delete, but is still running (as indicated by the fact that once, I forced a power off and after that restart the event log indicates the previous stop at was not planned), then watch the usual BSoD screen.

    After doing some googling, I began to suspect that this should be a memory or a hard drive problem, or maybe an overheating causing the two since he not there no significant change of software on my computer recently again issues just appeared without reason. So I cleaned my laptop fan and the heatsink and ensured that the hot air can leave the chassis without being blocked, did some checking of memory with memory auditing Windows - no problems in 5 innings and ran chkdsk on my system partition with all available options - perfectly normal, but the chkdsk has acted quite strangely that check all took about 30 seconds and no normal as the ID information of partition, size etc. that should be there never appeared; is this a normal behavior? or something is wrong with my chkdsk?

    I'm still (lol) impatiently waiting for the next crash, not sure whether the problem is still there or not. Meanwhile could you please help me understand what is the problem with my system?

    It seems that the disc is the most likely cause. If it is intermittent, it may be difficult to diagnose.

    The manufacturer of the laptop provides any diagnosis?  Several manufacturers have a key at startup to access the diagnostics.

    CHKDSK should last several minutes. There is information about the different ways to run chkdsk here:

    http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

    You can try this disc test program:

    http://www.Seagate.com/www/en-us/support/downloads/SeaTools/

    If the version of WIndows does not find anything. Try to use the version BACK from a CD.

  • Random BSOD, get several error codes: IRQL_not_less_or_equal. Error code USB bug; memory management error

    For the last two months I get random blue screen of death, codes seem to change from time to time, initially it was level IRQL each time and then one or twice USB bug and then error code once, it was an error of memory management code.  Sometimes I get a screen saying something about checking some recently installed device causing problem, but nothing has been installed recently.

    I have and HP Windows Vista Home Premium SP2, AMD athlon 64 X 2 Dual core 5000 + 2.60 GHz memory is 3.0 GB; system is 32-bit graphics card is NVIDA

    The BSOD happens randomly and it can happen just when I turn on pc (so I don't think overheating is the question) or pc will be fine for a day or two and hang after that pc sat for an hour.  PC GOLD may be on all day and is very good.  I tried to run the "controls" and everything keeps the fine.  I even thought it may have been my antivirus so I changed it and still doesn't solve problem.  I ran checks software malware, viruses, etc. and have not led to what.

    It seems that after some update was made with windows was when I started to have problems, but could be a coincidence.  I looked around but have not found anyone with a similar problem like mine, in regards to get multiple error codes and bsod.  To restart, I usually have to unplug the pc and wait a bit to try to restart and go through all process control but all "passes". Thanks in advance for your help.

    Hi kcsun,

    Blue screen errors can be caused by either a software or hardware problem.

    See the below Microsoft article that could help you solve random blue screen of death on the computer.

    How to fix bluescreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly
    http://support.Microsoft.com/kb/958233

     

    I hope this helps!

    Halima S - Microsoft technical support.

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

  • BSOD: 10 d error Code

    Original title: Stop error Code

    I get frequently (almost once every session) error code 10 d BSOD in Win7 64 core by what seems to be my firewire driver.  Could you tell me how to get troubleshooting on this? All the drivers are up to date.  I have my Skydrive put in place if I understand that I may need to compress my dmp file.  Thank you for all that you do!

    No problem. Actually, that's the way it should be made clear, but it's a long story.

    The minidump files denounces yfwbus.sys (Yamaha Steinberg FW Driver) as a possible cause of the error with the 1394ohci.sys (1394 OpenHCI Driver), taking responsibility for the accident:

    10 d error checking, {8, 57ff5f12558, 4, fffffa800ae06c50}

    WARNING: Unable to verify timestamp for yfwbus.sys
    ERROR: Module load completed but symbols can be loaded for yfwbus.sys
    Probably caused by: 1394ohci.sys (1394ohci! IsochTx::HandleIsochAttachBuffers + 3ce)

    If you have tried update or restore the Yamaha rider you can try to move to the old driver 1394 - steps in the following link:

    http://KC.FlexRadio.com/Print50433.aspx

    However if the memory is showing errors substitute the faulty memory must come first.

  • Random BSOD with the following error code: 0 x 00000116 whenever I'm in a game.

    For some time now, I have random BSOD with the following error code: 0 x 00000116 whenever I'm in a game.
    I tried to update the video drivers, rolling back to an older version of the driver, even reinstall windows and without having to install anything else except the video driver (without windows updates) I went and started a game(APB:Reloaded) one played for a while and he always gave me this JUDGMENT. I'm out of ideas.
    The machine that I use windows with is an Ace Aspire 5750 G laptop.
    The specifications are the following:
    Intel i5 - 2410 m with Intel HD 3000 (time, 83 all in game).
    NVIDIA GT540m (time, 76 while gaming),
    8 GB of ram.
    I took a picture of the BSOD and uploaded to Skydrive, link here: https://skydrive.live.com/redir?resid=AB28B2FD7DC5BA0E! 196 & authkey =! AF849R6EMQvYixs

    Hello

    Unfortunately I'm not surprised at all symptoms you described.

    As I said above:

    My main concern is that the material side of the issue is rooted in the video to verify that
    as much as you can. And of course it can still be heat related.

    Do not forget to ask in the Nvidia Forums (and support) to see if others have the same
    sort of problems with this video card.

    Rob - SpiritX

  • Received error BSOD, ran Diagnostics, got the error code 2000-0146, tried to boot from different HARD drive, got the same stop error message

    So my friend gave me his computer dell laptop. The thing would boot normally for a few days until he would give me a blue screen of death with the "UNMOUNTABLE_BOOT_VOLUME" message constantly to not even upward. I ran the diagnostics and got the error code 2000-0146. What I've read, this code error means that the HARD drive is bad and must be replaced. So, to make sure that it's the hard drive, tried to boot from an old hard drive, I got around the installation by USB and windows gave me the same stop error message. May - so that means it's a motherboard problem?

    No, it isn't - unless the operating system was installed on this drive AND the system in question, that it won't work as a bootable drive.

    Unplug the system, remove or disconnect the battery and hold the power for 30 seconds approximately.  Turn on and re-run the diagnostic tests - if the same error appears again, the drive is bad.  Replace it.

  • In Safari, I get the error code BSO D 0 X 80060402, error code Windows defender in the available boot device. He told me to contact Microsoft certified technicians. I do not use Microsoft or windows.

    In Safari, I get the error code BSOD 0 X 80060402, error code Windows defender in the available boot device. He told me to contact Microsoft certified technicians. I do not use Microsoft or windows.

    You have utilities installed on the computer antivirus, cleanup, or other third party maintenance?

  • On screen error code Blue 0000009c, parameter1 00000001

    original title: blue screen of death on windows xp pro sp2 2002

    Sorry I duno how to write the problem... but I hope below the error obtained someone help me... Thank you

    Event type: error
    Event source: System error
    Event category: (102)
    Event ID: 1003
    Date: 28/04/2011
    Time: 20:00:18
    User: n/a
    Computer: JASON
    Description:
    Error code 0000009c, parameter1 00000001, parameter 2 8054d5f0, b6000000 parameter3, parameter4 00000181.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6 d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 30 30 30 30 30 30 39 0000009
    0020: 63 20 20 50 61 72 61 6 d Param c.
    0028: 65 74 65 72 73 20 30 30 00 very
    0030: 30 30 30 30 30 31 2 C 20 000001.
    0038: 38 30 35 34 64 35 66 30 8054d5f0
    0040: 2 c 20 62 36 30 30 30 30, b60000
    0048: 30 30 2 c 20 30 30 30 30 00, 0000
    0050: 30 31 38 31 0181
    p.

    Hello.

    This error code and the behavior you describe tells me you have a hardware problem with your machine.  With time to amend the BSOD, I would say the problem is a problem of overheating.  Take the machine to a service centre/repairman good reputation.

  • blue screen error code 1000008e death.

    Original title: error code?

    I sometimes get the "blue screen of death"... with this error code:

    BCCode: 1000008e BCP1: E0000001 BCP2: B8400925 BCP3: AC4178B8
    BCP4: 00000000 OSVer: 5_1_2600 SP: 3_0 product: 768_1

    Can someone help me solve this problem?

    Since the MS Answers forum does not prompt for any information system when a new question is asked, we know absolutely nothing about your system.  This makes troubleshooting difficult unless you like to try things.

    All the Microsoft Engineers do sometimes (most of the time) is just use the Bing search engine to see what happens to your error message and publish the first Microsoft KB article that appears in the search engine Bing (try it yourself and you will get the article sent you the MSE - which is unlikely to help all).  Who is troubleshooting not, is it?

    Did you take a glance at this KB article?  It's a bit overwhelming, and it requires you to have an XP installation CD and if you have one, it better be the same Service Pack as your Service Pack installed or things will go back.  However, the MSE was using the word "try" and that does not sound very confident for me-, but feel free to try.

    If you sometimes get only the BSOD, you provide a us with more information about your system and use something like BlueScreenView to see if you can understand what is underway.

    Please provide additional information on your system:
    What is your system brand and model?
    What is your Version of XP and the Service Pack?
    Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..
    The question was preceded by a loss of power, aborted reboot or abnormal termination?  (this includes the plug pulling, buttons power, remove the battery, etc.)
    The afflicted system has a CD/DVD drive work?
    You have a true bootable XP installation CD (it is not the same as any recovery CD provided with your system)?
    Your system seems to start OK and then crash or didn't he start not at all?
    If your system works fine, what do you think might have changed since the last time it worked correctly?
    Can you make the system crash when you want
    ?  For example, you would say that there is no specific system activity that coincides with the accidents (like watching videos, playing games, etc.).

    The next time your system crashes, provide more information on what you see.

    Here's a BSOD example showing information you provide:
    Send for the nose and the Red arrows (3 to 4 lines total).
    Send all * line STOP message since there are clues in the 4 parameters.
    If there is a name of the file listed in the STOP message, don't forget to include this information too.
    Ignore the boring text unless it seems important to you.  We know what a BSOD looks like, we need to know what your BSOD looks like.
    Now provide more information about your system and data against more recent accidents.
    Click Start, run and enter in the box:
    Msinfo32
    Click on OK and when the system info summary appears, click on Edition, select all, copy, and then paste the information here.
    For information about video drivers, expand components, click view, click on edit, select all, copy and then paste the information here.
    There will be some personal information (such as the user name and the name of the system), and anything that turns information private for you, simply delete the pasted information.
    This will minimize back Q & A and eliminate guesswork.
    Download BlueScreenView here:
    Unzip it and run it (BSV installs nothing) and let him complete the digitization of all your crash dump files.
    If you double-click on depressed, you will get information on it (including the field caused by the driver) and you should be able to spot the problem right away - especially if you see a model in landfills where Caused by field pilot is the same (beginning with this driver).
    BlueScreenView tries to find the right driver or module that caused the blue screen by looking inside the stack of the accident. However, be aware that the driver detection mechanism is not 100% reliable, and you should also look in the lower pane, that display all drivers/modules found in the stack.
    Select (highlight) one or more of the most recent dump files by clicking on them and hold down the CTRL key to select multiple files.  Try to select only the most recent links that relate to your problem (perhaps five or six to start dump files).
    Click on file, save selected items and save information from the dumps to a text file on your desktop called BSOD.txt
    .  Open BSOD.txt with a text editor, copy the text and paste it in your next reply.
    Here's an example of report ASB to a single BSOD I initiated on purpose that indicates the cause of the accident as the pilot i8042prt.sys belonging to Microsoft Corporation:
    ==================================================
    Dump file: Mini062110 - 01.dmp
    Crash time: 21/06/2010-11:51:31
    Bug Check String: MANUALLY_INITIATED_CRASH
    Bug check code: 0x000000e2
    Parameter 1: 0x00000000
    Parameter 2: 0x00000000
    Parameter 3: 0x00000000
    Parameter 4: 0x00000000
    Caused by the driver: i8042prt.sys
    Caused by the address: i8042prt.sys + 27fb
    Description of the file: i8042 Port driver
    Product name: Microsoft® Windows® Operating System
    Company: Microsoft Corporation
    File version: 5.1.2600.5512 (xpsp.080413 - 2108)
    Processor: 32-bit
    Computer name:
    Full path: C:\WINDOWS\minidump\Mini062110-01.dmp
    ==================================================
    Send the information of the last 5 memory dumps (if you don't have 5 memory dumps yet, send the newest, you have).
    While you wait, please follow these steps:
    Perform scans for malware, and then fix any problems:
    Download, install, update and do a full scan with these free malware detection programs:
    Malwarebytes (MMFA): http://malwarebytes.org/
    SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
    They can be uninstalled later if you wish.
    Restart your computer and solve the outstanding issues.
  • 0xc000000fb solutions to this error code must be running in safe mode or stop crashing

    very annoying is not good for the soul! any help would be great... must be free however!

    I find it curious that a Google search of your error code come up with zero hits.

    As MS Answers still don't ask for information when a new question is asked, the best response to emerging issues is a wasted messages cycle and time to get additional information.

    Perhaps you should tell us a little about your system:

    What is your system brand and model?
    What is your Version of XP and the Service Pack?
    Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..
    The question was preceded by a loss of power, aborted reboot or abnormal termination?  (this includes the plug pulling, buttons power, remove the battery, etc.)
    The afflicted system has a CD/DVD drive work?
    You have a true bootable XP installation CD (it is not the same as any recovery CD provided with your system)?

    Your system seems to start OK and then crash or didn't he start not at all?

    If your system works fine, what do you think might have changed since the last time it worked correctly?
    Can you make the system crash when you want?  For example, you would say that there is no specific system activity that coincides with the accidents (like watching videos, playing games, etc.).
    If your system uses to work properly, what do you think has changed sine the last time, he did not work properly?

    The next time your system crashes, provide more information on what you see.
    Here's a BSOD example showing information you provide:
    Send for the nose and the Red arrows (3 to 4 lines total).
    Send all * line STOP message since there are clues in the 4 parameters.
    If there is a name of the file listed in the STOP message, don't forget to include this information too.

Maybe you are looking for