I'm working on a computer with Windows XP. This computer restarts at least a couple of times each day. I downloaded the dump file generated to my personal computer (Windows 10) but I can't find how fix this issue. The Minidump file generated is always samething like:
`Loading Dump File [....Mini072422-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Path element is empty
WARNING: Path element is empty
************* Path validation summary **************
Response Time (ms) Location
OK C:\WINDOWS\symbols
OK C:\WINDOWS\symbols\dll
WARNING: Path element is empty
WARNING: Path element is empty
Symbol search path is: C:\WINDOWS\symbols;C:\WINDOWS\symbols\dll;;
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jul 24 19:30:39.421 2022 (UTC + 2:00)
System Uptime: 0 days 4:18:26.962
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
............
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym
noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
For analysis of this file, run !analyze -v
Unable to load image iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
eax=8a936990 ebx=8a936938 ecx=8a936000 edx=8a936990 esi=00000000 edi=8a9290e8
eip=ba67492a esp=8055127c ebp=80551298 iopl=0 nv up ei pl nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
iaStor+0x992a:
ba67492a 8b4628 mov eax,dword ptr [esi+28h] ds:0023:00000028=????????`
Could you give any idea? Thanks in advance.
Related
I'm trying to download a specific directory from Windows XP and Windows Server 2012 using a Get Directory method of SSHLibrary. This directory is on a different volume that the one in which the ssh connection it's established. For clarity when I open the connection this points to volume C:, the source directory is in volume D:. The issue that I'm seeing is that on my local machine the path to directory tries to include the volume letter resulting in something like: C:\path\to\robot\executable\D:\source\directory thus resulting in WindowsError: [Error 123] The filename, directory name, or volume label syntax is incorrect:
Is there a way to not have this issue but result in a path like C:\path\to\robot\executable\source\directory and successfully download the directory? I've tried doing Execute command d: before Get Directory but no luck there. Also is there a way to open a connection pointing to a specific volume?
Code I used:
*** Settings ***
Documentation Suite description
Library SSHLibrary timeout=120 seconds
*** Variables ***
${HOST_XP} remote.win.xp.machine
${USER_XP} user
${PASSWORD_XP} pass
${DIR} D:\\source\\
*** Test Cases ***
Test Win XP
SSHLibrary.open_connection ${HOST_XP}
SSHLibrary.login ${USER_XP} ${PASSWORD_XP}
SSHLibrary.get directory ${DIR}
Edit1: various typo
I actually found out the problem for Get Directory method. In path variables / should be used and not \. So my DIR variable should be ${DIR} D:/source/
I am able to run a number of GUI applications successfully on windows subsystem for linux (WSL), Ubuntu 14.04.4 LTS, using X-forwarding (via MobaXterm).
I recently tried to run an application that uses OpenGL. Although the GUI opens, there are a number of errors and some aspects of the GUI don't work properly. The errors are:
QT error: 1
QT error: <PyQt5.QtCore.QMessageLogContext object at 0x7f88e21d9ba8>
QT error: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user'
libGL error: failed to load driver: swrast
I can get rid of the swrast error by setting export LIBGL_ALWAYS_INDIRECT=1 but the other errors remain:
QT error: 1
QT error: <PyQt5.QtCore.QMessageLogContext object at 0x7fed3689e828>
QT error: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-user'
A typical error when attempting to use part of the GUI is:
WARNING: QT error: 1 (Gui.qtMessageHandler:51)
WARNING: QT error: <PyQt5.QtCore.QMessageLogContext object at 0x7f9b35e7b6d8> (Gui.qtMessageHandler:51)
WARNING: QT error: QOpenGLWidget: Failed to make context current (Gui.qtMessageHandler:51)
I can run glxgears, but I realise this only checks a fraction of OpenGLs functions. If I run glmark2 I get the following:
glmark2
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
Error: Glmark2 needs OpenGL(ES) version >= 2.0 to run (but version string is: '1.4 (4.0.0 - Build 10.18.10.4358)')!
Error: main: Could not initialize canvas
If I run find /usr -iname "*libGL.so*" -exec ls -l -- {} + suggested on this link https://askubuntu.com/questions/541343/problems-with-libgl-fbconfigs-swrast-through-each-update I get the following output but I'm not sure if this indicates an error or not?
lrwxrwxrwx 1 root root 14 Jan 12 2016 /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 -> libGL.so.1.2.0
-rw-r--r-- 1 root root 413968 Jan 12 2016 /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0
Running glxinfo seems to indicate the on-chip graphics card is used (there is a separate AMD graphics card but I don't think it's necessary to use that).
glxinfo | grep render
direct rendering: No (LIBGL_ALWAYS_INDIRECT set)
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
OpenGL renderer string: Intel(R) HD Graphics 4000
How can I successfully run OpenGL applications via WSL?
I am trying to install TinyTeX via the convenient tinytex-package for R.
After having had a few issues with getting the installation to run smoothly on MacOS, the install_tinytex() function now executes properly and ends with the statement:
TinyTeX installed to /Users/X/Library/TinyTeX
However, when trying to execute pdflatex('test.tex') to test the installation, the console instead returns:
Error: Failed to compile test.tex
Apparently the installation did not execute properly. Am I missing something or isn't this supposed to work after a successful TinyTeX installation via tinytex?
The texput.log displays the following error message:
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex 2018.11.2) 2 NOV 2018 14:47
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**test.tex
! Emergency stop.
<*> test.tex
Here is how much of TeX's memory you used: 3 strings out of 494585
99 string characters out of 6174649 51539 words of memory out of
5000000 3743 multiletter control sequences out of 15000+600000 3640
words of font info for 14 fonts, out of 8000000 for 9000 14
hyphenation exceptions out of 8191 0i,0n,0p,1b,6s stack positions out
of 5000i,500n,10000p,200000b,80000s
! ==> Fatal error occurred, no output PDF file produced!
The quoted error message indicates that there is no file test.tex in your current working directory. Either create a sample LaTeX file or use an existing file. If you do not have any LaTeX file available, you can try
pdflatex('sample2e.tex')
This will translate smaple2e.tex, which should be part of every LaTeX distribution.
I install quantum espresso 6.2 and use cygwin.
I run example01 to test quantum espresso, which calculate energy and band structure for Si, Al, Cu and Ni. I get an error message as follows:
running the scf calculation for Si...from test_input_xml: input file not opened or empty
At line 1999 of file read_namelists.f90 (unit = 9, file = 'input_tmp.in')
Fortran runtime error: End of file
Error termination. Backtrace:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
from test_input_xml: input file not opened or empty
At line 1999 of file read_namelists.f90 (unit = 9, file = 'input_tmp.in')
Fortran runtime error: End of file
Could you help me to overcome this problem ?
What is PARA_PREFIX in your environment_variables file set to?
Try running with
PARA_PREFIX=" "
or if you have MPI you can try
PARA_PREFIX=" mpirun -np 1 "
Most tests and examples are meant to be run serially.
I'm running a small Julia program using PyPlot in Juliabox (IJulia Notebook) but it's errors out with an error mesg as listed below. I not sure if it's trying to use my machine's disk to write to but I have valid R+W access there. Basically I'm trying out the examples as mentioned here: https://www.juliabox.org/notebooks/tutorial/Plotting%20in%20Julia.ipynb#
LoadError: unlink: read-only file system (EROFS)
Pkg.add("PyPlot")
using PyPlot
for i = 1.0:300.0
for j = 1.0+i:250.0, k=1.0:10
plot(i+j, i*k/j, color="red", linewidth=1.0, linestyle="--")
i += 0.1
j += 0.05
k += 0.01
end
end
Error log:
INFO: Nothing to be done
INFO: Precompiling module PyPlot...
INFO: Recompiling stale cache file /opt/julia_packages/.julia/lib/v0.4/Compat.ji for module Compat.
ERROR: LoadError: unlink: read-only file system (EROFS)
in unlink at fs.jl:102
in rm at file.jl:59
in create_expr_cache at loading.jl:330
in recompile_stale at loading.jl:461
in _require_from_serialized at loading.jl:83
in _require_from_serialized at ./loading.jl:109
in require at ./loading.jl:219
in include at ./boot.jl:261
in include_from_node1 at ./loading.jl:304
[inlined code] from none:2
in anonymous at no file:0
in process_options at ./client.jl:257
in _start at ./client.jl:378
while loading /home/juser/.julia/v0.4/PyCall/src/PyCall.jl, in expression starting on line 26
ERROR: LoadError: Failed to precompile PyCall to /home/juser/.julia/lib/v0.4/PyCall.ji
in error at ./error.jl:21
in compilecache at loading.jl:384
in require at ./loading.jl:224
in include at ./boot.jl:261
in include_from_node1 at ./loading.jl:304
[inlined code] from none:2
in anonymous at no file:0
in process_options at ./client.jl:257
in _start at ./client.jl:378
while loading /home/juser/.julia/v0.4/PyPlot/src/PyPlot.jl, in expression starting on line 5
LoadError: Failed to precompile PyPlot to /home/juser/.julia/lib/v0.4/PyPlot.ji
while loading In[10], in expression starting on line 2
in error at ./error.jl:21
in compilecache at loading.jl:384
in require at ./loading.jl:250
If I use 0.3.12 version (IJulia Notebook), then it compiles and shows INFO: Nothing to be done but doesn't show anything as output (some graphics plot diagram etc).
Thanks to ali_m. Here's the main summary on what that post says.
The problem seems to be that JuliaBox ships some precompiled cache files in a read-only directory /opt/julia_packages/.julia/lib/v0.4. If at some point it detects that the cache is stale and tries to recompile it, it fails.
This needs to be fixed in Julia itself—it shouldn't try to delete cache files from a read-only directory when recompiling.
Issue link is https://github.com/JuliaLang/julia/issues/14368
To resolve it only in 0.4.2, one can use (this will remove the 3rd index value from Base.LOAD_CACHE_PATH array/set/tuple) to your .juliarc file on JuliaBox to remove the read-only cache directory from the search path. Or just run this manually before typing using Compat etc to rebuild the cache without using the read-only search path.
splice!(Base.LOAD_CACHE_PATH, 3)
A nice example of splice! function
(PS: A function in Julia which ends with ! with its names means, that function will not only do its work but also will change its arguments data/value).
# Remove elements from an array by index with splice!
arr = [3,4,5]
splice!(arr,2) # => 4 ; arr is now [3,5]
The suggested workaround works for 0.4.2 (using echo 'splice!(Base.LOAD_CACHE_PATH, 3)' > ~/.juliarc.jl to insert the line into juliarc) but apparently LOAD_CACHE_PATH isn't defined while launching Julia 0.3.12 so this would fail there.
Adding the following line in the same file fixed this issue (adding a condition to work when version in Julia is 0.4 or above). I didn't see this issue in the 0.5 development version so we are good there.
VERSION >= v"0.4" && splice!(Base.LOAD_CACHE_PATH, 3)