WTF is happening with Windows 11? And nothing else
-
@topspin said in WTF is happening with Windows 11? And nothing else:
@Applied-Mediocrity said in WTF is happening with Windows 11? And nothing else:
❌
-
@Applied-Mediocrity said in WTF is happening with Windows 11? And nothing else:
@topspin said in WTF is happening with Windows 11? And nothing else:
@Applied-Mediocrity said in WTF is happening with Windows 11? And nothing else:
❌
-
Status: Rather curious what "Remote processes" is, and why it's used 85GB of data in the last week...
-
@Tsaukpaetra Windows Update?
-
@Arantor said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra Windows Update?
That's presumably under Svchost.
-
@Tsaukpaetra I wasn’t being entirely serious, I assumed that it’s downloading the next “patch” for Windows and it’s only 85GB in size combined with Windows Telemetry.
-
@Arantor said in WTF is happening with Windows 11? And nothing else:
85GB in size combined with Windows Telemetry
Only 85 GB for Windows telemetry? Must have been a slow week.
-
@HardwareGeek given the user and the expected uptime, this seems normal?
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
Status: Rather curious what "Remote processes" is, and why it's used 85GB of data in the last week...
Those shitcoins won't mine themselves!
-
@HardwareGeek said in WTF is happening with Windows 11? And nothing else:
@Gern_Blaanston said in WTF is happening with Windows 11? And nothing else:
I would like them to stop fucking things up
I would like a flying car, a few billion dollars, and to be God-Emperor of Earth. Whose wish is more likely to come true?
You don’t want the last one. Just think of the admin.
-
A program I'm using is reporting my Windows version as 10.0 What version of Windows am I running? Let's check.
OS Name: Windows 11
OS Version: Version 10.0.22621Windows 11
Version 10.0
Is this another one of those stupid "compatibility" things, like when they skipped Windows 9 ?
-
@Gern_Blaanston said in WTF is happening with Windows 11? And nothing else:
A program I'm using is reporting my Windows version as 10.0 What version of Windows am I running? Let's check.
OS Name: Windows 11
OS Version: Version 10.0.22621Windows 11
Version 10.0
Is this another one of those stupid "compatibility" things, like when they skipped Windows 9 ?
I think it’s more that marketing got out over their skis and decided they had to have a new version to pump, but the technical people know it’s just really another cumulative feature update so they’re rebelling with the ultimate power, setting the version number.
-
@Gern_Blaanston said in WTF is happening with Windows 11? And nothing else:
A program I'm using is reporting my Windows version as 10.0 What version of Windows am I running? Let's check.
OS Name: Windows 11
OS Version: Version 10.0.22621Is this another one of those stupid "compatibility" things, like when they skipped Windows 9 ?
Pretty much, just like 2000/XP were 5.0/5.1 and Windows Vista/7/8/8.1 were 6.0/6.1/6.2/6.3. 10 started as 6.4 in the early betas. In theory it represents the NT kernel build version, not necessarily the entire OS.
-
status: so enjoying when every File Explorer window navigates to the Desktop whenever a drive is unmounted (including implicit unmounting due to network confusion).
I could understand the specific window viewing that was in that drive doing that, but ALL of them?
-
@Tsaukpaetra Every other OS besides Windows has had tabbed file managers for 10 - 20 years. So I wish I could say I was surprised.
-
@jinpa I'm befuddled at how you arrived at anything relating to tabbed file managers based on my post....
-
@Tsaukpaetra I can easily believe you were befuddled. You had to have multiple windows open. You should not have had to do this.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra I can easily believe you were befuddled. You had to have multiple windows open. You should not have had to do this.
I did this because it's easier to drag files between disparate folders than via tabs.
-
@Tsaukpaetra Ah, I thought you did it because you had no choice. I have to use Windows (11?) at work, and, as far as I know, it does not give the option of opening multiple tabs of one window of File Explorer.
And anyway, it's usually as easy to drag files between tabs as between windows. Occasional exceptions exist, however.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra Ah, I thought you did it because you had no choice. I have to use Windows (11?) at work, and, as far as I know, it does not give the option of opening multiple tabs of one window of File Explorer.
WOMM. But natch, despite this particular thing "working", other things are necessarily broke.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
Occasional exceptions exist, however.
And yet, my post had nothing to do with any of the above.
-
@Tsaukpaetra Actually it did, but you were befuddled, remember? And the missing piece of information (that File Explorer actually did support multiple tabs for you) has now been supplied?
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra Actually it did, but you were befuddled, remember? And the missing piece of information (that File Explorer actually did support multiple tabs for you) has now been supplied?
Absolutely not.
What has anything you're commenting about tabs have anything to do with Explorer windows self navigating to an arbitrary folder on an arbitrary unrelated event?
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
status: so enjoying when every File Explorer window navigates to the Desktop whenever a drive is unmounted (including implicit unmounting due to network confusion).
I could understand the specific window viewing that was in that drive doing that, but ALL of them?
It's an improvement from it just closing the window.
-
@Zecc said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
status: so enjoying when every File Explorer window navigates to the Desktop whenever a drive is unmounted (including implicit unmounting due to network confusion).
I could understand the specific window viewing that was in that drive doing that, but ALL of them?
It's an improvement from it just closing the window.
True. I suppose I have also been getting fewer "couldn't map the drive because it's already mapped" errors. 😒
-
@Tsaukpaetra Seems you need to upgrade your machine to a real OS: Windows 7.
-
@BernieTheBernie said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra Seems you need to upgrade your machine to a real OS: Windows 7.
It's even worse on 7! On that version if the drive decides it already exists, you'll never be able to access it again without a reboot.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
You should not have had to do this.
You won't believe this crazy fact but some people choose to use different windows in File Explorer (or Finder etc).
@jinpa said in WTF is happening with Windows 11? And nothing else:
I have to use Windows (11?) at work, and, as far as I know, it does not give the option of opening multiple tabs of one window of File Explorer.
Windows 11 does - it was an update to 22H2.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
And anyway, it's usually as easy to drag files between tabs as between windows.
This seems exactly backwards, unless you've made the other window smaller than the tab.
-
@boomzilla "as easy" is commutative. "as easy to drag files between tabs as between windows." So it's still true phrasing it backwards.
"as easy to drag files between tabs as between windows." = "as easy to drag files between windows as between tabs"
Well, I suppose it could be different if the easiness levels were different in the two cases, but that was not what was implied here.
-
@boomzilla said in WTF is happening with Windows 11? And nothing else:
@jinpa said in WTF is happening with Windows 11? And nothing else:
And anyway, it's usually as easy to drag files between tabs as between windows.
This seems exactly backwards, unless you've made the other window smaller than the tab.
He's probably going to also mention you can easily make a "Copy to" and "Move to" item in files' context menus.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
Well, I suppose it could be different if the easiness levels were different in the two cases
I contend that the added complication of tab-switching mechanics necessarily implies a difference in difficulty.
But still, completely irrelevant to unexpected navigation due to a mundane event unrelated to the state of that instance of the program.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
@boomzilla "as easy" is commutative. "as easy to drag files between tabs as between windows." So it's still true phrasing it backwards.
"as easy to drag files between tabs as between windows." = "as easy to drag files between windows as between tabs"
Well, I suppose it could be different if the easiness levels were different in the two cases, but that was not what was implied here.
Lame commutative pedantic dickweekery aside, the easiness is obviously different between the two, unless, as I said, you make that target window the size of a tab in Explorer.
-
@boomzilla Call it what you wish. I'll continue to write accurately and logically, whether it's over the head of my opponents or not.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
@boomzilla Call it what you wish. I'll continue to write accurately and logically, whether it's over the head of my opponents or not.
Not on this subject you aren't.
-
@jinpa said in WTF is happening with Windows 11? And nothing else:
logically
Error: Self identified status used as an instance descriptor for external context.
-
Status: When Windows decides all the graphics cards are sus.
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
WOMM.
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
But natch, despite this particular thing "working", other things are necessarily broke.
That's more like it.
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
Status: When Windows decides
Well
-
Status: Kernel panicked because it accessed memory outside the right IRQ level.
IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace PROCESS_NAME: svchost.exe TRAP_FRAME: ffffa30c40cade20 -- (.trap 0xffffa30c40cade20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=ffff80082ead3b58 rdx=00000000000000a0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8060c88fba4 rsp=ffffa30c40cadfb0 rbp=ffffa30c40cae049 r8=0000000000000000 r9=ffff80082ead3aa0 r10=0000000000000002 r11=a957000000050542 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!MiIdentifyPfn+0x255334: fffff806`0c88fba4 488b4048 mov rax,qword ptr [rax+48h] ds:00000000`00000048=???????????????? Resetting default scope STACK_TEXT: ffffa30c`40cadcd8 fffff806`0c8462a9 : 00000000`0000000a 00000000`00000048 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffa30c`40cadce0 fffff806`0c841934 : ffffa30c`0000018e fffff806`0c666085 ffffa30c`40cade50 ffffa30c`40cadec8 : nt!KiBugCheckDispatch+0x69 ffffa30c`40cade20 fffff806`0c88fba4 : 00000000`000018c0 00000000`00000000 00000000`42506650 fffff806`0c732d2f : nt!KiPageFault+0x474 ffffa30c`40cadfb0 fffff806`0c63a7d5 : 00000000`00000100 00000013`41bf9fc0 ffff9500`08a295b0 fffff806`0caaf995 : nt!MiIdentifyPfn+0x255334 ffffa30c`40cae0b0 fffff806`0cacf86a : ffff8008`00000000 ffff8008`3bff1860 ffff8008`27c2d080 ffff8008`3bff18c0 : nt!MiIdentifyPfnWrapper+0x75 ffffa30c`40cae0f0 fffff806`0caaf64c : 00000000`00000000 00000000`00000001 ffff8008`3bff0000 00000000`00000001 : nt!MmQueryPfnList+0x7a ffffa30c`40cae130 fffff806`0caaf253 : 00000000`00000000 00000000`00000000 ffff9500`00000000 ffff8008`3bff0000 : nt!PfpPfnPrioRequest+0x80 ffffa30c`40cae1a0 fffff806`0cae0565 : 00000013`41bf9f68 fffff806`0c7324b7 00000000`0000004f 00000000`00000000 : nt!PfQuerySuperfetchInformation+0xe7 ffffa30c`40cae270 fffff806`0cae01cb : 00000000`00000000 00000000`00000000 00000013`41bf9fa0 00000000`00000000 : nt!ExpQuerySystemInformation+0x335 ffffa30c`40caeaa0 fffff806`0c8459e8 : 00000013`41bf0000 ffff8008`1754f2e0 00000000`00000000 ffff8008`00000000 : nt!NtQuerySystemInformation+0x7b ffffa30c`40caeae0 00007ffe`4eb2f414 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 00000013`41bf9e68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`4eb2f414 SYMBOL_NAME: nt!MiIdentifyPfn+255334 MODULE_NAME: nt IMAGE_VERSION: 10.0.22621.2070 STACK_COMMAND: .cxr; .ecxr ; kb IMAGE_NAME: ntkrnlmp.exe BUCKET_ID_FUNC_OFFSET: 255334 FAILURE_BUCKET_ID: AV_nt!MiIdentifyPfn OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4f0b8d4b-7219-bc8c-33a3-7bfc14bc92e1} Followup: MachineOwner ---------
Darn. I wish I could blame a driver.
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
despite this particular thing "working", other things are necessarily broke.
Windows
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
Darn. I wish I could blame a driver.
What's stopping you? You can always blame a driver. Or disk. Or other hardware things. shouldn't be a to blame...
-
@TimeBandit said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
despite this particular thing "working", other things are necessarily broke.
Windows@Tsaukpaetra
-
@HardwareGeek said in WTF is happening with Windows 11? And nothing else:
@TimeBandit said in WTF is happening with Windows 11? And nothing else:
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
despite this particular thing "working", other things are necessarily broke.
Windows@Tsaukpaetra?
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
I wish I could blame a driver.
The Bad driving thread is
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
Status: Kernel panicked because it accessed memory outside the right IRQ level.
Status: The kernel performed an illegal operation and was swiftly cancelled....
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the BugCheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: fffff80616ebae70 Arg3: fffff80616e93000 Arg4: fffff8061c632444 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3624 Key : Analysis.Elapsed.mSec Value: 8887 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 1 Key : Analysis.Init.CPU.mSec Value: 281 Key : Analysis.Init.Elapsed.mSec Value: 5813 Key : Analysis.Memory.CommitPeak.Mb Value: 99 Key : Bugcheck.Code.LegacyAPI Value: 0x1000007f Key : Dump.Attributes.AsUlong Value: 1008 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x7f_8_STACKPTR_ERROR_clipsp!unknown_function Key : Failure.Hash Value: {48f2dfdf-6e28-ad4e-f693-f41bb475ff86} BUGCHECK_CODE: 7f BUGCHECK_P1: 8 BUGCHECK_P2: fffff80616ebae70 BUGCHECK_P3: fffff80616e93000 BUGCHECK_P4: fffff8061c632444 FILE_IN_CAB: 081123-7453-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump BAD_STACK_POINTER: fffff80616e93000 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: svchost.exe STACK_TEXT: fffff806`16e93000 2722fc70`00000000 : 00000000`ffffd409 00000000`00000000 00000000`00000000 16ebb000`00000000 : clipsp+0x32444 fffff806`16e93008 00000000`ffffd409 : 00000000`00000000 00000000`00000000 16ebb000`00000000 16ec9000`fffff806 : 0x2722fc70`00000000 fffff806`16e93010 00000000`00000000 : 00000000`00000000 16ebb000`00000000 16ec9000`fffff806 16ec2000`fffff806 : 0xffffd409 SYMBOL_NAME: clipsp+32444 MODULE_NAME: clipsp IMAGE_NAME: clipsp.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 32444 FAILURE_BUCKET_ID: 0x7f_8_STACKPTR_ERROR_clipsp!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {48f2dfdf-6e28-ad4e-f693-f41bb475ff86} Followup: MachineOwner ---------
Double fault powerrr!!!
-
composer.textarea.placeholder
The Cloud Clipboard service was trying to do something (probably memory management) when it was interrupted, and whatever interrupted it didn't clean up properly after itself. The next time it tried to save a register to the stack, the CPU said "um, there's no memory there, I can't save anything." This triggered a page fault, and Windows tried to save some information so it could load what should have been there from the page file. The place it tried to save it is the stack, so the CPU said "still no memory there boss." This triggered a double fault, which crashes the system since things have clearly gotten bad enough Windows can't fix it. (Incidentally, if there was a problem with that, the CPU would trigger a triple fault and immediately reboot the computer.)
Check for updates, System File Checker, DISM whatever whatever, you know the rites and rituals better than I do at this point.
Edit: The instructions for how to come up with the proper stack trace likely wouldn't help. I didn't see a good
bp
value in there anywhere.Edit, again: Windows adds special tags to the last page or two of the stack, which cause the processor to raise a different fault, and that tells Windows to make the stack bigger. It's likely some driver intercepted that fault in a misguided attempt to convince users "we are never the cause of your system crashes, nyeh!", but since that fault only triggers once, Windows didn't know to expand the stack and accidentally let
clipsp
run off the end of it. This replaces my earlier analysis ofclipsp
being interrupted somehow.
-
@TwelveBaud I know some of those words
-
@TwelveBaud said in WTF is happening with Windows 11? And nothing else:
Check for updates, System File Checker, DISM whatever whatever, you know the rites and rituals better than I do at this point.
Windows swears up and down all the files are kosher and clean.
I updated Bluetooth, so it didn't blame that this go around.
Thinking of poking the memory settings once again...
-
@Tsaukpaetra said in WTF is happening with Windows 11? And nothing else:
Thinking of poking the memory settings once again...