ASUS Zenbook Infinity - blue screen

Similar Questions

• Various blue screen of death windows 7, Asus laptop

  Experts/dear Microsoft community,

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

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

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

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

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

  Look forward to hearing your suggestions.

  Concerning

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

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

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

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

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

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

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

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

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

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

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

  Saturday, November 1, 2014 8:22:52 CEST your computer crashed
  crash dump file: C:\Windows\Minidump\110114-18142-01.dmp
  This was probably caused by the following module: ntoskrnl.exe (nt + 0x75B90)
  Bugcheck code: 0x1E (0x0, 0x0, 0x0 0 x 0)
  Error: "KMODE_EXCEPTION_NOT_HANDLED"
  file path: C:\Windows\system32\ntoskrnl.exe
  product: Microsoft® Windows® Operating System
  company: Microsoft Corporation
  Description: NT Kernel System &
  Bug control description: This indicates that a kernel-mode program generated an exception which did not catch the error handler.
  This seems to be a typical software driver bug and is not likely to be caused by a hardware problem.
  The accident took place in the Windows kernel. Maybe this problem is caused by another driver who cannot be identified at this time.

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

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

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

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

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

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

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

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

  Crash dump directory: C:\Windows\Minidump

  Dumps are enabled on your computer.

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

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

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

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

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

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

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

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

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

  dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)

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

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

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

  PC! PK

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

  

• Blue screen on Asus laptop when it is connected to the printer OfficeJet 4620 computer

  I have a laptop Asus U47A, Windows 7, 64 bit. When I connect my laptop to the printer Officejet 4620 via USB and it has print my computer gets the blue screen and turns off. This doesn't happen every time, however. I tried to uninstall and reinstall the printer software, and I tried to plug the usb cable to the port instead of port 3.0 2.0. None of this worked well. Any suggestions?

  This problem normally only when the USB 3.0 port is used and the Intel chipset that causes the problem has not been updated. First of all update and see if it helps. Here's my post on how to know who is who, but also update this driver:

  http://h30434.www3.HP.com/T5/printer-all-in-one-install-setup-e-g-Windows-8/handling-problems-with-USB-3-0/TD-p/2001211

  In addition, you need to maybe just remove the software and reinstall from the software available on the site of HP full setting:

  http://h10025.www1.HP.com/ewfrf/wc/softwareCategory?cc=us&LC=en&DLC=en&product=5191646

  Let me know if that helps you!
  

• Blue screen 0x0000009f DRIVER_POWER_STATE_FAILURE death in newly acquired ASUS laptop computer g750JM

  Hi, I get a blue screen of death every time in a while for no discernible reason. I've had this laptop for about 2 weeks, I just received my third blue screen of death about an hour ago. The location of the address is the same, bug control code, the driver is ntoskrnl.exe

  Landfills are:

  https://www.dropbox.com/sh/w7k1x6zs8c7i4bz/AADWTHwEluQNtq1gExw2rgB3a

  I hope someone can help

  Hello

  I've been scouring the internet for weeks looking for help with my BSOD problems.  I finally made a discovery that fixed it all and thought I'd share it with as many people as possible.

  Some background on my question:

  I installed the 337,88 and the beta drivers but kept on getting random BSOD due a DRIVER_POWER_STATE_FAILURE.  I watched the dump file and debugged myself as BlueScreenviewer offered no answers for me.  He showed a driver ntoskrnl.exe and dig more pci.sys has shown to be the culprit, but this may not be true.  More digging in the minidump gave nviddmkm.sys, so naturally I thought it was a driver problem. (I have a background inproramming, so I was able to do a pretty thorough analysis of the file).  I installed the 332,50 drivers and no more problems.  However, I was not satisfied with this solution.  I did more research on the internet and several other cases have been solved by powering down of overclocking.  I had already uninstalled GPUTweak, so what else could it be?

  Well, the BIOS has the answers.  Here is my solution:

  1. turn off your laptop.  (Full stop)
  2. press the power button.
  3. quickly and repeatedly hit the F2 key to enter the BIOS setup.
  4. go to the "Advanced" tab
  5 scroll down to "Graphical Configuration" and press the Enter"" key.
  6. highlight "Turbomaster setting" and press the Enter"" key.
  7. you will see two options, 'Activate' and 'Disable', choose 'disable '.
  8. Finally, press the "Esc" key and go to the tab "Quit" and "save changes and exit".

  You can now install the latest drivers without experiencing a BSOD.  I hope I helped.  If you guys have any questions be sure to ask me, I'l answer to the best of my ability.

• ASUS Zenbook UX32A BSOD with pilot error, out of State

  Original title: ASUS Zenbook UX32A driver power state failure

  Hello

  I hope that someone (anyone!) can help you. I experienced the dreaded blue screen of death about 2 weeks ago, now the computer simply refuses to open 'sleep' mode and is very slow when to start full is needed. I've updated the drivers (for as much as I can) and updated the laptop as well. Nothing has solved the problem. Help :-)

  The last referenced error iastora.sys (Intel storage driver):

  BUCKET_ID: 0x9F_3_POWER_DOWN_IMAGE_iaStorA.sys

  However, there may be a conflict between the iastora.sys and the excsd.sys (driver ExpressCacahe):

  KD >! devstack fffffa8004415060
  ! DevObj! DrvObj! DevExt ObjectName
  fffffa80066dcb10 \Driver\partmgr fffffa80066dcc60
  fffffa80059fc880 * ERROR: Module load completed but symbols could not be loaded for excsd.sys
  \Driver\excsd fffffa80059fc9d0 excsd0
  fffffa80066dc060 \Driver\disk fffffa80066dc1b0 DR0
  \Driver\ACPI fffffa8004342590 fffffa80044165b0
  > fffffa8004415060 \Driver\iaStorA fffffa80044151b0 00000040
  ! DevNode fffffa80044158e0:
  DeviceInst is 'SCSI\Disk & Ven_ATA & Prod_Hitachi_HTS54505\4 & 238af970 & 0 & 000000'
  ServiceName is "disk".

  What I might suggest is to uninstall ExpressCache, then update the Intel storage driver, then reinstall ExpressCache.

  There should be versions updated to ExpressCache and the Intel storage driver in the following link:

  http://support.ASUS.com/download.aspx?SLanguage=en&m=UX32A&p=3&s=411

  ExpressCache is no software required, so if you uninstall ExpressCache you can leave it uninstalled, if you wish.

• Error blue screen on Satellite Pro A10

  Hello

  I try to help my in-laws with their SPA10 Pro Satellite. I had set this up for them a few months ago and it was working fine.
  Now it reboots about two seconds after the "use last good configuration ' screen etc, gets to the screen again then restarts immediately to infinity, never a break on error message for long enough to see what he says.
  I managed to boot from the Windows XP home and got disc with respect to the repair or continue with the installation screen. When I asked the computer don't either TI stuck on blue screen almost immediately. The error message is
  STOP: 0X000000C5 (0X00000002, 0X00000001, 0X00000000, 0X8082B98B)

  This is beyond my skill level, someone can help?
  Thank you

  Hello

  It is not easy to tell what the problem is here and what your in-laws have made with this device. Try to start the machine in safe mode by pressing F8 at the beginning upward. What unit starts check a bit if some strange software is installed.

  If there is no important data, I advise you to install the new OS. On this way, you will be sure that it is not because of software. If the problem persists then is the question is more complicated and there may be a hardware failure.

  At the moment I can't tell you more. Try to make the clean OS install and post again on the results.

• Latest Skype causes Blue Screen of Death

  Whenever I have install/update Skype on windows 7 to the current version, I get a blue screen as I can't use older versions because he says "Skype cannot connect." Any help on any of these questions is accepted. Thank you.

  You have the well known problem of the Webcam HP HD [Fixed] .

  The last 6.16/6.18 Skype are causing BSOD on HP laptops with this installed webcam.

  You can try to uninstall the version 6.18 and install the previous 6.14.0.104 Skype version using the download links provided here:

  http://community.Skype.com/T5/Windows-desktop-client/ASUS-USB2-0-webcam-not-recognized-by-Skype-6-18...

  Be sure to turn off the automatic updates.

  Tools-> Options-> Advanced-> automatic updates-> turn off automatic updates

  The other option is to uninstall the HP drivers and install generic Microsoft webcam drivers.

  http://community.Skype.com/T5/Windows-desktop-client/query-about-BSOD-fix/m-p/3589407#M295633

• Install Windows server 2008 r2 blue screens before

  I try to install windows server 2008 r2 on my system and it blue screens right after that the disc is loaded in the ram.  I don't not even to the selection of installation phase. It crashes just after the windows logo charge. IM receives the stop error 0x0000001e.

  my system is as follows
  Asus rog crosshair iv formula
  processor AMD 1100 t blacke edition x 6
  16 GB of ram
  ATI radeon hd 6950 graphics card
  and several discs hard digital western
  If someone has a possible solution to this problem would be great because I won't have a chance to make it work. Windows 7, it works, boots and install perfectly on this machine, but I need to put the server on it.

  Hello

  Your question would be more by experts Windows 7 IT Pro Installation, Setup, and deployment Forum. Check out the following link.

  http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer

• Get the blue screen when you play a game (COD modern warfare 2), ID: 1044. At all the most recent drivers.

  This is part of the error code, if you need more just ask. (It's in Norwegian, but I guess you'd understand it anyway)

  Problemsignatur:
  Pa problemhendelse Navn: BlueScreen
  OS-versjon: 6.1.7600.2.0.0.256.1
  ID for nasjonal innstilling: 1044

  Tilleggsinformasjon om problemet:
  BCCode: 124
  BCP1: 0000000000000000
  BCP2: FFFFFA80082494B8
  BCP3: 0000000000000000
  BCP4: 0000000000000000
  OS version: 6_1_7600
  Service Pack: 0_0
  Product: 256_1

  I have all the latest drivers, and no update is available in Windows Update. When I check the event viewer, it is said:

  System

  - Provider of [ Nom ] Microsoft-Windows-Kernel-Power [ Guid ] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

  Event ID 41

  Version 2

  Level 1

  Task 63

  OpCode 0

  Keywords 0 x 8000000000000002

  - TimeCreated [ SystemTime ] 2009-11-16 T 12: 53:50.350843600Z

  EventRecordID 4618

  Correlation

  - Execution of [ ProcessID ] 4 [ ThreadID ] 8

  Computer:
  Motherboard:    ASUS P5E WS Professional
  Chart:           Sapphire Radeon HD 3870 X 2 1024 MB
  CPU:                 Intel Core 2 Quad Q9450
  RAM:                 OCZ PC2 - 6400 Platinum Vista PErformance Edition 8 GB (4 x 2 GB)
  Power:             Power PC & Cooling Silencer 750W

  Nothing is overclocked, and my cooling system is running on max, never had a problem with the heat.

  So what is the power of the nucleus, and why he will enter the blue screen only when I am games? And most importantly, how do I do?

  Thanks for the replies!

  sweppes

  sweppes,
  It was just a possibility that heat is a problem.  Also in your games if you operate in high res\max video settings you can turn them down to smaller settings and test.

  You also mentioned that the motherboard has not yet all drivers for Windows 7.  Maybe it's that you will have this kind of problem until you get correct chipset drivers.

  Mike - Engineer Support Microsoft Answers
  Visit our Microsoft answers feedback Forum and let us know what you think.

• How can I stop blue screen with stop error code (0x00000002, 0x00000000, 0x804e70ed)

  How can I stop blue screen with error code stop 0 x 00000050 (0xf05c371c, 0 x 0, 00000002 00000000, 0x804e70ed)

  If you are not real tied to the current installation of Windows - then a cloth and then reinstall are the best way to see if you can fix this

  Here's a suggestion on how to do a 'clean ': install
  [quote]
  For testing purposes, it is best to install Windows "clean".
  It is, basically, install the way that Microsoft intended (with the drivers from Windows Update).
  This procedure is for Windows 7, Vista is similar (but has 2 service packs)

  You will need your installation/recovery DVD (s) before you start.  Once you wipe the hard drive, there is no going back!

  1 back up all your data.
  It will wipe everything off of your hard drive, so what you want to keep should be backed up elsewhere.

  NOTE: If this is due to an infection, remember to analyze the data with current antivirus to another system to locate and remove malware.

  2. connect the system to the internet (if the system shows then disconnect from the Internet, do).

  3. use one of these free utilities to wipe the hard drive:
  DBAN ( http://www.dban.org/download )
  KillDisk ( http://www.killdisk.com/downloadfree.htm ).
  This will also remove the system recovery partitions - so the installation/restore DVD is essential!

  4 install Windows by booting from the installation/recovery DVD - DO NOT change any settings!

  5 visit Windows Update and get all updates

  6. check device for all unknown/disabled devices Manager - if there are unknown disabled devices, secure them with the latest drivers from the website of the manufacturer of the device (not the PC manufacturer)

  7 visit Windows Update and download the Service Pack 1 (normally under important updates).  Read these notes for installing SP1: http://support.microsoft.com/kb/2505743

  8 visit Windows Update and get any other available updates

  9 download, install and update a free antivirus, so it does not get infected during the test ( http://www.carrona.org/freeav.html ).

  If problems persist, then the problem is probably with your hardware.

  Warning: If you have an Asus motherboard, check the date on the file C:\Windows\System32\driver\ASACPI.sys.  2004/2005 is a problem, 2009,2010 is OK.  Updates are available on the Web from Asus site.

  Warning: If you have a Sony system, make sure that you do NOT have the 2007 version (or earlier) Extension of Firmware of Sony Analyzer (SFEP.sys).  To update this driver immediately!
  [/ quote]

• Blue screen: 0x7e during installation of windows xp

  original title: blue screen of death during the installation of windows xp

  I just bought a motherboard ASUS p5g41t-mlx with a Pentium E5400 2.7 GHz dual core and a hard drive when booting with the windows xp cd in, it goes through the initial configuration and is preparing to restart the computer when I get a blue screen (this is before we get to make a partition)

  It's basically my blue screen message

  problem detected windows stops to prevent damage of the model
  Check for sufficient disk space. If a driver is identified in the stop message, disable it or check updates,
  try changing video cards

  control the bios upgrade. Disable the bios memory options such as implementing caching or shading. Start in
  safe mode to remove or disable components

  STOP: OXOOOOOO7E (0xc0000005, 0xf748e0bf, oxf78da208, 0xf78d9f08)
  PCI.sys - address f748e0bf base at f7487000, DateStamp 3b7d855c

  "superbuddha" wrote in message News: * e-mail address is removed from the privacy * .com...

  I just bought a motherboard ASUS p5g41t-mlx with a Pentium E5400 2.7 GHz dual core and a hard drive when booting with the windows xp cd in, it goes through the initial configuration and is preparing to restart the computer when I get a blue screen (this is before we get to make a partition)

  It's basically my blue screen message

  problem detected windows stops to prevent damage of the model
  Check for sufficient disk space. If a driver is identified in the stop message, disable it or check updates,
  try changing video cards

  control the bios upgrade. Disable the bios memory options such as implementing caching or shading. Start in
  safe mode to remove or disable components

  STOP: OXOOOOOO7E (0xc0000005, 0xf748e0bf, oxf78da208, 0xf78d9f08)
  PCI.sys - address f748e0bf base at f7487000, DateStamp 3b7d855c

  Have you installed the drivers SATA asks to press F6 to install drivers from floppy drive?  Assuming you have this type of "new HDD" with your new motherboard.  (small cable from motherboard to the drive instead of wide ribbon cable.)
   
  You may need to go into the bios of the computer to IDE mode to install the operating system.  Once installed, you can install the SATA drivers and then move into the bios SATA mode for the HARD disk controller.

• Power failure blue screen of Windows Vista - driver

  Hi all

  ASUS laptop computer under Win Vista Home 32-bit Edition. Have 2 problems:

  1 power driver blue screen failure.

  Please see my 2 Dump files to:

  https://www.dropbox.com/s/5c4subvkhw2lryf/Mini031615-03.dmp?DL=0

  https://www.dropbox.com/s/qsd0nv61yer4e3b/Mini031615-04.dmp?DL=0

  After studying this problem it seems it has to do with the USB drivers? I have no yellow question mark in Device Manager.

  (a) it - I have to refresh battery USB? If yes pls show me how?

  (b) do I avoid Windows update to reinstall the drivers on the original from ASUS drivers? If yes Pls tell me how?

  (c) do I reinstall the drivers Asus? which device?

  The problem could be related to a HP mouse wireless connected to the laptop?  It always worked fine until I disconnected and reconnected.

  2 laptop won't wake up from sleep, I have to use the switch to close.

  Appreciate your help.

  OR

  There are two related issues here.  First associated with snp2uvc.sys generic PC Camera Driver and secondly to Kaspersky.  I update the reader of the camera (your is 2007) aware and remove Kaspersky and replace it with MSE >

  Kaspersky is a common cause of BSOD.

  
  

  I remove and replace it with Microsoft Security Essentials if you use vista or win 7.  If you are using win 8 or higher, I would use the built-in Defender.

  http://support.Kaspersky.com/downloads/utils/kavremover10.zip
  http://www.Microsoft.com/security_essentials/

• How to fix the blue screen (OD)?

  Hello

  I frequently get a BSOD that I believe is directly related to my purchased recently Bluetooth speaker (Logitech EU Boombox). Which suggests as possible my bluetooth driver is involved.

  I managed to get the speaker to pair once, and I was able to listen to wireless music via Spotify. However, I had problems reconnecting, which could sometimes be fixed by deleting the bluetooth device and then add it again. To the course to add it again, however, my computer would regularly crash, show me the blue screen and then restart. I am a novice and have no idea how these problems. FYI, I'm in a constant dialogue with the dailies with Logitech, but they are very slow and does not give clear instructions.

  I really hope that someone can help you.

  The blue screen shows IRQL_NOT_LESS_OR_MORE at the top and I am paste the error below, log that includes the BC code:

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

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.0.6002.2.2.0.768.3
  Locale ID: 1035

  More information about the problem:
  BCCode: a
  BCP1: 805ED000
  BCP2: 00000002
  BCP3: 00000000
  BCP4: 826E1F33
  OS version: 6_0_6002
  Service Pack: 2_0

  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\Mini030914-03.dmp
  C:\Users\ilda pc\AppData\Local\Temp\WER-38657-0.sysdata.xml
  C:\Users\ilda pc\AppData\Local\Temp\WERD335.tmp.version.txt

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

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

  Thank you, David!

  All attached files of the DMP are the bug check IRQL_NOT_LESS_OR_EQUAL (a) .

  This indicates that Microsoft Windows or a driver in mode accessed kernel memory paged at DISPATCH_LEVEL level or above.

  This bug check is issued if the memory paged (or invalid) is accessible when the IRQL is too high. The error that usually generates this bug check occurs after the installation of the faulty device driver or service system, BIOS.

  If we take a look at the call stack:

  1: kd > kv
  ChildEBP RetAddr Args to child
  805ec518 826e1f33 badb0d00 00000001 85f81d02 nt! KiTrap0E + 0x1c5 (FPO: [0,0] TrapFrame @ 805ec518)
  805ec594 913ce545 86a00a88 805ec5b4 82670011 nt! memcpy + 0 x 33
  WARNING: Information not available stack unwind. Sequence of images may be wrong.
  805ec8f4 913ce842 86a26e00 00000000 86a009c4 BthAvrcp + 0 x 2545
  805ec934 826e00fb 86a26e00 00000000 01a009c4 BthAvrcp + 0 x 2842
  805ec96c 8ef2a25c 00000000 805ec994 8ef2a2a1 nt! IopfCompleteRequest + 0x11d
  805ec978 8ef2a2a1 86a0ddd0 86a26e00 86a26e00 bthport! BthCompleteRequestEpilogue + 0 x 38 (FPO: [Non - Fpo])
  805ec994 8ef62d20 86a0ddd0 86a26e00 00000000 bthport! BthCompleteRequestEx + 0 x 27 (FPO: [Non - Fpo])
  805ec9c0 8ef5e4d5 86475070 015ecaa8 86613960 bthport! L2Cap_CompleteReadIrpList + 0x8c (FPO: [Non - Fpo])
  805ecab4 8ef3669d 01722ea0 b 86475070 86963 08 bthport! L2CapInt_ProcessReadBip + 0x3ef (FPO: [Non - Fpo])
  805ecaf4 8ef35f65 86722e40 86613960 86722e40 bthport! HCI_ProcessAclReadBip + 0x6d3 (FPO: [Non - Fpo])
  805ecb28 8ef5a0db 86613960 00000000 00000016 bthport! HCI_ProcessAclRead + 0x25b (FPO: [Non - Fpo])
  805ecb44 8ef2c7a8 86613960 87c77f78 00000000 bthport! HCI_ProcessMpBip + 0 x 67 (FPO: [Non - Fpo])
  805ecb60 8f3ca5ef 87c77f78 865cb520 865cb4e0 bthport! BTHPORT_RecvMpBip + 0x3c (FPO: [Non - Fpo])
  805ecb74 8f3cdc4a cd 86733 0 8660f000 00000016 BTHUSB! BthUsb_ReadTransferComplete + 0x4b (FPO: [Non - Fpo])
  805ecbcc 8f3cdec6 86a0dd18 805ecbe8 865e546b BTHUSB! UsbWrapWorkRoutine + 0 x 78 (FPO: [Non - Fpo])
  805ecbf4 826e00fb 86a0dd18 865e5368 015cb4e0 BTHUSB! UsbWrapInterruptReadComplete + 0xb4 (FPO: [Non - Fpo])
  805ecc28 8e543e0a 82680734 87c79d08 00000000 nt! IopfCompleteRequest + 0x11d
  805ecc64 8e542132 85f81028 865e5368 87c7e960 USBPORT! USBPORT_Core_iCompleteDoneTransfer + 0x6cb (FPO: [Non - Fpo])
  805ecc94 8e54495f 85f81028 85f81bf8 39585043 USBPORT! USBPORT_Core_iIrpCsqCompleteDoneTransfer + 0x4f5 (FPO: [Non - Fpo])
  805eccc0 8e53e24f 85f81028 85f81bf8 85f81002 USBPORT! USBPORT_Core_UsbIocDpc_Worker + 0 x 122 (FPO: [Non - Fpo])
  805ecce8 826e35a2 85f81c04 34776478 00000000 USBPORT! USBPORT_Xdpc_Worker + 0 x 274 (FPO: [Non - Fpo])
  805ecd50 0000000e 826e177d 00000000 00000000 nt! KiRetireDpcList + 0 x 147
  0000000e 805ecd54 00000000 00000000 00000000 nt! KiIdleLoop + 0 x 49 (FPO: [0,0,0])

  -FAILURE_BUCKET_ID: 0xA_BthAvrcp + 2545

  ^^ Driver Bluetooth audio/video of the system.

  Go to the Asus website - http://support.asus.com/download.aspx?SLanguage=en&p=3&s=78&m=F3Ka&os=&hashedid=JFMwUdQ1L5V3eIKf

  Download and install the Bluetooth for Vista 32-bit driver.

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

  Remove and replace avast! with Microsoft Security Essentials for purposes of troubleshooting temporary as it may cause conflicts:

  avast! removal - http://www.avast.com/uninstall-utility

  -MSE http://Windows.Microsoft.com/en-us/Windows/Security-Essentials-download 

  Kind regards

  Patrick

• Compaq Presario C700 CTO - blue screen drivers/events/mode RAID or AHCI?

  Hello

  I need to know if my PC Compaq Presario C700 CTO Notebook is running in RAID or AHCI mode because of problems with a driver Intel Matrix Storage Manager (IMSM).  The Read Me text file in the menu start > all programs > intel Matrix Storage Manager folder said if my system works in RAID or AHCI mode determines if my computer needs this driver.

  For the past month, my computer stops and restarts with a blue screen and message when the desktop appears as a message. (The blue screen does not last long enough to read.)  The message is always the same except one I had yesterday which is described at the end of this post.

  "Windows has stopped unexpectedly. '.  The details are:

  Signature of the problem:
  Problem event name: BlueScreen
  The system version: 6.0.6002.2.2.0.768.3
  Locale ID: 1033

  More information about the problem:
  BCCode: 8086
  BCP1: 00000000
  BCP2: 00000000
  BCP3: 00000000
  BCP4: 00000000
  OS version: 6_0_6002
  Service Pack: 2_0
  Product: 768_1

  Files helping to describe the problem:
  C:\WINDOWS\Minidump\Mini062513-01.dmp
  C:\Users\Dawna\AppData\Local\Temp\WER-48001-0.SysData.XML
  C:\Users\Dawna\AppData\Local\Temp\WERE54F.tmp.version.txt

  A solution:

  Problem with the Intel IMSM driver.

  Intel IMSM driver has stopped working properly.

  Press or click on to download the update on the site of ASUS computer.

  I several times installed upgrading after the blue screen event ever.  The download is an application called V8.9.2.1002_logo_Win7Vista3264.exe.

  The Intel Matrix Storage Manager driver is not in the list of devices in Device Manager > show hidden devices.  I found information on the HP site indicating how do I know if my computer has the driver, because I thought that maybe it has not been installed correctly.  I found the Intel Matrix Storage Manager program folder in the start menu > new programs.  I can't know what version it is.  Reading tells Me to text file in the folder to open the Device Manager and search for specific controllers SATA RAID and SATA AHCI controllers.  If not in the list then it appears that my OS is not running in two modes.  I can't find these devices in the list, but the Read Me text file advises me to contact the manufacturer in case of doubt.  My warranty has expired, so I'm here asking for help.

  When I use the HP product detection analysis to try to automatically scan for driver updates, it reads my product incorrectly.   Running the tool has sometimes followed by a crash and blue screen.

  I do not remember the changes that I made at the time when the events of the blue screen started to happen.  There was an event yesterday blue screen and the message on the desk said a problem with the HP Recovery Manager and backup.   He advised me to install an update from the HP website.  The link did not open so I downloaded the version 4.0.100.1189sp39296.exe of HP update.  I've also updated my graphics driver.

  I would be grateful if someone could help me solve this problem.   I'm worried about damaging my computer.

  Dawna

  HP Compaq Presario C700 CTO Notebook PC
  OS 32-bit of Windows Vista Home Premium Service Pack 2
  x-86 based PC
  SM BIOS version 2.4
  Physical memory (RAM) installed 2.00 GB
  Total physical memory 1.99 GB
  866 MB available physical memory
  4.22 GB total virtual memory
  2.69 GB available virtual memory
  Page file 2.28 GB of space

  Hello:

  First of all your needs from laptop to have the hardware (CPU and chipset) Intel to run the Intel Matrix Storage Manager.

  Your C700 CTO may have either hardware Intel or an AMD/Nvidia chipset so I can't tell you what your laptop has.

  You can tell however, and you can tell what mode of the controller to your PC is currently running (AHCI or RAID).

  If you have PC, go into the Device Manager and if you have a category of an ATA/ATAPI IDE controller based on an Intel processor, click to expand that and if your laptop is running in AHCI mode, the controller will have the AHCI word in the description of the controller.

  If your mobile phone is set to RAID (which I doubt), scroll down further on the Device Manager list, and there would be a category of storage controllers if the command is set to RAID.

  Click to expand, and you would see a description of disk with the word inside RAID controller.

• The matching blue screens and random reboots/crashes.

  Greetings. A year ago, I built a new computer, including the following parts:

  AMD Athlon 64 Dual Core 89W

  Motherboard ASUS M3A78 Pro

  Seagate Barracuda 7200.10 250 GB Sata internal HD

  4 GB of Ram DDR2 (not sure of the speed/brand)

  Since installing windows, I started getting blue screens of various types. Here are some blue screens I have met:

  Interrupt Unhandled Exception, failure of Page in the paginated, computer space made an attempt to write to read only memory, Memory_Management, IRQL not less or equal and Driver IRQL not less or equal. When these blue screens occur, some remain on the screen, while other flick on briefly and the computer begins to restart.

  On top of these blue screens, I also sound experience breaks down in loop in games. These experiences are breakers occur anywhere from 5 minutes to more than two hours of play.

  In the first dealing with this issue, I decided to test the memory with memtest86. A test actually froze on me. A second test showed no problems. Because of the freeze, I took a bit of ram to see if there could be a problem with some of the sticks is bad. Low and here are the problems disappeared. For a period of time. Some games have kept crashing on me, while others have worked without a hitch. I will mention that a game (World of Warcraft) seems to have more memory than others still ran without encountering any problem later.

  Because of all the questions, I decided to reformat/reinstall windows to make sure that everything has been installed correctly. Right out of the door, it began freezing at all normal intervals.

  I have this post is because I am curious about how of course, I can be that these problems are caused by a single hardware issue (I think I'm the ram). I ask because DDR2 Ram is cheaper and my motherboard will not support DDR3. However, if I buy the overvalued price DDR2 and it does not solve the problem, then it ends up being a pretty big money sink.

  Any guidance would be greatly appreciated.

  Hello

  Check this thread for more information on using BlueScreenView, MyEventViewer and other methods
  to troubleshoot the BlueScreens - first two responses.

  http://social.answers.Microsoft.com/forums/en-us/vistahardware/thread/8cd8362e-7d06-46FB-afd7-84d54b6a8ea7

  I hope this helps.

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