Blue screen of death whenever I have windows shutdown.

Similar Questions

• Windows Vista crashes, I get the 'Blue screen of Death' and I have to restart. Different errors each time it crashes.

  Windows Vista crashes, I get the 'Blue screen of Death' and I have to restart. Different errors each time it crashes. I tried to reinstall vista without success of the problem being fixed

  Hello

  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

  -------------------------------------------------------------------------
  Also this, so you can see the probable bluescreens.

  Windows Vista restarts automatically if your computer encounters an error that requires him to plant.
  http://www.winvistatips.com/disable-automatic-restart-T84.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 - now cannot load Windows (even in safe mode)

  Laptop last night (Satellite L500-19Z;) Win 7 64 bit) crashed while playing CIV4. Had a blue screen of death. before I had the chance to read one of the error messages about the computer restarted.

  It loaded windows in SafeMode very well then and informed me that he had loaded OK the problem safe mode will be linked to some recently installed software and I should uninstall programs I had installed until it loads normally. As it was late last night I closed and thought I would sort the morning (with the benefit of hindsight it may have been a mistake...).

  Today, when the computer tries to start, it tries a startup repair; Unfortunately it does not work every time and it says "Startup Repair tried several times but still cannot determine the cause of the problem"

  I looked at the paper it produces, but it passes all of the individual tests.

  I can't access also advanced recovery options system & support, that appears in the Startup Repair dialog box as it requires that I be connected, which apparently I am not (probably the machine never got to the windows screen connection before attempting repair system). The error message reads "you must be logged to access system recovery options. If you encounter problems to connect, please contact your computer administrator for help. Please click OK to restart the computer. »

  I had a go at the start in the advanced options (safe mode, safe mode with command etc., but the result is the same).

  I also tried the repair of your computer to the screen option options advanced boot, but after the screen where it asks you to choose the language and keyboard, I get the same error of connection mentioned above.

  Is it possible to repair or even run windows based hard drive recovery (do not have the DVD of recovery with me as I'm away from home for a few weeks) without connecting to windows? I expected here, but have not yet find a way to do it.

  (there is no disc in the disc drive, no other devices connected to the laptop - I tried with power outlet and the battery and have not noticed differences)

  Thank you
  James

  Hello

  Pitty, you cannot retrieve the HEXADECIMAL code
  On this side, I think that your HD or registry is damaged and you have to reinstall the entire system

  Good luck

  Post edited by: Praepositus

• Blue screen of death after I intalled Windows XP Prof

  OK Let's go I hope someone can help me! I have sinned in the eyes of Lenovo and deleted the partition of Nova Scotia on my Y710 and installed a dual boot XP Prof and Windows Vista Bussiness system not on different partitions, but on separate hard disks, I added an another 160gig hard drive to my system. I had to do this for reasons of bussiness log on my server of bussiness and like you all without TEACHER XP and Vista Bussiness and above can log on to a domain server, but now I have a problem with the two operating systems Vista Buss is very slow on the network and my biggest problem is Windows XP Prof who after a few minutes after it starts throw a blue screen and restarts just with a critical error message that this is the case whenever I keep on reinstall, but nothing seems to help. Please help guys I need this phone to work as my job become more behind whike I am struggling to untangle the computer I'm realt desperate at this point.

  Thank you so long

  Concerning

  Martin

  Hi skripatch

  Thanks a lot for trying to help, but I think I found the problem. The culprit was Norton Internet security 2008. I uninstalled and so far for the last two hours my computer has not crashed again. Maybe you can me why Norton will do and if it is possible that it was incompatible with one of the drivers of Lenovo. Another thing can u sugest a good security program preferably something I can buy and download online.

  Thank you

  Martin

• error sthive 999 #0 with Blue Screen Of Death, when I run Windows.

  Original title: error 999 sthive #0

  Windows Vista

  When starting to the point that he must run windows, it goes to blue screen and after a very long time 1-2 hours gives error message 999, etc..

  Ive tried F8, F11, return to factory settings, but no action complete despite his departure for several hours.

  I need to replace the hard drive?

  Hello

  What is you get the exact error message?

  Follow all the steps of the article which is also valid for Windows Vista.

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

• Nvlddkm.sys for my GeForce 6150SE nForce 430 graphics card driver causes a blue screen of death, whenever I look at a video of youtube for a long period of time. I have re-installed Windows 7 Ultimate 64-bit, and it always does.

  I run Windows 7 Ultimate 64 bit, Skype, Teamviewer, client Pidgin, mIRC, Firefox, Kaspersky Internet Security 2010, openDNS updater, iTunes, and Outlook 2007.

  This problem has caused a unbootible machine when it happened first. It stops happening when I uninstall the display nvlddkm.sys driver, but when it gets reinstalled via Windows U [date and I restart, it bluescreens.] When I reinstalled the operating system, I was able to work normally again. I'm afraid that this problem could start again however, please help me.

  Try the following drivers from NVIDIA:

  http://www.nvidia.com/object/win7_winvista_64bit_191.07_whql.html

  Uninstall the video drivers that are currently installed and turn off any antivirus real-time protection before installing the new drivers.

  Make sure that antivirus real-time protection is reactivated after the installation.

• I get the blue screen of death whenever I try to play a video - regardless of the source (you tube or CNN). Instant death! I tried to reinstall Adobe Flash player. Any help would be appreciated, if not his return to IE...

  Blue death screen / system crash when you try to play the video or to copy an image from the internet

  On further study, please do not go on the road to perdition as I trod.

  However, to do this: go to http://www.adobe.com/software/flash/about/ and right CLICK on the logo that is being charged. THEN: Navigate down until "settings", click it, and you should have the choice: "disable hardware acceleration". NOTE: If you do NOT have this choice, study the icons down quickly: on MY screen, the left-most is an icon that looks like a video monitor: click on it and give you the opportunity to "disable hardware acceleration".

  It works, if you can get it done before you get a BSOD! AND do not take the life of your computer in your hands by updating your video drivers. I do not really recommend doing that!

• Random Blue Screen Of Death after upgrade to Windows 7 Ultimate 64 bit

  I was running Windows 7 Ultimate 32 bit for many years without any serious problem. After the upgrade to Windows 7 ultimate 64-bit I was prey to a BSOD random. Sometimes I can get several BSOD in one day. Sometimes I could get any same-day heavy after multitasking.  The BSOD may occur during any task or when I try to quit. I have the latest drivers and BIOS. I disconnected all my equipment and refurbished it. I used the diagnostic tools to test my memory 4G and my Seagate 1 t SSHD hybrid and they passed. I changed the sata connection cable my HD to the MB. I did a Windows repair (scannow) and also done a repair install and it did not help. Although these questions is past the BSOD after upgrade to Win 7 64 bit, that I suspect may not be associated with Win 64 bit but could be hardware related. Any help to solve this issue will be appreciated.

  Kind regards

  Chris

  All 5 associated with your ATI video driver.

  Completely, remove the current (or software) driver and install the latest driver available.  For instructions on how to do read everything to update the drivers of my partner JMH3143 http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149 here

• I just upgraded to vista 64-bit for windows home 7 home 64-bit away from the occational blue screen of death. Now with windows 7 the problem of blue screen that happens all the time. How can I fix?

  More information about the problem:

  BCCode: 116

  BCP1: FFFFFA8003FC44E0

  BCP2: FFFFF8800FFD2230

  BCP3: 0000000000000000

  BCP4: 0000000000000002

  OS version: 6_1_7600

  Service Pack: 0_0

  Product: 768_1

  Files helping to describe the problem:

  C:\Windows\Minidump\122809-22526-01.dmp

  C:\Users\Owner\AppData\Local\Temp\WER-41667-0.SysData.XML

  The upgrade in the hope of resolving a problem, it's rarely a good idea.

  Bug Check 0 x 116: VIDEO_TDR_ERROR
  Bug VIDEO_TDR_ ERROR control has a value of 0 x 00000116. This indicates that an attempt to reset display driver and recover a timeout failed.
  [Source: http://msdn.microsoft.com/en-gb/library/aa469184.aspx]

  I suspect that you need an update of the graphics driver or a new card chart or food to cope.

  In any case this has nothing to do with Windows Update. Post here to get help: http://social.answers.microsoft.com/Forums/en-US/w7hardware/threads ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

• 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

  

• I have a windows 8 blue screen of death!

  I get the "blue screen of death" driver_irql_not_less_or_equal randomly throughout the my computer and ive downloaded 2 different programs that were considered very to solve this problem, but never solved or even escaped the blue screen for a long time. IM asking is someone can help me with this problem?

  Austin

  If it is under warranty, I would call their support

• Whenever I start my computer, I get the blue screen of death. I'm not getting in what concerns the opening of session and there is no prompt to start in safe mode. Whenever I start my computer the error code and message on blue screen are different.

  I have Windows Vista Home Premium. I was on the internet when my computer screen turned blue and a message told me that a problem has been detected and Windows has been shut down. He said that I had tried to do something with memory executable not executable (I don't have a note of the code). He said as he poured out memory. Now, whenever I start, the blue screen of death gives me different messages and different error codes. Today, he says:

  IRQL_NOT_LESS_OR_EQUAL

  and codes of error STOP: 0x0000000A (0x0000001B, 0 x 00000600, 0x810A90B0, 0x00000001).

  PC World say that they need to reinstall Windows, but I have some really really important files on there that I have not supported (I know, really stupid on my part) and they said they cannot guarantee their recovery. Is there another way to fix it?

  I've been on the forums and suggestions involve me to be able to connect to my computer. Blue screen hits me before I can log on, and there is no prompt to start in safe mode.

  Thank you very much!

  Try this to save your data:

  Data recovery:

  1. slave of your hard drive in another computer and read/save your data out there.

  2. put your Hard drive in a USB hard drive case, plug it into another computer and read/save from there.

  3 Alternatively, use Knoppix Live CD to recover data:

  http://www.Knopper.NET/Knoppix/index-en.html

  Download/save the file Knoppix Live CD ISO above.

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  http://isorecorder.alexfeinman.com/isorecorder.htm

  Download the Vista software from the link above.

  After installing above ISO burning software, right click on the Knoppix ISO file > copy the Image to a CD.

  Knoppix is not installed on your PC; use only the resources of your PC, RAM, graphics etc.

  Change the boot order in YOUR computer/laptop to the CD/DVD Drive 1 in the boot order.

  Plug a Flash Drive/Memory Stick, BOOT with the Live CD, and you should be able to read the hard drive.

  When the desktop loads, you will see at least two drive hard icons on the desktop (one for your hard drive) and one for the USB key.

  Click on the icons of hard drive to open and to understand which drive is which.

  Click the icon for the USB drive and click on "Actions > Change the read/write mode" so you can write to disk (it is read-only by default for security reasons).

  Now to find the files you want to back up, just drag and drop them on the USB. When you're done, shut down the system and remove the USB key.

  See you soon.
  Mick Murphy - Microsoft partner

• Windows 7 clean installation Blue Screen of Death (BSoD) on a loop of reboot

  Aloha everyone,
  I did an install customized windows 7 on a new Western Digital 1 TB sata hard drive, which has been formatted, partitioned, scandisk, and a ntfs c drive was created prior to installation.
  The installation ended safely.  I then install my screen reader, Window-Eyes, requiring a reboot.  After the reboot, I started to install critical updates to Windows.  On my fourth update and restarting, I got the blue screen of death, that of some people call a BSoD.  I rebooted and Windows itself restored to a previous state of good, of my just accept the default choice.  Then the rear computer works, but if I stop, restart I get the blue screen of death (BSod) is back, and the loop begins again, i.e. windows restores good condition that works well, until you stop, but on reboot - BSoD is BACK!
  I removed the automatic update option, I disabled ScanDisk, drivers updated, bluetooth devices, deactivated sideshow, etc., without any positive result.  I called Microsoft for assisstance and the technician acted like this isn't a known issue, but he assured me that he could solve the problem.  He took control of my computer remotely and do not tell me anything except that the computer would check and repair any problem on reboot, and if he did does not resolve the problem, I have to remember.  The computer has rebooted without the BSod, but I stopped to check if the loop went, and it is not!  To restart the BSOd was back.  It is to note that if I put the computer to sleep, I get a clean start, but stop, restart or hibernation, I get the blue screen of death (BSoD)!
  It is a Dell Dimension XPS 420 with a intel Q6600 processer, 3 GB of ddr2 memory, which came with OS Vista Home premium 32-bit.  The Vista system, the last time I got a BSoD has been for more than a year.

  After researching this problem on Google, it appears that there is a problem without a solution.
  I ran "which has crashed, you can get:
  http://www.resplendence.com/downloads

  The following accident report:
  Monday, December 21, 2009 23:23:44 your computer crashed
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA800573B060, 0xFFFFFA800573B340, 0xFFFFF80002D91240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\122109-16972-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Monday, December 21, 2009 20:22:10 crashed your computer
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\122109-33306-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Sunday, December 20, 2009 15:28:42 crashed your computer
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002ADC00C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\122009-17565-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Thursday, December 17, 2009 12:27:45 AM your computer crashed
  This was probably caused by the following module:
  Ntoskrnl.exe
  Verification of error code: 0 x 50 (1, 0xFFFFF80002A9300C, 0xFFFFFFFFFFFFFFD0, 0 x 0 x 0)
  Error:
  PAGE_FAULT_IN_NONPAGED_AREA
  Empty the file: C:\Windows\Minidump\121609-28111-01.dmp
  file path: C:\Windows\system32\ntoskrnl.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: NT Kernel System &
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Monday, December 14, 2009 20:59:21 crashed your computer
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA80059A3060, 0xFFFFFA80059A3340, 0xFFFFF80002DC4240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\121409-25506-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Sunday, December 13, 2009 02:17:55 your computer crashed
  This was probably caused by the following module:
  Wininit.exe
  Bug check code: 0xF4 (0x3, 0xFFFFFA80058A4060, 0xFFFFFA80058A4340, 0xFFFFF80002D8A240)
  Error:
  CRITICAL_OBJECT_TERMINATION
  Empty the file: C:\Windows\Minidump\121209-24648-01.dmp
  file path: C:\Windows\system32\wininit.exe
  product:
  Microsoft® Windows® operating system
  company:
  Microsoft Corporation
  Description: Application to Windows startup
  The accident took place in a standard Microsoft module. Your system configuration can
  be incorrect, perhaps the culprit may be another driver on your system which cannot
  be identified at this time.
  Conclusion
  6 dumps were found and analysed. Note that it is not always possible to
  assert with certainty whether a reported driver is really responsible for crashing
  your system or that the cause is in another module. However, it is suggested
  looking for updates for the products that these drivers belong to and regularly
  Visit the Windows Update or activate the automatic updates for Windows. In the case of a piece of
  defective material is in trouble, a Google search on the bug control
  Errors, as well as the name of the model and brand of your computer can help you investigate
  This further.
  end of the crash report.
  A side comment:
  Them are 56 reported problems, and none of them have solutions. If I go through each problem report and check for solutions, about 80% of the times I ask myself to send to Microsoft for more information about the problem and I click on send, but I always get the following:
  [Window title]
  Incident reports

  [Main instruction]
  Problem connecting to the Windows error reporting service

  [Content]
  Some of the reports can not be uploaded to the Windows error reporting service. Please try again later.

  [Close] »
  I tried several times with the same result, that is, the details of the problem which has need of Microsoft is not be received.  To this end, the problem will not be found.
  Thanks much for any help.
  Manny
  P.S. I'll never upgrade a Windows operating system.  My recommendation for anyone who is planning to upgrade to Windows 7 is to try first on a dual boot using the free download.  If it works for you, consider yourself lucky and buy the upgrade.  If it does not, then remove Windows 7 and stay with your old system.

  Please check your RAM for errors (use memtest86 + to test). "A programmer is just a tool that converts the caffeine in code" Deputy CLIP - http://www.winvistaside.de/

• Blue screen of death (stop 0x0000007B) after April Windows Update on XP Home.

  My machine (Dell Dimension 3100 with XP Home) home is set for automatic recovery of Windows updates. I reload often, but when I was forced to start again last week, I got the blue screen of death. Apart from the general BSOD error message, I got the stop code:

  STOP 0x0000007B...

  I forgot the subsequent stop codes, but search recall I was doing on them indicated drivers disk or storage-related problem.

  I ran all sorts of Dell diagnostics on my hardware, get absolutely no problem. Scan of a viral infection was also negative. A colleague help out me suggested removing the updates of Windows of April, he did help and usefulness of the ERD. XP loaded and started after that, if I had to go through a process of slooow restart for most updates. My office also now charge many times slower - I suspect drivers and services can't find what they expect to find and take considerable time to make mistakes.

  My Dell has a range of Intel (RAID-1) matrix installed. I strongly suspect that this pilot was in trouble after the April update Windows Update.

  So, what should I do to prevent this from happening again? I don't know the specific fix involved. I have disabled the automatic updates for now.

  TIA

  Rick

  Complete sweep of Kaspersky AV, booted from the CD, turned up negative, so I doubt that it is an infection.

  I'm sorry, but this does not exclude the possibility of infection. See step # 3 in my previous response, or contact Ms. PCSafety for assistance.

  Or see http://msdn.microsoft.com/en-us/library/ff559218 (VS.85) .aspx and/or http://aumha.org/a/stop.php#0x7b for more troubleshooting ideas.

  Or if you let Windows Update to install an update for the driver (never a good idea), try a roll-back of pilot.

  ~ Robear Dyer (PA Bear) ~ MS MVP (that is to say, mail, security, Windows & Update Services) since 2002 ~ WARNING: MS MVPs represent or work for Microsoft

• Blue Screen of Death After Windows Update

  I was out of the House one night and while outside, my cell phone went through a routine Windows Update and restarted (what he did specifically I'm not aware of). Unfortunately, when I came back, I met a blue screen of death. I tried a system repair and restoration of the system, and none of them worked. I'm typing this from my wife's computer as we speak. I am very anxious, and I would like to use my laptop again. If anyone can help, please reply as soon as possible.

  Visit the Microsoft Solution Center and antivirus security for resources and tools to keep your PC safe and healthy. If you have problems with the installation of the update itself, visit the Microsoft Update Support for resources and tools to keep your PC updated with the latest updates.

  MS - MVP - Elephant Boy computers - don't panic!