Blue screen of death occur frequently.

Similar Questions

• How a Windows error reports tire disorder - specifically the following code which resulted in a Blue Screen of Death?

  The blue screen of death occurred during online communication using a Logitech VID communications program. The following error report translated by:
  -Fault bucket 0x7E_lvrs. ReadWriteThread + 243, type 0
  Event name: BlueScreen
  Answer: no
  Cabin ID: 0

  Signature of the problem:
  P1:
  P2:
  P3:
  P4:
  P5:
  P6:
  P7:
  P8:
  P9:
  P10:

  Attached files:
  C:\Windows\Minidump\Mini013110-01.dmp
  C:\Users\Douglas\AppData\Local\Temp\WER-78015-0.SysData.XML
  C:\Users\Douglas\AppData\Local\Temp\WER7CDD.tmp.version.txt

  These files are available here:
  C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Report0eeec72b
  Online from the best part of twenty minutes before it occurred. The two users of the
  program had the same result. (Blue screen of death) The two of us are running Windows Vista Ultimate Edition on motherboards model Intel D850EMVR with the latest bios update, Intel Pentium IV 3.06 Ghz, 533FSB CPUs, 2 GB of 168 pin memory of Samsung PC800 ECC, ATI AIW 9600XT 256 MB AGP video cards, Sound Blaster Audigy 2ZS with discs Live sound cards, ASB3940 Advansys SCSI adapters , Nakamichi5 disk SCSI MJ - 5.16 drives, Iomega SCSI ZIP 100 drives, and Lite on model SHM-165H6S DVD/CD rewritable EIDE drives. The two systems using model Logitech 9000 Pro webcam. (The two systems are essentially clones) Communication between Memphis, TN and Windsor, ON, CAN.

  Hello

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

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

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

  BCCode: 7F 0x0000007E

  Cause

  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug control is a very common bug control. To interpret it, you must identify which exception has been generated.

  Common exception codes are:

  • 0xc0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation has occurred.

  For a complete list of exception codes, see the Ntstatus.h file located in the directory Inc. of the Microsoft Windows Driver Kit (WDK).

  Solve the problem

  If you do not have to debug this problem, you must use certain basic troubleshooting techniques.

  • Make sure you have enough disk space.
  • If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
  • Try changing video cards.
  • Check with your hardware vendor for updates to the BIOS.
  • Disable the BIOS memory options such as implementing caching or shading.

  If you plan to debug this problem, you may find it difficult to get a stack trace. Parameter 2 (the address of the exception) should identify the driver or function that caused the problem.

  If exception code 0 x 80000003 occurs, a hard-coded breakpoint or assertion was hit, but the system was launched with the /nodebug. switch. This problem should occur infrequently. If it occurs repeatedly, make sure that a kernel debugger is connected and the system is booted with the Switch/DEBUG .

  In case of exception code 0 x 80000002, the trap frame provides additional information.

  If you do not know the specific cause of the exception, consider the following questions:

  • Hardware incompatibility. Ensure that any new hardware that is installed is listed in the list of the products tested Microsoft Windows market.
  • Service driver or defective peripheral system. A chauffeur service or defective peripheral system could be responsible for this error. The hardware problems, such as BIOS incompatibilities, conflicts of memory and IRQ conflicts can also generate this error.

  If a driver is listed by name in the bug check message, disable or remove that driver. Disable or remove drivers or services that have been recently added. If the error occurs during the startup sequence and the system partition is formatted with the NTFS file system, you may be able to use Safe Mode to rename or to delete the faulty driver. If the driver is used as part of the start-up procedure of the system Safe Mode, you must start the computer by using the Recovery Console to access the file.

  If the problem is associated with Win32k.sys, the source of the error may be a third-party remote control program. If this software is installed, you can remove the service by starting the computer by using the recovery and then Console by removing the offending system service file.

  Check the system log in Event Viewer for additional error messages that might help identify the device or driver responsible for control of bug 0x7E.

  You can also disable memory cache BIOS may try to resolve the error. You must also run the diagnostics of material, especially the scanner memory, which provides the manufacturer of the system. For more information about these procedures, see the manual of your computer.

  The error that generates this message may occur after the first reboot during Windows Setup, or after installation is complete. A possible cause of the error is lack of disk space for installation and the system BIOS incompatibilities. For any problems during the installation of Windows that are associated with lack of disk space, reduce the number of files on the hard disk drive target. Search and delete temporary files that you do not have to have, files hidden Internet, application backup files and files saved .chk , which contain fragments of files on disk scans. You can also use an another hard disk drive with more free space for the installation. You can solve the problems of BIOS by upgrading the version of the system BIOS.

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

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

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the entire file.
  http://www.NirSoft.NET/utils/my_event_viewer.html

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

  As examples:

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

  or in this format:

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

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

  BlueScreenView scans all your minidump files created during "blue screen of death," collisions
  Displays information on all the "crash" of a table - free
  http://www.NirSoft.NET/utils/blue_screen_view.html

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

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

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

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

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

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

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

  Enter this at the command prompt - sfc/scannow

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  In some cases, it may be necessary.

  The Options or Vista recovery disk Startup Repair

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

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

  I hope this helps.
  Rob - bicycle - Mark Twain said it is good.

• Blue Screen of Death UnMountable_Boot_Volume 0x000000ED

  I get the same message on two desktop computers.  Two of these errors occurred in few days when computers "freeze" while he was working and there was no way out except to turn off and loose.  Neither has been able to load Windows since!

  Both are running Windows xp professional that has been purchased for each computer an update for XP provided on these computers.  I UPGRADE the two original install discs, but I can't use the drive for repairs because the computer boots apparently directly from the HD.

  I still go into this loop.  Windows has encountered an error.  Please restart in: safe mode, last known config or normal etc).  Of course, none of these options do restart except the process of starting the same way.

  I got to the Console of Microsoft recovery with some extra options, but that takes me right to the Blue Screen of Death with details about the error message: Unmountable_boot_volume with the hex codes (the first being 0x000000ED on both computers).

  I found several solutions on the internet, but they all assume that you can go to Safe Mode and run other programs like Chckdisk.  But I just can't.  I got (accidentally I might add) on the screen of the Bios utility.  Maybe it's (HP) computers or age, but on one of the computers, the BIOS page it shows:

  Configuration of the BIOS:

  Master of the first string: Maxtor with numbers.

  First channel slave (none)

  2nd channel Master (HP DVD Writer)

  2nd channel slave (IDE-DVD-Rom 16 x)

  3rd channel Master (None)

  4 channel Master (none).

  In the BIOS utility menu, I tried the F5 to reset the values by default, recorded and released, but everything is still show no change.

  I spend more than 2 hours on the phone with HP trying to get this resolved nothing doesn't.  The technician that I talked to had no idea how to fix this error - even if he said "no problem we will fix that in a minute."  While with this technology, I disconnected everything, rebooted several times by pressing F8 F9, F10 and DELETE, F1.  Finally, he said that the best thing I could do was wipe my hard drive and reinstall the software.

  Of course this is not a solution if the start of corruption can be solved.  And besides, even if I was willing to do that (I'm not still), how the hell I get computers to reinstall the software for two obvious reasons: 1) I have windows XP upgrade disks are installed and 2) the computer cannot read the discs anyway.

  I searched and found a lot of "bugs" on the internet, so it must be a fixable problem.  But most of the solutions assume that you can access your BIOS and change (even if nobody ever says what you should change to?), and then run the patches since the installation of XP discs.  I was also on many other sites that provide a Bootable CD to start Windows XP, but I can not get my computer to see the CD before it starts up.  I tried all suggestions as press F2 when the computer is turned on, and then select boot from CD.  But while on a few occasions, I got the "press any key to boot from CD" (once accidentally so I do not know how to get this message again), it doesn't matter what key has been pressed, it just took me in the loop.

  Does anyone have an answer that starts from the beginning assuming that the computer will not read from the CD and walking then how to understand and fix this problem.  I am sure that there is someone out there who knows how to help with this error message.  At least I hope.  I'm not technical, please keep answers in simple language.  Thanks a lot for your help

  Hi LucyAdams,

  You can follow this link & check if the problem persists.

  When you restart your computer or upgrade to Windows XP, you receive the error message "STOP 0x000000ED UNMOUNTABLE_BOOT_VOLUME".

  
  Reference: Unmountable Boot Volume

  Hope the helps of information.
  Please post back and we do know.

• Intermittent blue screens of death.

  I have a Toshiba Satellite P205-S7402 app, works with Vista Home Premum SP2.  I've been doing the blue screens of death intermittently.  It has been about three weeks since the last one, then I had one night.  It says check recent changes to software or hardware changes.  The only changes I made were to update Windows. He finished an update just before that happens tonight.  I took a picture of the screen if there is a way to download it or send it to anyone who responds to this post.  When I get these I stop, restart and I'm usually good for a week or two...

  Hello

  Check with Toshiba Support, their drivers and documentation online and ask questions in the forums on
  known issues.

  Toshiba - Forums
  http://laptopforums.Toshiba.com/

  Toshiba - Contacts
  http://www.CSD.Toshiba.com/cgi-bin/TAIS/support/JSP/navShell.jsp?CF=su_contact

  Toshiba - drivers - access your model
  http://www.CSD.Toshiba.com/cgi-bin/TAIS/support/JSP/home.jsp?NAV=download

  Toshiba - Support
  http://www.CSD.Toshiba.com/cgi-bin/TAIS/support/JSP/home.jsp

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

  Pick up the pieces after a computer crash
  http://Windows.Microsoft.com/en-us/Windows-Vista/picking-up-the-pieces-after-a-computer-crash

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

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

  We can analyze the minidumps if make you it available to the SkyDrive or another file
  sharing sites (such as MediaFire). If you have problems to download the copy of minidumps
  for the office or in the Documents folder and download them from there.

  ZIP or download the content of the C:\Windows\minidump

  Use SkyDrive to upload collected files
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

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

  Also this, so you can see the probable bluescreens.

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

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

  Check out these utilities to see if information may be collected:

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

  -Free - BlueScreenView scans all your minidump files created during "blue screen of death," collisions
  and displays information about all accidents of a table.
  http://www.NirSoft.NET/utils/blue_screen_view.html

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

  MyEventViewer can be verified at the time of the blue screen (BSOD) within a second or so of the
  time of the BSOD to provide more information about the possible cause - see TIP.

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
  Set it for a bit before and after the time of the BSOD.
  http://www.NirSoft.NET/utils/my_event_viewer.html

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

  AppCrashView - free - a small utility for Windows Vista and Windows 7 that displays the details of all the
  application goes down has occurred in your system. The information breaks down is extracted from the .wer
  the files created by the Windows Error Reporting (WER) of the operating system component of each
  time that an accident has occurred. AppCrashView also allows you to easily record the list of accidents to
  text/html/csv/xml file.
  http://www.NirSoft.NET/utils/app_crash_view.html

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

• blue screen of death and no. INTERNET!

  armel seconds to turn on my computer, it goes to the blue screen of death (IRQ_LESS_THAN_OR_EQUAL). When I load in safe mode, I have no internet access and can not look for solutions or try to solve any problems... Help, please!

  Oh and a Vista.

  In addition to the suggestion of auggy you can try the following methods.

  Hello

  You did changes to the computer before the show?

  Method 1: If the problem does not occur in safe mode then put the computer to boot and check which third-party driver is causing the problem:

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

  Note: after a repair, be sure to configure the computer to start as usual as mentioned in step 7 in the above article.

  Method 2: You can also try the steps from the link to fix the problem:

  How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly

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

  Method 3: You can also view the following link to resolve the problem:

  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

  Note: steps also apply to Windows Vista.

• OfficeJet 6500 has more Blue Screen of Death

  Sometimes my laptop (Vaio VPCZ2, Win 7-64) Gets a Blue Screen Of Death when my 6500 officejet is printing. This occurs when the printer is connected via usb and also wireless. I have run all the programs of diagnosis of HP and re-installed the driver and software. I guess the problem is the printer driver. What can I do to fix this?

  Initially, I connected the printer to the USB 2.0 docking station. Same result; dbo. Now I connected the printer directly to the USB 2.0 laptop and the problem seems to be resolved. Thank you.

• All new computer, blue screen of death/accident

  My boyfriend and I bought a new computer 3 weeks ago, it was an e-machine. Kept crashing, got the blue screen of death error. Back to Best Buy for a new computer. Compaq Presario. Has taken a House. The same problem. Returned to Best Buy and exchanged for a new one, exact model. Exactly the same problem. Problem occurs when it is on Facebook, play games or even a game installed on the computer.

  I came to the conclusion after hours of research that the problem is Windows 7.  It is a brand new computer that I paid a lot of hard earned money for. It should not keep breaking without reason.  Was on the phone with HP tech support for over an hour, that still does not solve the problem.

  I don't know much about computers and what information you need, so I'll just tell you what's on the box. Let me know if you need more information.

  It is a Compaq Presario CQ5320Y PC with a processor dual-core AMD Athlon II X 2 240 Dual-core processor, 3 GB, 500 GB HDD, Nvidia GeForce 6150 SE graphics card.

  When it crashes it said space disk or something on a pilot. Launch of Nvidia and the updated graphics driver, it wouldn't let me update the driver for the card mother, says that there is a problem of incompatibiltiy.

  Here is the error message we continue to do.

  Signature of the problem:

  Problem event name: BlueScreen

  OS version: 6.1.7600.2.0.0.768.3

  Locale ID: 1033

  More information about the problem:

  BCCode: 1e

  BCP1: 0000000000000000

  BCP2: 0000000000000000

  BCP3: 0000000000000000

  BCP4: 0000000000000000

  OS version: 6_1_7600

  Service Pack: 0_0

  Product: 768_1

  Files helping to describe the problem:

  C:\Windows\Minidump\061910-15693-01.dmp

  C:\Users\lance\AppData\Local\Temp\WER-27830-0.SysData.XML

  I've always hated apples but I'm seriously thinking about getting one until Windows can recover, if that's even possible.

  As happens with more than one system, it probably isn't a Windows problem and not likely to be a hardware problem.  Looks like it's maybe a driver issue, but without more details, it will be difficult to know.  Add nothing to the system (software, hardware, etc.) after he unboxing and problems?  If you care about that resolve at all - and I don't really think, you should because you get the behavior with new systems (use the warranty and keep complaining the problem if it keeps recurring; get your money back if it is an option, and choose another brand of system.) Keep in mind that you've got a failed system [or the entire model is a dud!] and this should not reflect on Windows 7)-start by downloading the vacuum as described below.

  Start here:   you can download the c:\windows\minidump content to your SkyDrive and provide a link?

  To treat blue screens, following general tips:

  Consider running chkdsk on all partitions.  Leave complete chkdsk on each partition and see if that helps.

  Also consider running SFC/scannow.

  Other common suggestions include ensuring drivers are up to date (including video drivers), but also to ensure that you use the latest version of the BIOS.

  Consider the memory with memtest86 or Windows Memory Diagnostic test. Note that memory that passes the test is not necessarily good - he just failed a test.  Examine systematically to eliminate the system RAM - run with a few modules for awhile and see how things are going. Then try the other modules.

  If you start in safe mode, do you still feel bugs? What if you do a clean boot, or boot device?

  It may be useful to use the driver verifier.  To activate the... Driver Verifier start-> verifier.exe-> OK-> create standard settings - > then-> the names of the drivers select in a list-> next-> sort by provider-> select all non-Microsoft drivers-> finish and OK your way out of the dialog box.

  Then restart and use the system as you normally and wait for a problem.  In case the system does not completely start after activation of the Verifier, boot mode safe and run driver verifier and tell him to remove the changes.

  Wait for an error checking to happen after you have enabled the auditor as described and then transfer it to your SkyDriveand provide a link.

• Various blue screen of death windows 7, Asus laptop

  Experts/dear Microsoft community,

  Recently I had some problems with my laptop. I tried reformatting and everything but nothing seems to solve the problem long term, brief (2-3 days)

  My computer crashes (blue screen of death), whenever I play big games online. Games such as Company of Heroes, or Dota 2, etc. If I don't play these games solo (offline) I have no problems. Also all other programs work perfectly.

  I have a feeling that it has to do with my Asus laptop drivers, I tried to update, restore and re - install, but without result.

  To tell you that as the scenario for the crash: I start the game, I log on online, join a game. Then after 20 to 25 minutes of play online with no loss of FPS, it auto-shutsdown the game with absolutely no message, followed with an accident soon after, sometimes immediately.

  Here's the accident report I got the program: Whocrashed

  Look forward to hearing your suggestions.

  Concerning

  computer name: ICRASHEVERYWEEK
  Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
  Windows dir: C:\Windows
  Material: N61Ja, ASUSTeK Computer Inc..
  CPU: GenuineIntel Intel (r) Core i5 CPU M 430 @ 2.27 GHz Intel586, level: 6
  4 logical processors, active mask: 15
  RAM: 4140355584 total
  VM: 2147352576, free: 1929850880

  --------------------------------------------------------------------------------
  Crash Dump Analysis
  --------------------------------------------------------------------------------

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Friday, November 7, 2014 22:01:49 this computer crashed
  crash dump file: C:\Windows\Minidump\110714-44912-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x5996A0)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, November 7, 2014 22:01:49 this computer crashed
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheckEx + 0x0)
  Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80003BF56A0, 0xFFFFF880035AEE88, 0xFFFFF880035AE6E0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  Bug control description: this bug check indicates that a system thread threw an exception that the error handler did not.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Friday, November 7, 2014 18:29:29 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-17737-01.dmp
  This was probably caused by the following module: athrx.sys (athrx + 0x1C4F76)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88005E67F76, 0xFFFFF880035A7438, 0xFFFFF880035A6C90)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\athrx.sys
  product: Atheros CB42/CB43/MB42/MB43 network card driver
  company: Atheros Communications, Inc.
  Description: Atheros Extensible wireless device driver
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
  Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

  Friday, November 7, 2014 18:27:43 GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-14570-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x1421E5)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005B4A1E5, 0xFFFFF88003E795E0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION

  Friday, November 7, 2014 6:26:57 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110714-15194-01.dmp
  This was probably caused by the following module: atikmdag.sys (0xFFFFF88005B20B5B)
  Verification of error code: 0 x 50 (0x0, 0xFFFFF88005B20B5B, 0xFFFFF8A0024CF000, 0x0)
  Error: PAGE_FAULT_IN_NONPAGED_AREA
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: This indicates that invalid system memory was referenced.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. PAGE_FAULT_IN_NONPAGED_AREA

  Friday, November 7, 2014 17:57:41 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\110714-49280-01.dmp
  This was probably caused by the following module: atikmdag.sys (atikmdag + 0x899D90)
  Bugcheck code: 0xBE (0x12F9A6860, 0xFFFFF880035BC560, 0xFFFFF880062ACD90, 0xE)
  Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
  file path: C:\Windows\system32\drivers\atikmdag.sys
  product: ATI Radeon Family
  company: ATI Technologies Inc.
  Description: ATI Radeon driver in Kernel Mode
  Bug control description: sounds if a driver attempts to write to a memory segment read-only.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
  Google search: ATI Technologies Inc. ATTEMPTED_WRITE_TO_READONLY_MEMORY

  Friday, November 7, 2014 17:55:49 this computer crashed
  crash dump file: C:\Windows\Minidump\110714-16692-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000395AA49, 0xFFFFF8800AB310C0, 0x0)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Saturday, November 1, 2014 8:24:12 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\110114-17550-01.dmp
  This was probably caused by the following module: rdyboost.sys (rdyboost + 0x2C476)
  Bug check code: 0x1000007E (0x0, 0xFFFFF880035248B8, 0xFFFFFFFFC0000005, 0xFFFFF88003524110)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\rdyboost.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: driver for ReadyBoost
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.

  Saturday, November 1, 2014 8:22:52 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\110114-18142-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  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 control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Wednesday, October 15, 2014 9:09:56 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\101514-50856-01.dmp
  This was probably caused by the following module: athrx.sys (athrx + 0xF9D77)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880051BED77, 0xFFFFF880033A7708, 0xFFFFF880033A6F60)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\drivers\athrx.sys
  product: Atheros CB42/CB43/MB42/MB43 network card driver
  company: Atheros Communications, Inc.
  Description: Atheros Extensible wireless device driver
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  A third-party driver has been identified as the likely cause of the system error. It is suggested that you search for an update the following driver: athrx.sys (pilot device wireless Atheros Extensible, Atheros Communications, Inc.).
  Google search: Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

  --------------------------------------------------------------------------------
  Conclusion
  --------------------------------------------------------------------------------

  13 dumps were found and analysed. Only 10 are included in this report. 2 third party drivers have been identified to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  athrx.sys (Atheros Extensible, Atheros Communications, Inc. wireless device driver.)
  atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.)

  If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

  Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  Analysis of Dump 1Crash
  --------------------------------------------------------------------------------

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

  Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-17004-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
  Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
  Error: CID_HANDLE_DELETION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: this bug control appears very rarely.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 5:41:45 PM GMT crashed your computer
  crash dump file: C:\Windows\memory.dmp
  This was probably caused by the following module: ntkrnlmp.exe (nt! KeBugCheck + 0x0)
  Verification of error code: 0 x 17 (0x0, 0x0, 0x0 0 x 0)
  Error: CID_HANDLE_DELETION
  Bug control description: this bug control appears very rarely.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 12:15:52 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\101314-17784-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x2EDF95)
  Bug check code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003145F95, 0xFFFFF88004650448, 0xFFFFF8800464FCA0)
  Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a system thread threw an exception who did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 11:09:34 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-14320-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0xA (28, 0 x 2, 0 x 0 x 0, 0xFFFFF80002F21D80)
  Error: IRQL_NOT_LESS_OR_EQUAL
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Monday, October 13, 2014 2:53:45 AM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\101314-46987-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x3B (0xC0000005, 0x0, 0x0, 0xFFFFF88002DA2910)
  Error: SYSTEM_SERVICE_EXCEPTION
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an exception happened during execution of a routine that passes from non-preferred to the privileged code code.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  Sunday, September 28, 2014 17:57:12 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\092814-16926-01.dmp
  This was probably caused by the following module: dxgmms1.sys (dxgmms1 + 0xC0A1)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\drivers\dxgmms1.sys
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: DirectX Graphics MMS
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in a standard Microsoft module. Your system configuration is perhaps incorrect. Maybe this problem is caused by another driver on your system which cannot be identified at this time.
  Google search: Microsoft Corporation KMODE_EXCEPTION_NOT_HANDLED

  Monday, September 22, 2014 6:50:05 PM GMT crashed your computer
  crash dump file: C:\Windows\Minidump\092214-42525-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75BC0)
  Bugcheck code: 0x1A (0xFFFFF780C0000000, 0x1DEE, 0 x 5003, 0x420700003BD8)
  Error: MEMORY_MANAGEMENT
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that an error occurred serious memory management.
  This could be a case of corruption of memory. The corruption of memory more often happens because of software errors in the defective drivers buggy, not because of RAM modules.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

  --------------------------------------------------------------------------------
  Conclusion
  --------------------------------------------------------------------------------

  7 dumps were found and analysed. A third-party driver has been designated to be the cause of breakdowns of the system on your computer. It is strongly recommended that you check the updates for these drivers on their corporate Web sites. Click on the links below to search with Google for updates these drivers:

  dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)

  If no updates for these drivers is available, try searching with Google on the names of these drivers in combination errors that have been reported for these drivers and include the brand name and model of your computer as well in the query. This often gives interesting results of the discussions of the users who have similar problems.

  Read the WARNINGS GENERAL topic for troubleshooting failures of the system for more information.

  Note that it is not always possible to say with certainty whether a reported driver is in fact responsible for crash your system or cause is in another module. However, it is suggested that you look for updates for the products that these drivers belong to and regularly visit Windows Update or activate the automatic updates for Windows. In case a piece of defective material is originally wrong, a Google search on the errors of control of bug with the name of the model and brand of your computer can help you to deepen this review.

  PC! PK

  These two were related to the material.  Specifically of the RAM.  Please run memtest

  

• Blue screen of death situation

  Whenever I start some games (Borderlands 2, FEAR3, the two portals and a few others), I get the blue screen of death with these codes BCP

  BCCode: 124

  BCP1: 0000000000000000

  BCP2: FFFFFA800DB8D7B8

  BCP3: 0000000000000000

  BCP4: 0000000000000000

  OS version: 6_1_7601

  Service Pack: 1_0

  Product: 256_1
  I'm not very good with computers, but this situation let me no choice to ask people for help
  Does anyone have a suggestion/help?
  Thank you
  Stop 0 x 124 is a hardware error

  If you are overclocking try to reset your settings to standard processor and see if that helps.

  If you keep getting the BSOD here are things more than you may want.
  This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.
  
  Stop 0 x 124 - what it means and what to try
  Synopsis:
  A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
  Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.
  

  Generic troubleshooting ' Stop 0 x 124 ":

  1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.
  (2) ensure that the machine is sufficiently cooled.
  If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).
  3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
  It is best to run the latest drivers anyway.
  (4) update the BIOS of your motherboard according to the manufacturer's instructions and clear CMOS.
  Their website should provide detailed instructions on the brand and model-specific procedure.
  (5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
  At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.
  6) trying (stress) test these hardware components that can be put to the test artificially.
  The most obvious examples are the RAM and HDD (s).
  For the RAM, use the 3 rd-party memtest86 utility to run several hours a test value. (6-8 passes to stress the ram)
  For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".
  Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.
  7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.
  Who stops working mitigate the problem of the 0 x 124, jump to the next step.
  If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.

  
  Smash back, obviously the latest addition of software may be somehow connected to the root cause.
  If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
  Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:
  (8) clean and carefully remove the dust inside the machine.
  Reinstall all memory modules and connectors.
  Use a can of compressed air to clean the RAM DIMM supports as much as possible.
  (9) If all else fails, start removing items of hardware one by one in the hope that the culprit is something non-essential that can be eliminated.
  Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

  If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

• How to troubleshoot audio issues cause by the blue screen of death?

  I faced a problem with my audio laptop. This operating system: Windows 7 Home Premium SP1. He has some kind of problem when I watch a movie, I can't hear any sound coming through the speakers, and even when I plugged in a headset, the same thing always happens. The problem occurs after I have reformat my laptop because of the blue screen of death.

  Hi Luqmanmuaz,

  Sound problems can be caused by cables that are not connected properly, damaged drivers, incompatible drivers, sound settings, missing updates and problems with your sound card.

  See this article to resolve the problem of aid:

  No sound in Windows

  http://Windows.Microsoft.com/en-us/Windows/no-sound-help#no-sound=Windows-7&V1H=win8tab1&V2H=win7tab1&V3H=winvistatab1&v4h=winxptab1

  Reference:

  Tips for solving common audio problems

  http://Windows.Microsoft.com/en-us/Windows7/tips-for-fixing-common-sound-problems

  Let us know the status of the issue. If you need help, please after return. We will be happy to help you.

• Paviljoen dm1-3125ed: power adapter causes a blue screen of death

  Regularly, I get a blue screen of death on my portable entertainment dm1 which is 4 years old now. After lots of research and the elimination of the possible causes, I discovered that the problem only occurs with the associated map. When I work on computer only battery seems fine. I replaced the power supply, but that has not solved the problem. Any ideas?

  I have upgraded to Windows 10 some time ago and the problem seems to be resolved. Probably a driver problem which was solved by the upgrade.

• When I print, I get the blue screen of death.

  I'm running an Asus U47A, intel i7, 8 GB of ram.  Bought a printer cheap for the College, the printer HP Deskjet 1000 J110a (printer of $ 30 million).  Please don't tell me I'm cheap and I should have bought the model upward, it would not be useful.  Whenever I have print or the print job will complete successfully, either during the print job, my PC will crash and gives me the blue screen of death.  What should I do? I uninstalled the printer drivers, reinstalled them, check the updates, and install them directly from the HP site... you name it.  I am ready to throw my head through the wall because I need to print frequently and having my computer crash in the middle of a document is not what I need.

  Any help would be greatly appreciated, thank you very much.

  In addition, the issue may be the iusb3xhc.sys:

  Bugcheck 1E, {0, 0, 0, 0}

  WARNING: Unable to verify timestamp for iusb3xhc.sys
  ERROR: Module load completed but symbols can be loaded for iusb3xhc.sys

  The iusb3xhc.sys, which is dated December 5, 2011 is an Intel USB 3.0 driver.

  Try to update the iusb3xhc.sys by installing the next update:

  http://Downloadcenter.Intel.com/Detail_Desc.aspx?DwnldID=21129

  The same error was reported by other users, as in the following link:

  http://www.SevenForums.com/crashes-debugging/236644-BSOD-mostly-when-printing-photos-Ntoskrnl-exe-iusb3xhc-sys.html

  If the error persists, try the printer on another USB port such as the USB 2.0 port.

  You might also uninstall the Intel USB 3.0 driver and let the USB ports operate at 2.0 speed as which seems to have stopped errors blue screen in the link above for a user.

  Also, another printer, not necessarily a more expensive, but a different brand or model may not exhibit the same problem.

  You might try using a printer if possible.

• Blue Screen of Death: Driver IRQL not less or equal (Windows 8)

  So my computer started to plant a month ago and gives a blue screen of death. It occurred about once a day, usually by playing games. Does anyone know what I can do to fix this?

  Here are my files dmp for the last two accidents.

  https://onedrive.live.com/redir?RESID=CFF15ADE8F05C8A2%21147

  PW

  Check enabled, but don't have not 'take' GIS behave pilot.  In all cases, this accident was related to nVidia Display Driver nvlddmkm.sys.  I remove the current driver and install the latest driver available.  Yours is about a year.  You need to re - install, even if the driver is on the same date that drivers become often corrupt

• Blue Screen of Death-unable to start

  My brother could not open his laptop.

  He had his laptop for about a year.

  The problem he knows is that he received the blue screen of death.

  We tried to restart but it does not help.

  When we press the power button it lights, loads, and then the blue screen of death and said it will automatically fix it for us by restarting it. It just flashes and I didn't see even the error code or anything like that. Restart the computer, the same thing over and over again. As a loop.

  My brother has a Dell laptop, inspiron 15z.

  Help, please!

  Hello

  In 'some' case will help this article.

  Crashes Windows or freezes
  http://support.Microsoft.com/kb/2681286

  Do not forget to check with support of system manufacturer (manufacturer of motherboard for custom
  online systems), their resources and the drivers and ask in their forums (if any)
  on known problems. Don't forget to update BIOS, drivers of low level chipset,
  and the other pilots of major on-board and separate devices. Those who alone can
  set all or part of these issues.

  Note the use of Win Key + X and Win Key + W (to go on the Control Panel, Run and parameters
  According to needs). Win + D key calls the office and using Win Key active / disable the Office
  and the splash screen.

  Translate Windows 7 methods and use them on Windows 8.

  Resolution of the blue screen in Windows 8/8.1 errors
  http://Windows.Microsoft.com/en-CA/Windows-8/resolve-Windows-blue-screen-errors

  Resolve errors stop (blue screen) in Windows 7, has a section for if you can or can not
  Start Windows (applies to Windows 8). If you cannot start Windows 8 try using a repair
  Disc (see methods of doing a below) to access Mode without failure and other troubleshooting
  steps.
  http://Windows.Microsoft.com/en-us/Windows7/resolving-stop-blue-screen-errors-in-Windows-7

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

  http://answers.Microsoft.com/en-us/Windows/Forum/Windows_7-system/sometimes-i-get-a-blue-screen-when-using-IE-8/c675b7b8-795f-474d-a1c4-6b77b3fcd990

  We can analyze the minidumps if make you it available to the SkyDrive or another file
  sharing sites (such as MediaFire). If you have problems to download the copy of minidumps
  for the office or in the Documents folder and download them from there.

  ZIP or download the content of the C:\Windows\minidump

  Use SkyDrive to upload collected files
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

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

  Also this, so you can see the probable bluescreens.

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

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

  Check out these utilities to see if information may be collected:

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

  -Free - BlueScreenView scans all your minidump files created during 'blue screen of death '.
  hangs and displays information about all accidents of a table.
  http://www.NirSoft.NET/utils/blue_screen_view.html

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

  MyEventViewer can be verified at the time of the blue screen (BSOD) to in a
  second or so time of the BSOD to provide more information as possible
  cause: see TIP.

  MyEventViewer - free - a simple alternative in the standard Windows Event Viewer.
  TIP - Options - Advanced filter allows you to see a period of time instead of the whole of the record-
  Set it for a bit before and after the time of the BSOD.
  http://www.NirSoft.NET/utils/my_event_viewer.html

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

  AppCrashView - free - a small utility for Windows Vista and Windows 7 which shows the
  Details of all application crashes occurred in your system. The information of the plant are extracted
  the .wer files created by the Windows Error Reporting (WER) of exploitation component
  system each time that an accident has occurred. AppCrashView also allows you to easily record the
  list of accidents to the text/html/csv/xml file.
  http://www.NirSoft.NET/utils/app_crash_view.html

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

  Windows 8 includes special discount methods (keep files and settings) or a reset
  (new installation remove all).

  How to restore, refresh or reset your PC
  http://Windows.Microsoft.com/en-us/Windows-8/restore-refresh-reset-PC

  How to create a system image to refresh your PC in Windows 8
  http://support.Microsoft.com/kb/2748351

  How to update Windows 8
  http://www.eightforums.com/tutorials/2293-refresh-Windows-8-a.html

  How to reset Windows 8
  http://www.eightforums.com/tutorials/2302-reset-Windows-8-a.html

  If you have need of a system repair disc or other methods:

  How to create a "system repair disc" (CD/DVD) in Windows 8
  http://www.eightforums.com/tutorials/2855-system-repair-disc-create-Windows-8-a.html

  How to create a recovery USB in Windows 8

  http://www.eightforums.com/tutorials/5132-recovery-drive-create-USB-flash-drive-Windows-8-a.html

  How to start on the "System Recovery Options" in Windows 8
  http://www.eightforums.com/tutorials/2269-system-recovery-options-boot-Windows-8-a.html

  Boot to the tip "Startup parameters" in Windows 8
  http://www.eightforums.com/tutorials/4924-advanced-startup-settings-boot-Windows-8-a.html

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

• Blue screen of death WITHOUT Flash Player!

  When I try to watch video on YouTube I have Blue Screen Of Death. Sometimes after 1 min and sometimes after 10 min. I have installed Adobe Flash Player because it is not necessary to watch videos on YouTube. I checked disable "enable hardware acceleration and I always get BSOD.» I am running Windows 8.1 with all the updates, and also I've always updated Firefox when there is a new update. I tried to install Flash Player and tried all the solutions I found on the internet but non of them work so I uninstalled Flash Player. On Google Chrome, everything works normally, but I don't want to switch to him whenever I want to watch some videos in the fear of having BSOD. Please if anyone has a solution or an idea, it would be very useful. Thanks in advance!

  Hmm, since you have already disabled the main hardware acceleration, it could be a problem with the video (or audio) decoding. For video decoding, you can try these setting changes:

  (1) in a new tab, type or paste Subject: config in the address bar and press enter/return. Click on the button promising to be careful.

  (2) in the search above the list box, type or paste media and make a pause so that the list is filtered

  (3) double-click the preference media.directshow.enabled to true to false

  (4) double click on the media.mediasource.mp4.enabled preference from true to false

  (5) double-click the preference media.mediasource.webm.enabled to false to true

  (6) double-click the preference media.windows - media - foundation.enabled from true to false

  The effect of everything that should be blocking MP4/h.264 decoding and place you in the latest format WebM (VP9) YouTube. You can check the result on this page, but that might not show up after leaving Firefox and start it again:

  https://www.YouTube.com/HTML5 (the two h.264 should be red)

  It's not so convenient for other video sites, but I'm curious to know if it helps on YouTube or has the same problems.