Unexpected stops, probably caused by ntkrnlmp

Similar Questions

• 2012 R2 server hangs randomly - Dump shows "probably caused by: ntkrnlmp.exe.

  Try to find what has caused the problem. Please check below for debugging details:

  HP (ProLiant DL380p Gen8) with Windows Server 2012 R2

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  Use! analyze - v to obtain detailed debugging information.

  Error checking 133, {1, 1e00, 0, 0}

  Probably caused by: ntkrnlmp.exe (nt! FNODOBFM: 'chain' + adbe)

  Follow-up: MachineOwner
  ---------

  14: kd >! analyze - v
  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  DPC_WATCHDOG_VIOLATION (133)
  The CPD watchdog detected an extended operation to an IRQL of DISPATCH_LEVEL level
  or higher.
  Arguments:
  Arg1: 0000000000000001, the system has cumulatively spent a long period of time to
  DISPATCH_LEVEL or above. The offending component may generally be
  identified with a stack trace.
  Arg2: 0000000000001e00, the monitoring period.
  Arg3: 0000000000000000
  Arg4: 0000000000000000

  Debugging information:
  ------------------

  SYSTEM_SKU: 665552-B21

  BIOS_DATE: 02/08/2014

  BUGCHECK_P1: 1

  BUGCHECK_P2: 1e00

  BUGCHECK_P3: 0

  BUGCHECK_P4: 0

  DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

  CPU_COUNT: 10

  CPU_MHZ: a21

  CPU_VENDOR: GenuineIntel

  CPU_FAMILY: 6

  CPU_MODEL: 3rd

  CPU_STEPPING: 4

  CUSTOMER_CRASH_COUNT: 1

  DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER

  BUGCHECK_STR: 0 X 133

  Nom_processus: EndpointServic

  CURRENT_IRQL: d

  ANALYSIS_VERSION: 10.0.10240.9 amd64fre

  LAST_CONTROL_TRANSFER: from fffff8019a1e0f7e to fffff8019a1c5ca0

  STACK_TEXT:
  ffffd001 '9dd31c88 fffff801' 9a1e0f7e: 00000000'00000133 00000000'00000001 00000000' 00001e00 00000000' 00000000: nt! KeBugCheckEx
  ffffd001 '9dd31c90 fffff801' 9a0b1871: ffffd001 '9efc0c80 00000000' 15bf41c1 ffffe001' d6c621a0 00000001' 00000000: nt! : FNODOBFM: 'string' + 0xadbe
  ffffd001 '9dd31d20 fffff801' 9a00d7b5: 00000000 00000001' fffff801 '9a3d0000 00000000 00000001' ffffe001' ec99e580: nt! KeClockInterruptNotify + 0 x 91
  ffffd001 '9dd31f40 fffff801' 9a14c143: ffff9ee3'c1e337dd fffff801 '9a 174057 00000000 00000001' ffffe001' ec99e580: hal! HalpTimerClockIpiRoutine + 0x15
  ffffd001 '9dd31f70 fffff801' 9a1c712a: ffffe001'd6a03e00 fffff801 '9a3d0000 ffffe001' e41be080 00000000 00000001': nt! KiCallInterruptServiceRoutine + 0xa3
  ffffd001 '9dd31fb0 fffff801' 9a1c750f: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiInterruptSubDispatchNoLockNoEtw + 0xea
  ffffd001 'a25946b0 00000000' 00000000: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: nt! KiInterruptDispatchLBControl + 0x11f

  STACK_COMMAND: kb

  FOLLOWUP_IP:
  NT! : FNODOBFM: 'chain' + adbe
  fffff801'9a1e0f7e cc int 3

  SYMBOL_STACK_INDEX: 1

  SYMBOL_NAME: nt! : FNODOBFM: 'chain' + adbe

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nt

  Nom_image: ntkrnlmp.exe

  DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6

  IMAGE_VERSION: 6.3.9600.17736

  BUCKET_ID_FUNC_OFFSET: adbe

  FAILURE_BUCKET_ID: 0x133_ISR_nt! _ ?? _::FNODOBFM:_string_

  BUCKET_ID: 0x133_ISR_nt! _ ?? _::FNODOBFM:_string_

  PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt! _ ?? _::FNODOBFM:_string_

  ANALYSIS_SOURCE: KM

  FAILURE_ID_HASH_STRING: km:0x133_isr_nt! _ ?? _::fnodobfm:_string_

  FAILURE_ID_HASH: {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}

  Follow-up: MachineOwner
  ---------

  This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)
  *
  http://social.technet.Microsoft.com/forums/en-us/home s/fr-U.S./Accueil
  http://social.msdn.Microsoft.com/Forum
  We need the log files themselves (called a DMP files) because they contain the only record of the sequence of events that led to the accident, what drivers have been loaded, and what has been loaded.
  Please follow our instructions to find and download the files, we need to help you fix your computer. They can be found at here
  If you have any questions regarding the procedure, please ask

• 2010 15 "MacBook Pro unexpected stops and defects of the screen

  As stated in the subject, I have a 2010 15 "MacBook Pro that runs on OSX Mavericks.

  I have experienced unexpected stops and, more recently, the screen glitches (see photos).

  I also have this message since Photoshop at a secure startup: "Photoshop gave up waiting for the assessment of the display driver.  Improvements using graphics hardware have been disabled.  Check the Web site of the manufacturer for the latest version of the software.

  Please review my images for more information.  I made a Starter course and managed to back up my computer (took 6 hours).  Now, I just need to fix it.

  PROPOSED ISSUE: I think I'll have problems of GPU and is forced to remove my components materials dust or replace certain parts.

  Please let me know if you have any ideas or solutions that could make me run!  Thank you!

  

  I suggest to install "El Capitan", a clean install, in this case, could be better

• Satellite L300D - unexpected stops on startup

  Hi, just had a few unexpected stops (separated) at startup. (after you have installed Windows Vista KB971029-Update) I use "HDD thermometer" to monitor the temperature of the HARD drive. Temp at the time were reported to 43degC - usually between 35 and 40. Laptop was plugged in at the time.

  WMI error reported around the same time - error 0 x 80041003

  Questions: -.
  1. I ran the basic diagnostics - no problem. y at - it a better monitor health for fans, cpu, time?
  2. I checked fan and exhaust for dust build up - no problem.
  3. laptop is old 14; Maybe I should buy the warranty of 2 years exentended?

  Thank you.

  Hey,.

  > after you install Windows Vista KB971029-Update
  Do you still have the same problem when you remove the update?

  Higher internal temperature could also be dust by a lot of dust that blocks the fan. I recommend you to clean the laptop from time to time using a jet of compressed air.

  I clean my cell phone every 3 months. I use it everyday but I m still wondering how much dust out even I use only my own office. Truly amazing

• Windows cannot connect to the Internet using HTTP, HTTPS or FTP. __This is probably caused by settings of firewall on this computer. __

  I recently installed the version of Norton, after that I was unable to use the internet, I thought it was the Norton firewall settings. After having playing with her for 30 minutes, I gave up and uninstalled Norton. I have disabled the firewall, I have reset the default settings. Here is the message I get when I run a diagnostic. A crazy thing is that I can connect to internet when I connected to this same computer as a guess.

  Please help me!

  Windows cannot connect to the Internet using HTTP, HTTPS or FTP.
  This is probably caused by the settings of firewall on this computer.

  Check the settings of firewall for the HTTP port (80), HTTPS port (443) and FTP port (21).

  Hi rhonda9937,

  1. what browser you are using to connect to the internet?

  It is not recommended to keep Windows Firewall disabled on the computer.

  This would happen if the ports are not open in the Windows Firewall.

  I suggest that you open ports in Windows Firewall and check if it works.

  How to manually open ports in Internet Connection Firewall in Windows XP

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

  Troubleshooting settings of Windows Firewall in Windows XP Service Pack 2 for advanced users

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

  I hope this helps!

  Halima S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• probably caused by the settings of the firewall on your computer. Check the settings for HTTP port (80), HTTPS port (443) and FTP.

  Change the title: internet connection.

  Unable to connect to the internet, suddenly, message that I can't connect to the internet using HTTP<>< or="" ftp.="" thios="" is="" probably="" caused="" by="" firewall="" settings="" on="" your="" computer.="" check="" settings="" for="" http="" port(80),="" https="" port(443)="" and="" ftp.="" funny="" i="" was="" just="" on="" the="" net="" not="" more="" than="" 10="" minutes="" prior="" to="" this.="" checked="" all="" conections-="" good.="" what's="" my="" next="">

  Try a system restore to a Date before the problem began:

  Restore point:

  http://www.howtogeek.com/HOWTO/Windows-Vista/using-Windows-Vista-system-restore/

  Do Safe Mode system restore, if it is impossible to do in Normal Mode.

  Try typing F8 at startup and in the list of Boot selections, select Mode safe using ARROW top to go there > and then press ENTER.

  Try a restore of the system once, to choose a Restore Point prior to your problem...

  Click Start > programs > Accessories > system tools > system restore > choose another time > next > etc.

  http://www.windowsvistauserguide.com/system_restore.htm

  Read the above for a very good graph shows how backward more than 5 days in the System Restore Points by checking the correct box.

  See you soon.

  Mick Murphy - Microsoft partner

• My computer started randomly closing overnight - then the left on download. Internet points out the unexpected stop down and gives me a link dead at error number: 0x8DDD0002 - I'M the only user/administrator

  I've been downloading for years, but the last 3 - 4 times when I let the computer do its things while I'm in bed, I come down in the morning and the computer restarted itself and I get the Vista - computer has recovered from an unexpected stop, then he gives me the windows update link, which tells me that I must be an administrator to apply updates!  I AM she!  only one user on this computer, checked my settings and its fine!

  Someone has any ideas why this started all of a sudden the most stupid and frustrating now!

  Thanks in advance people :D

  "computer has recovered from an unexpected shutdown, then he gives me the windows Update link.

  Most of the time, it restarts itself during the update process.

  Change it to no automatic installation, which is what I was hoping you would do to dismiss this case.

  That's what brought me to update problems.

  See you soon.

  Mick Murphy - Microsoft partner

• After Windows7 SP1, sleep = "unexpected stop.

  On my system quad i7 since the Windows7 Pro SP1 update, whenever my system goes to sleep, he gets an "unexpected stop. How to solve this?
  The system log contains:
  The computer was restarted after a bugcheck.  The bugcheck was: 0x000000a0 (0xffffffffc000000e, 0000000000000001 0 x, 0 x 0000000000000009, 0 x 0000000000000000). A dump was saved in the: C:\Windows\MEMORY. DMP. Report ID: 030211-83928-01.

  What is an error checking?

  BSOD Stop Code A0 immediately after Eve hybrid:
  Http://support.microsoft.com/kb/2495523 patch may fix the problem.

  Windows 7 service pack 1 after you install this update, get a blue screen when pc will stand-by or sleep mode:
  Update the SATA 6Gbs. device driver go to the computer manufacturer's web page or the card mother driver download/support and download the latest device driver SATA for your make and model.

  Windows 7 will be hibernation is more: memory crash dump file is not created or hibernation does not work, when you use a miniport driver SCSIport as the boot device driver in Windows 7 or in Windows Server 2008 R2
  http://support.Microsoft.com/kb/2495523/en-us

  J W Stuart: http://www.pagestart.com

• My computer crashes when I try to run some games and crash report says that it's probably caused by rwdrv.sys.

  My computer crashes when I try to run some games and crash report says that it's probably caused by rwdrv.sys. I looked and I couldn't find anything. I found it in my computer under windows/syswow64/drivers/rwdrv.sys.

  What should I do? What does rwdrv.sys do?

  This is not a MS win file kernel;

  Scan of malware http://www.malwarebytes.org/products/malwarebytes_free/

• BSOD: For the Bug Check Code: 0000009F is probably caused by: nt Driver

  I recently met a problem with BSOD when I was afk or configure my computer to Hibernate, whereby Soluto has picked up the information on:

  Bug check code: 0000009F, probably caused by: nt DRIVER_POWER_STATE_FAILURE driver bug check has a value of 0x0000009F. This bug check indicates that the driver is in an inconsistent or invalid power state.
  How should I proceed? I got the message about 3 times prior.

  RS

  It was linked to rimvndis6_AMD64.sys RIM Tunnel driver of Research In Motion Limited.  I would like to re - install the latest driver available.

  If you continue to plant I would remove Avast & replace it with MSE

  Avast can be a cause of BSOD.

  Please delete and replace by Microsoft Security Essentials at LEAST FOR TESTER

  http://files.avast.com/files/eng/aswclear5.exe
  http://www.Microsoft.com/security_essentials/

• Windows 7 - unexpected stops

  Hello

  We have a desktop PC running Windows 7 Home Premium, 32-bit computer.  Recently, at the initial start-up or wake up from hibernation, we get the error "Windows has recovered from an unexpected shutdown.  The file system and Windows Memory Diagnostic tool check both check out OK.  I understand that this is probably a driver issue, but have not been able to isolate.  Maintenance of the Action Center indicates the graphic driver NVIDIA stopped working 6 times, the last time which take place on 17/09/2014 at 16:53. Windows Update indicates that the driver NVIDIA GE Force 8500 GT is up-to-date.

  It is an example of info of the observer of recent events below. Minidump files can be found at:

  https://www.dropbox.com/sh/5qmkrai0gjxg1kp/AAD24AhGCOhEYFcZZA23zQgFa?DL=0

  Any help to isolate the source of the problem is appreciated.  If any additional info is needed, please advise.  Thank you in advance.
   
  Details of the Event Viewer:

  Log name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 17/09/2014 12:22:31
  Event ID: 41
  Task category: (63)
  Level: critical
  Key words: (2).
  User: SYSTEM
  Computer: Seagate
  Description: The system has rebooted without judgment properly first. This error can be caused if the system unresponsive, crashed or unexpected power loss.

  Some recent events produced the following troubleshooting error details:

  5 September 2014:

  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: 116
  BCP1: 87E56008
  BCP2: 9433CABC
  BCP3: 00000000
  BCP4: 00000002
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\090514-24850-01.dmp
  C:\Users\Alan\AppData\Local\Temp\WER-50637-0.SysData.XML

  September 9, 2014:

  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: 116
  BCP1: 87EB9308
  BCP2: 93717ABC
  BCP3: 00000000
  BCP4: 00000002
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\090914-21403-01.dmp
  C:\Users\Alan\AppData\Local\Temp\WER-38173-0.SysData.XML

  September 12, 2014:

  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: 116
  BCP1: 87EAD008
  BCP2: 9353DABC
  BCP3: 00000000
  BCP4: 00000002
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  September 13, 2014:

  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: 116
  BCP1: 87E8A008
  BCP2: 9272BABC
  BCP3: 00000000
  BCP4: 00000002
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\091314-22495-01.dmp
  C:\Users\Alan\AppData\Local\Temp\WER-50544-0.SysData.XML

  September 15, 2014:

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

  Additional information about the problem
  BCCode: 116
  BCP1: 87EBD008
  BCP2: 9354AABC
  BCP3: 00000000
  BCP4: 00000002
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  September 17, 2014; morning:

  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: 116
  BCP1: 87EB3008
  BCP2: 93517ABC
  BCP3: 00000000
  BCP4: 00000002
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\091714-25521-01.dmp
  C:\Users\Alan\AppData\Local\Temp\WER-71323-0.SysData.XML

  September 17, 2014; afternoon:

  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: 116
  BCP1: 856E9228
  BCP2: 9511238E
  BCP3: 00000000
  BCP4: 00000002
  OS version: 6_1_7601
  Service Pack: 1_0
  Product: 768_1

  Files helping to describe the problem:
  C:\Windows\Minidump\091714-20779-01.dmp
  C:\Users\Alan\AppData\Local\Temp\WER-43898-0.SysData.XML

  Hello Alan,.

  We were finally able to access the files that you have shared the link, I analyzed the dumps using WinDBG and this is the output:

  Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 processors) free x 86 compatible

  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 7601.18409.x86fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0x82a1c000 PsLoadedModuleList = 0x82b655b0
  The debugging session: Mon 1 Sep 14:44:28.991 2014 (UTC - 04:00)
  System Uptime: 0 days 0:00:35.880

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  VIDEO_TDR_FAILURE (116)

  Try to reset the display driver and recover from timeout failed.

  Arguments:
  Arg1: 87eaf510, optional pointer recovery environment internal TDR (TDR_RECOVERY_CONTEXT).
  Arg2: 93538abc, the pointer in the responsible device driver module (owner tag).
  Arg3: 00000000, error code optional (NTSTATUS) for the last operation has failed.
  Arg4: 00000002, optional internal context dependent data.

  Debugging information:
  ------------------

  TRIAGER: Could not open the file of triage: e:\dump_analysis\program\triage\modclass.ini, error 2

  FAULTING_IP: nvlddmkm + 112abc
  93538abc push ebp 55

  DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

  BUGCHECK_STR: 0 X 116

  Nom_processus: System

  CURRENT_IRQL: 0

  STACK_TEXT:
  8e253b74 93ef1fb3 87eaf510 00000116 93538abc nt! KeBugCheckEx + 0x1e
  8e253b98 93ee699c 00000000 00000002 dxgkrnl 93538abc! TdrBugcheckOnTimeout + 0x8d
  8e253bbc 93f2392c 00000000 00000102 87bd6788 dxgkrnl! TdrIsRecoveryRequired + 0xb8
  8e253c34 93f4da7c fffffcfb 000007e3 dxgmms1 00000000! VidSchiReportHwHang + 0x3c0
  8e253c5c 00000000 00000000 00000000 dxgmms1 93f4e19d! VidSchiCheckHwProgress + 0 x 68
  8e253c98 93f2a8f0 8e253c90 82a52b99 87bd6788 dxgmms1! VidSchiWaitForSchedulerEvents + 0x1b1
  8e253d28 93f4f501 87bd6788 82a52b99 87bd6788 dxgmms1! VidSchiScheduleCommandToRun + 0xaa
  8e253d3c 93f4f5bd 00000000 87099030 dxgmms1 87bd6788! VidSchiRun_PriorityTable + 0xf
  82 c 25141 a29d5b3b 00000000 dxgmms1 87bd6788 8e253d50! VidSchiWorkerThread + 0x7f
  8e253d90 82acc559 93f4f53e 87bd6788 00000000 nt! PspSystemThreadStartup + 0x9e
  00000000 00000000 00000000 00000000 00000000 nt! KiThreadStartup + 0x19

  STACK_COMMAND: .bugcheck; Ko

  FOLLOWUP_IP:
  nvlddmkm + 112abc
  93538abc push ebp 55

  SYMBOL_NAME: nvlddmkm + 112abc

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nvlddmkm

  Nom_image: nvlddmkm.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 5315b 301

  FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  Follow-up: MachineOwner
  ---------

  **************************************************************************************************************************************

  Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 processors) free x 86 compatible

  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 7601.18409.x86fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0x82a04000 PsLoadedModuleList = 0x82b4d5b0
  The debugging session: Wed Sep 17 19:50:38.453 2014 (UTC - 04:00)
  System Uptime: 0 days 2:51:49.341

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  VIDEO_TDR_FAILURE (116)

  Try to reset the display driver and recover from timeout failed.

  Arguments:
  Arg1: 856e9228, optional pointer recovery environment internal TDR (TDR_RECOVERY_CONTEXT).
  Arg2: 9511238e, the pointer in the responsible device driver module (owner tag).
  Arg3: 00000000, error code optional (NTSTATUS) for the last operation has failed.
  Arg4: 00000002, optional internal context dependent data.

  Debugging information:
  ------------------

  TRIAGER: Could not open the file of triage: e:\dump_analysis\program\triage\modclass.ini, error 2

  FAULTING_IP:
  nvlddmkm + 11238e
  9511238e push ebp 55

  DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

  CUSTOMER_CRASH_COUNT: 1

  BUGCHECK_STR: 0 X 116

  Nom_processus: System

  CURRENT_IRQL: 0

  STACK_TEXT:
  8e2aeb74 95b01fb3 856e9228 00000116 9511238e nt! KeBugCheckEx + 0x1e
  8e2aeb98 9511238e 95af699c 00000000 00000002 dxgkrnl! TdrBugcheckOnTimeout + 0x8d
  8e2aebbc 95b3392c 00000000 00000102 87664788 dxgkrnl! TdrIsRecoveryRequired + 0xb8
  8e2aec34 95b5da7c fffffcfb 000a146c dxgmms1 00000000! VidSchiReportHwHang + 0x3c0
  8e2aec5c 00000000 00000000 00000000 dxgmms1 95b5e19d! VidSchiCheckHwProgress + 0 x 68
  8e2aec98 95b3a8f0 8e2aec90 876a34a8 87692868 dxgmms1! VidSchiWaitForSchedulerEvents + 0x1b1
  8e2aed28 95b5f501 87664788 82a3ab99 87664788 dxgmms1! VidSchiScheduleCommandToRun + 0xaa
  8e2aed3c 87664788 00000000 8769ea48 dxgmms1 95b5f5bd! VidSchiRun_PriorityTable + 0xf
  8e2aed50 82c0d141 87664788 a29b8c61 dxgmms1 00000000! VidSchiWorkerThread + 0x7f
  8e2aed90 82ab4559 95b5f53e 87664788 00000000 nt! PspSystemThreadStartup + 0x9e
  00000000 00000000 00000000 00000000 00000000 nt! KiThreadStartup + 0x19

  STACK_COMMAND: .bugcheck; Ko

  FOLLOWUP_IP:
  nvlddmkm + 11238e
  9511238e push ebp 55

  SYMBOL_NAME: nvlddmkm + 11238e

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nvlddmkm

  Nom_image: nvlddmkm.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 53b 44481

  FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  Follow-up: MachineOwner
  ---------

  **************************************************************************************************************************

  Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 processors) free x 86 compatible

  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 7601.18409.x86fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0x82a43000 PsLoadedModuleList = 0x82b8c5b0
  The debugging session: Wed Sep 17 16:58:08.943 2014 (UTC - 04:00)
  System Uptime: 0 days 0:00:36.831

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  VIDEO_TDR_FAILURE (116)

  Try to reset the display driver and recover from timeout failed.

  Arguments:
  Arg1: 873d 6008, optional pointer recovery environment internal TDR (TDR_RECOVERY_CONTEXT).
  Arg2: 9354e38e, the pointer in the responsible device driver module (owner tag).
  Arg3: 00000000, error code optional (NTSTATUS) for the last operation has failed.
  Arg4: 00000002, optional internal context dependent data.

  Debugging information:
  ------------------

  TRIAGER: Could not open the file of triage: e:\dump_analysis\program\triage\modclass.ini, error 2

  FAULTING_IP:
  nvlddmkm + 11238e
  9354e38e push ebp 55

  DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

  CUSTOMER_CRASH_COUNT: 1

  BUGCHECK_STR: 0 X 116

  Nom_processus: System

  CURRENT_IRQL: 0

  STACK_TEXT:
  8e237b74 93f3dfb3 00000116 d 873-6008 9354e38e nt! KeBugCheckEx + 0x1e
  8e237b98 93f3299c 00000000 00000002 dxgkrnl 9354e38e! TdrBugcheckOnTimeout + 0x8d
  8e237bbc 93f6f92c 00000000 00000102 8747 has 538 dxgkrnl! TdrIsRecoveryRequired + 0xb8
  8e237c34 00000819 00000000 dxgmms1 fffffcfb 93f99a7c! VidSchiReportHwHang + 0x3c0
  8e237c5c 00000000 00000000 00000000 dxgmms1 93f9a19d! VidSchiCheckHwProgress + 0 x 68
  8e237c98 93f768f0 8e237c90 82a79b99 8747 has 538 dxgmms1! VidSchiWaitForSchedulerEvents + 0x1b1
  8e237d28 93f9b501 8747 has 538 8747 has 538 dxgmms1 82a79b99! VidSchiScheduleCommandToRun + 0xaa
  8e237d3c 93f9b5bd 8747 has 538 00000000 and 87549030 dxgmms1! VidSchiRun_PriorityTable + 0xf
  8e237d50 82c4c141 8747 has 538 a2896b6a dxgmms1 00000000! VidSchiWorkerThread + 0x7f
  8e237d90 82af3559 93f9b53e 8747 has 538 00000000 nt! PspSystemThreadStartup + 0x9e
  00000000 00000000 00000000 00000000 00000000 nt! KiThreadStartup + 0x19

  STACK_COMMAND: .bugcheck; Ko

  FOLLOWUP_IP:
  nvlddmkm + 11238e
  9354e38e push ebp 55

  SYMBOL_NAME: nvlddmkm + 11238e

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nvlddmkm

  Nom_image: nvlddmkm.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 53b 44481

  FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  Follow-up: MachineOwner
  ---------

  **********************************************************************************************************************

  Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 processors) free x 86 compatible

  Product: WinNt, suite: TerminalServer personal TerminalServer
  By: 7601.18409.x86fre.win7sp1_gdr.140303 - 2144
  Computer name:
  Kernel base = 0x82a4a000 PsLoadedModuleList = 0x82b935b0
  The debugging session: Wed Sep 17 15:21:29.130 2014 (UTC - 04:00)
  System Uptime: 0 days 0:00:37.018

  *******************************************************************************
  *                                                                             *
  * Bugcheck analysis *.
  *                                                                             *
  *******************************************************************************

  VIDEO_TDR_FAILURE (116)

  Try to reset the display driver and recover from timeout failed.

  Arguments:
  Arg1: 87eb3008, optional pointer recovery environment internal TDR (TDR_RECOVERY_CONTEXT).
  Arg2: 93517abc, the pointer in the responsible device driver module (owner tag).
  Arg3: 00000000, error code optional (NTSTATUS) for the last operation has failed.
  Arg4: 00000002, optional internal context dependent data.

  Debugging information:
  ------------------

  TRIAGER: Could not open the file of triage: e:\dump_analysis\program\triage\modclass.ini, error 2

  FAULTING_IP:
  nvlddmkm + 112abc
  93517abc push ebp 55

  DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

  CUSTOMER_CRASH_COUNT: 1

  BUGCHECK_STR: 0 X 116

  Nom_processus: System

  CURRENT_IRQL: 0

  STACK_TEXT:
  8e243b74 93ed0fb3 87eb3008 00000116 93517abc nt! KeBugCheckEx + 0x1e
  8e243b98 93ec599c 00000000 00000002 dxgkrnl 93517abc! TdrBugcheckOnTimeout + 0x8d
  8e243bbc 93f0292c 00000000 00000102 87be3788 dxgkrnl! TdrIsRecoveryRequired + 0xb8
  8e243c34 93f2ca7c fffffcfb 6 00000000 dxgmms1 000007d! VidSchiReportHwHang + 0x3c0
  8e243c5c 00000000 00000000 00000000 dxgmms1 93f2d19d! VidSchiCheckHwProgress + 0 x 68
  8e243c98 93f098f0 8e243c90 82a80b99 87be3788 dxgmms1! VidSchiWaitForSchedulerEvents + 0x1b1
  8e243d28 93f2e501 87be3788 82a80b99 87be3788 dxgmms1! VidSchiScheduleCommandToRun + 0xaa
  8e243d3c 93f2e5bd 87be3788 876c9d48 00000000 dxgmms1! VidSchiRun_PriorityTable + 0xf
  82 c 53141 87be3788 a2bdef1d 00000000 dxgmms1 8e243d50! VidSchiWorkerThread + 0x7f
  8e243d90 82afa559 93f2e53e 87be3788 00000000 nt! PspSystemThreadStartup + 0x9e
  00000000 00000000 00000000 00000000 00000000 nt! KiThreadStartup + 0x19

  STACK_COMMAND: .bugcheck; Ko

  FOLLOWUP_IP:
  nvlddmkm + 112abc
  93517abc push ebp 55

  SYMBOL_NAME: nvlddmkm + 112abc

  FOLLOWUP_NAME: MachineOwner

  MODULE_NAME: nvlddmkm

  Nom_image: nvlddmkm.sys

  DEBUG_FLR_IMAGE_TIMESTAMP: 5315b 301

  FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

  Follow-up: MachineOwner
  ---------

  ******************************************************************************************************************

  The dump file downloaded leading to the same results, such as mentioned in the previous post. The defective module here is the nvlddmkm.sys, which is a NVIDIA driver. However, try to update the drivers for this video card.

  Reference: Update a hardware driver that is not working properly

  Hope this information is useful. Please get back to us, if still face issues with Windows in the future.

• System unexpectedly stop restart and go to the blue screen "error code 0141.

  Original title: error code

  my lap top is suddenly happened to bluescreen, shut down and then after reboot, one, (error code 0141), appears. can you please tell me how to fix this?

  Hello

  Thank you to contact the community Microsoft and we will be happy to help you with your concern.

  According to the description, it looks like you have a problem with Windows Vista, getting automatically restart with a blue screen.

  He would be grateful if you can answer this question in order to help you further.

  1. have you made changes on the computer before this problem?
  2 what happens while accessing any special request or programs?

  I suggest you to check the information contained in the event logs? (Event Viewer)

  http://Windows.Microsoft.com/en-us/Windows-Vista/what-information-appears-in-event-logs-Event-Viewer

  Perform a clean startup will check if any third-party application is causing the problem, as the clean boot helps eliminate software conflicts.

  How to solve the problem by running the clean boot in Windows vista: http://support.microsoft.com/kb/929135

  Note: Once you have completed troubleshooting, perform the steps in the step 3: to reset the computer as usual.

  I suggest you to see the steps in the following Microsoft article and check if it helps.

  How to fix a blue screen stop errors that cause Windows Vista to shut down or restart unexpectedly: http://support.microsoft.com/kb/958233

  Resolve stop (blue screen) errors in Windows 7 (similar to a few steps of the mentioned below, the section applies to windows vista): http://windows.microsoft.com/en-US/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

  Notes:

  When you perform the system restore to restore the computer to a previous state, programs and updates that you have installed are removed.

  Before you perform the upgrade installation, I recommend you back up your files using windows backup.

  We would be more than happy to help you if the steps above did not solve the problem.

• 5.7.1 - unexpected stop importing in Lightroom

  Hello!

  I am a photographer using Lightroom 5.7.1

  My work computer is a 2.7 GHz i5 iMac from Apple with 16 GB 1600 Mhz DDR3.

  Lately (these two to three weeks) Lightroom 5.7.1 was unexpectedly shut down on imports. Before you attempt to import, I noticed the window import shows all as importable photos, even the pictures that have already been added to my catalog. Closing out of this forum and the opening of new import (cmd + shift + i) window will remedy the issue, stressing only photographs that have not been added to the catalog, but in almost all cases, after that the images are imported Lightroom stops unexpectedly. When you re - open my catalog Lightroom will not display images newly imported until I re - synchronize folders.

  Someone at - it similar problems? It's very frustrating, without detectable cause I can say (Nothing in my workflow has changed)

  The question must have been caused by the map that I'm importing. I am currently using a new card for the last three days without any problem (normally I would have a question several times a day).

• MBP 2015 unexpected stops down.having problems with my card closing down.i have reset smh and Landau, used utility disk without result and get this report.

  It happened one month almost on a daily basis.continues close unexpectedly.please help

  Anonymous UUID:

  Sat Apr 16 05:11:26 2016

  Panic report *.

  panic (cpu 0 0xffffff80003ce40a appellant): Kernel trap at 0xffffff7f827954f0, type 14 = page fault, registers:

  CR0: 0 X 0000000080010033, CR2: 0 X 0000000000000134, CR3: 0X00000002C423309B CR4: 0X00000000001627E0

  RAX: 0 X 0000000000000134, RBX: 0XFFFFFF803CD04DD8 RCX: 0 X 0000000000000000, RDX: 0X000000000000004D

  RER: 0XFFFFFF91ECD33560, RBP: 0XFFFFFF91ECD33740, IHR: 0 X 0000000000000002 RDI: 0 X 0000000000000000

  R8: 0X000000000000FFFF, R9: 0 X 0000000000000001, R10: 0 X 0000000000000002, R11: 0XFFFFFF9250DD0000

  R12: 0X00000000183B1101, R13: 0X00000000183F1101, R14: 0 X 0000000018431001, R15: 0X00000000182B1101

  RFL: 0 X 0000000000010286, RIP: 0XFFFFFF7F827954F0, CS: 0000000000000008, SS 0 X: 0 X 0000000000000010

  Lack of CR2: 0 x 0000000000000134, error code: 0 x 0000000000000002, CPU error: 0x0, PL: 0

  Backtrace (CPU 0), frame: return address

  0xffffff91ecd331f0: 0xffffff80002dab12

  0xffffff91ecd33270: 0xffffff80003ce40a

  0xffffff91ecd33450: 0xffffff80003ec273

  0xffffff91ecd33470: 0xffffff7f827954f0

  0xffffff91ecd33740: 0xffffff7f8279bd2d

  0xffffff91ecd337b0: 0xffffff7f82742939

  0xffffff91ecd337e0: 0xffffff7f8279bab9

  0xffffff91ecd33820: 0xffffff7f8274299a

  0xffffff91ecd33850: 0xffffff7f8279ba2a

  0xffffff91ecd33890: 0xffffff7f82742daa

  0xffffff91ecd33b10: 0xffffff7f8274242b

  0xffffff91ecd33b50: 0xffffff7f827422de

  0xffffff91ecd33b80: 0xffffff7f827419b4

  0xffffff91ecd33bc0: 0xffffff7f8279befd

  0xffffff91ecd33be0: 0xffffff80008df277

  0xffffff91ecd33d20: 0xffffff8000397cc0

  0xffffff91ecd33e30: 0xffffff80002df283

  0xffffff91ecd33e60: 0xffffff80002c28b8

  0xffffff91ecd33ea0: 0xffffff80002d2665

  0xffffff91ecd33f10: 0xffffff80003b8bda

  0xffffff91ecd33fb0: 0xffffff80003eca96

  Extensions of core in backtrace:

  com.apple.iokit.IOAcceleratorFamily2 (205.3) [1B6944F0-F0F4-26-892C-46EB6C5C743 3D 3]@0xffffff7f82719000-> 0xffffff7f82792fff]

  dependency: com.apple.iokit.IOPCIFamily (2.9) [4FE41F9B-2849-322A-BBF8-A94816C003D6] @ 7f80b2c000 0xffffff

  dependency: com.apple.iokit.IOGraphicsFamily (2.4.1) [172C2960-EDF5-382D-80A5-C13E97D74880] @0 xffffff7f81629000

  com.apple.driver.AppleIntelHD5000Graphics (10.1.4) [D35C5903-CC83-3824-8F8B - 810-8 A8A3430]@0xffffff7f82793000-> 0xffffff7f82800fff]

  dependency: com.apple.iokit.IOSurface (108.2.1) [7B01F01F-CC13-328B-BA71-E574C5FA3E25] @ ff7f81498000 0xffff

  dependency: com.apple.iokit.IOPCIFamily (2.9) [4FE41F9B-2849-322A-BBF8-A94816C003D6] @ 7f80b2c000 0xffffff

  dependency: com.apple.iokit.IOGraphicsFamily (2.4.1) [172C2960-EDF5-382D-80A5-C13E97D74880] @0 xffffff7f81629000

  dependency: com.apple.iokit.IOAcceleratorFamily2 (205.3) [3]@0xffffff7f82719000 1B6944F0-F0F4-26-892C-46EB6C5C743 3D

  The process corresponding to the current thread BSD name: com.apple.WebKit

  Mac OS version:

  15E65

  Kernel version:

  15.4.0 Darwin kernel version: Fri Feb 26 22:08:05 PST 2016; root:XNU-3248.40.184~3/RELEASE_X86_64

  Kernel UUID: 4E7B4496-0B81-34E9-97AF-F316103B0839

  Text __HIB base: 0xffffff8000100000

  Name of system model: MacBookPro11, 4 (Mac-06F11FD93F0323C5)

  Availability of the system in nanoseconds: 109407725656992

  last load kext to 4551417542: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7f8231c000 size 32768)

  Finally unloaded kext to 109463299999: com.apple.driver.AppleFileSystemDriver 3.0.1 (addr 0xffffff7f82c19000 size 8192)

  kexts responsible:

  com.apple.driver.AudioAUUC 1.70

  com.apple.driver.AGPM 110.21.18

  com.apple.driver.ApplePlatformEnabler 2.6.0d0

  com.apple.driver.X86PlatformShim 1.0.0

  com Apple.filesystems.autofs 3.0

  com.apple.driver.AppleOSXWatchdog 1

  com.apple.driver.AppleGraphicsDevicePolicy 3.7.7

  com.apple.driver.AppleUpstreamUserClient 3.6.1

  com.apple.driver.AppleHDA 274.7

  com Apple.Driver.pmtelemetry 1

  com.apple.iokit.IOUserEthernet 1.0.1

  com.apple.iokit.IOBluetoothSerialManager 4.4.4f4

  com.apple.driver.AppleIntelHD5000Graphics 10.1.4

  com.apple.Dont_Steal_Mac_OS_X 7.0.0

  com.apple.driver.AppleHV 1

  com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.4.4f4

  com.apple.driver.AppleBacklight 170.8.9

  com.apple.driver.AppleLPC 3.1

  com.apple.driver.AppleSMCLMU 208

  com.apple.driver.AppleCameraInterface 5.46.0

  com.apple.driver.AppleIntelFramebufferAzul 10.1.4

  com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0

  com.apple.driver.AppleThunderboltIP 3.0.8

  com.apple.driver.AppleMCCSControl 1.2.13

  com.apple.driver.AppleUSBCardReader 3.7.1

  com.apple.driver.AppleTopCaseHIDEventDriver 86

  com.apple.driver.AppleUSBTopCaseDriver 86

  2.8.5 com.apple.iokit.IOAHCIBlockStorage

  com.apple.iokit.AppleBCM5701Ethernet 10.2.0

  com.apple.driver.AirPort.Brcm4360 1040.1.1a6

  com.apple.driver.AppleAHCIPort 3.1.8

  com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

  com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0

  com.apple.BootCache 38

  com.apple.driver.AppleSmartBatteryManager 161.0.0

  com.apple.driver.AppleACPIButtons 4.0

  com.apple.driver.AppleRTC 2.0

  com.apple.driver.AppleHPET 1.8

  com.apple.driver.AppleSMBIOS 2.1

  com.apple.driver.AppleACPIEC 4.0

  com.apple.driver.AppleAPIC 1.7

  com Apple.NKE.applicationfirewall 163

  com Apple.Security.Quarantine 3

  com.apple.security.TMSafetyNet 8

  com Apple.kext.Triggers 1.0

  com.apple.driver.DspFuncLib 274.7

  com.apple.kext.OSvKernDSPLib 525

  com.apple.iokit.IOSerialFamily 11

  com.apple.iokit.IOSurface 108.2.1

  com.apple.driver.CoreCaptureResponder 1

  com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.4.4f4

  com.apple.iokit.IOBluetoothFamily 4.4.4f4

  com.apple.driver.AppleHDAController 274.7

  com.apple.iokit.IOHDAFamily 274.7

  com.apple.iokit.IOAudioFamily 204.3

  com.apple.vecLib.kext 1.2.0

  com.apple.driver.AppleBacklightExpert 1.1.0

  com.apple.iokit.IONDRVSupport 2.4.1

  com.apple.driver.AppleGraphicsControl 3.12.6

  com.apple.AppleGraphicsDeviceControl 3.12.6

  com.apple.iokit.IOAcceleratorFamily2 205.3

  com.apple.driver.X86PlatformPlugin 1.0.0

  com.apple.driver.IOPlatformPluginFamily 6.0.0d7

  com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

  com.apple.driver.AppleSMC 3.1.9

  com.apple.driver.AppleSMBusController 1.0.14d1

  com.apple.iokit.IOGraphicsFamily 2.4.1

  com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.7

  com.apple.iokit.IOUSBMassStorageDriver 1.0.0

  com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7

  com.apple.driver.AppleThunderboltDPInAdapter 4.1.3

  com.apple.driver.AppleThunderboltDPAdapterFamily 4.1.3

  com.apple.driver.AppleThunderboltPCIUpAdapter 2.0.2

  com.apple.driver.AppleThunderboltPCIDownAdapter 2.0.2

  com.apple.driver.usb.AppleUSBHub 1.0.1

  com.apple.driver.usb.IOUSBHostHIDDevice 1.0.1

  com.apple.driver.AppleHIDKeyboard 181

  com.apple.driver.AppleMultitouchDriver 304.10.2

  com.apple.driver.AppleHIDTransport 5

  com Apple.Driver.USB.cdc 5.0.0

  com.Apple.Driver.USB.Networking 5.0.0

  com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1

  com.apple.driver.CoreStorage 517.20.1

  com.apple.iokit.IOEthernetAVBController 1.0.3b3

  com.apple.driver.AppleThunderboltNHI 4.0.4

  com.apple.iokit.IOThunderboltFamily 6.0.2

  com.apple.iokit.IO80211Family 1110.26

  com.apple.driver.mDNSOffloadUserClient 1.0.1b8

  com Apple.Driver.corecapture 1.0.4

  com.apple.iokit.IOAHCIFamily 2.8.1

  com.apple.driver.usb.AppleUSBXHCIPCI 1.0.1

  com.apple.driver.usb.AppleUSBXHCI 1.0.1

  com.apple.iokit.IONetworkingFamily 3.2

  com.apple.iokit.IOUSBFamily 900.4.1

  com.apple.iokit.IOUSBHostFamily 1.0.1

  com.apple.driver.AppleUSBHostMergeProperties 1.0.1

  com.apple.driver.AppleEFINVRAM 2.0

  com.apple.driver.AppleEFIRuntime 2.0

  com.apple.iokit.IOHIDFamily 2.0.0

  com.apple.iokit.IOSMBusFamily 1.1

  com Apple.Security.sandbox 300.0

  com.apple.kext.AppleMatch 1.0.0d1

  com.apple.driver.AppleKeyStore 2

  com.apple.driver.AppleMobileFileIntegrity 1.0.5

  com.apple.driver.AppleCredentialManager 1.0

  com.apple.driver.DiskImages 417.2

  com.apple.iokit.IOStorageFamily 2.1

  com.apple.iokit.IOReportFamily 31

  com.apple.driver.AppleFDEKeyStore 28.30

  com.apple.driver.AppleACPIPlatform 4.0

  com.apple.iokit.IOPCIFamily 2.9

  com.apple.iokit.IOACPIFamily 1.4

  com.apple.kec.Libm 1

  com Apple.KEC.pthread 1

  com Apple.KEC.corecrypto 1.0

  Model: MacBookPro11, 4, MBP114.0172.B09 of BootROM, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, MSC 2.29f24

  Graphics card: Intel integrated Iris Pro, Intel Iris Pro,

  Memory module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020

  Memory module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533642465238412D50422020

  Airport: spairport_wireless_card_type_airport_extreme (0x14E4, 0 x 152), Broadcom BCM43xx 1.0 (7.21.95.175.1a6)

  Bluetooth: Version 4.4.4f4 17685, 3 services, 27 aircraft, 1 incoming serial ports

  Service network: Ethernet, Ethernet, en4 Thunderbolt

  Network service: Wi - Fi, AirPort, en0

  PCI card: Apple 57762-A0, controller, Ethernet, Thunderbolt@195,0,0

  Serial ATA Device: APPLE SM0256G, 251 GB SSD

  USB device: USB 3.0 Bus

  USB device: Apple keyboard / Trackpad

  USB Device: USB Bluetooth host controller

  USB device: USB RECEIVER

  USB device: USB 2.0 Hub

  USB device: Series OfficeJet 4650

  USB device: USB 2.0 Hub

  USB device: USB printer

  Bus crush: MacBook Pro, Apple Inc., 27.1

  Device of lightning: lightning to Gigabit Ethernet adapter, Apple Inc., 1, 5.5

  The problem may be caused by a bug in OS X, triggered by "Flash Player."

  Please open Safari preferences window and select the Security tab uncheck the box marked

  Enable Plug-ins

  See if there is an improvement.

  You can watch videos on YouTube and other sites without using Flash by installing the extension "ClickToFlash" or "ClickToPlugin' Safari. This isn't an endorsement. You should always do your own research to determine the safety and effectiveness of any third-party software before using it.

• A satellite - unexpected stops

  Hi... This is my 2nd laptop Toshiba Satelite.
  The 1st was replaced after that continuous stops make unusable when I was not able to start again.

  I've had this one since November 2011 and it starts displaying the same behavior as the first with the stops happening. When I return to my computer, after leaving it for a while, he stopped.

  Is this an inherent problem with the Toshiba Satellite and it can be the cause?

  Your contribution is appreciated.
  Jane

  Hello

  The laptop stops automatically due to high temperature.
  It is a kind of protection to protect the internal parts from damage.

  The question is: why the temperature is too high?
  Clean the vents? Dust and debris can affect cooling performance
  If the cooling fans should be cleaned periodically

  Also, you must make sure that the laptop s of aeration is not blocked using the laptop in a bad position.