-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whois Address crashing System Informer #2089
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
Well, for me, it crashed because of what @dmex says previously. I don't know why your System Informer worked fine when doing the exact same thing, but me it's not. |
@ToddIndry37 - Yeah, I wonder why it works for me. But I am glad atleast @dmex acknowledged it's a problem as it might crash maybe under certain conditions that I haven't tried as I only tried once so it could crash in other instances. Probably your crash dump is what really help show what triggered the problem. |
Yeah hehe, exactly. Glad I did send the crash dump though, so it's easy to identify what's the issue. Also, you use Windows 11, right? Or 10? Mine is Windows 11 23H2. |
Windows 11 23H2 22635.3720 Beta Insiders |
Ah, that is why it didn't crash on you. |
I have a higher chance of crashing as my CPU is hitting 100% due to CPU temperature throttling, will need to replace the thermal grease when I open the notebook to replace the keyboard in the next few weeks. |
Brief description of your issue
When I check the Whois address under network tools in System Informer, after I type the website address, System Informer immediately crashed due to "Invalid access to the memory location".
Steps to reproduce (optional)
Expected behavior (optional)
It should be showing the whois details on the window
Actual behavior (optional)
Crashed with error code
0xC0000005
, invalid access to the memory locationAnd here is the dump for troubleshooting:
SystemInformer_DumpFile_FNRQRVBXORZRKZH.dmp
Environment (optional)
The text was updated successfully, but these errors were encountered: