Forum Widgets
Latest Discussions
Externe Kamera mit Windows Hello benutzen während das Surface Book geschlossen ist
Ich würde gerne mein Surface Book welches an einer Dockingstation mit zwei Bildschirmen angeschlossen ist, mit Windows Hello und Face recognition öffnen selbst wenn es zugeklappt ist. - Das Problem: Die Kamera wird immer erkannt und ich kann sie für alles Benutzen auch um Hello einzurichten, jedoch sobald dass Surface im abgemeldeten Modus zugeklappt ist, wird die Kamera nicht mehr erkannt. Sobald das Surface jedoch auch nur einen cm angehoben wird, schaltet sich die Kamera ein und man kann sich einloggen. - Frage: Gibt es irgendeine Möglichkeit das ich mich mit Face recognition einloggen kann, ohne das Surface aufzumachen?
Rubber feet issues from the Surface Book 2 base
Good evening, Quick disclamer: I am not here seeking for support. I already went through costumer support and am only here to report on the proceeding done over the issue so that the experience can be shared with the team behind designing and engineering the device. I acquired my Surface Book 2 15'' in April 2018 in pre-order for the PT-PT variant of the device. The device ran without issues for the first months. First thing that I noticed was that the rubber feet installed on the base of the Book seemed to be bigger than the notch machined to acommodate them. The tip bulged a bit and was sitting about 0.5mm off the notch. It's understandable that being the two parts made of different materials under tight tolerances might end up making the two not fit exactly well on the final product, specially given that these were made for the first time for a 15'' variant of the Book. In late November that same tip started peeling off from the Book's base, which I simply pressed back into place to glue it again. The feet usually "snapped" to get over the 0.5mm difference in size between the feet and the notch. The same happened to the pair. As soon as dirt started getting glued to the gap created, it became more difficult to snap the feet tip back in place. With each subsequent heating and cooling from recharging/GPU activity, the unglueing of the rubber feet kept getting worse. After a few weeks the two rubber feet were detaching from the base on about 40% on one side and starting to peel off on the other. Due to repetitive reattachement of the unglued stretchs, the rubber feet started developing stress ruptures. It was at this moment, in February, that I contacted Microsoft online support to seek help for this issue. After contact with a member of support for Microsoft Portugal Surface Support, this is what I learned: - Replacement rubber feet and tape glue parts were not available for warranty maintenance nor purchase by the user to install; - Rubber feet damage was considered outside damage and are not covered by warranty; - Removing the feet and replacing them by a user solution wouldn't void the warranty since it did not interfere with the internals of the computer and would be considered aftermarket personalization (like applying skins or decals to the surface of the device); - Even if replacement of the feet wouldn't void warranty, the damaged feet should be kept in reservation so that in case of failure of the device due to hardware issues both the device and the feet can be sent together for maintenance; - The DIY feet should be removable if necessary. Given the conclusions taken from the chat with the Surface Costumer Service, I decided to remove the damaged feet and glueing tape from the device and, as instructed, were reserved. I then designed and manufactured two new feet in brushed stainless steel and glued it to the device. It has been working without issues for two months already. After this experience, I suggest the Surface team to review design and engineering of the rubber feet on the Surface Book's base, particularly the Surface Book 2 15'' variant with PT-PT keyboard layout, to check for eventual issues in manufacturing, tolerances, fit and finish of the feet in the base of the device. I also would recommend reviewing the effectiveness of the solution over repeated use, both in terms of the feet's fatigue resistance to abrasion and heating cycles of the device. Alternatives solutions should be considered. Given the nature of the part in question, providing replacement parts for existing devices should be considered by labelling the rubber feet as a "consumable" (like the rubber tires of a car). This concludes my report of the situation. If any more details are needed for further development feel free to ask.
Surface book 2, screen dimming with 30 seconds of inactivity.
Hi all, Not sure if windows issue or with my surface book 2. hoping someone can let me know how to turn off screen dimming due to inactivity after 30 seconds. hasn't been too much of an issue but today I wanted to watch a movie and couldn't see it properly because the screen would dim. I've tried all the power saver settings and turned off all screen savers. It does it whether plugged or on battery.
Touch locks up, round faded-center dots across screen with cursor stuck in one
So it isn't Vivaldi doing this. Last night it happened in the Qobuz music app. I tapped a track to play, and got a stripe of the faded-center dots across the screen - the position of the Vivaldi dot, plus lots more to the left of it. No zooming in Qobuz, the app was just totally locked up, and nothing touch could do would escape. I brought over my keyboard and mouse. Qobuz remained locked up, but everything else worked, and the dots remained visible. I didn't see this in Vivaldi without a mouse, but there was a cursor stuck over the rightmost dot, in addition to the actively moving cursor. (The image is from a bit of phone video - screenshots didn't show either cursor.) The dots remained visible when I switched users, but the stuck cursor pointed to a different one: They stayed visible through the entire shutdown process, even over the colored screens with the shutdown steps. And when Windows came back, my taskbar was extra wide and locked. As before, nothing in Windows logs, or Qobuz log. Could this be a GPU problem? Qobuz uses it, but I've set Vivaldi not to. At least I think I have... The "GPU Process" still shows, but it is ~50 MB instead of ~500 MB. I think Windows is out of control...How to resolve USB Conflict Between SD Card and Line 6 HX Stomp?
I have a Surface Book 2 that doesn't want to play nice with a Line 6 HX Stomp. The HXS has the latest firmware updates, and I have the latest Line 6 drivers for the pedal loaded. From Windows Task Manager, I can see the HX Edit application attempt to load and connect to the pedal, then the process just dies. The only way to connect via USB is to eject my SDXC drive. I was hoping to find a workaround, hear something more productive than "Get a Mac!" https://line6.com/hx-stomp/ Surface Model: 1832 i5 Processor: Intel i5-8350U @ 1.70GHz 1.90 GHz Mem Installed: RAM 8.00 GB OS: Windows 10 Pro 64-bit Touch Driver: 242.0.1.5 Wi-Fi Driver: 15.68.17021.121 App Version: 61.60.139.0Surface Book 3 - BSOD when using external monitor (Windows 10 20H2)
Dear community, I am facing an issue where my Surface Book 3 device goes into a BSOD when it is idle for some minutes, while connected to an external Samsung S24R650 monitor. From Event Viewer, I get this error: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000019c (0x0000000000000050, 0xffffa10b079af080, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b0e12159-a128-4fa6-9dcc-d5a842b5e62a. And from the WinDbg analysis, the result is the following: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WIN32K_POWER_WATCHDOG_TIMEOUT (19c) Win32k did not turn the monitor on in a timely manner. Arguments: Arg1: 0000000000000050, Calling monitor driver to power on. Arg2: ffffa10b079af080, Pointer to the power request worker thread. Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3218 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 13751 Key : Analysis.Init.CPU.mSec Value: 999 Key : Analysis.Init.Elapsed.mSec Value: 7335 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: 19c BUGCHECK_P1: 50 BUGCHECK_P2: ffffa10b079af080 BUGCHECK_P3: 0 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: csrss.exe FAULTING_THREAD: ffffa10b079af080 STACK_TEXT: fffffa0f`cf845040 fffff806`6559481a : 00000000`00000012 00000000`00000000 fffffa0f`cf845400 00001f80`00000000 : igdkmdn64+0x374f87 fffffa0f`cf845050 fffff806`6558d855 : 00000000`00045454 ffffa10b`00a82000 fffffa0f`cf845348 ffffa10b`062ee7d0 : igdkmdn64+0x37481a fffffa0f`cf845130 fffff806`6558509c : 00000000`00000000 ffffa10b`06247be0 00000000`00000064 fffff806`65594f2a : igdkmdn64+0x36d855 fffffa0f`cf8451a0 fffff806`6526d29f : 00000000`00045404 00000000`00000003 00000000`00000000 00000000`00000000 : igdkmdn64+0x36509c fffffa0f`cf8451d0 fffff806`652717df : 00000000`00000001 00000000`00045404 ffffa10b`00a82000 fffff806`6558509c : igdkmdn64+0x4d29f fffffa0f`cf845260 fffff806`6529f5ff : 00000000`ffffffd0 fffff806`6526d3a4 00000000`01000000 00000000`00000000 : igdkmdn64+0x517df fffffa0f`cf8452d0 fffff806`6529fdf3 : fffff806`0000000f 00000000`00000028 ffffa10b`06247be0 00000000`00000000 : igdkmdn64+0x7f5ff fffffa0f`cf845370 fffff806`652a0516 : 00000000`00000010 00000000`00000000 ffffa10b`06731400 ffffa10a`fdb59bf0 : igdkmdn64+0x7fdf3 fffffa0f`cf8453f0 fffff806`6529e114 : 00000000`00000107 ffffa10b`06731400 ffffa10b`06731410 00000000`00000000 : igdkmdn64+0x80516 fffffa0f`cf8454e0 fffff806`65280dc3 : ffffa10b`00000101 00000000`00000022 fffffa0f`00000107 00000000`00000001 : igdkmdn64+0x7e114 fffffa0f`cf845550 fffff806`65273e90 : 00000001`00000004 ffffa10b`06244560 fffffa0f`cf845630 ffffa10a`f7c02000 : igdkmdn64+0x60dc3 fffffa0f`cf845590 fffff806`6527e604 : 00000000`00000010 00000000`00000001 fffffa0f`cf845600 fffff806`5b01f500 : igdkmdn64+0x53e90 fffffa0f`cf8455e0 fffff806`6546e206 : ffffa10b`00a82000 fffff806`5b084ea4 00000000`00000001 00000000`00000000 : igdkmdn64+0x5e604 fffffa0f`cf845610 fffff806`6546c27f : 00000000`00000000 ffffa10b`06244560 00000000`00000001 fffffa0f`cf845759 : igdkmdn64+0x24e206 fffffa0f`cf845670 fffff806`65452cf7 : ffffa10b`0601c2b6 00000000`0002625a ffffa10b`0601c230 ffffa10a`fda24501 : igdkmdn64+0x24c27f fffffa0f`cf8456f0 fffff806`65451c0e : 00000000`000c323a fffffa0f`cf840000 00000000`00000000 00000000`000c31c3 : igdkmdn64+0x232cf7 fffffa0f`cf8457c0 fffff806`6544ec87 : 00000000`00000080 ffffa10b`06247be0 00000000`00000000 ffffa10a`fda24510 : igdkmdn64+0x231c0e fffffa0f`cf8458f0 fffff806`65430760 : 00000000`00000000 ffffa10a`fda24510 fffffa0f`cf845af8 ffffa10b`0688e4e0 : igdkmdn64+0x22ec87 fffffa0f`cf845950 fffff806`654251a7 : ffffa10b`20fb0cb8 00000000`00000005 fffffa0f`cf845b20 fffff806`6526c2d5 : igdkmdn64+0x210760 fffffa0f`cf8459b0 fffff806`65422740 : 00000000`00000000 fffffa0f`cf845b20 00000000`00000005 ffffa10b`20fb0cb8 : igdkmdn64+0x2051a7 fffffa0f`cf845a20 fffff806`65436310 : da6c18ee`8bf0cebc 00000000`00000003 00000000`00004032 ffffa10b`162187c8 : igdkmdn64+0x202740 fffffa0f`cf845bc0 fffff806`6543ef0d : ffffa10b`06244560 ffffa10b`162187b0 ffffa10b`06244560 00000000`00000000 : igdkmdn64+0x216310 fffffa0f`cf845c30 fffff806`6543eac7 : ffffa10b`06244560 00000000`00000000 ffffa10b`1e8a65d0 00000000`00000000 : igdkmdn64+0x21ef0d fffffa0f`cf845d90 fffff806`6542de02 : ffffa10b`06244560 fffffa0f`cf846007 ffffa10b`06244560 ffffa10b`06247be0 : igdkmdn64+0x21eac7 fffffa0f`cf845f00 fffff806`654268bb : 00000001`00000004 ffffa10b`1e8a65d0 ffffa10b`06244560 fffff806`6526e400 : igdkmdn64+0x20de02 fffffa0f`cf846050 fffff806`6541f262 : ffffa10b`1e8a65d0 fffffa0f`cf846540 fffffa0f`cf846540 00000000`00000000 : igdkmdn64+0x2068bb fffffa0f`cf846130 fffff806`653fa41d : 00000000`00000001 ffffa10b`06919dc0 00000000`00000040 fffffa0f`cf8465c0 : igdkmdn64+0x1ff262 fffffa0f`cf8464c0 fffff806`653ef308 : 00000000`00000000 fffff806`5b0f405f ffffa10b`06247be0 00000000`00000000 : igdkmdn64+0x1da41d fffffa0f`cf8467b0 fffff806`653b6351 : ffffa10a`ff730000 fffffa0f`cf846999 fffffa0f`cf846999 00000000`00989680 : igdkmdn64+0x1cf308 fffffa0f`cf846810 fffff806`65257026 : ffffa10b`00a82000 ffffa10a`fdf49180 ffffa10b`00a82000 00000000`00000000 : igdkmdn64+0x196351 fffffa0f`cf846860 fffff806`603337ad : 00000000`00000000 ffffa10a`fdf49ec8 fffffa0f`cf846940 00000000`00000000 : igdkmdn64+0x37026 fffffa0f`cf8468c0 fffff806`602b4aeb : 0000001d`0e01fb64 fffffa0f`cf846999 fffffa0f`cf847130 fffff780`00000320 : dxgkrnl!DpiDxgkDdiDisplayDetectControl+0x7eb95 fffffa0f`cf846920 fffff806`60332d33 : ffffa10a`fdf49180 ffffa10a`fdf49180 ffffa10a`fdf49180 00000000`00000001 : dxgkrnl!DpiFdoInvalidateChildRelations+0x10b fffffa0f`cf846a00 fffff806`6025ede6 : 00000000`00000021 fffffa0f`cf846be8 00000000`ffffffff fffff806`5b460c20 : dxgkrnl!DxgkPowerOnOffMonitor+0x7f76f fffffa0f`cf846b20 fffff806`60266270 : ffffa10b`ffffffff ffffa10a`fe3b2e20 ffffa10b`06bbae90 00000048`0000001e : dxgkrnl!DpiGdoDispatchInternalIoctl+0x586 fffffa0f`cf846bd0 fffff806`5b08f825 : 00000000`00000000 ffffa10a`00000000 00000000`c0000002 00000000`00000010 : dxgkrnl!DpiDispatchInternalIoctl+0x100 fffffa0f`cf846d00 fffff4e3`be863a39 : fffffa0f`cf846dd0 00000000`00000000 fffff4a7`82ca8490 fffff4e3`be8caa3a : nt!IofCallDriver+0x55 fffffa0f`cf846d40 fffff4e3`be8ca672 : fffff4a7`82ca8490 fffffa0f`cf846ee0 00000000`00000000 ffffa10b`00000000 : win32kbase!GreDeviceIoControlImpl+0xed fffffa0f`cf846de0 fffff4e3`be8ca43f : fffffa0f`cf847130 00000000`00000000 00000000`00000001 00000000`00000050 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x212 fffffa0f`cf846f50 fffff4e3`be88d5af : 00000000`00000050 00000000`c00000bb 00000000`c00000bb 00000000`00000001 : win32kbase!DrvSetMonitorPowerState+0x2f fffffa0f`cf846f80 fffff4e3`be88cb7b : 00000000`00000000 fffffa0f`cf847100 00000000`00000000 00000000`00000001 : win32kbase!PowerOnMonitor+0x1cf fffffa0f`cf847000 fffff4e3`be88c7e2 : ffffa10b`25a02720 ffffa10b`25a02720 00000000`00000001 00000000`00000000 : win32kbase!xxxUserPowerEventCalloutWorker+0x20b fffffa0f`cf847370 fffff4e3`beb80ce1 : ffffa10b`079af080 00000000`00000000 00000000`00000025 00000000`00000025 : win32kbase!xxxUserPowerCalloutWorker+0xe2 fffffa0f`cf8473e0 fffff4e3`bf0e474e : ffffa10b`079af080 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!NtUserCallNoParam+0x71 fffffa0f`cf847410 fffff806`5b208cb5 : ffffa10b`00000005 00000000`00000025 00000000`00000000 00000000`00000000 : win32k!NtUserCallNoParam+0x16 fffffa0f`cf847440 00007ff8`de1110e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 0000003d`c78bfe58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`de1110e4 STACK_COMMAND: .thread 0xffffa10b079af080 ; kb SYMBOL_NAME: igdkmdn64+374f87 MODULE_NAME: igdkmdn64 IMAGE_NAME: igdkmdn64.sys IMAGE_VERSION: 30.0.101.1340 BUCKET_ID_FUNC_OFFSET: 374f87 FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_igdkmdn64!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {cfff9c4c-cbec-2dd9-38ae-0ef8cae456c9} Followup: MachineOwner Device is fully patched (January 2022) and even after updating to the latest Intel driver, it still crashes. I am now applying February patches, but I am not sure it will be fixed. Any ideas? Kind regards, Bruno MartinsWindows Hello & External 3D Webcams
My Surface Book spends much of its time running "lid-closed" while connected (through a Surface Dock) to a pair of 34" LG monitors. Of course, that means that I can't use the Surface Book's depth-sensing camera for Windows Hello logins -- and Windows Hello is something that I REALLY like about Windows 10 and the Surface Book! No problem, I thought, since there are a few external 3D webcams on the market that support Windows Hello. So I purchased a Creative BlasterX Senz3D webcam for this purpose. This should allow me to mount a 3D webcam atop one of my monitors and keep my Windows Hello login. WRONG!!! Unfortunately, the Windows Hello Settings does NOT provide the ability to choose a specific webcam. It exclusively uses the built-in webcam on the Surface Book, meaning Windows Hello is looking at a black picture from the closed lid of the Surface Book at login time. Is a fix in the works for this? At the very least, the Windows Hello Settings should be permit switching between available video sources. An even better solution would be the ability to specify a separate webcam when running "lid open" vs "lid closed" or "Docked" vs "Undocked".
Surface Book Keyboard battery present BUT NOT ON USE
Hello, Recently I changed keyboard battery of my surface book with performance base model. After replacement the battery is present on screen and battery reports. But it shows all the time 93%. Also I realized the device only using tablet battery and after it finished it turn off. Guarentee already finished and I don`t have any microsoft store in my country. So I need to fix myself. How can I fix this issue ?
