However during conversation I was told how the new device would be under warranty for 3 months but that means in effect they are reducing my warranty because their hardware is faulty. The following day after over 3.5hrs on the phone I was told that as the device was over 30 days old I could not have a refund (someone even told me I wasn’t eligible for anything). He offered me a refund, replacement or advanced exchange where you basically pay for a second device and are refunded once you return the other one. the new device regularly throttles the processor down from about 3.5GHz to just 0.19GHz making it unusable (the last time processors were that speed was about 1996).Ī Microsoft representative connected to the machine remotely and accepted my hardware was definitely faulty after finding he couldn’t even type messages into Notepad it was that slow. However after spending over £2,000 on the new device, dock, keyboard etc. the next line will only zero out bit, the BD PROCHOT bitĭo you have an enterprise account with Microsoft? If so, you may be able to escalate this through your TAM and get a better solution.I purchased a Surface Pro 7 to upgrade from my already replaced Surface Pro 4, which itself was getting too slow to effectively work on. Rough C++ code from Uncle Webb to do it the right way. exe via this call but it needs to execute in kernel mode: You can probably do the same in a Windows. You actually only need to set one bit of the 0x1FC register, not all the bits. The key piece of code is one line which is actually not the correct way to do it, but works. You may be able to script this approach through SCCM or some other management tool, but its really a manual workaround so I would not suggest an automated deployment. Here is a workaround that can get you up and running: it you can also sue the deivce manger to manually change the driver point to the SurfaceSam.inf in the cab. So I tired it, Used Devcon to install the driver. Which means both devices share firmware ? He even told me I could load version 239.2638.257.0 into a Surface Pro 6. Then I was told by the MS enterprise support agent ( outsourced by Concentrix Corporation) that the Verizon 239.3001.139.0 had the same fixes of the 239.2638.257.0 in it. I was told that the original post was a mistake, it was meant for the Surface Pro 5. When I opened our support call with MS, I asked for a clarification. Surface System Aggregator - Firmware 239.3001.139.0 improves battery stability and Type Cover connectivity scenarios. Surface System Aggregator - Firmware 239.2638.257.0 improves battery stability, resolves CPU throttling to 400MHz and Type Cover connectivity scenarios. What's interesting is in the April 4th release notes for the Surface Pro 6. We opened a support ticket with MS and apart from making sure we are running the last firmware / update there is not much incite on the problem. : HWiNFO No Prochot when the MS dock is connected. Surface Pro 6 : HWiNFO NO Prochot when the MS dock is connected. Surface Pro 5 (2017 model) : HWiNFO reports Prochot of a few seconds when the MS dock is connected. All are running the same image via deployed via SCCM and all are running the last firmware / driver package from MS Update : I have access to different Surface devices. When you connect the simple MS changer to the surface, this Prochot does not occur. I bet that in same cases its stays on, causing our slow Process issue. When running HWiNFO you can see the processor enter Prochot for a few seconds every time the MS Dock is connected. ![]() ( device stays in ProcHot, this one does not make sens logical as it should give the same result as disconnecting the AC from the Ms dock) Disconnect the Mag dock cable from the dock to the Surface.Shutdown wait a few min power back up) Prochot stays.Install a firmware / driver updates ( the latest April 2019 updates do not resolve the issue ).Run Hwinfo64, the act of starting Hwinfo64 sometimes seems to jolt the CPU back in normal state.Surface device goes from AC to batter back to AC. Disconnected AC power from MS dock re-connected.Getting a device back to working properly can be achieved by using different methods, but not consistently. The devices have a tendency to stay stuck in this state when they transition from Power states, Sleep on Battery to Ac power, using a Balanced energy profile. Running HWinfo shows the Cpu in Prochot state, but no other sensors indicates any over heating conditions. Our users are reporting cases where the devices are very slow. We have a fleet of about 200 Surface Pro 6 devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |