Windows error 0x000000E7, 231

Detailed Error Information

PIPE_BUSY^[1]

Message	All pipe instances are busy.
Declared in	winerror.h

This appears to be a raw Win32 error. More information may be available in error 0x800700E7.

INVALID_FLOATING_POINT_STATE^[2]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0xE7: INVALID_FLOATING_POINT_STATE.

HRESULT analysis^[3]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.

Flags	Severity	Success This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.
	Reserved (R)	false
	Origin	Microsoft
	NTSTATUS	false
	Reserved (X)	false
Facility	Code	0 (0x000)
	Name	FACILITY_NULL^[3]^[1]
	Description	The default facility code.^[3]^[1]
Error Code		231 (0x00e7)

Questions

Why is the p-state status MSR on ryzen not changing?

I am trying to detect the current p-state of my cpu. I have noticed that the p-state status MSR (C001_0063) always returns 2 on my ryzen 1700x system, even if the core is clearly not in that state. I think it used to work with the initial bios (v0403) that [...] read more

linux

cpu

hardware

amd-processor

power-saving

Identically configured urxvt has different width/font rendering on different X servers

I have two different desktop hosts connected via their DisplayPort outputs to two DisplayPort inputs on the same 4K monitor: * idyllic, a small-form-factor PC using the onboard Intel HD Graphics 500 of its Celeron N3350 processor. (I've also a similar system at another location with a Pentium N4200 processor [...] read more

fonts

x11

xorg

urxvt

Comments

Sources

winerror.h from Windows SDK 10.0.14393.0
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0