Satellite L775 goes into BSOD after upgrade to Win 8.1

hello
First, I have win7 on this device, then I purchased a mictosoft windows 8 pro for it.
When I upgraded it went fine for a few months and then it started to crash on its own.
I tried so much to rebuild the PC using Toshiba's software to no avail.
In the end I deleted all partitions and rebuilt it with win8.
As I upgrade to win8.1 it only gets to first sceen and then back again, even through there's nothing installed.
When I re-did it three times and in the end I gave up, and now just want it at least to work with win8
all Toshiba's software ask for .net3.5, whereas what I have is 4.5.
I went to several websites to find answer and it tells of a method to re-enable feature, but when I do it, it can't find the necessar files.
Now I would like to restart from scratch ... where can I download tosh's original software as a pack?
Or find a solution to this BSD problem
thanks.

Can you please post full notebook model number? I just want to check Toshiba download page and be sure your notebook is supported for Win8 or Win8.1.
By the way: have you created recovery media for original Win7 that you got with your machine?
I don't know what could be the reason for BSOD but I presume it must be software related issue. if your notebook is not supported for Win8.1 who knows what have you installed and how it works.
Maybe the best option for you should be data back-up and clean OS installation as you have done it in the past. Start with Win7 and upgrade to Win8.
If your notebook is supported for Win8 you can make clean Win8 installation.
Post please the model number and we can check this.
As far s I know some older Win7 machines are supported for Win8 update only.

Similar Messages

Satellite Pro A10: No sound after upgrade to Win XP Home SP2

Hi,
Just used the recovery discs on my Sat Pro A10, no problem with sound, and then upgraded XP Home to SP2, no sound.
From what I have read elsewhere, this is a problem, and there doesn't appear to be an answer. I have spent hours searching for updated drivers to no avail.
I have also contacted Toshiba support, after much huffing, and puffing they pointed me to the following driver, 5.12.01.3542, which is the same as the one I already installed, and does not work.
Surely there must be something out there that works.
Ant.

Install the newest available sound driver fro this sound chip and perform the all the Windows updates available on the Microsoft page!
Update simply the whole OS!!!
http://www.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us
Note; possibly you have to reboot the notebook and have to connect to this site several times to get all the available patches.

Satellite P10 automatically goes into Standby after 15 minutes

My Satellite P10 automatically goes into Standby after 15 minutes. This is a setting that is controlled by the Toshiba Power Management settings, or the Toshiba Console.
When I change the settings there the system still goes into Standby after 15 minutes. When I go to Control Panel/Performance and Maintenance/Power Options, it tells me to go to the Toshiba Power Management to change the settings, but I can still see the settings in grey stating 15 minutes standby time.
But in the Toshiba Power Management I can't seem to be able to ajust Standby settings so that they actually work. There must be a trick to it..
Can anyone help me figure it out?
Thanks a lot,
Lerak

Thank you for your replies. As I now understand it there are 3 power management utilities fighting for control of the power management settings:
1) The windows OS power options("Power Option Properties, from the control panel/performance and maintenance/power options);
this utility is overridden by:
2) Toshiba Power management;
and
3) the "power save modes", activated by pressing the Function key and the F2 key, which in turn can override the Toshiba Power management.
If this last Function/F2 combination is used to change the power save modes, the windows OS power settings (which are shown in grey and cannot be changed because this is overridden by the Toshiba Power management) DO actually change.
Hold down the Function key (Fn) and press F2, holding down the Fn key. Each time you then press the F2 key again you scroll down the different "Power Schemes". The last mode is called: Toshiba Power Management. One would think that by choosing this setting the Toshiba Power management utility would effectively take over control of the power settings. Unfortunately this does not seem to be the case..
At least using this last option provides a workaround. Some of the "Power Schemes" disable the standby options.

System recovery fails after upgrade to Win 8.1 on Satellite L75D-A7283

My elderly uncle forgot the password to his Win 8 user account sometime after upgrading to Win 8.1. He was the administrator, we haven't been able to get Microsoft to reset the account, so I thought to roll back the computer to its factory installation of Win 8.
However, when I try to do that, I get as far as the Reset your PC screen and find that the only target OS is Win 8.1, not the original Win 8. Ok, I accept that. But after choosing to restore Win 8.1, it says "Unable to reset your PC. A required drive partition is missing."
I have examined the disk by removing it and attaching it to another computer and find that both the original Win 8 recovery partition and the new Win 8.1 GPT recovery partition are both there. They just don't seem to be accessible.
It seems that the Win 8.1 upgrade has made the original factory recovery partition inaccessible, which is not particularly helpful. We have no recovery disks to work from, so I think my only recourse is to try to get a Win 8 factory recovery disk from Toshiba, but I wondered if anyone else has a suggestion? Thanks.

Satellite L75D-A7283
It's my understanding the upgrade does not modify any other partitions while upgrading Windows itself. Seems likely something else is wrong.
If you did not create recovery media before and cannot do so now, then obtain it from Toshiba. Scroll down to Get Recovery Media here.
All the information in the section Recovering the Internal Storage Drive, which begins on p. 53 of the User's Guide, should still be applicable.
Satellite/Satellite Pro L40/L50/L70/S40/S50/S70 - A Series User’s Guide
-Jerry

After upgrading from Win 8 to 8.1 my DVD RAM GT80N SATA Drive is no longer working

After upgrading from Win 8 to 8.1 my DVD RAM GT80N SATA Drive is no longer recognizing discs. When I first put a disc in the drive runs for a bit and then stops. I've tried updating the driver but it says it has the most current driver. Under manage, it does not show any error codes and it says it is working correctly. I've looked at the regedit and it does not have any of upper and lower filters. I've tried disabling, rebooting, and reenabling. What am I missing? Another issue I've had since upgrading is that my network adapter needs reset several times a day in order to remain connected to wifi.

Hey hvbnfrgvn,
Thank you for the information on your HP Pavilion g7-2270us Notebook PC.
I suggest following the steps in this document for Drive Cannot Read Discs (Windows 8).
If your CD/DVD Drive Is Not Detected (Windows 8), follow the steps in this document.
I hope this information helps, please keep me posted on how it goes.
Best of luck and have a great day!
I worked on behalf of HP.

After upgrade to Win 8, the key's has changed

After upgrade to Win 8, the key's has changed, for example, when i am trying type @ but the key has changed as ". so please help me to rectify the problem.

Hi,
What was the keyboard language BEFORE and what it is NOW ? Did you use SAME KB language for both Windows 7 and Windows 8 ? When click to the KB (bottom right corner) what do you see ? This is mine:
Please use instructions from the following link to fix:
http://windows.microsoft.com/en-AU/windows-vista/Change-your-keyboard-layout
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

HP Compaq CQ60-215dx: sound will not switch to headphones after upgrade to Win Vista 64bit Ultimate

HP Compaq CQ60-215dx: sound will not switch to headphones after upgrade to Win Vista 64bit Ultimate
what can I do?

Uninstall the current audio driver and install it again.
other option is trying driver from microsoft update.
Pavilion DV2922TX, XP-SP3 32bit, Intel T5750 2.0Ghz, Nvidia Geforce 8400M GS with 128MB, 4GB 667 DDR2, 250GB HDD

Icloud stopped after upgrading to win 8

icloud stopped working after upgrading to win 8.
Says "map cannot be found".
Any suggestions? Or will it simply not work with Win 8?

Solved.
Needed upgrade to 2.1

Help, MBP 2,2 won't turn into Standby after upgrade to 10.7.2

Recently I've upgraded from 10.7.1 to 10.7.2 via the Software-update utility, however now my MBP model 2,2 won't turn into standby mode when it is connected to the power adapter. Not when I close the lid, or when I select Standby via Apple -> Standby.
On the other hand, when my MBP is running on battery there is no problem with going into Standby mode, so I thing it has something to do with the settings that are suddenly changed...
Does anyone now if the settings have changed somehow? Or where I can change the settings?
Thanks in advance!

Hello Bastiaan,
The first two days after installation of 10.7.2 and the Aperture update my laptop also refused to go to sleep, but that behaviour stopped recently all by its own. When I looked at the Activity monitor I saw the mac was indexing spotlight and rebuilding libraries, so probably it did not want to go to sleep while there still was critical work to be done to migrate properly to iCloud.
I do not know of any other preference settings that might prevent sleep.
So perhaps you should look at the Activity Monitor, if some high priority process is running, that might prevent sleep.
If closing the lid does not work, that might be a hardware problem, but it seems to be unlikely, since it works when on battery power. Does your computer go to sleep when on power adapter, if you set the computer sleep interval to a very short time?
Regards
Léonie

Brand new Macbook Pro goes into pinwheel after log in

I just purchased a Macbook Pro and transfered my system from my old Macbook Air. Everything went fine but now, after I log in, it goes into pinwheel.
I have reinstalled the OS to no avail. Suggestions?

Is it possible it is trying to connect to the MBA but can't?
Joe

MSI Z77A-GD65 BSODS after upgrade..

Hi to everyone,
Ive an upgrade to my PC build. Before upgrade i have:
CPU: i7-3770k @ 4,5ghz runnin on offset mode (detail at screenshots)
RAM: 2x4GB Kingston Predator @ 2400Mhz
graphic: GTX780 from Palit
It was very stable, 0 bsods.
After upgrade now it is:
CPU: stays the same
RAM: 2x4GB Kingston Predator 2400Mhz and 2x4GB Kingston Savage 2400Mhz
Graphics: 2x GTX970 Asus Strix
Now in games Dying Light and BF4 ive random BSODs called:
IRQL_NOT_LESS_OR_EQUAL or KMODE_EXCEPTION_NOT_HANDLED
I do some research at many forums, searching for explanation and i think its maybe a ram problem because its not the same part.
2 sticks are Predator model and 2 strick are Savage.
But technically timings and voltage operation are the same in both models.
I found opinion that when its 4sticks there im need to raise CPU I/O Voltage because its more stressed to IMC controler on CPU.
Before my upgrade CPU I/O Voltage it was set to 1,11V.
I raised it today to 1,15V but no go anyway - its not stable, but i feel it happens now not that often like before rising.
Maybe i do smth wrong in bios? How far can i go with CPU I/O voltage? and its the good direction anyway to find stability?
Here are shots from UEFI, maybe someone can help me to stabilize my rig.
Sorry for my EN btw.
thank you.

Predator
HX321C11T2K2/8T 240-Pin DDR3 SDRAM 8GB (2 x 4GB) DDR3 2133
Cas Latency
11
Timing
11-12-12
Voltage
1.6V
Savage
HX324C11SRK2/8 240-Pin DDR3 SDRAM 8GB (2 x 4GB) DDR3 2400 (PC3 19200)
Cas Latency
11
Timing
11-13-14
Voltage
1.65V
Back in the days of much slower RAM and single channel (before DDR) it was usually no problem mixing different RAM sizes, brands etc. as long as they had similar specs otherwise. At the high speeds modern RAM runs in 2, 3 and 4 channel they are much less forgiving and can cause many problems when miss-matched RAM is used. The fact is over time even though model, part number remains the same manufacturers change chip suppliers for various reasons (price, availability, etc.) so you can't even be assured to get the same if purchasing same model at different times unless you get lucky enough to get 2nd set RAM from the same lot number as the 1st set.

Thinkpad S440 systematic crashes after upgrade to Win 8.1

Hi,
After installing Windows 8.1 I've had big problems with my brand new Thinkpad S440. The laptop has generated systematic bluescreens, mostly related to the Intel Wireless-N 7260 WiFi module. Disabling it in the Device Manager helped a little bit, but I also get other Bluescreens related to e.g.. to "usbxhci.sys" and other modules. After the BSoD the laptop always goes into a reboot-loop at the Lenovo logo during the boot-up with the only solution do do a hard shut down (keeping the power-button pressed for 5 sec).
Yesterday I tried doing a fresh install, but it did not help at all. A few minutes after installing Win 8.1 from scratch the laptop generated a bluescreen.
I have updated all drivers to the latest version, and also tried to solve it by installing an earlier version of e.g. the WiFi driver. Neither one has helped.
Below is a list of the minidumps generated during BSoD's I've had during the last 12 hours since installing a fresh copy of Windows 8.1.
Please, what can I do about this situation? I would not like to return the machine since I like the hardware, but in the current state my Thinkpad S440 is useless. I have not found a way going back to Windows 8.0, since the recovery partition on the HDD apparently was destroyed (according to an Microsoft engineer) during my first trial to update to Win 8.1. (the first update ended in a Black Screen of Death). Microsoft was only willing supply me with a Win 8.1 product key (since a clean install was the only way to recover from the Black Screen of Death back then), which, of course, doesn't work for installing Win 8.0.
System Information (local)
computer name: LENOVO
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: 20AY001DMS, LENOVO
CPU: GenuineIntel Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8284897280 total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 11/20/2013 1:12:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4734-01.dmp
This was probably caused by the following module: storport.sys (storport+0x1400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000740400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 1:12:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: storport.sys (storport!memset+0xC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000740400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 10:03:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-9437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802A67DE929, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 11/20/2013 10:03:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: storport.sys (storport!StorPortExtendedFunction+0xEBB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802A67DE929, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 6:23:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4750-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C71AFE)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF80002C71AFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 10:50:16 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4375-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C5DAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 8:50:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-4921-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002EFDB12)
Bugcheck code: 0xD1 (0x38, 0x2, 0x0, 0xFFFFF80002EFDB12)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 8:02:46 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-5640-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C76B12)
Bugcheck code: 0xD1 (0x1038, 0x2, 0x0, 0xFFFFF80002C76B12)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/19/2013 7:38:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111913-7296-01.dmp
This was probably caused by the following module: netwbw02.sys (0xFFFFF800021A763A)
Bugcheck code: 0xD1 (0xFFFFE00069F99A4D, 0x2, 0x0, 0xFFFFF800021A763A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netwbw02.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netwbw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

Is there something I can disable in the Device Manager to stop USBXHCI.sys from crashing?
On Wed 11/20/2013 8:57:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11421-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CF2AFB)
Bugcheck code: 0xD1 (0xFFFFE008048F5240, 0x2, 0x0, 0xFFFFF80002CF2AFB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:57:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0xD1 (0xFFFFE008048F5240, 0x2, 0x0, 0xFFFFF80002CF2AFB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:52:19 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5265-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002F3EAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:47:44 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11218-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002C97AFE)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF80002C97AFE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:29:32 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5218-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CE9B20)
Bugcheck code: 0xD1 (0x2261DC, 0x2, 0x0, 0xFFFFF80002CE9B20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:20:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11140-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002D44AFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 8:08:45 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-5000-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E9DAFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 7:46:12 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-11093-01.dmp
This was probably caused by the following module: usbxhci.sys (USBXHCI+0x22AFB)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C90AFB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 6:53:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-4937-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80002CBAB20)
Bugcheck code: 0xD1 (0x225EEC, 0x2, 0x0, 0xFFFFF80002CBAB20)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Wed 11/20/2013 6:21:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\112013-10140-01.dmp
This was probably caused by the following module: storport.sys (storport+0x1400)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800006BF400, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Hp Mini 110 1013tu Keyboard is Not working after upgrade to win 7

Hello need help on weird happenings to my keyboard..
Before i upgrade the Operating System From Windows XP to Windows 7 the Hp Mini 110 is working fine..
All keys on keyboard is working and touchpad is also working.
But after upgrading to windows 7 some keys on keyboard are not working like z,x,c,v, left ctrl and other more keys..
what do you think is the problem??
Hardware Issue? or Driver Issue?
please help thank you..

Hello @MysticDragon ,
Welcome to the HP Forums!
I understand some of the keys on your keyboard are not working after installing Windows 7.
I do not see any drivers available for your notebook for Windows 7 on the HP website, so their might be some compatibility issues as it's going to rely on Windows update to find current drivers. This doesn't mean it will not work, but I cannot say for sure that it will.
Try this:
1. Click Start.
2. Click Control Panel.
3. Click Clock, Language, and Region.
4. Click Region and Language.
5. Click the Keyboards and Languages tab.
6. Click Change keyboards...
7. On the General tab, make sure English (United States) - US is selected in the Default input language field.
8. Click on any other keyboards in the Installed services list.
9. Click Remove.
10. Repeat for all other non-English (United States) keyboards.
You may also want to try rolling back to Windows XP and see if the issue persists. It is possible the issue is coincidental and not the direct result of the update to Windows 7.
Let me know if this works!
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

BIAS SoundSaver Input Level Not Working after upgrade from Win 8 to 8.1

Have been using BIAS SoundSaver for INport software to digitize music LPs and cassette tapes to load on MP3 player. Worked fine with Windows 8. However, now that I have upgraded to Win 8.1, I can get sound of LPs and cassette tapes but the Input Level that controls the recording level on the software no longer functions. My computer is an HP ENVY Phoenix h9-1355 Desktop Computer with IDT High Definition Audio CODEC. I am wondering if the problem may be with the audio drivers installed on the computer.
This question was solved.
View Solution.

Hi @Alkay
I see that you are having sound issues after your 8.1 upgrade. Did you update to the 8.1 versions of the drivers?
They may be found here: HP ENVY Phoenix h9-1355 Desktop PC Drivers
Is it only the one application seeing this problem?
Malygris1
I work on behalf of HP
Please click Accept as Solution if you feel my post solved your issue, it will help others find the solution.
Click Kudos Thumbs Up on the right to say “Thanks” for helping!

Cannot print to Adobe PDF printer from Word after upgrading to Win 7 64bit

Hi. After upgrading my operating system from Windows XP to Windows 7 64 bit, I can no longer print to the Adobe PDF printer (e.g. from Word). It just sits in the Adobe PDF printer queue saying "Error" without bringing up the "Save As" dialog box, and nothing happens. I am running Adobe Acrobat 8.0.0 (I've checked for updates but it says none are available). I have tried doing a repair installation following the instructions on this website (http://helpx.adobe.com/creative-suite/kb/error-file-adobepdf-dll-needed.html) but to no avail.
Thank you in advance for your help.

I think it's time to upgrade. 64-bit systems weren't much in use at the time of Acrobat 8.0.

Satellite L775 goes into BSOD after upgrade to Win 8.1

Similar Messages

Maybe you are looking for