Windows error 0x00000188, 392

Detailed Error Information

CLUSTER_CSVFS_LIVEDUMP[1]

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

HRESULT analysis[2]

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

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
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][3]
DescriptionThe default facility code.[2][3]
Error Code392 (0x0188)

Questions

3votes
2answers

Out of bound address when directly reading from array

I am developing a CUDA application which has some routines for allocation and deallocation of arrays in shared memory. In this application (that, I am sorry, I cannot make available), I have a class that encapsulate a chunk of memory as an array. This class has a count method that [...] read more
c++
memory
memory-management
cuda
1vote
1answer

DPI scaling problem with hosted native HWND control inside WPF window

I have a high dpi setting on my monitor as the monitor is a fairly small 3840 x 2160 monitor. This is causing issues with one of the applications I am writing as I am hosting a control in my main application. I developed it based off a nice example [...] read more
c#
wpf
scale
1vote
0answers

C - Get File Bytes as Unsigned Int

I need the bytes of a BIN file converted to a unsigned int, in this format (JavaScript): p.write4(shellcode.add32(0x00000000), 0x00000be9); p.write4(shellcode.add32(0x00000004), 0x90909000); p.write4(shellcode.add32(0x00000008), 0x90909090); p.write4(shellcode.add32(0x0000000c), 0x90909090); p.write4(shellcode.add32(0x00000010), 0x0082b955); p.write4(shellcode.add32(0x00000014), 0x8948c000); p.write4(shellcode.add32(0x00000018), 0x415741e5); p.write4(shellcode.add32(0x0000001c), 0x41554156); p.write4(shellcode.add32(0x00000020), 0x83485354); p.write4(shellcode.add32(0x00000024), 0x320f18ec); p.write4(shellcode.add32(0x00000028), 0x89d58949); p.write4(shellcode.add32(0x0000002c), 0x64b948c0); p.write4(shellcode.add32(0x00000030), 0x77737069); p.write4(shellcode.add32(0x00000034), 0x49000000); p.write4(shellcode.add32(0x00000038), 0x4120e5c1); p.write4(shellcode.add32(0x0000003c), 0x000200bc); p.write4(shellcode.add32(0x00000040), [...] read more
c

Comments

Leave a comment

(plain text only)

Sources

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

User contributions licensed under CC BY-SA 3.0