Similar Questions

• Blue screen of death during recovery

  Apparently, the latest updates from MS caused problems and I had the blue screen of death during the start several times on my Pavilion p6610f desktop computer. I try a system recovery and got the screen died shortly after the recovery began. Now it does not start or even turn on a screen.  Any help would be appreciated.

  Well, this is my fourth attempt at this announcement, I hope it will work this time.  Below are my answers to your questions.

  Hello jp-3,

  Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the Forums of HP, I would like to draw your attention to the Guide of the Forums HP first time here? Learn how to publish and more.

  I read your post about how you are not able to boot your Windows computer after attempting a recovery, and I'd be happy to help you! To start, I have to ask you a few questions:

  Mech Hi and thanks for your help.

  • What is product and model number from your desktop?

  It is a Pavilion p6610f desktop PC

  • What version of Windows you have installed on your computer?

  I was running 7 Home Pro

  • Has your computer finished all his important updates from Windows?

  The updates had been installed, which was when I started to have problems

  • Have you updated your drivers from HP the HP SupportWizard?

  I didn't have a chance to update anything after you restart MS. updates He immediately started crashing. I restarted three times and got a truncated blue screen every time, that's why I tried the recovery.

  • What is a current or recent problem?

  He started just after the latest version of Windows update.

  • You are able to get an image from another monitor?

  In general, I run two monitors (bothHP) via USB converter j5create JUA310, which I unplugged in case of conflict. It crashed with two configuration simple and double monitor. When I was running food, I had only the primary monitor upward.

  In the meantime, I recommend that you follow this document on screen is blank after you start the computer. This should help with the display on your screen when you start first to the top of your computer.

  I unplugged everything - HP Color laser printer duplicator Kensington USB port and USB mouse Logitech wireless (wired mice HATE!). Had previously removed just in case USB Sandisk flash drive. The computer started, monitor went up, and I received a message "windows recovered from an unexpected shutdown - check online solutions. Did respond to the message again. Did not try a BIOS update.

   

  Thanks for your help!

  Please re-post with the results of your troubleshooting, as well as the information requested above. I look forward to your reply!

  Concerning

  MechPilot
  I work on behalf of HP

• KB2503665 causes a blue screen of death during restart

  I'm on a Samsung Q210 running Windows Vista Home Premium Service Pack 2 and used to have automatic updates enabled. Yesterday after installation of updates, the PC crashed with a BSoD during boot. I used Safe Mode to uninstall the updates one by one, and I've identified KB2503665 to be causing the blue screen of death. I tried to contact Microsoft support, but for some reason any their site tells me my ID of the computer cannot be used in the country, I reside (although I am sure that the version of Vista and the serial number are 100% legit).

  Is it possible to configure the automatic updates as it automatically excludes this update in the future?

  Hello

  1. What is the blue stop screen error message?

  You can follow the methods below and see if it works very well.

  Method 1

  Step 1

  You can temporarily disable the anti-virus.

  Disable the antivirus software

  http://Windows.Microsoft.com/en-us/Windows-Vista/disable-antivirus-software

  Important note: Antivirus software can help protect your computer against viruses and other security threats. In most cases, you should not disable your antivirus software. If you need to disable temporarily to install other software, you must reactivate as soon as you are finished. If you are connected to the Internet or a network, while your antivirus software is disabled, your computer is vulnerable to attacks.

  Step 2

  You can try to download and install the update manually and see if it works very well.

  http://www.Microsoft.com/download/en/details.aspx?ID=26275

  Method 2

  If the problem persists, you can auto hide the update.

  (a) click Start, point to all programs, and then click Windows Update or Microsoft Update.

  (b) click on custom.

  (c) click to uncheck the box next to the update you want to hide.

  (d) develop the update you want to hide, and then click to clear the don't show this update again check.

  (e) click on review and install the updates.

             

   

• 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

  

• Installed the network updated drivers hp support page now I get the blue screen of death

  Installed the network updated drivers for my laptop hp support page and now I get the blue screen of death a few minutes of Internet usage.

  http://h10025.www1.HP.com/ewfrf/wc/softwareCategory?OS=4063 & LC = on & CC = US & DLC = in & sw_lang = & Product = 5171...

  I can reboot the computer, but it only works for a little bit before again becoming the blue screen.

  I tried to download and reinstall the hp 8 drivers network twice now. (Product number: QJ793AV-#ABA)

  I am running windows 7 (x 64) and downloaded all the updates as well.

  Any help would be greatly appreciated.

  I made an another windows update and seems to be ok for now

• Windows 7 - Crash blue screen - STOP: 0X000000F4

  Hi all

  Windows 7 - Crash blue screen - STOP: 0X000000F4

  Screen shows e blue screen will display the following error code:

  STOP: 0X000000F4 (0XFFFFFA800C4C4B10, 0XFFFFFA800C4C4DF0, 0 X 0000000000000003, 0XFFFFF8000418FE20).
  I tried to restore the mode, the safe & all the option available to start properly.  Given that I have no DVD of windows 7 to re - install windows again.
  My question is as follows:
  -Is - error code says something.
  -A way to re - install windows without CD or DVD or save the image.
  -Also, I can read and access data from the C: & D: drive in cmd in restore mode guest mode.
  Waiting for your suggestions.
  concerning
  Jagdish kone

  Blue_Screen_image_.PDF

  Hi Philippe,.

  Thanks for your reply. I want to reinstall windows on the same SSD. Given that the SSD drive works great as external drive.

  So please could you confirm, how do I reinstall windows again. As I see there are recovery drive comes when I use the SSD as external drive.

  Waiting for your suggestions.

  Concerning

  Jagdish

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

• I tried "Remapping ACTIVE" in BIOS > Advanced tab in my Windows 7 Pro 64 bit, 8 Gb RAM (3.24 usable) computer and get the Blue Screen of Death.

  My computer is

  Intel Core i7 860 @ 2.80GHz processor
  Installed RAM 8 Gb (usable 3.24) - G.SKILL RIPJAWS, DDR3 1600 GB PC3-12800 2 x 4 sticks.
  System type: 64-bit
  Motherboard: ASUSTek Comp Inc.  Model: P7P55D
  BIOS Date: 2009-12-07 Ver: 08.00.15

  Operating system: Windows7 Professional 64-bit Service Pack 1

  GeForce GTX 275
  Tried "Remapping ACTIVE" in BIOS > tab advanced, then restarted and the system was fine and kicked + 100%
  (Checked system properties - display of 8 GB of RAM installed perfectly usable)
  then stop.  Then restarted the system, but after the system attempts to restart I get "Blue Screen of Death" - unstable system and "Dumping Memory.  So now, he is off again.
  Necessary assistance in this regard, been looking for solution for a while.

  Dear Gerry,

  I think I solved my problem.

  I have reset the motherboard and CMOS by removing the battery.

  I now get on my system properties
  -installed memory 8Gb and (usable 6.99)

  Thanks for your help once again.

• 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

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

• Crash / blue screen / not freezing Vista - no disk error - no viruses?

  Hey there - I have a dell with vista OS pc. For a week simply freezes small without apparent reason shortly after the start of vista. It seems not
  Plan of exactly when it freezes. I tried not to use some programs, nothing helps - the motive seems to be that if I use a microsoft program - crash of things - I can use firefox etc. without problem. Running in safe mode is very good, and I have access to all my files this way. So far, I have:

  1 received all the important data from the system to a PC on a network in windows 7
  2. tried several restore points - did not help
  3 run several virus - including ms security essentials scans and FSecure online scanner. both have not reported any problem
  4. in the start menu I have run diagnostics from the dell system - which don't report no disk error
  5. starting at cmmd line run chkdsk and chkdsk /f - no effect
  6a ran the event viewer to check what was going on - who himself, then crashed.
  7. waived after 6 and thought, I'd ask the experts instead! :)

  What should I try next?

  Thank you and best regards,
  Howard
  PS quite happy to reformat if you can send me a link to a tutorial / instruction list for this?

  Hello

  Do not forget to check with Support from Dell, their online documentation, diagnostics, drivers and ask in their forums
  for problems known.

  Dell support
  http://support.Dell.com/

  Dell support drivers - product manual & warranty Info (left side) - and much more
  http://support.Dell.com/support/index.aspx?c=us&l=en&s=DHS

  Dell forums
  http://en.community.Dell.com/forums/

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

  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.

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

• Crash blue screen when I use the internet? Urgent need help, thesis at the end!

  my laptop was pretty rubbish for a while, but now whenever I connect to the internet I get about 30 seconds before the thing of crash dump blue screen appears.

  The error report details are

  -System

  -Supplier

  [Name]  Service Control Manager
  [Guid]  {555908D1-A6D7-4695-8E1E-26931D2012F4}
  [EventSourceName]  Service Control Manager
   
  -EventID 7026

  [Qualification] 49152
   
  Version 0
   
  Level 2
   
  Task 0
   
  Opcode 0
   
  Keywords 0 x 80000000000000
   
  -TimeCreated

  [SystemTime] 2010-12 - 12T 09: 50:42.000Z
   
  EventRecordID 283429
   
  Correlation
   
  -Execution

  [ProcessID] 0
  [ThreadID] 0
   
  Channel system
   
  Jo computer PC
   
  Security

  -EventData

  param1 aswSP aswTdi spldr Wanarpv6
   
  I can use internet in safe mode. I do a virus check. Device Manager it says the 4to6 adapter #7 and the ISATAP #15 card do not work properly, but there seems to be no updates for them. I tried unchecking IpV6 on my network card. This did nothing.

  I tried to restore to an earlier point, and it does not help.

  Hello

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

  http://social.answers.Microsoft.com/forums/en-us/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

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

  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 and happy holidays!

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• Windows blue screen of death (ASF) when I play Garrysmod

  Windows blue screen of death (ASF) when I play Garrysmod

  Hey,.

  When I started to play Garrysmod (GMod) as blue screen arrives (happened 2 twice now)...

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.1.7600.2.0.0.256.1
  Locale ID: 2057

  More information about the problem:
  BCCode: 101
  BCP1: 0000000000000061
  BCP2: 0000000000000000
  BCP3: FFFFF880009E7180
  BCP4: 0000000000000001
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

  Operating system: Windows 7

  Graphics card: Nvidia Geforce 9800 Gt

  If you want something else, ask here.

  Help, please!

  Thank you

  Christopher Kelly

  CEO Christopher Kelly - ChrisJets432 - ChrisJets Corporation - Check http://cjcw.sm4.biz/ for updates, etc.

  Right, I found the problem, the card (s) has an addon called HDR source and what is the cause of the crash.
  For example on gm_construct that I never go on the plan, due to the fact it triggers it

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

• Crash blue screen and restart

  Hi all!

  I have a blue screen and it's really annoying.

  Maybe 3-4 days, I have reinstalled Windows because of an error on a blue screen. It worked without problem, quick, and there no crash so far.

  Here is the error code:

  Signature of the problem:
  Problem event name: BlueScreen
  OS version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033

  More information about the problem:
  BCCode: c2
  BCP1: 0000000000000007
  BCP2: 000000000000109B
  BCP3: 00000000041F000C
  BCP4: FFFFFA816C18B3A0
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\101712-24460-01.dmp
  C:\Users\Beams\AppData\Local\Temp\WER-27909546-0.SysData.XML

  Read our privacy statement online:
  http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409

  If the online privacy statement is not available, please read our offline privacy statement:
  C:\Windows\system32\en-US\erofflps.txt

  I couldn't find any help online.

  If this can help:

  CPU: Intel Core i7 - 2600K @ 3.4

  8 GB RAM

  Mobo ASUS - P67

  Graphics card: ASUS GTX560 Ti

  Thanks for reading.

  Hello

  something about the control bug 0xC2 is here:

  http://msdn.Microsoft.com/en-us/library/ff560185 (v = vs. 85) .aspx

  Can you zip the minidump in the C:\Windows\Minidump folder files and make available (link) via Windows Live SkyDrive or similar site?

  The following link has information about the use of Windows Live SkyDrive:
  http://social.technet.Microsoft.com/forums/en-us/w7itproui/thread/4fc10639-02dB-4665-993a-08d865088d65

  LC