Windows 8.1 Blue Screen

I have increase from 4 gb of RAM to 8 gb of RAM on my DELL Ispiron 1321 Laptop, and Is getting blue screens with sad face recollecting information and shuts down. If someone have a solution for this problem, please Advise.

We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash,
what drivers were loaded, and what was responsible.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask
Wanikiya and Dyami--Team Zigzag

Similar Messages

IPod touch 4G causes windows 7 to blue screen when connecting to iTunes

Wife bought me a new iPod Touch 4G for Christmas. A few days ago it started to cause my Windows 7 (64bit) to blue screen randomly while connected or sometimes when I first connected it. Did a Windows re-install and crashes Windows each time I connect it. It is not the USB port as other devices work fine through all my USB ports. I do load various apps on the iPod several times a day. And it is also bluetooth'd to my wireless wifi switch (same network as my PC). ITunes program on PC is latest version. Anyone have a clue on this one?

Try here:
iPhone, iPad, or iPod touch: Windows displays a blue screen message or restarts when connecting your device

Windows 7 Crash (Blue Screen) with Skype 6.18 on H...

Hi,
I think a lot of people are having the same problem with Skype 6.18 on HP Pavilion notebooks.
Windows 7 crashes during the auto-update or installation of 6.18
After about 3-4 hours of troubleshooting the Blue Screen / service exception error (in ks.sys) I discovered that it's caused by the HP HD Webcam [Fixed] driver (version is 6.0.1113.1 released 2012-11-20 (or 20-11-2012)).
The driver is written by Sonix and is unlikely to be updated. So you have the choice of going back to an older version of Skype or disabling the webcam / driver through Device Manager. As soon as you disable the driver / device Skype will install / start - but of course you won't be able to use video during Skype calls.
Hopefully Microsoft / Skype will fix the driver incompatibility in a future release.
Skype Support - the issue is with the HP / Sonix driver - file is snp2uvc.sys
There are similar issues reported with a previous version of the HP HD Webcam driver as well (SPUVCBv_x64.sys).
Please fix it. I'd like to use video in calls again!

The best working solution at this time is to download and install Skype 6.14 and disable updates. If you still get prompts to upgrade you can ignore them and the program should continue to function as it has not been retired as of yet. Hopefully there will be a resolution in a future Skype update or an updated driver from HP that might resolve the issue.
http://community.skype.com/t5/Windows-desktop-client/BSOD-on-startup-and-installation/m-p/3511645/hi...

Windows XP displaying Blue screen of death!

I just bought an iPod Classic last week and installed iTunes 8.1.1.10 and have had nothing but problems since day 1. The software *****, it ***** up my processor, freezes, and suddenly started crashing my system. i'm getting the BSoD and I am NOT on Vista. I am running XP Pro. Now I'm getting windows popping up saying that my computer can't find vital system files. This all started when I installed iTunes 8. PLEASE HELP! I backed up all of my important information onto an external hard drive because I am scared to lose my data because of this crashing. It seemed to start happening after i cleared my library out a few times because it was uploading 2 versions of some songs because my playlists were store in My Music. I moved the playlists and tried to resync my 3,000+ song library and my computer got the BSoD. I got one error the first time that said KernelStack_InpageError. So I rebooted, cleared my library, then set it to reload my music library into iTunes. Worked ok, then started to resync my iPod and it crashed again. It seems to keep happening when I try to sync a large number of songs at once, so I tried doing 1-2 letters of the alphabet at a time, which worked for a while, syncing 1-300 songs at once. Then my computer crashed for maybe the third or fourth time when syncing the S's. I'm sick and tired of this blue screen and my computer crashing and I don't want to be afraid of losing my data or my laptop. I'd really appreciate ANY help anyone can offer me.
Extra specs:
iPod Classic black
about 99/120GB free (nowhere near being full)
both iPod and iTunes running the most up-to-date software
If you need any other info, let me know
last few times I tried to sync, iTunes malfunctioned and had to close

I have a similar problem, except I can't even get to a command prompt or any sort of stopping point b/c my computer keeps restarting after it hits the BSOD. My usb-based keyboard can't stop the process either for some reason, so I can't get into the bios or the safe mode. I can't do squat except watch the blue screen over and over until I just unplug the **** thing and swear a lot. This all started happening right after the reboot following the install of iTunes8, so I gather this is the culprit (and, besides, a ton of folks out there seem to have the same problem). I don't even have an iPod or iPhone, so it's not that synching issue. If this is a way to get people to throw out their Windows PCs in frustration to buy Macs, then that's just a really malicious move. The only other way I see it is that this is another terrible deployment of an iTunes software update for windows, so what happened to reliable beta testing? Either way it ***** ***** *****. Can I just have my computer back please?!
Any tips on how to break the cycle when the keyboard doesn't function; and then how to resolve the BSOD issue after that? I miss my turntable.

Windows 7 Crashes (Blue Screen Of Death) As Soon As My iPhone4 Connects

Ok, so I have Windows 7 with the latest version of iTunes and the latest software version for my iPhone4, everything was working fine until just the other day, whenever I plug my iPhone into my computer, as soon as it makes that little noise when it connects, I get a blue screen of death.
That's about all I know...

I updated Windows drivers (it said I had three updates to download) but still no luck.
This is the error report I receve upon reboot:
Problem signature:
Problem Event Name:    BlueScreen
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    4105
Additional information about the problem:
BCCode:    1000007e
BCP1:    FFFFFFFFC0000005
BCP2:    FFFFF8800F4249F2
BCP3:    FFFFF88003292918
BCP4:    FFFFF88003292170
OS Version:    6_1_7601
Service Pack:    1_0
Product:    768_1
Files that help describe the problem:
C:\Windows\Minidump\011213-18985-01.dmp
C:\Users\Gumballthechewy\AppData\Local\Temp\WER-44444-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 privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Windows 7 Ultimate Blue Screen of Death (BSOD)

Hello,
I have Windows 7 Ultimate and very recently I have started experiencing this BSOD with an automatic restart.
I took a photo of the BSOD but I'm not sure how to attach it to this post. I even downloaded that Nirsoft BlueScreenView program but it doesn't show up on there. Should I change some setting?
The message says:
STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80002AC32C2, 0xFFFFFFFFFF880009A9230)
I ran the CheckDisk program and there were no errors. I ran MemTest86 (2 passes) and there were no errors with the memory. I have an NVidia GTX-295 that I downloaded drivers for and it was working fine until a couple of days ago.
I did however install my old ATi Radeon X1900XTX along with the other card and downloaded the drivers for that. It worked fine for a couple of days and then it crashed (BSOD) a couple of times. I have 2 monitors so I removed the ATi card (pulled it out) and deleted every single file related to ATi in the Program Files folder (forgot to "uninstall" the drivers before physically pulling out the card). Connected both monitors to my NVidia GPU and things were back to normal. A few days later, I got the BSOD while playing Call of Duty: Modern Warfare 2 (through Steam) and then it started happening when I was just surfing the Internet. Now it happens more often and it is extremely frustrating.
I spent several thousand dollars on a BRAND NEW custom SYSTEM BUILD and I am now faced with this BSOD problem.
PLEASE HELP ME!!
I have an ASUS P6T7 WS Supercomputer Mobo and the release version of the BIOS; have not updated it because I was told I could ruin the whole computer if I screwed something up.
Have 2 SLC SSDs (G-Skill) for my OS drive in RAID-0. This is where Windows 7 Ultimate is installed.
My mouse driver (Logitech MX20 Laser cordless) is from 2006 but I am unable to update it even through the Logitech website. Not sure why.
Every other driver is up to date (or it says 'best version currently installed').
PLEASE HELP!!
Thanks in advance.

Hello Suzerain,
First of all, upgrade BIOS to the latest version, remove all unnecessary hardware devices from the computer and try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue. If so, please download and run Windows 7 Upgrade Advisor to check the reason for the issue. If the issue is caused by some incompatible driver, you might go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software.
If you still get the BSOD error after installing the latest driver, please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services).
The system goes to a blue screen because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).
To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
I hope the problem will be resolved soon. Thanks!
Andy

Windows 7 (64) Blue Screen of Death at Start up after installing iTunes 10

I just got a brand new computer a week ago and decided to install iTunes 10 this evening. The install finished successfully and a message prompted me to restart to complete the installation. So I did. Now my machine will not boot. Each time it does, I get a blue screen of death. Attempting to restore the system fails.
I was able to start Windows in Safe Mode once but I wasn't able to uninstall programs while in safe mode so I couldn't remove itunes 10. And now I can no longer start my machine in Safe Mode.
Has anyone else experienced this? Any ideas to solve it?
Message was edited by: BrianCoker

Windows 7 64 bit core i7
BSOD while updating to iTunes 10 with suspended installation of Apple Mobile Device Support. Network drivers no longer working as a result. Attempted fix by downloading from a different machine and competing install via files transferred over on flash drive. No dice. Attempted removal of iTunes, QuickTime, Apple Mobile Device Support, Apple Application Support, Apple Software Update to see if this would fix. Followed this up with a restart. This seems to have improved matters as system is starting up faster. No dice. Try reinstall network drivers from Sony ViaoCare disk. Installed and restarted. No dice. Next, try Widows 7 Network and Sharing diagnostics. No dice. Next try manual removal & reinstall of network driver using Device Manager, restart. Can't seem to re-install Network Controller. Still trying to solve this.

Windows 8.1 Blue Screen of Death "Critical process died" after Windows update

Hey there, my Envy laptop has the "Critical Process Died" blue screen of death error after doing 3 things today:
1. A BIOS update through HP Support Assistant.
2. An x64 windows process update (optional) through the Control Panel.
3. An NVIDIA update.
What can I do to fix this error? I'm okay with a complete system wipe. Please help.
*Windows 8.1 64bit

The only option that worked for me was to "reset" my PC, as in a complete wipe. it's working properly again, when I read reviews of windows 8.1 I didn't really believe the people who said stay away from it, but since I've had more problems than I'd wish to, I'm too afraid to go back to it. Thanks anyways guys.

USB727 Windows 7 x64 Blue Screen of Death BSOD

Hi,
Every time I use my Verizon USB727 on Windows 7 x64, after removing, when I try and suspend (sleep) my laptop I get a BSOD. I have a Lenovo T500. I am running in NDIS mode.
This worked great under Vista x32.
If I shutdown my laptop before removing the adapter all is well, however I'd like to put it to sleep as I often travel from place to place and I like to resume my work where I left off. The issue seems to be Windows can't put the device into a sleep state and unload/suspend the Novetel drivers. Without using the USB727, I have no issues. The suspend will hang trying to suspend. Sometimes it will go back to locked screen. After 5-20 minutes the BSOD occurs and the laptop reboots itself.
Windows x64 Enterprise Edition -- all latest MS updates applied as of 12/18/2010
VZaccess Manager v7.2.1.2 (2420b)
I have called support and all they can tell me is, there are no reported problems and I have the latest drivers.

Hello Suzerain,
First of all, upgrade BIOS to the latest version, remove all unnecessary hardware devices from the computer and try entering Windows safe mode to test whether it is a third-party software/hardware compatibility issue. If so, please download and run Windows 7 Upgrade Advisor to check the reason for the issue. If the issue is caused by some incompatible driver, you might go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software.
If you still get the BSOD error after installing the latest driver, please understand that Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services).
The system goes to a blue screen because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).
To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for regional support phone numbers.
I hope the problem will be resolved soon. Thanks!
Andy

Windows 7 64Bit - Blue Screen

I got Asus P5g41T-MXL , 4G Ram, Windows 7 64Bit
I got Blue screen and freeze Issue.
First time was at 9:19 Am with the blue screen Report and Memory DMP and Other DMP Files
Second Time was at 10:40 Am With the Blue Screen Reports
All in one Here
http://www.mediafire.com/download/9udfoda9aex979x/Blue+Screen+2014.rar
Mohamed Mahmoud IT Specialist

If the crashes are still happening after uninstalling Ultra ISO, then yes, let's run Memtest for no less than 8 passes:
Memtest86+:
Download Memtest86+ here:
http://www.memtest.org/
Which should I download?
You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary
files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works (you don't need to read, it's only for those interested in the specifics):
Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have
been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.
The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead
and ensure that all adjacent cells have at least been written with all possible one and zero combinations.
The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with
a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.
Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.
Any other questions, they can most likely be answered by reading this great guide here:
http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama

Windows crashes with Blue Screen

i'm working with windows XP and after installing the BB Desktop software, i get quite often a blue screen.... Can anybody help me with this? Is a special Service pack necessary to run it properly? Thanks in advance for any help.
J-P

Which version of desktop manager you're trying to install?
tanzim
If your query is resolved then please click on “Accept as Solution”
Click on the LIKE on the bottom right if the post deserves credit

Windows 7 (64) blue screen on startup

Hi,
I went to turn on my computer today (Toshia qosmio x505-q880) and everything seemed normal until about halfway through the startup process I received a blue screen error. I can boot in safe mode, but I can't figure out whats causing this problem.
Here is the error message that I get when I boot into safe mode.
Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7600.2.0.0.768.3
  Locale ID: 1033
Additional information about the problem:
  BCCode: 51
  BCP1: 0000000000000001
  BCP2: FFFFF8A000024010
  BCP3: 000000000156B000
  BCP4: 0000000000000374
  OS Version: 6_1_7600
  Service Pack: 0_0
  Product: 768_1
Files that help describe the problem:
  C:\Windows\Minidump\090710-8065-01.dmp
  C:\Users\Matt\AppData\Local\Temp\WER-16910-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 privacy statement offline:
  C:\windows\system32\en-US\erofflps.txt
Problem signature:  Problem Event Name: BlueScreen  OS Version: 6.1.7600.2.0.0.768.3  Locale ID: 1033
Additional information about the problem:  BCCode: 51  BCP1: 0000000000000001  BCP2: FFFFF8A000024010  BCP3: 000000000156B000  BCP4: 0000000000000374  OS Version: 6_1_7600  Service Pack: 0_0  Product: 768_1
Files that help describe the problem:  C:\Windows\Minidump\090710-8065-01.dmp  C:\Users\Matt\AppData\Local\Temp\WER-16910-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 privacy statement offline:  C:\windows\system32\en-US\erofflps.txt

Also this is what I get when I use my crash reporter.
Seems to keep pointing to some WerFault.exe and Wer.dll
Version=1
EventType=BlueScreen
EventTime=129283576105180317
ReportType=4
Consent=1
UploadTime=129283576484580156
ReportIdentifier=79710af8-baad-11df-a1bc-c80aa96bb319
IntegratorReportIdentifier=090710-8065-01
Response.type=4
Response.AnalysisBucket=X64_0x51_nt!HvpSetRangeProtection+8fae8
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\windows\system32\wer.dll
UI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=Cancel
UI[8]=Windows has recovered from an unexpected shutdown
UI[9]=A problem caused Windows to stop working correctly. Windows will notify you if a solution is available.
UI[10]=Close
Sec[0].Key=BCCode
Sec[0].Value=51
Sec[1].Key=BCP1
Sec[1].Value=0000000000000001
Sec[2].Key=BCP2
Sec[2].Value=FFFFF8A000024010
Sec[3].Key=BCP3
Sec[3].Value=000000000156B000
Sec[4].Key=BCP4
Sec[4].Value=0000000000000374
Sec[5].Key=OS Version
Sec[5].Value=6_1_7600
Sec[6].Key=Service Pack
Sec[6].Value=0_0
Sec[7].Key=Product
Sec[7].Value=768_1
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=CA
State[1].Value=1
State[2].Key=BLOB
State[2].Value=CHKSUM=366D14228723C1834DCC14382AED3B0B;BID=OCATAG;ID=5fed2613-7bb3-46f3-b4fc-0915969aa15d;SUB=9//8//2010 8:27:22 AM
File[0].CabName=090710-8065-01.dmp
File[0].Path=090710-8065-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\090710-8065-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-16910-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\Matt\AppData\Local\Temp\WER-16910-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WERDE8B.tmp.WERInternalMetadata.xml
File[2].Flags=589827
File[2].Type=5
File[2].Original.Path=C:\Users\Matt\AppData\Local\Temp\WERDE8B.tmp.WERInternalMetadata.xml
File[3].CabName=Report.cab
File[3].Path=Report.cab
File[3].Flags=196608
File[3].Type=7
File[3].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe
Version=1
EventType=BlueScreen
EventTime=129283576105180317
ReportType=4
Consent=1
UploadTime=129283576484580156
ReportIdentifier=79710af8-baad-11df-a1bc-c80aa96bb319
IntegratorReportIdentifier=090710-8065-01Response.type=4Response.AnalysisBucket=X64_0x51_nt!HvpSetRangeProtection+8fae8
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033UI[2]=C:\windows\system32\wer.dllUI[3]=Windows has recovered from an unexpected shutdown
UI[4]=Windows can check online for a solution to the problem.
UI[5]=&Check for solution
UI[6]=&Check later
UI[7]=CancelUI[8]=Windows has recovered from an unexpected shutdownUI[9]=A problem caused Windows to stop working correctly. Windows will notify you if a solution is available.
UI[10]=CloseSec[0].Key=BCCode
Sec[0].Value=51Sec[1].Key=BCP1
Sec[1].Value=0000000000000001
Sec[2].Key=BCP2Sec[2].Value=FFFFF8A000024010
Sec[3].Key=BCP3Sec[3].Value=000000000156B000
Sec[4].Key=BCP4Sec[4].Value=0000000000000374
Sec[5].Key=OS Version
Sec[5].Value=6_1_7600
Sec[6].Key=Service PackSec[6].Value=0_0
Sec[7].Key=Product
Sec[7].Value=768_1
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=CA
State[1].Value=1
State[2].Key=BLOB
State[2].Value=CHKSUM=366D14228723C1834DCC14382AED3B0B;BID=OCATAG;ID=5fed2613-7bb3-46f3-b4fc-0915969aa15d;SUB=9//8//2010 8:27:22 AM
File[0].CabName=090710-8065-01.dmp
File[0].Path=090710-8065-01.dmp
File[0].Flags=851970
File[0].Type=2
File[0].Original.Path=C:\Windows\Minidump\090710-8065-01.dmp
File[1].CabName=sysdata.xml
File[1].Path=WER-16910-0.sysdata.xml
File[1].Flags=851970
File[1].Type=5
File[1].Original.Path=C:\Users\Matt\AppData\Local\Temp\WER-16910-0.sysdata.xml
File[2].CabName=WERInternalMetadata.xml
File[2].Path=WERDE8B.tmp.WERInternalMetadata.xml
File[2].Flags=589827
File[2].Type=5
File[2].Original.Path=C:\Users\Matt\AppData\Local\Temp\WERDE8B.tmp.WERInternalMetadata.xml
File[3].CabName=Report.cab
File[3].Path=Report.cab
File[3].Flags=196608
File[3].Type=7
File[3].Original.Path=Report.cab
FriendlyEventName=Shut down unexpectedly
ConsentKey=BlueScreen
AppName=Windows
AppPath=C:\Windows\System32\WerFault.exe

Ideapad S405 windows 8 startup blue screen failure

When it is turned on, it shows
Your PC needs to be repaired
A required device isn't connected or can't accessed
error code 0xc0000034
You'll need to use recovery tools on your installation media. If you don't have any installation media like aDISC or USB device, contact your system administrator or PC manufacturer.
i tried to enter recovery mode by pressing power button while lenovo logo apear but it always go to blue screen.
i dont have usb recovery.
Please help me

Dear Customer
Welcome in Lenovo forums
To processed the recovery process please follow the below steps :-
1- Shut down the machine and connect the power cable
2- Press on the novo button once at the left hand side to get alist of options
3- Choose from the list System recovery to start the process
Please let me know
Thanks
Alaa
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Windows 8.1 Blue Screen of Death

Hi Again!
I'm getting the BSOD once again, here are my files:
https://www.dropbox.com/s/zsyrae2s3fq8x2c/Minidump3.rar?dl=0
Some are DRIVER_POWER_STATE_FAILURE's and others aren't.

Hi Cynosural,
My apologize.
But the result is the same:
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe0003eb688c0, ffffd001a7ff8960, ffffe000417aa9d0}
Probably caused by : usbccgp.sys
Followup: MachineOwner
6: kd> !analyze -v
* Bugcheck Analysis *
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0003eb688c0, Physical Device Object of the stack
Arg3: ffffd001a7ff8960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe000417aa9d0, The blocked IRP
Debugging Details:
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe0003dfee480
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1b3
MODULE_NAME: usbccgp
FAULTING_MODULE: fffff8017b481000 usbccgp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE: FFFFD001A7FFFFB0
STACK_TEXT:
ffffd001`a7ff8928 fffff801`0b61e36e : 00000000`0000009f 00000000`00000003 ffffe000`3eb688c0 ffffd001`a7ff8960 : nt!KeBugCheckEx
ffffd001`a7ff8930 fffff801`0b61e28e : ffffe000`44cc6d90 00000000`00000001 ffffe000`397fa9f0 fffff801`0b509c19 : nt!PopIrpWatchdogBugcheck+0xde
ffffd001`a7ff8990 fffff801`0b48de67 : 00000000`00000000 ffffd001`a7ff8ae0 ffffe000`44cc6dd0 ffffd001`a7fce180 : nt!PopIrpWatchdog+0x32
ffffd001`a7ff89e0 fffff801`0b56acea : ffffd001`a7fce180 ffffd001`a7fce180 ffffd001`a7fda3c0 ffffe000`3dc63880 : nt!KiRetireDpcList+0x4f7
ffffd001`a7ff8c60 00000000`00000000 : ffffd001`a7ff9000 ffffd001`a7ff3000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_IMAGE_usbccgp.sys
BUCKET_ID: 0x9F_3_POWER_DOWN_IMAGE_usbccgp.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_power_down_image_usbccgp.sys
FAILURE_ID_HASH: {447d6c25-e30e-cab7-b8c4-6eeb621d3df1}
Followup: MachineOwner
6: kd> lmvm usbccgp
start end module name
fffff801`7b481000 fffff801`7b4a8000 usbccgp (pdb symbols) d:\symbols\usbccgp.pdb\217FA7FC5CEC4B5BB135931D6DF2DB732\usbccgp.pdb
Loaded symbol image file: usbccgp.sys
Mapped memory image file: d:\symbols\usbccgp.sys\53D0F1B327000\usbccgp.sys
Image path: \SystemRoot\System32\drivers\usbccgp.sys
Image name: usbccgp.sys
Timestamp: Thu Jul 24 19:44:51 2014 (53D0F1B3)
CheckSum: 00032E6F
ImageSize: 00027000
File version: 6.3.9600.17238
Product version: 6.3.9600.17238
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: USBCCGP.SYS
OriginalFilename: USBCCGP.SYS
ProductVersion: 6.3.9600.17238
FileVersion: 6.3.9600.17238 (winblue_gdr.140723-2018)
FileDescription: USB Common Class Generic Parent Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
6: kd> !drvobj ffffe0003dfee480 f
fffff8010b6d5970: Unable to get value of ObpRootDirectoryObject
fffff8010b6d5970: Unable to get value of ObpRootDirectoryObject
Driver object (ffffe0003dfee480) is for:
\Driver\usbccgp
Driver Extension List: (id , addr)
Device Object list:
ffffe0003eb688c0 ffffe0003e1788c0
DriverEntry: fffff8017b48a330 usbccgp!GsDriverEntry
DriverStartIo: 00000000
DriverUnload: fffff8017b4a0280 usbccgp!USBC_DriverUnload
AddDevice: 00000000
Dispatch routines:
[00] IRP_MJ_CREATE fffff8017b482f00 usbccgp!USBC_Dispatch
[01] IRP_MJ_CREATE_NAMED_PIPE fffff8010b51184c nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE fffff8017b482f00 usbccgp!USBC_Dispatch
[03] IRP_MJ_READ fffff8010b51184c nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE fffff8010b51184c nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION fffff8010b51184c nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION fffff8010b51184c nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA fffff8010b51184c nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA fffff8010b51184c nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS fffff8010b51184c nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff8010b51184c nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION fffff8010b51184c nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL fffff8010b51184c nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff8010b51184c nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL fffff8017b482f00 usbccgp!USBC_Dispatch
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff8017b482f00 usbccgp!USBC_Dispatch
[10] IRP_MJ_SHUTDOWN fffff8010b51184c nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL fffff8010b51184c nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP fffff8010b51184c nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT fffff8010b51184c nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY fffff8010b51184c nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY fffff8010b51184c nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER fffff8017b482f00 usbccgp!USBC_Dispatch
[17] IRP_MJ_SYSTEM_CONTROL fffff8017b482f00 usbccgp!USBC_Dispatch
[18] IRP_MJ_DEVICE_CHANGE fffff8010b51184c nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA fffff8010b51184c nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA fffff8010b51184c nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP fffff8017b482f00 usbccgp!USBC_Dispatch
Further troubleshootings is beyond my knowledge, you may contact Microsoft if you would like further troubleshooting.
Thank you for your understanding.
Best regards
Michael Shao
TechNet Community Support

Windows crashed with Blue Screen. Dump file content attached.

Loading Dump File [C:\Windows\Minidump\121712-35786-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333 Machine Name: Kernel base = 0xfffff800`03407000 PsLoadedModuleList = 0xfffff800`0364b670 Debug session time: Mon Dec 17 11:57:26.477 2012 (UTC - 4:00) System Uptime: 4 days 17:23:45.304 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........ Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {10, 2, 0, fffff8000341f852}
Unable to load image \SystemRoot\System32\drivers\lcencvm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for lcencvm.sys *** ERROR: Module load completed but symbols could not be loaded for lcencvm.sys Unable to load image \SystemRoot\System32\Drivers\lcfiltvm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for lcfiltvm.sys *** ERROR: Module load completed but symbols could not be loaded for lcfiltvm.sys Probably caused by : lcencvm.sys ( lcencvm+26b9a )
Followup: MachineOwner ---------
2: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000010, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000341f852, address which referenced memory
Debugging Details: ------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b5100 0000000000000010
CURRENT_IRQL: 2
FAULTING_IP: nt!IopInsertRemoveDevice+62 fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Rim.Desktop.ex
TRAP_FRAME: fffff8800c8a52f0 -- (.trap 0xfffff8800c8a52f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=00000000000000a0 rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000341f852 rsp=fffff8800c8a5480 rbp=0000000000000000 r8=fffff88003365890 r9=0000000000000000 r10=0000000000000000 r11=fffffa800ec2a900 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei pl nz na pe nc nt!IopInsertRemoveDevice+0x62: fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi ds:00000000`00000010=???????????????? Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003485569 to fffff80003485fc0
STACK_TEXT: fffff880`0c8a51a8 fffff800`03485569 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0c8a51b0 fffff800`034841e0 : fffffa80`0e0cdbf0 fffff880`01202bcf fffff880`0c8a5300 fffffa80`0a272300 : nt!KiBugCheckDispatch+0x69 fffff880`0c8a52f0 fffff800`0341f852 : 00000000`00000000 fffffa80`0a272300 00000000`00000000 fffffa80`07d6e8d0 : nt!KiPageFault+0x260 fffff880`0c8a5480 fffff800`0341f729 : fffffa80`0a272350 fffffa80`07d6e8d0 fffffa80`07d6e8d0 00000000`0000000a : nt!IopInsertRemoveDevice+0x62 fffff880`0c8a54b0 fffff800`0377dfb7 : fffffa80`0f871a30 fffffa80`0a5aa070 00000000`00000001 fffffa80`07321210 : nt!IopCompleteUnloadOrDelete+0x9d fffff880`0c8a5560 fffff800`0348f1d4 : fffff880`0c8a5660 fffffa80`0a447ab8 fffffa80`07321210 fffff880`0c8a5668 : nt!IopDeleteFile+0x1a7 fffff880`0c8a55f0 fffff880`0146db9a : fffffa80`0a447ab8 fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 : nt!ObfDereferenceObject+0xd4 fffff880`0c8a5650 fffffa80`0a447ab8 : fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 : lcencvm+0x26b9a fffff880`0c8a5658 fffffa80`0a491c28 : fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 : 0xfffffa80`0a447ab8 fffff880`0c8a5660 fffffa80`0a54e628 : fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 : 0xfffffa80`0a491c28 fffff880`0c8a5668 fffff880`0144ac90 : 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 : 0xfffffa80`0a54e628 fffff880`0c8a5670 00000000`000003e3 : fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 : lcencvm+0x3c90 fffff880`0c8a5678 fffff880`00ff86d0 : fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 : 0x3e3 fffff880`0c8a5680 fffff8a0`14ddc760 : fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 : lcfiltvm+0xf6d0 fffff880`0c8a5688 fffff880`00ff58d8 : fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 fffff880`012016df : 0xfffff8a0`14ddc760 fffff880`0c8a5690 fffff880`00ff86d0 : 00000000`00000000 fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 : lcfiltvm+0xc8d8 fffff880`0c8a5698 00000000`00000000 : fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 00000000`00000000 : lcfiltvm+0xf6d0
STACK_COMMAND: kb
FOLLOWUP_IP: lcencvm+26b9a fffff880`0146db9a ??              ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: lcencvm+26b9a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lcencvm
IMAGE_NAME: lcencvm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e3c8eac
FAILURE_BUCKET_ID: X64_0xA_lcencvm+26b9a
BUCKET_ID: X64_0xA_lcencvm+26b9a
Followup: MachineOwner ---------
2: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000010, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8000341f852, address which referenced memory
Debugging Details: ------------------
READ_ADDRESS: 0000000000000010
CURRENT_IRQL: 2
FAULTING_IP: nt!IopInsertRemoveDevice+62 fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Rim.Desktop.ex
TRAP_FRAME: fffff8800c8a52f0 -- (.trap 0xfffff8800c8a52f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=00000000000000a0 rdx=0000000000000010 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8000341f852 rsp=fffff8800c8a5480 rbp=0000000000000000 r8=fffff88003365890 r9=0000000000000000 r10=0000000000000000 r11=fffffa800ec2a900 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0         nv up ei pl nz na pe nc nt!IopInsertRemoveDevice+0x62: fffff800`0341f852 48393a          cmp     qword ptr [rdx],rdi ds:00000000`00000010=???????????????? Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003485569 to fffff80003485fc0
STACK_TEXT: fffff880`0c8a51a8 fffff800`03485569 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0c8a51b0 fffff800`034841e0 : fffffa80`0e0cdbf0 fffff880`01202bcf fffff880`0c8a5300 fffffa80`0a272300 : nt!KiBugCheckDispatch+0x69 fffff880`0c8a52f0 fffff800`0341f852 : 00000000`00000000 fffffa80`0a272300 00000000`00000000 fffffa80`07d6e8d0 : nt!KiPageFault+0x260 fffff880`0c8a5480 fffff800`0341f729 : fffffa80`0a272350 fffffa80`07d6e8d0 fffffa80`07d6e8d0 00000000`0000000a : nt!IopInsertRemoveDevice+0x62 fffff880`0c8a54b0 fffff800`0377dfb7 : fffffa80`0f871a30 fffffa80`0a5aa070 00000000`00000001 fffffa80`07321210 : nt!IopCompleteUnloadOrDelete+0x9d fffff880`0c8a5560 fffff800`0348f1d4 : fffff880`0c8a5660 fffffa80`0a447ab8 fffffa80`07321210 fffff880`0c8a5668 : nt!IopDeleteFile+0x1a7 fffff880`0c8a55f0 fffff880`0146db9a : fffffa80`0a447ab8 fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 : nt!ObfDereferenceObject+0xd4 fffff880`0c8a5650 fffffa80`0a447ab8 : fffffa80`0a491c28 fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 : lcencvm+0x26b9a fffff880`0c8a5658 fffffa80`0a491c28 : fffffa80`0a54e628 fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 : 0xfffffa80`0a447ab8 fffff880`0c8a5660 fffffa80`0a54e628 : fffff880`0144ac90 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 : 0xfffffa80`0a491c28 fffff880`0c8a5668 fffff880`0144ac90 : 00000000`000003e3 fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 : 0xfffffa80`0a54e628 fffff880`0c8a5670 00000000`000003e3 : fffff880`00ff86d0 fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 : lcencvm+0x3c90 fffff880`0c8a5678 fffff880`00ff86d0 : fffff8a0`14ddc760 fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 : 0x3e3 fffff880`0c8a5680 fffff8a0`14ddc760 : fffff880`00ff58d8 fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 : lcfiltvm+0xf6d0 fffff880`0c8a5688 fffff880`00ff58d8 : fffff880`00ff86d0 00000000`00000000 fffff880`0c8a5840 fffff880`012016df : 0xfffff8a0`14ddc760 fffff880`0c8a5690 fffff880`00ff86d0 : 00000000`00000000 fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 : lcfiltvm+0xc8d8 fffff880`0c8a5698 00000000`00000000 : fffff880`0c8a5840 fffff880`012016df fffffa80`0b5236f0 00000000`00000000 : lcfiltvm+0xf6d0
STACK_COMMAND: kb
FOLLOWUP_IP: lcencvm+26b9a fffff880`0146db9a ??              ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: lcencvm+26b9a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: lcencvm
IMAGE_NAME: lcencvm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e3c8eac
FAILURE_BUCKET_ID: X64_0xA_lcencvm+26b9a
BUCKET_ID: X64_0xA_lcencvm+26b9a
Followup: MachineOwner ---------

The best working solution at this time is to download and install Skype 6.14 and disable updates. If you still get prompts to upgrade you can ignore them and the program should continue to function as it has not been retired as of yet. Hopefully there will be a resolution in a future Skype update or an updated driver from HP that might resolve the issue.
http://community.skype.com/t5/Windows-desktop-client/BSOD-on-startup-and-installation/m-p/3511645/hi...

Windows 8.1 Blue Screen

Similar Messages

Maybe you are looking for