BSOD on shutdown/reboot bug check 9f

I get d BSOD saying DRIVER_POWER_STATE_FAILURE
all d minidumps are in given link
I've updated all my drivers for a version more recent but problem still persits
Product F2C09PA #ACJ number

Operating system: Windows 8.1 64bits

Report Viewer blue screen:

062814-35812 - 01.dmp 2014/06/28 02:14:47 DRIVER_POWER_STATE_FAILURE 0x0000009f 00000000 00000003' ffffe001 '46cbe730 fffff802' e7dfe930 ffffe001'4e104250 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062814-35812-01.dmp 4 15 9600 706 528 2014/06/28 09:25:09
062714-36859 - 01.dmp 2014/06/27 20:20:55 ffffe000 'eb7ed060 ffffd001' 00000000'00000003 0x0000009f DRIVER_POWER_STATE_FAILURE c0fec930 ffffe000'fabc76f0 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062714-36859-01.dmp 4 15 9600 722 816 2014/06/27 21:42:43
062614-49375 - 01.dmp 26/06/2014-15:12:54 fffff802 '5249ce70 fffff802' 00000000'00000008 0x0000007f UNEXPECTED_KERNEL_MODE_TRAP 5248df40 fffff802'4f6ece94 ntoskrnl.exe ntoskrnl.exe + x 64 ntoskrnl.exe 153fa0 + 153fa0 C:\WINDOWS\Minidump\062614-49375-01.dmp 4 15 9600 288 768 26/06/2014-15:14:45
062614-46765 - 01.dmp 26/06/2014-15:06:15 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 00000000'00000008 '28df5e70 fffff803' fffff803 28ddff60 fffff803'26ef3f2c werkernel.sys werkernel.sys + a238fe70 x 64 ntoskrnl.exe + 153fa0 C:\WINDOWS\Minidump\062614-46765-01.dmp 4 15 9600 289 632 26/06/2014-15:07:58

Minidump:

Debug version of Microsoft Windows (R) 6.3.9600.17029 X 86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading dump file [E:\ImageDiags_1.8.56.0\Minidumps\062614-41046-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. *
* using the argument y < symbol_path > then to start the debugger. *
* 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 8 Kernel Version 9600 MP (4 procs) free x 64
Product: WinNt, suite: TerminalServer personal TerminalServer
By: 9600.17085.amd64fre.winblue_gdr.140330 - 1035
Computer name:
Kernel base = 0xfffff800 '48a7f000 PsLoadedModuleList = 0xfffff800' 48d492d0
The debugging session: Thu Jun 26 19:28:32.858 2014 (UTC + 05:30)
System Uptime: 0 days 0:57:48.770
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
* *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable. *
* using the argument y < symbol_path > then to start the debugger. *
* 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
...........

Summary of the symbol load error *.
Name of the module error
Ntoskrnl the system cannot find the specified file

You can solve most symbol related issues by turning the symbol loading diagnostics (! sym noisy) and repeating the command that caused the symbols to load.
You should also check that your symbol search path (.sympath) is correct.
*******************************************************************************
* *
* Bugcheck analysis *.
* *
*******************************************************************************

Use! analyze - v to obtain detailed debugging information.

9F error checking, {3, ffffe001b66a2060, ffffd000c51e1930, ffffe001ca506790}

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

*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _DEVICE_OBJECT *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! TRIAGE_9F_POWER *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _IO_STACK_LOCATION *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _DEVICE_OBJECT *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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! _IRP *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 *.
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
Either you have specified an absolute symbol, or your debugger *.
has no information complete symbol. Absolute symbol *.
resolution is disabled by default. Please specify a *.
complete symbol module! NomSymbole, or activate the resolution *.
symbols unskilled by typing '.symopt 100 '. Note that *.
allowing unqualified symbol with the network symbol resolution *.
shares of server in the symbol path can cause the debugger to *.
appear to hang for long periods of time when an incorrect *.
symbol name is typed or the symbol of the network server is down. ***
*** ***
For some commands work properly, 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 + 153fa0)

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

Rather you should mention that I don't have symbols told me how to get them

and this link Forum called youtube video and youtube video was useless by itself it did not show how to solve my problem.

But in any case I solved it and here is how I did it

1. restored by computer laptop to an earlier time of the first restore point was himself on the day where the problem started, but nevertheless I did

2 uninstalled all my network drivers and all tha application uses internet (Hotspot service as conectify) except of WEb browsers

3. in the event viewer WIndows stopped all service ontenet which appear to come from a third party application or so.

4. voila it worked

5. thanks for your useless highly appreciated <

Tags: Notebooks

Similar Questions

  • BSOD on shutdown/reboot bugcheckcode CRITICAL_OBJECT_TERMINATION error 0x000000F4

    Hi guys im currently crashes BSOD every time that I restart or shutdown my desktop im running windows 7 Ultimate SP1 and I used bluescreenview, but the results were so vague, that I'm a hard time figuring what went wrong

    the error is bugcheckcode 0x000000F4 CRITICAL_OBJECT_TERMINATION

    Thank you.

    CRITICAL_OBJECT_TERMINATION (f4)

    This indicates that a process or thread crucial to system operation has unexpectedly is released or ended.

    BugCheck F4, {3, fffffa80060f8aa0, fffffa80060f8d80, fffff800031d7db0}

    1st argument is 3, indicating that it was a process as opposed to a thread that is stopped.

    1: kd >! fffffa80060f8aa0 process 3
    GetPointerFromAddress: unable to read from fffff80003105000
    PROCESS fffffa80060f8aa0
    SessionId: no Cid: 08C 8 Peb: 7efdf000 ParentCid: 06f4
    DirBase: 7c47d000 ObjectTable: fffff8a001ddaa00 HandleCount:
    Image: winlogon.exe

    The process that ended a winlogon.exe.

    1: kd > k
    Call child-SP RetAddr site
    00000000'00000000 00000000'00000000, 0 x 0

    Battery set to zero.

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

    With only a minidump, it is impossible to say what caused the end of winlogon. If I had to guess, it's probably a software conflict. However, if I had a kernel image, I would have a solid answer as well as the question of whether or not there is the possibility of a rootkit. With only a minidump, it is impossible to say.

    For now, we will do the following:

    1. make sure that your Asmedia ASM-106 x Sata 6 G controller drivers are up-to-date.

    2 uninstall all Asus bloatware.

    3 uninstall cFosSpeed - The Internet Accelerator, software bug.

    If the above does not stop the breaks down, I'll need a kernel image.

    Kind regards

    Patrick

  • BSOD 0x000000f4 and 0x0000007a bug check code

    http://jeffreybugahod.com/images/Screenshot_1.PNG Hi guys,.

    I am running Windows 7 64 bit and I do experience blue screen almost every week with bug 0x000000f4 and 0x0000007a random control. I don't really have any idea what the problem with my PC. I ran memtest86 for a night or Pluss and past 7 tests (it was 8 test said in the way). I also run chkdsk and there is no error. What could cause my PC BSOD issue?

    Here is the screenshot of my BSOD using BlueScreenView.
    I hope someone could help me solve this problem. Thank you.

    Jeffrey

    Most of Jan 2 accidents so far is called critical process terminated.  (something is to kill a windows process).  Please run the Driver Verifier to discover what


    If you're overclocking (pushing components beyond their design) return you to default at least until the crash is resolved. If you don't know what it is that you're probably not overclocking.

    Driver Verifier (for full instructions, see our wiki here)
    Co-written by JMH3143

    .

  • Portege R830 - 10 L BSOD during shutdown, reboot, go to sleep and crashed

    My Portege started to plant stopped two days ago. I tried the following:
    -Check that McAfee was updated ok, I tried spybot and superantivirus, couldn't find any threat
    -Check disk ok
    -Follow-up of all Toshiba TEMPRO messages to update the drivers
    -Back to a point of recovery a week ago ok

    Everything works fine, I can use all my programs and Hibernate works well so that... the system wants to close

    Closing the window will not disappear
    The laptop heats up, the fan increases speed and finally the crash with blue screen
    The TI restarts and the cycle starts again

    The only way to stop this process is to keep the power switch for a few seconds

    I ran out of ideas how to solve this problem, suggestions are welcome

    Obviously something blocks regular stops.

    Last step to solve this problem is installation of recovery image. After dong that you will own preinstalled OS and everything will be OK again.

    By the way: until you stop your portable computer check what background processes are active and try to put an end to some of them manually, just to see if the stop is blocked by some of them. If you will be able to know what is the problem here, you can delete some applications or disable any service that may be responsible for this.

    Play a little with it.

  • BSOD on win server 2008 r2 std PAGE_FAULT_IN_NO_PAGED_AREA bug check code 0 x 50

    Hi all, I have this problem:

    My server gets a BSOD evrytime I try to log in, I can only log in safe mode.

    I've seen so many pages saying that this error is caused by a hardware failure, but I have not intall anything new on this, I guess an update caused the problem, I already ran the unsuccessful memory test, also had executed tools hard disk without finding anything to help solve the problem I have also updated the BIOS without success, I also uninstalled the latest updates but the problem persists. Can someone help me?

    • Server: DELL PowerEdge 310
    • OS: Windows 2008 R2
    • bug control chain: PAGE_FAULT_IN_NONPAGED_AREA
    • bug check code: 0 x 00000050
    • caused by the address: ntoskrnl.exe + 73c00

    A problem has been detected and Windows has been shut down to avoid damage
    on your computer.

    The problem seems to be caused by the following file: ntoskrnl.exe

    PAGE_FAULT_IN_NONPAGED_AREA

    If this is the first time you've seen this stop error screen,
    Restart your computer. If this screen appears again, follow
    the following steps:

    Check to make sure any new hardware or software is installed correctly.
    If this is a new installation, ask your hardware manufacturer or software
    the Windows updates, you might need.

    If problems continue, disable or remove any newly installed hardware
    or software. Disable the BIOS memory options such as implementing caching or shading.
    If you need to use safe mode to remove or disable components, restart
    your computer, press F8 to select Advanced Startup Options and then
    select Safe Mode.

    Technical information:

    STOP: 0 X 00000050 (0XFFFFF8A0103AF000, 0 X 0000000000000000, 0XFFFFF8000235FDFF,)
    0 x 0000000000000000)

    Ntoskrnl.exe - address 0xfffff800020c9c00 base at 0xfffff80002056000 DateStamp
    0x5684191c

    Thank you very much for your help!

    Oscar

    Hello

    Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

    http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

    See you soon.

  • BSOD: For the Bug Check Code: 0000009F is probably caused by: nt Driver

    I recently met a problem with BSOD when I was afk or configure my computer to Hibernate, whereby Soluto has picked up the information on:

    Bug check code: 0000009F, probably caused by: nt DRIVER_POWER_STATE_FAILURE driver bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.
    How should I proceed? I got the message about 3 times prior.

    RS

    It was linked to rimvndis6_AMD64.sys RIM Tunnel driver of Research In Motion Limited.  I would like to re - install the latest driver available.

    If you continue to plant I would remove Avast & replace it with MSE

    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/

  • BSOD problem error bug check code is 0xd1.

    Original title: BSOD issue.

    Hello

    I'm having consistent BSOD issues and have not recently installed new hardware other than a new keyboard. Might help you to check what the problem is please?

    minidmp files have been downloaded below

    https://onedrive.live.com/redir?RESID=3F8A3757B75723FF! 275 & authkey =! AJLWy31mgYj0vXE&ithint=folder%2c.rar

    Thank you for your help.

    Nick

    These accidents were caused by the cmudaxp.sys (description of the driver below.)  The bug check code is 0xd1.

    The debugging session: 20:46:57.022 Sun may 4, 2014 (UTC - 04:00)
    System Uptime: 0 days 1:17:13.657
    Loading the kernel symbols
    ...............................................................
    ................................................................
    .................................
    Loading user symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    * Bugcheck analysis *.
    *                                                                             *
    *******************************************************************************

    Use! analyze - v to obtain detailed debugging information.

    BugCheck D1, {fffff86c052b3410, 2, 0, fffff88005298e8b}

    Failed to load image \SystemRoot\system32\drivers\cmudaxp.sys, 0n2 error Win32
    WARNING: Unable to verify timestamp for cmudaxp.sys
    ERROR: Module load completed but symbols can be loaded for cmudaxp.sys
    Probably caused by: cmudaxp.sys (cmudaxp + 1c0e8b)

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 the kernel debugger is available, get a stack backtrace.
    Arguments:
    Arg1: fffff86c052b3410, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88005298e8b, address memory

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

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff802b1bc6168
    Unable to get nt! MmPoolCodeStart
    Unable to get nt! MmPoolCodeEnd
    fffff86c052b3410

    CURRENT_IRQL: 2

    FAULTING_IP:
    cmudaxp + 1c0e8b
    fffff880'05298e8b ff9080000000 call qword ptr [rax + 80 h]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0XD1

    Nom_processus: chrome.exe

    TRAP_FRAME: fffff802b0d7e700-(.trap 0xfffff802b0d7e700)
    NOTE: The frame trap does contain not all registers.
    Some registry values can be set to zero or incorrect.
    Rax = fffff86c052b3390 rbx = 0000000000000000 rcx = fffffa8003c103e0
    RDX = fffffa8003c43130 rsi = 0000000000000000 rdi = 0000000000000000
    RIP = fffff88005298e8b rsp = fffff802b0d7e890 rbp = 0000000000000080
    R8 = 0000000000000040 r9 = fffffa8003c5eaa0 r10 = fffff880052b59f0
    R11 = fffff802b0d7e948 r12 = 0000000000000000 r13 = 0000000000000000
    R14 = 0000000000000000 r15 = 0000000000000000
    iopl = 0 nv up ei pl zr po nc
    cmudaxp + 0x1c0e8b:
    fffff880 "05298e8b ff9080000000 call qword ptr [rax + 80 h] ds:3500:fffff86c" 052 b 3410 =?
    Reset the default scope

    LAST_CONTROL_TRANSFER: from fffff802b18ea369 to fffff802b18eb040

    STACK_TEXT:
    fffff802 'b0d7e5b8 fffff802' b18ea369: fffff86c' 00000000 0000000 a ' 052b 3410 00000000'00000002 00000000'00000000: nt! KeBugCheckEx
    fffff802 'b0d7e5c0 fffff802' b18e8be0: 00000000 00000000' fffffa80 '03c103e0 00000000' fffff802 00000000' b0d7e700: nt! KiBugCheckDispatch + 0 x 69
    fffff802 'b0d7e700 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiPageFault + 0 x 260

    STACK_COMMAND: .bugcheck; Ko

    FOLLOWUP_IP:
    cmudaxp + 1c0e8b
    fffff880'05298e8b ff9080000000 call qword ptr [rax + 80 h]

    SYMBOL_NAME: cmudaxp + 1c0e8b

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: cmudaxp

    Nom_image: cmudaxp.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 51669462

    FAILURE_BUCKET_ID: X64_0xD1_cmudaxp + 1c0e8b

    BUCKET_ID: X64_0xD1_cmudaxp + 1c0e8b

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

    0: kd > lmvm cmudaxp
    start end module name
    05406000 fffff880 '050 d 8000 fffff880' cmudaxp T (no symbol)
    Loaded symbol image file: cmudaxp.sys
    Image path: \SystemRoot\system32\drivers\cmudaxp.sys
    Image name: cmudaxp.sys
    Timestamp: Sat Apr 11 06:45:54 2013 (51669462)
    CheckSum: 002A485F
    ImageSize: 0032E000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

    Driver Description: C-Media Audio Interface Driver (WDM) C-Media
     Interface driver Audio ASUS Xonar DG
    HTO CLARO Audio Interface Driver

    Driver update site: http://www.cmedia.com.tw/EN/DownloadCenter_Detail.aspx?pserno=0&dtype=ALL
    http://support.ASUS.com/download/download.aspx
    http://www.htomega.com/downloads.html

    Uninstall and reinstall after a repair KB2862330, noted below.

    ================================================================================================
    Please delete Hotspot shield.
    ERROR: Module load completed but symbols can be loaded for hssdrv6.sys
    WARNING: Unable to verify timestamp for taphss6.sys
    ERROR: Module load completed but symbols can be loaded for taphss6.sys

    Driver Description: Hotspot shield
    Cause possible BSOD seen in mid-2012

    Driver update website: http://hotspotshield.com/
    ================================================================================================
    Please remove immediately update utility. This software is problematic and may corrupt your system

    Unloaded modules:
    fffff880 ' 17747000 fffff880' 1774f000 TuneUpUtilities
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    ImageSize: 00008000
    ================================================================

    Check updates systems installed to KB2862330. Is it installed?

    This security update was initially released on 8 October 2013. The security update was re-released on January 14, 2014, for computers that are running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. The reissue resolves an issue in which one of the pilots of the stack kernel USB 2.0 is not updated in some specific computer configurations.

    http://support.Microsoft.com/kb/2862330/en-us

    Note: compare the versions of your file in the link above. I suspect you've found BCCode 0xD1 due to improperly installed or missing update.

  • 0x1000007e bug check code

    How can I fix these 2, played games and cela happened.

    Mini091414 - 02.dmp 14/09/2014-19:24:23 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff "c0000005 fffffa60 '1111326e fffffa60' 01 b 70828 fffffa60 ' 01 b 70200 AtihdLH6.sys AtihdLH6.sys + x 64 AtihdLH6.sys + 526e C:\Windows\Minidump\Mini091414-02.dmp 6002 b210 15 3 274 448 14/09/2014 19:27:15

    Mini091414 - 01.dmp 14/09/2014-18:44:20 SYSTEM_SERVICE_EXCEPTION 0x0000003b fffff960 '000800 b 0 fffffa60' c0000005 00000000' 0d8bde10 00000000 00000000' win32k.sys win32k.sys + 500 b 0 x 64 + 57150 6002 C:\Windows\Minidump\Mini091414-01.dmp ntoskrnl.exe 15 3 274 448 14/09/2014-18:46:52

    I can add more files later and more information if necessary

    https://onedrive.live.com/redir?RESID=36D6A79D11E530C6! 183 & authkey =! ANTs6HK8p55VXPQ & ithint = dump files record %2 c it

    Hello

    The Bug_Check were 3 b and 7th.

    Bugcheck 3B {c0000005, fffff960000800b0, fffffa600d8bde10, 0}

    Probably caused by: win32k.sys (win32k! PFEOBJ::vFreepfdg + e8)<-- a="" windows="">
    which means something else he has led astray.

    Bugcheck 1000007E, {ffffffffc0000005, fffffa601111326e, fffffa6001b70828, fffffa6001b70200}

    Probably caused by: AtihdLH6.sys ( AtihdLH6 + 526e)<-- amd="" high="" definition="" audio="" function="">

    AtihdLH6.sys dated 07/05/2013 AMD High Definition Audio function Driver.

    fffffa60'1110e000 fffffa60'11129000 AtihdLH6 T (no symbol)
    Loaded symbol image file: AtihdLH6.sys
    Image path: \SystemRoot\system32\drivers\AtihdLH6.sys
    Image name: AtihdLH6.sys
    Timestamp: Fri Jul 05 11:10:34 2013 (51D70C1A)
       
    1. check with Acer Support, their drivers and documentation online and ask in their forums
    on known problems. Updated BIOS, drivers of low level chipset and on-board major
    and separate device drivers. Especially all the ATI/AMD drivers - check also with the support of the ATI,

    their documentation online and drivers and ask questions in the forums about known problems. (See
    driver update methods in the next post.)

    BiosVersion = R01 - B3
    BiosReleaseDate = 2008-10-31
    SystemManufacturer = Acer
    SystemProductName = Aspire M3201
    BaseBoardManufacturer = Acer
    BaseBoardProduct = RS780HVF

    Acer - USA - Service and Support - drivers
    http://us.Acer.com/AC/en/us/content/support

    Acer - Community/Forums
    http://community.Acer.com/

    Acer - worldwide
    http://www.Acer.com/worldwide/

    AMD/ATI - assistance and pilot - search
    http://support.AMD.com/us/psearch/pages/psearch.aspx?type=2.4.2&product=2.4.2.3.9&ContentType=GPU+download+detail&OSType=Windows+8+Preview+-+32-bit+Edition&keywords=&items=20

    Download the Catalyst Drivers here
    http://game.AMD.com/us-en/drivers_catalyst.aspx

    ATI - Forums
    http://forums.AMD.com/game/categories.cfm?CATID=260&forumid=11

    ATI - Support and drivers
    http://support.AMD.com/us/pages/AMDSupportHub.aspx

    2 use ALL methods in the troubleshooters below and in the next message.

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

    Pick up the pieces after a computer breakdown - see what to do if Windows won't start correctly
    http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

    Check this thread for more information using BlueScreenView, MyEventViewer and other methods
    to troubleshoot the BlueScreens - top 3 responses (+ 1 other).

    http://answers.Microsoft.com/en-us/Windows/Forum/windows_vista-system/blue-screen-plug-and-play-detected-an-error-most/3deab2fa-4000-4136-8c78-a3d22b1db009

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

    Also this, so you can see the probable bluescreens.

    Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
    (also Windows 7)
    http://www.winvistatips.com/disable-automatic-restart-T84.html

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

    The system has RAID? If so, it's also very suspicious.

    This error is usually a driver problem and display adapter (video) driver is the most suspicious if
    It could be others. Antivirus/antispyware/security programs, major software and hardware (heat)
    questions can also cause the error. When you get to the section of the driver to use the Troubleshoot utility my
    generic methods in the next message and then return to the if necessary troubleshooting tool.

    Have you recently added hardware or drivers updated? Don't forget to look in Control Panel - Windows
    Updates to see if all drivers have been updated it. Other donor opportunities include the antivirus/anti-
    spyware/security programs.

    When you get to the pilot and sections of the memory of the troubleshooter check the following message to update drivers and test the memory and then return to the troubleshooter if necessary.

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

    BCCode: 7F 0x0000007E which is also 0x1000007E

    Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED<-- read="" this="">
    http://msdn.Microsoft.com/en-us/library/ff559239(v=vs.85).aspx

    BCCode: 7F 0x00000007E who is also a 0x1000007E<-- read="" this="">
    * 1141.html? order = votes http://www.faultwire.com/solutions-fatal_error/System-thread-exception-not-HANDLED-0x0000007E-

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

    BCCode: 3B 0x0000003b

    Try to remove and replace the cards memory and cables (both ends where possible)-in fact
    delete and replace - not just in the warm (on a PC) and clean the dust bunnies and vents. On
    a laptop on everything that can be done is to reinstall the memory and clean the vents. (Of course delete
    ALL power before opening the case).

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION<-- read="" this="">
    http://msdn.Microsoft.com/en-us/library/ff558949 (v = VS. 85) .aspx

    BCCode: 3B 0x0000003b<-- read="" this="">
    http://www.faultwire.com/solutions-fatal_error/system-service-exception-0x0000003B-* 1074.html

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

    Look in the Event Viewer to see if something is reported on those.
    http://www.computerperformance.co.UK/Vista/vista_event_viewer.htm

    MyEventViewer - free - a simple alternative in the standard event viewer
    Windows. TIP - Options - Advanced filter allows you to see a time rather
    of the entire file.

    http://www.NirSoft.NET/utils/my_event_viewer.html

    Here are a few ways to possibly fix the blue screen issue. If you could give the blue screen
    info that would help. Such as ITC and 4 others entered at the bottom left. And all others
    error information such as codes of STOP 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 the.
    death ' crashes and displays information about all accidents of a table.
    Free
    http://www.NirSoft.NET/utils/blue_screen_view.html

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

    You can do mode if necessary safe or the Vista DVD command prompt or
    Options recovery if your system is 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 into the search-> find COMMAND to top box 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. (Does not work
    tell all possible driver issues).

    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, part 3
    keyboard and mouse, 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
    quit 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 Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

  • Computer re-started from a bug check?

    I was in another room and I heard my PC Boot back to Windows.  When I infrom him, I saw a Message saying that my computer Re-started... etc.

    I went to the event viewer... and that's what he interprets: "the computer has rebooted from a control bug.  Bug check was: 0x0000009f (0 x 00000003), (and several other codes that not many men know what they meant...); An image has been saved in c:\windows\MemoryDump.DMP. Report id: 051712-22604-01 "

    Why Microsoft can't write these messages that normal people can understand what they mean?  I went to c:\Windows\MemoryDump.DMP...the report was there... but yet another obstacle to Microsoft... when I try to open it I get ACCESS DEINIED.  What good is it to clear a report that may... and I say may... tell me what going on if I can't open it?

    Any input would be appreciated; I wish you to know what caused my re-Boot and what should I do to avoid the cause in the future.

    I suggest go ahead and install the driver.

    Create a restore point from the system in advance.

    Also, if you have not already, create a system repair disc, so you have the ability to perform a restore of the system outside of Windows:

    http://Windows.Microsoft.com/en-us/Windows7/create-a-system-repair-disc

  • Some keys on my MacPro keyboard have suddenly changed character. More precisely: move 2 product "instead of @;" Shift 3 product £ instead of a hashtag. and two RBI Maj @. I rebooted and checked the settings keyboard without result.

    Some keys on my MacPro keyboard have suddenly changed character. More precisely: move 2 product "instead of @;" Shift 3 product £ instead of a hashtag. and two RBI Maj @. I rebooted and checked the settings keyboard without result. It worked fine yesterday and has not been moved since then. What should do?

    Check the sources of the system/preferences/keyboard again.  You have active the British PC keyboard.  Remove it and make sure that you have only on the list.

  • BSOD error - Win 7 - Stop error/Bug Check Information

    I've been trying my brain for days trying to figure this one. Some of this information might be useless, but I write it just in case where. For someone who can help me, or is ready, thank you in advance.

    Computer information:
    I just bought a lenevo w520. for my wife and me for Christmas.
    Features: processor i7 2820QM 2.3 GHZ, 8 GB Ram, 500 GB HDD, Quadro of Nividia graphics card, ask for more information.

    It's a costly computer, so I really prefer that it does not break, or that I don't have to spend even more money on it. But I'm sure you've all heard this before. (:

    In any case, for those who want to help, I got this error checking information and Event Viewer:

    + System

    -Supplier

    [Name]  Microsoft-Windows-WER-SystemErrorReporting
    [Guid]  {ABCE23E7-DE45-4366-8631-84FA6C525952}
    [EventSourceName]  Error checking
     
    -EventID 1001

    [Qualification] 16384
     
    Version 0
     
    Level 2
     
    Task 0
     
    Opcode 0
     
    Keywords 0 x 80000000000000
     
    -TimeCreated

    [SystemTime] 2012-12 - 09T 21: 06:53.000000000Z
     
    6307 EventRecordID
     
    Correlation
     
    -Execution

    [ProcessID] 0
    [ThreadID] 0
     
    Channel system
     
    Master computer PC
     
    Security

    -EventData

    param1 0x000000f4 (0xfffffa8006efd060, 0xfffffa8006efd340, 0 x 0000000000000003, 0xfffff80003be1540)
    param2 C:\Windows\MEMORY. DMP
    param3 120912-29608-01

    What I did:
    I checked BlueScreen Viewer is mentions the ntkrnl.exe, but side form the param data he says nothing about how to fix this.
    I tried to restore on the eve of the day the BSODS happened. Nothing has changed.
    A ran Malwarebytes, he cought something and got rid of him. Nothing has changed.
    I tried the Windows Update. Nothing has changed.

    Weird part:
    This BSOD occurs only when the computer is off, rebooted, disconnected. That's all so far. I don't want to ruin anything!

    Thank you for your time in advance and as always, a quick response would be much appreciated!

    sbh0129

    These were related to windowss.exe.  CAN BE MALICIOUS

    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

    If she comes clean back please update Service Pack 1

    Run (SURT) system update readiness tool and then update to Service Pack 1

    32 bit
    http://www.Microsoft.com/download/en/details.aspx?displaylang=en&ID=3132

    64 bit
    http://www.Microsoft.com/download/en/details.aspx?displaylang=en&ID=20858

    Now updated for Service Pack 1

    http://Windows.Microsoft.com/installwindows7sp1

    Learn how to install Windows 7 Service Pack 1 (SP1) http://windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1

    Additional resources:

    http://Windows.Microsoft.com/en-us/Windows7/uninstall-SP1
    http://Windows.Microsoft.com/troubleshootwindows7sp1

  • Get a BSOD on shutdown fairly regularly - need help troubleshooting - even a cardboard open :(

    Hello!

    I hope that I might be able to get troubleshooting tips the BSOD I seem to now on a regular basis.  I guess it's maybe a USB driver problem, but I don't know how to understand this.  Here are the details I received after the most recent BSOD reboot:

    Signature of the problem:
    Problem event name: BlueScreen
    OS version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033

    More information about the problem:
    BCCode: 9f
    BCP1: 0000000000000003
    BCP2: FFFFFA8004F0F3C0
    BCP3: FFFFF800035183D8
    BCP4: FFFFFA8005322850
    OS version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files helping to describe the problem:
    C:\Windows\Minidump\093015-5881-01.dmp
    C:\Users\Alan\AppData\Local\Temp\WER-8923-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

    I am pleased to provide you with any information that might help identify the culprit and any support are really appreciated...

    These accidents were related to the corruption of memory (probably caused by a driver).

    Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

    If you are overclocking anything reset by default before running these tests.
    In other words STOP! If you don't know what it means that you're probably not  


    1-Driver Verifier (for full instructions, see our wiki here)

    2-Memtest. (You can learn more about running memtest here)
  • BSOD error 1001 0x0000007e error checking

    I am Windows 7 64 bit and get the BSOD market, suspecting that it is linked to the video because it is during the game that often happens. I made sure my drivers have been updated and it still occurs. Below is an excerpt from the log event message with a link to the Memory.dmp file.

    Here is the link to the Memory.dmp file (report Id: 081816-15022-01). Any help would be appreciated!  =)

    https://www.dropbox.com/s/iro8p8kuzh5g3v5/memory.zip?DL=0

    -Alan

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

    Excerpt from Event Viewer:

    -System

    -Supplier

    [Name]  Microsoft-Windows-WER-SystemErrorReporting
    [Guid]  {ABCE23E7-DE45-4366-8631-84FA6C525952}
    [EventSourceName]  Error checking
     
    -EventID 1001

    [Qualification] 16384
     
       
    EventRecordID 273881
     
      
    param1 0x0000007e (0xffffffffc0000005, 0xfffff800039d8b88, 0xfffff88003e79168, 0xfffff88003e789c0)
    param2 C:\Windows\MEMORY. DMP
    param3 15022-081816-01

    You are welcome! Let us know if you encounter any problems more.

  • Get BSOD under control of bug, I found the issue was csrss.exe. I uninstalled the video drivers intel, but the machine is still crushing.

    Hello

    I Keep getting this blue screen under bug death check I found that the issue was csrss.exe. I uninstalled the video drivers intel, but the machine is still crushing.

    https://onedrive.live.com/redir?RESID=BE2C45CEFD325C95! 162 & authkey =! AKZFqC6arezz-QI & ithint = the file % 2czip

    I join the crush dump files.

    Kindly help.

    First, you must upgrade to the Service Pack-1

    Service pack 1 update.

    http://Windows.Microsoft.com/installwindows7sp1

    Learn how to install Windows 7 Service Pack 1 (SP1)

    http://Windows.Microsoft.com/en-us/Windows7/learn-how-to-install-Windows-7-Service-Pack-1-SP1

    Additional resources:

    http://Windows.Microsoft.com/en-us/Windows7/uninstall-SP1
    http://Windows.Microsoft.com/troubleshootwindows7sp1

    After that, if you're still crashing

    These accidents were related to the corruption of memory (probably caused by Kaspersky).

    Run these two tests to check your memory and find which driver is causing the problem.  Launch auditor.  You don't need to run memtest again unless the auditor is not the cause, or you want to.

    If you are overclocking anything reset by default before running these tests.
    In other words STOP! If you don't know what it means that you're probably not  


    1-Driver Verifier (for full instructions, see our wiki here)

    2-Memtest. (You can learn more about running memtest here)
  • BSOD on shutdown

    I get this BSOD a few fair times now when I try and shut down the computer, just after it is just about complete stop this BSOD appears and the Pc reboots and I must continue to press stop until they stop the BSOD.

    IV ' e attached here the dump files

    Thank you very much

    I think the driver WHQL for VL800/801 and 805/806 USB 3.0 version 4.90, would be the latest driver. Create a restore point before proceeding, just in case, you have problems, you can return your system to its previous state safely

    Driver WHQL for VL800/801 and 805/806 USB 3.0 version 4.90 has

    http://www.via-Labs.com/archive/doc/VIA_XHCI_Driver_V4.90A_AP.zip

    Keep me updated on the State of the question

Maybe you are looking for