Codian 8510-Unexpected reboot

Hello

MCU: Codian MSE 8510 Blade (configured in HD mode)

Software version: 4.2 (1.46)
Build: 6.17 (1.46)

The bridge has been restarted unexpectedly this morning and we are currently investigating this problem. I would be grateful if you can help me and provide some ideas to identify this problem.

We assume that it is a power factor as on the MSE 8050 supervisor, there is an error message:

Insufficient current capacity (requires at least A 24.20)

Do you think that there is a relationship with this error message?

Hi Firdaush,

Could you please provide some basic information: -.

Is this a new installation?
It worked before?
Did you calculate the power required when installing it for the first time properly?
How many leaves are there in the frame?
You could also attach a brief overview of the the MCU event logs.

Thank you

Saurabh

Tags: Cisco Support

Similar Questions

MBP mid-2010 (15-inch, 2.53 GHz, i5) unexpected reboot of the system of dynamic switching map chart

Hi there, I've never had this problem when I bought my MBP in 2010, but after the problem with unexpected reboots of El Capitan passage has become more common and is really affecting the productivity of my laptop.

For clarity, here's my cell phone information:

MacBook Pro (15-inch, mid 2010)

Processor: Intel Core i5 2.53 GHz to

Memory: 8 GB 1067 MHz DDR3

Graphics card:

integrated - Intel HD Graphics 288 MB

discreet - NVIDIA GeForce GT 330 M 256 MB

I ran the the Apple Hardware Test with no problems found. After looking on the forums and identifying the problem I installed gfxCardStatus to keep the graphics card using only internally, however, some programs force the use of Nvidia, which translates as the unexpected restarts.

The latest report of panic is attached below:

In any case, it is quite upsetting that after spending thousands of dollars on apple and laptops high-end, these problems are properly does not recognize their existence. After discussing with them several times they fail to take responsibility, when it is clearly a case of defective material...

Any suggestions for managing at least this issue would be very useful.

Thank you

Philippe

Sam 5 17:01:31 dec 2015

Panic report *.

panic (cpu 1 0xffffff7f8ddf1bad appellant): "panic GPU: 7f [] 3 3 0 0 0 0 3: NVRM [0 / 1:0:0]: error 0 x 00000100 reading: CFG 0xffffffff, 0xffffffff, 0xffffffff, BAR0 0xd2000000 0xffffff91277cf000 sControl-3.11.33.1/src/AppleMuxControl/kext/GPUPanic.cpp:127 P2/4\n"@/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphic 0x0a5480a2, D0,

Backtrace (CPU 1), frame: return address

0xffffff811461b0a0: 0xffffff800ace5307

0xffffff811461b120: 0xffffff7f8ddf1bad

0xffffff811461b200: 0xffffff7f8b97ffa4

0xffffff811461b2c0: 0xffffff7f8ba4cadd

0xffffff811461b300: 0xffffff7f8ba4cb48

0xffffff811461b380: 0xffffff7f8bcd1a23

0xffffff811461b4f0: 0xffffff7f8ba70b79

0xffffff811461b510: 0xffffff7f8b986cfd

0xffffff811461b5c0: 0xffffff7f8b984690

0xffffff811461b7c0: 0xffffff7f8b98576f

0xffffff811461b8a0: 0xffffff7f8d2810ea

0xffffff811461b8e0: 0xffffff7f8d290aa3

0xffffff811461b900: 0xffffff7f8d2bf3ea

0xffffff811461b940: 0xffffff7f8d2bf449

0xffffff811461b980: 0xffffff7f8d296642

0xffffff811461b9d0: 0xffffff7f8d2620ae

0xffffff811461ba70: 0xffffff7f8d25df51

0xffffff811461baa0: 0xffffff7f8d25bae5

0xffffff811461bae0: 0xffffff800b2e2057

0xffffff811461bb80: 0xffffff800b2e4828

0xffffff811461bbe0: 0xffffff800b2e1967

0xffffff811461bd20: 0xffffff800ada07d0

0xffffff811461be30: 0xffffff800ace9aa3

0xffffff811461be60: 0xffffff800accd478

0xffffff811461bea0: 0xffffff800acdcfd5

0xffffff811461bf10: 0xffffff800adc13aa

0xffffff811461bfb0: 0xffffff800adf4b36

Extensions of core in backtrace:

com.apple.driver.AppleMuxControl (3.11.33b1) [FF6CE9C5-9D8F - a 3, 48 - 9 d 10-2BB9C2DDD22 7]@0xffffff7f8dde3000-> 0xffffff7f8ddf6fff

dependency: com.apple.driver.AppleGraphicsControl (3.11.33b1) [4ADB751E-5208-3DA7-A8C3-E9EC07 263B16]@0xffffff7f8dddb000

dependency: com.apple.iokit.IOACPIFamily (1.4) [CBAE26D8-0ACB-3C1F-8347-FDCA67EC40B3] @0xfffff f7f8b7b4000

dependency: com.apple.iokit.IOPCIFamily (2.9) [8E5F549E-0055-3C0E-93F8-E872A048E31B] @ 7f8b52d000 0xffffff

dependency: com.apple.iokit.IOGraphicsFamily (2.4.1) [48AC8EA9-BD3C-3FDC-908D-09850215AA32] @0 xffffff7f8b8d2000

dependency: com.apple.driver.AppleBacklightExpert (1.1.0) [5CB7D4B7-B100-34EE-BD40-1EC07E865C 67]@0xffffff7f8ddde000

com.apple.nvidia.classic.NVDAResmanTesla (10.0) [05FC5D7E-BB0B-3232-BBBD-8A49B687 0D8B]@0xffffff7f8b929000-> 0xffffff7f8bb9efff

dependency: com.apple.iokit.IOPCIFamily (2.9) [8E5F549E-0055-3C0E-93F8-E872A048E31B] @ 7f8b52d000 0xffffff

dependency: ffff7f8b919000 @0xff com.apple.iokit.IONDRVSupport (2.4.1) [814A7F4B-03EF-384A-B205-9840F0594421]

dependency: com.apple.iokit.IOGraphicsFamily (2.4.1) [48AC8EA9-BD3C-3FDC-908D-09850215AA32] @0 xffffff7f8b8d2000

com.apple.nvidia.classic.NVDANV50HalTesla (10.0) [CA 56199, 6 - 3C8D - 3EBB - B5EF - 7B1B467 8ACF9]@0xffffff7f8bba9000-> 0xffffff7f8be56fff

dependency: com.apple.nvidia.classic.NVDAResmanTesla (10.0.0) [05FC5D7E-BB0B-3232-BBBD-8A49B6 870D8B]@0xffffff7f8b929000

dependency: com.apple.iokit.IOPCIFamily (2.9) [8E5F549E-0055-3C0E-93F8-E872A048E31B] @ 7f8b52d000 0xffffff

com.apple.GeForceTesla (10.0) [49982DF3-8146-3BD0-AD3F-A7E7AB5ACBB5] @0xffffff7f8d 240000-> 0xffffff7f8d30bfff

dependency: com.apple.iokit.IOPCIFamily (2.9) [8E5F549E-0055-3C0E-93F8-E872A048E31B] @ 7f8b52d000 0xffffff

dependency: ffff7f8b919000 @0xff com.apple.iokit.IONDRVSupport (2.4.1) [814A7F4B-03EF-384A-B205-9840F0594421]

dependency: com.apple.iokit.IOGraphicsFamily (2.4.1) [48AC8EA9-BD3C-3FDC-908D-09850215AA32] @0 xffffff7f8b8d2000

dependency: com.apple.nvidia.classic.NVDAResmanTesla (10.0.0) [05FC5D7E-BB0B-3232-BBBD-8A49B6 870D8B]@0xffffff7f8b929000

Corresponding to the current thread BSD process name: WindowServer

Mac OS version:

15B 42

Kernel version:

Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:XNU-3247.10.11~1/RELEASE_X86_64

Kernel UUID: AB5FC1B4-12E7-311E-8E6F-9023985D8C1D

Slide kernel: 0x000000000aa00000

Text of core base: 0xffffff800ac00000

Text __HIB base: 0xffffff800ab00000

Name of system model: MacBookPro6, 2 (Mac-F22586C8)

Availability of the system in nanoseconds: 1557747038609

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

Finally unloaded kext to 240741317817: com.apple.driver.usb.AppleUSBUHCI 1.0.1 (addr 0xffffff7f8c248000 size 126976)

kexts responsible:

com.radiosilenceapp.nke.Filter 1.1

com.apple.driver.AudioAUUC 1.70

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AGPM 110.20.21

com Apple.filesystems.autofs 3.0

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.AppleMikeyHIDDriver 124

com.apple.driver.AppleMikeyDriver 272.50.31

com Apple.Driver.pmtelemetry 1

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.driver.AppleUpstreamUserClient 3.6.1

com.apple.iokit.IOBluetoothSerialManager 4.4.2f1

com.apple.GeForceTesla 10.0.0

com.apple.driver.AppleHDA 272.50.31

com.apple.driver.AppleIntelHDGraphics 10.0.0

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleHV 1

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.4.2f1

com.apple.driver.AppleSMCPDRC 1.0.0

com.apple.driver.AppleMuxControl 3.11.33b1

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0

com.apple.driver.AppleMCCSControl 1.2.13

com.apple.driver.AppleIntelHDGraphicsFB 10.0.0

com.apple.driver.AppleSMCLMU 208

com.apple.driver.AppleLPC 3.1

com.apple.driver.SMCMotionSensor 3.0.4d1

com.apple.driver.AppleUSBTCButtons 245,4

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0

com.apple.BootCache 37

com.apple.driver.AppleUSBTCKeyboard 245,4

com.apple.driver.AppleUSBCardReader 3.7.1

com.apple.driver.AppleIRController 327,5

com.apple.iokit.SCSITaskUserClient 3.7.7

com.apple.iokit.IOAHCIBlockStorage 2.8.0

com.apple.driver.AirPort.Brcm4331 800.20.24

com.apple.driver.AppleFWOHCI 5.5.2

3.1.5 com.apple.driver.AppleAHCIPort

com.apple.iokit.AppleBCM5701Ethernet 10.1.11

com.apple.driver.usb.AppleUSBEHCIPCI 1.0.1

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleACPIButtons 4.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.driver.AppleIntelCPUPowerManagementClient 218.0.0

com Apple.NKE.applicationfirewall 163

com Apple.Security.Quarantine 3

com.apple.security.TMSafetyNet 8

com.apple.driver.AppleIntelCPUPowerManagement 218.0.0

com.apple.AppleGraphicsDeviceControl 3.11.33b1

com Apple.kext.Triggers 1.0

com.apple.iokit.IOSurface 108.0.1

com.apple.iokit.IOSerialFamily 11

com.apple.nvidia.classic.NVDANV50HalTesla 10.0.0

com.apple.nvidia.classic.NVDAResmanTesla 10.0.0

com.apple.driver.DspFuncLib 272.50.31

com.apple.kext.OSvKernDSPLib 525

com.apple.driver.CoreCaptureResponder 1

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.4.2f1

com.apple.iokit.IOBluetoothFamily 4.4.2f1

com.apple.driver.AppleSMBusPCI 1.0.14d1

com.apple.driver.AppleBacklightExpert 1.1.0

com.apple.iokit.IONDRVSupport 2.4.1

com.apple.driver.AppleGraphicsControl 3.11.33b1

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

com.apple.driver.AppleSMBusController 1.0.14d1

com.apple.iokit.IOFireWireIP 2.2.6

com.apple.driver.AppleHDAController 272.50.31

com.apple.iokit.IOGraphicsFamily 2.4.1

com.apple.iokit.IOHDAFamily 272.50.31

com.apple.iokit.IOAudioFamily 204,1

com.apple.vecLib.kext 1.2.0

com.apple.driver.IOPlatformPluginFamily 6.0.0d7

com.apple.driver.AppleSMC 3.1.9

com.apple.driver.CoreStorage 517

com.apple.driver.usb.IOUSBHostHIDDevice 1.0.1

com.apple.driver.AppleUSBMultitouch 250.4

com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.7

com.apple.iokit.IOUSBMassStorageDriver 1.0.0

com.apple.iokit.IOUSBHIDDriver 900.4.1

com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.7

com.apple.iokit.IOBDStorageFamily 1.8

com.apple.iokit.IODVDStorageFamily 1.8

com.apple.iokit.IOCDStorageFamily 1.8

com.apple.driver.usb.AppleUSBHub 1.0.1

com.apple.iokit.IOAHCISerialATAPI 2.6.2

com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7

1101.24 com.apple.iokit.IO80211Family

com Apple.Driver.corecapture 1.0.4

4.5.8 com.apple.iokit.IOFireWireFamily

com.apple.iokit.IOAHCIFamily 2.8.0

com.apple.iokit.IOEthernetAVBController 1.0.3b3

com.apple.driver.mDNSOffloadUserClient 1.0.1b8

com.apple.iokit.IONetworkingFamily 3.2

com.apple.iokit.IOUSBFamily 900.4.1

com.apple.driver.usb.AppleUSBEHCI 1.0.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 415

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: MacBookPro6, 2, MBP61.0057.B11 of BootROM, 2 processors, Intel Core i5 2.53 GHz, 8 GB, MSC 1.58f17

Graphics: integrated graphics card Intel HD, Intel HD Graphics,

Graphics card: NVIDIA GeForce GT 330 M, NVIDIA GeForce GT 330 M, PCIe, 256 MB

Memory module: DIMM0/0 BANK, 4 GB DDR3, 1067 MHz, 0x029E, 0x434D5341344758334D314131303636433720

Memory module: DIMM0/1 BANK, 4 GB DDR3, 1067 MHz, 0x029E, 0x434D5341344758334D314131303636433720

Airport: spairport_wireless_card_type_airport_extreme (0x14E4, 0 x 93), Broadcom BCM43xx 1.0 (5.106.98.100.24)

Bluetooth: Version 4.4.2f1 16391, 3 services, 27 aircraft, 1 incoming serial ports

Network service: Wi - Fi, AirPort, en1

Serial ATA Device: TOSHIBA MK5055GSXF, 500,11 GB

Serial ATA Device: MATSHITADVD-R UJ-898

USB device: USB 2.0 Bus

USB device: Hub

USB device: USB receiver

USB Device: Card reader

USB device: Apple keyboard / Trackpad

USB device: Hub BRCM2070

USB Device: USB Bluetooth host controller

USB device: USB 2.0 Bus

USB device: Hub

USB Device: IR receiver

USB device: ISight built-in

Crush Bus:

You have the MacBookPro6, 2 - the Edsel of Mac. There may be the failure of logic-board that was covered by a recall program that is now complete.

The model was abandoned in February 2011. From five years from this date, it will be classified by Apple as "vintage product." This means that Apple will refuse probably a maintenance action (see exceptions on the linked page.) In this case, you will need to go to an independent service provider. The part can be is no longer available, or the repair may not be profitable.

An appointment of 'Genius' in an Apple Store, or go to a different service provider authorized, to have the tested machine. Diagnoses of current equipment used by service providers don't detect the fault. There is a specific test for the same problem that Apple calls "VST" (for "video switching Test.") Ask for it. A "Failed" result means that the defect is present.

You may be quoted a price of about $350 (in the United States) for a "repair," which is to send the unit to a repair shop central and lasts about two weeks. For this package, found nothing wrong with it should be fixed, not only the logic board.

Sometimes, the spare part is also faulty, so be prepared for this eventuality. If you decide to pay for a new logic board, rigorously test during the 90 day warranty on the repair. Some owners have reported that they went up to three replacement boards before you get one that worked.

If you don't want to pay for the repair, you may (or may not) be able to work around the problem by disabling automatic switching graphics. To use the separate graphics processor, you will need a third-party utility to manually switch to him.

Often, the problems start after an upgrade of the OS. If the upgrade has been recently, and you have backups, you can then go back to a previous version of OS X.

recovery of incomplete restore error problems, era could be unexpected reboot during the update of the factory"

Get incomplete restoration always returns to the screen when you start again. In the details, he said that there could be unexpected restarts during the upgrade of the plant

the process causes panic CTO because the image might not be normal.

Passes information on the HP forums:

http://h30434.www3.HP.com/T5/notebook-hardware/long-DST-failed/TD-p/2743587

http://h30434.www3.HP.com/T5/notebook-hardware/hard-disk-long-DST-test-failed/TD-p/4063766

That is right.

Server 2003 keeps encountering unexpected reboots

Hello

I really need help with that. We have a Windows Server 2003 Standard Edition R2 SP3. We have updated all the drivers of devices, run the updates of windows, reinstall hardware and blown out server (to remove fragments of dust). The server keeps restarting every 3 days on his own. I got a BSOD with damage to reserve in the file box. Can anyone provide an overview? I read the article for the damage to the reserve, but have yet to find a way to solve the http://support.microsoft.com/kb/304208/en-usproblem.

Thank you!

Support is located in the Windows Server Forums:
http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer/

Unexpected reboot Windows 2008 R2 server caused by PROCEXP111. SYS

The computer was restarted after a bugcheck. The bugcheck was: 0 x 00000050 (0xfffffa80bd8dc050, 0 x 0000000000000000, 0xfffff88008072ddd, 0 x 0000000000000000). A dump was saved in the: C:\Windows\Minidump\052313-36332-01.dmp. Report ID: 052313-36332-01.

Report of the debugger:

Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version

Copyright (c) Microsoft Corporation. All rights reserved.

Loading dump file [C:\Windows\Minidump\052313-36332-01.dmp]

The mini kernel dump file: only registers and the trace of the stack are available

Symbol search path is: * invalid *.

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

* Loading of the symbol may be unreliable without a symbol search path. *

* Use .symfix to get the debugger to choose a symbol path. *

* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *

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

Executable search path is:

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

* Symbols cannot be loaded because the path is not initialized. *

* *

* The symbol path can be defined: *.

* using the _NT_SYMBOL_PATH environment variable. *

* using the o - argument when starting the debugger. *

* using the .sympath and .sympath + *.

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

Could not load the ntoskrnl.exe, 0n2 error Win32 image

WARNING: Unable to verify timestamp for ntoskrnl.exe

ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (24 procs) free x 64

Product: Server, suite: TerminalServer SingleUserTS Enterprise

Computer name:

Kernel base = 0xfffff800 '01a1d000 PsLoadedModuleList = 0xfffff800' 01b 61670

The debugging session: 17:52:43.775 Thu May 23, 2013 (UTC + 10:00)

System Uptime: 118 days 1:53:41.084

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

* Symbols cannot be loaded because the path is not initialized. *

* *

* The symbol path can be defined: *.

* using the _NT_SYMBOL_PATH environment variable. *

* using the o - argument when starting the debugger. *

* using the .sympath and .sympath + *.

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

Could not load the ntoskrnl.exe, 0n2 error Win32 image

WARNING: Unable to verify timestamp for ntoskrnl.exe

ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe

Loading the kernel symbols

...............................................................

................................................................

..................

Loading user symbols

Loading unloaded module list

..................................................

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

* *

* Bugcheck analysis *.

* *

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

Use
! analyze - v to obtain detailed debugging information.

Bugcheck 50, {fffffa80bd8dc050, 0, fffff88008072ddd, 0}

The kernel symbols are FALSE. Correct symbols to do the analysis.

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt! _KPRCB *.

*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
! KPRCB ***
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
! _KPRCB *.
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
! KPRCB ***
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt! _KPRCB *.

*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
!_KPRCB ***
*** ***

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

Cannot load the image PROCEXP111. SYS, 0n2 error Win32

WARNING: Unable to verify timestamp for PROCEXP111. SYS

ERROR: Module load completed but symbols can not be loaded for PROCEXP111. SYS

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt! _KPRCB *.

*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt! _KPRCB *.

*** ***

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

Probably caused by: PROCEXP111. SYS (PROCEXP111 + 1ddd)

Follow-up: MachineOwner

---------

8: kd >
! analyze - v
*******************************************************************************

* *

* Bugcheck analysis *.

* *

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

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

It must be protected by a probe. In general, the address is simple bad or it

pointing to freed memory.

Arguments:

Arg1: fffffa80bd8dc050, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff88008072ddd, if not zero, the address of the instruction that refers to bad memory

address.

Arg4: 0000000000000000, (reserved)

Debugging information:

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

The kernel symbols are FALSE. Correct symbols to do the analysis.

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
!_KPRCB ***
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
! KPRCB ***
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
!_KPRCB ***
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt! KPRCB ***

*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
!_KPRCB ***
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt! _KPRCB *.

*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
!_KPRCB ***
*** ***

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

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

*** ***

*** ***

Your debugger is not using the appropriate symbols *.

*** ***

In order for this command works correctly, your symbol path *.

should point to .pdb files have the type information complete. ***

*** ***

Some (such as the public OS symbols) .pdb files are not *.

contain the required information. The contact group that *.

you provided with these symbols, if you need this command for *.

work. ***

*** ***

Type referenced: nt
! _KPRCB *.
*** ***

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

ADDITIONAL_DEBUG_TEXT:

Use '! findthebuild' command to search for the generation of target information.

If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.

FAULTING_MODULE: fffff80001a1d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 47194089

READ_ADDRESS: could not get nt! MmSpecialPoolStart

Unable to get nt! MmSpecialPoolEnd

Unable to get nt! MmPoolCodeStart

Unable to get nt
! MmPoolCodeEnd
fffffa80bd8dc050

FAULTING_IP:

PROCEXP111 + 1ddd

fffff880'08072ddd 66833805 cmp word ptr [rax], 5

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0 X 50

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80001a43eec to fffff80001a9bfc0

STACK_TEXT:

fffff880 '06-60348 fffff800' 01a43eec: 00000000'00000050 fffffa80 'bd8dc050 00000000 00000000' fffff880' 06a604b0: nt + 0x7efc0

fffff880 '06 a 60350 00000000' 00000050: fffffa80 'bd8dc050 00000000 00000000' fffff880' 06a604b0 00000000' 00000000: nt + 0x26eec

fffff880 '06-60358 fffffa80' bd8dc050: 00000000 00000000' fffff880 '06a604b0 00000000 00000000' fffffa80' 7d2c61d0: 0 x 50

fffff880'06 has 60360 00000000 00000000': fffff880 '06a604b0 00000000 00000000' fffffa80' 7d2c61d0 00000000' 00000000: 0xfffffa80'bd8dc050

STACK_COMMAND: .bugcheck; Ko

FOLLOWUP_IP:

PROCEXP111 + 1ddd

fffff880'08072ddd 66833805 cmp word ptr [rax], 5

SYMBOL_NAME: PROCEXP111 + 1ddd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: PROCEXP111

NOM_IMAGE: PROCEXP111. SYS

BUCKET_ID: WRONG_SYMBOLS

Follow-up: MachineOwner

---------

Hello

Support for Windows Server is not provided in these forums. On the other hand, it please repost your question in the relevant Microsoft TechNet forum here:

http://social.technet.microsoft.com/Forums/en-us/category/windowsserver .

Thank you. :)

My PC (Windows XP SP3) restarts unexpectedly when you run Picasa Google Chrome and since I installed Acrobat Reader 10 it also occurs with this program.

Original title: unexpected reboot

My PC (Windows XP SP3) restarts unexpectedly when you run Picasa Google Chrome and since I installed Acrobat Reader 10 it also occurs with this program.

Maybe the problem is related to this message in log file:
SSD HDD access service-service & can not start due to the following error: the system cannot find the path given.
Source: Service Control Manager

I would be very grateful if you can help me.

Hello

Step 1: Use disable automatic restart on system failure option and check if you can find any error message. Previous post the error message complete and accurate which could help us help you better.

Steps to select Disable automatic restart on system failure option:

1. reboot the computer
2 start typing the F8 key
3. you get it anticipated the startup option window
4. Select DisaDisable automatic restart in the event of system failure

Step 2: Check if the problem persists in the clean boot state.

From your computer by using a minimal set of drivers and startup programs so that you can determine if a background program is interfering with your game or program. This type of boot is known as a "clean boot".

Reference:
How to configure Windows XP to start in a "clean boot" State
http://support.Microsoft.com/kb/310353

When you are finished troubleshooting, follow these steps to reset the computer to start as usual:
1. click on start and then click Run.
2. type msconfig and click OK.
The System Configuration Utility dialog box appears.
3. click on the tab general, click Normal Startup - load all services and device drivers and then click OK.
4. When prompted, click on restart to restart the computer.

Unexpected stop blue screen when I turn on my TV

My Windows 7 PC (Nvidia GeForce GTX960) is connected to a TV LG 55LM7600 with a k HDMI AV Pioneer 1020 receiver. MY PC is always on. Everytime I turn on my TV, the PC suffers an unexpected reboot. Can someone tell me the culprit?

Signature of the problem:

Problem event name: BlueScreen

OS version: 6.1.7601.2.1.0.256.48

Locale ID: 1033

More information about the problem:

BCCode: 1000007e

BCP1: FFFFFFFFC0000005

BCP2: FFFFF88004177F4F

BCP3: FFFFF8800D154D08

BCP4: FFFFF8800D154560

OS version: 6_1_7601

Service Pack: 1_0

Product: 256_1

Files helping to describe the problem:

C:\Windows\Minidump\102115-10420-01.dmp

C:\Users\Djuan\AppData\Local\Temp\WER-30310-0.SysData.XML

Read our privacy statement online:

http://go.Microsoft.com/fwlink/?LinkId=104288&clcid=0x0409

If the online privacy statement is not available, please read our offline privacy statement:

C:\Windows\system32\en-US\erofflps.txt

Associated with the VirtuWDDM.sys LucidInterop Lucidlogix Inc. WDDM driver. Yours is 2011.

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

Failed to create the Conference ' 8801 - Test connection '-duplicate digital id

Running 13.1 TMS and Codian 8510 SD blade running 4.20 (1.43)

When I'm planning through TMS using this card, I get the following error:

Failed to create the Conference ' 8801 - Test connection '-duplicate digital id

However when I'm planning TMS using another slide with the same version of the software it works

Can someone tell me why this is happening?

Anthony

We had the same problem with > = 20 conferences on the blade, and I can tell you that we had the same thing

question and the question went after the 4.2 update (1.50) and TMS13.1.2 (if the MCU upgrade)

alone must fix).

And, you got the point in your last message, > = 20 conf == problem,.<20 =="no">

What I have is that the API MCU always reported only the first 20 conferences.

TMS has created the new conference (and I also saw a new reserved (e) of the Conference on the MCU)

but TMS checked once again if that's really where went wrong because he was not listed in the breast of the

first of all 20 and if it failed.

Codian updates may take some time until the blade is up again after the reboot, so be patient :-)

Good luck!

MacBook Pro hangs after upgrade to Sierra

Hello

I got no internet related topic by Googling on the subject.

Basically, my mac has worked fine before updating the operating system most recent.

Now when I use my Safari to surf on Internet, 9 of 10 times the laptop breaks down.

Can anyone suggest solutions?

Please notify.

Thank you.

TIG

Hi cocomalully,

Welcome to the communities of Apple Support!

We understand that your unexpected Mac restart after update to Mac OS Sierra. This sounds like a frustrating situation, but we are here to help.

To begin troubleshooting unexpected reboot, we propose first of all read and working with the suggestions in the following article:

OS x: when your computer spontaneously restarts or displays "your computer restarted because of a problem." - Apple Support

See you soon!

HP Envy 17-J113TX: incomplete restoration

After having many problems of serious computer I think to be a fault of the user, I decided to do a factory reset. I opened upward the HP's Manager and asked him to reboot to the Recovery Manager. I have selected the minimum image recovery and let it do its thing.

At one point, he said "Restoration incomplete", with the following log:

[17:56:01.30] ChkErrBB.CMD: detect an error in the PININST_BBV.
[17:56:01.33] ChkErrBB.CMD: check c:\system.sav\logs\BurnBootWarn.log
[17:56:01.33] ChkErrBB.CMD: or, visit c:\system.sav\logs\BurnBootMerge.log
[17:56:01.33] ----------------------------------------
[17:56:01.33] critical error condition has been detected to BBV1...
[17:56:01.33]
[17:56:01.33] see the following text of the file if it exists.
[17:56:01.33] - c:\system.sav\Logs\BurnBootWarn.log
[17:56:01.33] - c:\system.sav\Logs\BurnBoot.log
[17:56:01.33]
[17:56:01.33] Switch to 2ndCap WinPE and the show [Recovery Manager] incomplete dialogue.
[17:56:01.33] because the dialogue of RM cannot appear on the screen [start] on Win8 environment.
[17:56:01.33] customer may not notice that RM already shows the error dialog box.
[17:56:01.33]
[17:56:01.33] ----------------------------------------
There might be an unexpected reboot during the PBO clean or last...
The process will cause panic CTO because the image isn't normal...

I googled a bit, try alternatives, including the restoration of the default BIOS settings and set the time to the year 2012, and perform a hard reset. No solution worked.

I have no recovery disks.

What are my options? And this sounds like something that the computer must be returned under warranty?

Thank you.

You should not enter the activation of license key Microsoft Windows 8.1.

It is coded in the BIOS and the operating system should operate when you connect.

Make sure you that you install the version of Windows that your laptop came with. Otherwise, there could be a problem of activation.

E2E34AV: HP ENVY 15 t Quad - recovery is not complete

Hello

I got the blue screen. I try to get back with Flash Drive several times, ultimately has noticed that the hard drive is broken. I got the new hard drive and started the process of recovery with flash player. Laptop shows that Recovery is not over. He showed me below error:

ChkErrBB.CMD: Detects an error in the PININST_BBV.

ChkErrBB.CMD: Check C:\system.sav\logs\BurnBootWarn.log

ChkErrBB.CMD: or, visit c:\system.sav\logs\BurnBootMerge.log

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

Critical error condition has been detected to BBV1...

See the following file, if it exists.

-c:\System.sav\Logs\BurnBootWarn.log

-c:\System.sav\Logs\BurnBoot.log

Go to WinPE 2ndCap and dialog box [Recovery Manager] of Imcomplete.

because the RM dialog may appear on [start] screen on Win8 environment.

customer may not notice that RM already shows the error dialog box.

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

There might be an unexpected reboot during the PBO clean or last...

The process will cause panic CTO because the image isn't normal...

_____________________________________________________

I had the same error before after 6 months of purchase. My laptop is fixed by HP support team. A paper I got from HP says HDD and RAM replaced to solve the problem.

Warranty expired a couple months back. I'll ask experts to guide me how to solve the error above.

Thank you

Vincent

Hi @Venkat_N,

Thank you for visiting the HP Forums! A place where you can find solutions for your problems with the help of the community!

I stumbled upon your post on the laptop and wanted to help you! I looked in your question on your HP ENVY 15 t-j100 Quad Edition CTO Notebook and problems with the installation of the new HARD drive. I would reinsert the hard drive to make sure that all connections are tight. I recommend to restore the default BIOS settings. You could restore the BIOS withthis document by selecting the reload the default BIOS settings. In this way, it will look at the hardware installed on your laptop.

Here is a link to test the hard drive in the BIOS. If the BIOS does not see the hard drive you can not install Windows.

Please let me know how it goes.

You can say thanks for trying to help, by clicking on the Thumbs Up below! .

Thank you.

Pavilion g6-1d21dx: no luck update Pavilion g6-1d21dx to SSD

I tried to replace the hard drive in my g6-1d21dx with a SSD Pavilion before enjoying the free update of Windows 10. I installed the drive (a unit of SanDisk Extreme 480 GB that I had sat unopened for a while) and then used my recovery discs for Windows 7 on SSD. The process seemed to go very well - he went through all the discs five recovery, restarted from the SSD and began the installation process. Soon, I got an error message "restoration incomplete" well. So much for that. (The HP Recovery Manager also gave me this incredibly helpful explanation: "there could be unexpected reboot phase Specialize in BBV1.) ("The process will cause panic CTO because the image might not be normal") on the reset, I also had an error message about ntoskrnl.exe is damaged or missing.

I put the original back drive computer to and updated from Windows 7 to Windows 10 on this drive, just to get the license Windows 10 (it was the last day to get the free upgrade). I also used Windows 10 media creation tool to create a Windows 10 installation DVD. Then, I put the SDS back to and I tried to install Windows 10 using the DVD. I tried several times, but the installation has always fails. I got error messages like "Windows could not set the offline locale information. "Error code: 0x80FE0000" and "we could not format the selected partition. [Error: 0 x 8070057]. "I've also had this a few times:"Windows cannot be installed to this disk. Windows cannot read the selected drive. Windows cannot be installed to this disk. Windows has no determine if this disc and his parents have the necessary driver support. »

This computer isn't all what age - it is possible that the BIOS does not support the SSD? I updated the BIOS of the SSD, but that has not solved the problem. I also made sure the BIOS of the computer is up to date.

Thanks in advance for any relevant information.

Here are the conclusions that I have reached after spending a lot of time on this project to upgrade:

At the beginning of this thread, what you advised me strongly to clone my old hard drive instead of trying a new install of Windows 10 on my SSD. I recommend the contrary unless your system works perfectly with your old hard drive, because this way, you can leave the system, the software and the data files on your old hard drive intact in case you go account you have to go back and check on something or you decide to abandon the upgrade. I found that there is no mystery to a cleaning only install on an SSD, as long your SSD is compatible with your computer. I had updated my old HDD from Windows 7 to Windows 10, and after this upgrade, I was getting other error messages every time, I started the computer (inaccessible_boot_device, unexpected_store_exception and kernel_data_input_error). Since there are so many problems on my old HDD, I have probably restores it to Windows 7 so I can always, in case I ever need to refer to my old configuration. Web sites said that once that Windows 10 has been enabled on your computer, future Windows 10 installs on the computer is automatically turned on, even if you have restored the machine to Windows 7 or Windows 8.

If you try a new installation, make sure that you do so with an attached network cable. It makes a huge difference for me. A clean install without a connected network cable has led to all sorts of problems, including a lack of access to the Internet and some devices are not installed correctly. When I did a clean install with an attached network cable, all of my devices have been installed automatically. This includes the Synaptics touchpad, the HP wireless button, the AMD Radeon graphics card and the Realtek card reader. I didn't need to install whatever it is myself, and the Device Manager does not display the unknown devices. Wireless network connected during installation, even my Wi - Fi was not usable during or after installation.

One final note: my g6 Pavilion is 64-bit capable, but I installed 32-bit Windows 10 on it, because I use an old software running under Windows 64-bit 10. So far, 32-bit Windows 10 seems to work very well.

Pavilion x 360: Recovery Manager / incomplete restoration; Error of CTO

Hello folks...

Ok.. so... Last maybe ish around Friday, I managed to get some kind of virus/malware which took over. Tried to remove anything but simply opted to do a reset via the useful HP Recovery Manager.

Everything was fine until the end and he said that it has failed or something (if there are several days)... Would recover to zero the system (if this is important). Whatever - he said it has failed, you need to restart, click 'ok' and it was then that he would not start.

Just saw the logo screen HP, circles bit twirly, screen becomes black, gray and starts with the HP logo screen again and again. Made this for a few hours and finally just stop it completely.

I went into the start menus, ran tests (HARD drive, memory, battery, motherboard, etc.) and everything is in working order. Run try to reset the computer to factory settings... 1/2 day later, it ends upward (I see the office during the final stages) and then all of a sudden I get the «restoration incomplete - save log/details/try again»

Product Version information: 1.1530.23.0 # N5R10UA #ABA

Details: Unexpected reboot during [installation procedure for Windows} will cause panic CTO because the image might not be normal now.

Retry does nothing except continue the incomplete screen.

Tried the BIOS to 02/01/2014, 02/01/2013 including some messages/support pages suggested.

At the end of my tether.

The partition is the same as Recovery Media - but in case of corruption or hard disk failure, you will need a recovery media to boot from.

Fill a case of pension guarantee on the page here. They should take care of you without delay:

https://support.HP.com/us-en/contact-HP/product/HP-Pavilion-11-K100-x360-convertible-PC/8499314/model/8961275

How to copy data from one hard drive to another after the upgrade?

I have a HP e9220y, and I recently bought a new hard drive for it. There is nothing wrong with the former, but this one has a 64 MB cache and 7200 RPM so I hope it will be a little faster. I installed it and it works fine, but I want to copy all data from the old disk to the new so I can start everything off the faster hard drive and I seem to have a bit of doing wrong. I can't just copy and paste because of the Windows system files that are used. And last night when I set up Windows backup, and went to bed, when I thought it that Windows has recovered from a stop unexpected, rebooted, and only 2 GB of data saved obtained.

What is the best way to move all the data from the old drive to the new drive, make it the default C: drive and move partitions system and factory_image as well? Thank you!

Please read this link to another post made by Big_Dave and myself

http://h30434.www3.HP.com/T5/desktop-hardware/hard-drive-imminent-failure-problem/TD-p/438567

(1) If your old drive and the new drive is Seagate or Western Digital, then free House with their cloning software.

(2) before starting the clone process, I found best to perform a disk cleanup and defragmentation.

Cloning software to copy the two partitions. Example:

Old drive 250 GB formatted to 232 C: created 220 and 12 GB D:

New 1000GO drive formatted to 931 GB created 919 GB C: and D: to 12 GB

The "Seagate disc Wizard" cloning software will let create you a clone automatic or manual partition resizing.

The two modes to offer an overview of the actions before commit you. The manual on this page of Seagate (PDF) is 68 pages.

After the cloning process he complete, all you have to do is swap on the disks. Besure to connect your new disc on the original motherboard SATA port.

DV6 7200ee desire: restoration incomplete error

I repeated it for my laptop and I have this problem (Recovery Manager window appears with the following error message when I click on the Details button):

file ctoerror. FLG

[21:12:12.07] ChkErrBB.CMD: detect an error in the PININST_BBV.
[21:12:12.07] ChkErrBB.CMD: check c:\system.sav\logs\BurnBootWarn.log
[21:12:12.07] ChkErrBB.CMD: or, visit c:\system.sav\logs\BurnBootMerge.log
[21:12:12.08] ----------------------------------------
[21:12:12.08] critical error condition has been detected to BBV1...
[21:12:12.08]
[21:12:12.08] see the following text of the file if it exists.
[21:12:12.08] - c:\system.sav\Logs\BurnBootWarn.log
[21:12:12.08] - c:\system.sav\Logs\BurnBoot.log
[21:12:12.08]
[21:12:12.08] Switch to 2ndCap WinPE and the show [Recovery Manager] incomplete dialogue.
[21:12:12.08] because the dialogue of RM cannot appear on the screen [start] on Win8 environment.
[21:12:12.08] customer may not notice that RM already shows the error dialog box.
[21:12:12.08]
[21:12:12.08] ----------------------------------------
There might be an unexpected reboot during the PBO clean or last...
The process will cause panic CTO because the image isn't normal...

Please help me to restore my windows again!

TitoNabil wrote:
If its noway my windows again...

Please help me...

I did exactly that.

Have you contacted HP at the URL I provided in my previous answer?

To fix what you've done for yourself, the less expensive is to contact HP and order a restore for your laptop USB.

Codian 8510-Unexpected reboot

Similar Questions

Maybe you are looking for