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

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 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 <

• Portege R830 had dead blue when the screen connects to wifi or shared internet

  It seemed began as soon as the automatic update from Microsoft on Qualcomm, Atheros, every time when connect to any WIFi, share internet, my portege R830 shows blue screen and the following error message:
  unhandled system_thread_exception (athwb.sys)

  I found that I am not the isolated on the Web site. I tried to remove and stop updates. However, once I connect to the internet, the blue screen comes back.

  Is the problem because of the network adapter? The model is Qualcomm Atheros AR9002WB
  Can solve the problem if I download the new driver of Qualcomm-Atheros site? Or if I replace a new adapter?

  The athwb.sys file belongs to the Atheros wireless driver. Usually placed in C:\Windows\System32\drivers\athwb.sys
  It seems that in your case this file causing the BSOD.

  I found a very interesting detail about this problem and why it seems.

  A user wrote:
  {quote} The issue is due to a database hosted on Linux kernel mapped NAS drives and if the Client for NFS is installed on the windows machine. For some reason, this configuration does not work. If you mount your shares and NFS is installed it tries to use the NFS client and fails miserably. Trick is to disassemble all the shares of logging in Safe Mode and then rebooted and uninstall the NFS client and then mount your shares. {quote}

• Portege R830 - use of fingerprinting as part of Windows 8

  I have big problems with two drivers Toshiba on my Portege R830 computer in Win 8 Pro 64 bit upgrade.

  I did a clean update on a reformatted hard drive, then went to install display drivers and that totally crashed my machine out.

  When I put in my IDs of the machine would do a reboot of the force.
  Finally, I am in safe mode (with SHIFT-restart the login screen) and was able to fix it and remove the driver.

  Then I installed the utility of fingerprinting, this week still downloaded from Toshiba for my machine.
  He even marked as "new".
  That actually worked, in a way, but it caused my login icons user on-screen connection prior to appear as duplicates.

  Took me forever to understand it is the utility of fingerprinting and when I removed the user icons are returned to normal.

  So now the fingerprint reader is useless for me.
  In the hope of a solution soon.

  > So now the fingerprint reader is useless for me.
  > In the hope of a solution soon

  Have a look here:
  * Windows 8 Upgrade - Notes and Restrictions *.
  http://APS2.toshiba-tro.de/KB0/TSB2A03EL0000R02.htm

  Software reader Toshiba fingerprint + _ + _

  _Issue description: _
  Toshiba Fingerprint Software is not supported under Windows 8. Fingerprint records will be lost during the upgrade process.

  * Note: *.
  + Remember your Windows password. You will need to enter after the upgrade. If you have a fingerprint reader, fingerprint records will be lost during the upgrade process, which is connected to the Windows 8 will not be via a fingerprint authentication more. +

• Portege R830/PT321E: update the Bios stops with "year error occurred while...» »

  Portege R830/PT321E: update Bios end with ' year error occurred while preparing the environment of update...» »

  Following message appears first

  BIOS version: Worm. current 3.40-> update version 3.70
  THIS Version: worm. current 1.30-> update version 1.50
  BIOS and THIS should be updated

  During BIOS update seems following message:

  + An error occurred during the preparation of the updated environment. You have not given permission to run the update. +

  My settings:
  -BitLocker is turned off.
  -No connection to a docking station
  -Windows 7 is installed
  -Boot mode is enabled? I guess that means:
  "Close all open programs, shut down windows and then turns off your computer."

  Any idea what is the problem?

  Post edited by: ML

  Hi ML

  Stupid question maybe now but why do you want to update the BIOS on this, I think, fairly new laptop model?
  Have you noticed a few issues or hardware issues?

• Portege R830 - problems of 3G connection after installing Win 7 32 bit

  Hello

  I went down a Portege R830 Windows 7 64 bit for Windows 7 32 bit with drivers of Toshiba. I put a SIM from my provider.
  In the windows Network Manager, 7 and in the Toshiba Wireless Manager I can see the right provider and HSPA network but when I start the connection, it does not (I don't have a PIN code).

  It is failed with Windows 7 Network Manager and Manager Toshiba wireless (I don't have this problem with the Portege R700 windows 7 32bits)

  But I found a small solution (but I think that's not enough):
  I have created a dial-up connection, with a number * 99 #,.
  I started the connection, it does not happen, but after that, when I raise my first connection is good.

  I don't know why, it's as if the modem is in sleep and the dial-up connection wake-up the modem, because after all is good (win7 Network Manager, Manager wireless Toshiba) so if I reboot the Portege.

  I want to avoid the dial-up connection on my r700 portege with 32-bit windows 7

  Thanks for your help and sorry for my English.
  support for the toshiba told me to reinstall windows 7 64 bit to solve the problem :)

  Hello

  Are you sure that you have correctly configured the connection?
  Here is a nice FAQ that explains step by step how to connect 3G using the Toshiba Wireless Manager:

  + How to configure and set up a 3G connection via the preinstalled Toshiba Wireless Manager +.
  http://APS2.toshiba-tro.de/KB0/FAQ1A037W0000R01.htm

  and here you can find instruction how to create dial upward of connection using own configuration of Windows.

  + How to create a Dial-Up connection with 3 +.
  http://APS2.toshiba-tro.de/KB0/HTD9802OF0000R01.htm

  Recommend check them both!

• Portege R830 - updates BIOS and USB 3

  Hi all

  I have a Toshiba Portege R830, business management Windows 7 (SP1) 32-bit (for work).
  I also start Linux Mint 14 64-bit, that I installed it on a portable USB HDD (non-professional).

  I recently bought a 3 USB HARD drive, but when I connect it to the USB 3 port on my R830, it gives me only USB 2 speeds (25 MB/s).

  I checked with some diagnostic utilities (usbdeview, etc.), who say that the drive is connected in USB 2.1 mode.

  The drive reports itself as being 3 USB, cable is USB 3 (SuperSpeed) and the port that I use on the R830 is 3.

  I feel the same way, if I boot on windows or linux.

  I've updated all the drivers on the two operating systems, does not.

  then I tried to update the BIOS, but I get the following error:
  "An error occurred during the preparation of the updated environment.
  You have not given the permission to execute the update".

  For the record, it's the BIOS I'm leaving, & to.
  BIOS version: Current Ver.2.80--> updated Ver.4.10
  THIS Version: Current Ver.1.10--> update Ver.1.60

  Does anyone know why I wouldn't get USB 3 speed (which, for my drive, are expected to be around 40-50 MB/s), or why all the diagnostics say USB 2?

  Does anyone know how to overcome the problem of updating the BIOS?
  (I tried in safe mode, disable AV, disabling NX)

  See you soon

  This USB driver is installed?

  Please try to install it and check again speed USB.

• Portege R830 blue screen

  Hello

  I have problem in my business with one of notebooks and the problem is that when I connect dynadock on my portege R830 my portege screen flashes a few times and then I get a blue screen. The portege and dynadock are new and the portege has a preinstalled Windows 7 pro. I already reinstall the drivers for the display drivers and dynadock and always some problem.
  you have an idea?

  BR, Toma!

  What is a BSOD or just a blue screen?

  What color is the background wallpaper on your pc the value? even in blue white?

• Portege R830 - Download Cant PT321E value added package driver.

  Hello!
  I can't download the toshiba.eu/support/drivers/laptops/ driver for

  Toshiba Portege R830 - PT321E
  Windows 7 64 bit
  Location - Latvia

  Download keeps failing sometimes to 10% to 50% complete.

  Sometimes the page is inaccessible. Tried to download the driver of different networks.

  Thank you.

  Today, I tried again to download the driver package. Downloaded without any problem.
  Wasn't the best place where to post about him, but I couldn't find it on the page where I can report problem Web page technique.

• Portege R830 - functional keys not working after installing Windows 7

  Hello
  I have Toshiba portege R830.
  I install new windows 7, no recovery - new windows.
  Now, I have a problem because my function keys don't ' t work.
  I can't turn on y wifi with fn + F8.
  I was looking for drivers, but I don't ' get there for my toshiba.

  Originally posted by Tomasz
  

  Hello
  I have Toshiba portege R830.
  I install new windows 7, no recovery - new windows.
  Now, I have a problem because my function keys don't ' t work.
  I can't turn on y wifi with fn + F8.
  I was looking for drivers, but I don't ' get there for my toshiba.

  Have you installed the VAP (value added package)

  That should restore the functionality of your

• Question of compatibility of Toshiba Portege R830 - 1 8 RAM

  Hi all

  I know someone who owns a portege R830 - 1 8. He asked me, if my laptop RAM is compatible with your laptop.

  He did inside the laptop 2 gb 1Rx8 PC3 - 10600 S - 09 - 11 - B2.

  My RAM is 4 GB 2Rx8 PC3 - 12800S - 11 - 12 - F2.1600.

  Can he use my RAM?

  THX and greetz

  Both are PC3, but not sure about the speed difference.
  It can work, give it a try.

• Portege R830 - Win 8.1 Value Added Package (Flash cards)

  Hello.

  First of all I would like to say that I used my Toshiba Portege R830 with all the operating systems since Windows 7 and I have never installed fresh OS.
  That said, I could not use Intel WiDi on Win10 and had to return to Win8 (DVD which I happily bought as well as the upgrade).

  I installed all the software Toshiba using Upgrade Wizard and for the first time since the 2011', there was no Flash cards available (drop-down menu shown with use of the Fn keys). I used to like 2.5 years on Win 8/8.1 and now his party and is not available to the installation...

  WTF? After a week, I discovered that cards Flash is not present in VAP 1.6 (only in 1.5.X.X or earlier).
  Unfortunately I can't install only stand-alone Flash cards (or can I?).

  And here my question: if I install VAP 1.5 (with Flash cards), can I (ANYHOW) strengthen certain elements (such as system driver) without uninstalling the previous version of VAP?

  From my experience when I run VAP 1.6 installer first thing it does is an uninstall complete previous versions.

  Please help me! I can't imagine who thought that removing the 1.6 flash cards would be a good idea...

  Driver Toshiba UE page provides the Key Utility for Windows 8 Upgrade feature Toshiba v1.00.6626.03.

  So, if you have installed Value Added Package 1.6.0130. You must also install the key function Toshiba utility

  

• Portege R830 - need details template

  Hi - I have a Portege R830 and cannot identify the exact model - I have the serial number 4C047625H, but that's all

  The sticker on the back was covered by a sticker SUB and I can't get the model number!

  Help please

  Run Toshiba Service Station to display the model number.
  Another tool you can use is Crystal DMI (google it).

• Portege R830-10v / i7 / change internal SSD 225 GB

  Hello

  I need to change my flash drive SSD internal 225 GB for a 512 GB SSD!

  What should I do to the hardware and software level?
  Can I take any SSD?

  Thanks for the help?

  Best regards, Florence

  The HDD or SSD drive update requires no special modifications in the software or hardware.
  You need a compatible player SATA SSD 2.5.

  Here is a nice and very useful document how to upgrade / replace the Portege R830 & Satellite R830 series SSD or HARD disk drive.

  http://APS2.toshiba-tro.de/KB0/CRU18037E0000R01.htm

  Of course, after this upgrade, you'll need to install the system new the best choice would be its use or recovery disk and recover the laptop to factory settings.