The Elder Scrolls V: Skyrim Special Edition

The Elder Scrolls V: Skyrim Special Edition

Vis statistikker:
Denny Crane 19. juli 2019 kl. 4:56
Whole Computer Crashes...
I need help from the fattest and most knowledgeable nerd among you.
When I play this video game, I am in the screen where I have to create my character. I am sliding the bars back and forth, trying to make the guy look like me. It is approximately about 10 minutes within the process of using the slider going back and forth to get things just right when my whole computer freezes up, a single sound stutters like a drum roll; THEN my whole computer screen goes blue tell me it is collecting data and will restart. This happens EVERY time I am on that character creation screen approximately within 10 minutes of time. No exceptions.
Symptom observations:
1. "Launcher" is unable to detect my computer box's hardware.
2. Some in session sliders (i.e. difficulty) only let me slide in one direction unless I HOLD the opposite direction, but it keeps fighting to go back to the polar opposite side.
3. Body weight will be set, then if I go back to that setting, after setting eyes or mouth for a bit, will be slid to the far RIGHT. I reset it back, then come back and find it has slid to the far RIGHT again.
What is inside my computer box:
Windows 10 Home 64 bit
4970k
24 "gigs" of "Ram"
RX Vega 56
2 "TB" "SSD"
My office IT already turned off some kind of tablet setting on my computer box; he tried giving the video game "admin" status; he checked all "drivers" and "firmware" are up to date. Computer box does NOT feel hot at time of crash.
< >
Viser 31-45 af 51 kommentarer
Denny Crane 19. juli 2019 kl. 6:28 
Oprindeligt skrevet af Sinsling:
This might still be memory related. Please confirm your memory format and if possible, individual stick speeds.

How would I find this information out?


Oprindeligt skrevet af SpeedFreak1972:
Oprindeligt skrevet af Grumpy:

where did you got the information from that the problem is PCI-E related?

well from the code and indeed on google it often relates to pci-e related problems.

If it is, what do I do to fix it? My office IT guy says we could reseat the card? Does that mean it is loose?
Murky 19. juli 2019 kl. 6:31 
Download this handy little tool called "Bluescreenview".
https://www.nirsoft.net/utils/blue_screen_view.html

Open the program and look for "Dump files" entries and double click to open any one of them.
If you dont find any entries, wait for another BSOD and try again.

When you open one of those dump files, look for the values in "Bug check string" and "Caused by driver" fields.

You will find a code like "DRIVER_IRQL_NOT_LESS_OR_EQUAL" or something similar in those fields.

Copy that information and search up on Google or share here for someone to help you out.
Denny Crane 19. juli 2019 kl. 6:37 
"Bug Check String" is empty on all fields.
"Caused by" = "hal.dll"
"Caused by Address" = "hal.dll+477e8"
Denny Crane 19. juli 2019 kl. 6:37 
All four logs are the same in those fields.
Sinsling 19. juli 2019 kl. 6:39 
Oprindeligt skrevet af Denny Crane:
Oprindeligt skrevet af Sinsling:
This might still be memory related. Please confirm your memory format and if possible, individual stick speeds.

How would I find this information out?


Oprindeligt skrevet af SpeedFreak1972:

well from the code and indeed on google it often relates to pci-e related problems.

If it is, what do I do to fix it? My office IT guy says we could reseat the card? Does that mean it is loose?
Your second part first: that is possible. Reseating and making sure the card is properly installed is never a bad idea.


For memory: while reseating the card check your ram sticks. How many do you have? You likely have either 2(16gb+8gb) or 3(8gbx3).

Boot into bios. Find memory related properties in your bios. Check to make sure all of your memory sticks are set to a speed your cpu support and that they all match. Even 1 stick set to an incorrect speed can cause problems.
Grumpy 19. juli 2019 kl. 6:39 
Oprindeligt skrevet af Denny Crane:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffb20866d50028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7eb30d4e-36ce-46d4-903c-e0fa53088c4a.

Oprindeligt skrevet af Sinsling:
Oprindeligt skrevet af Grumpy:

where did you got the information from that the problem is PCI-E related?
0x00000124

Is a pci hardware fault.

And I assume can be due to drivers, configuration, or broken component.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error
Oprindeligt skrevet af windows:
0x4

An uncorrectable PCI Express error occurred.

the first parameter of the bugcheck is 0x0 not 0x4. which would lead to a machine check exception.

#2 what kind of IT guy sends his friend / client to a public gaming forum to troubleshoot a PC crash?

#3 if OP is sure that all driver are up to date then he needs...

#3.1 check his CPU with a stress test software like Prime95
#3.2 check his GPU with a stress test software like FurMark
#3.3 check his RAM with Memtest86 or Win10 internal RAM diagnostic tools
#3.4 check the disk with chkdsk CLICK[neosmart.net]

#4
Oprindeligt skrevet af Denny Crane:
Oprindeligt skrevet af SpeedFreak1972:

well from the code and indeed on google it often relates to pci-e related problems.

If it is, what do I do to fix it? My office IT guy says we could reseat the card? Does that mean it is loose?

why not ask your IT guy - just wtf on that part
Sinsling 19. juli 2019 kl. 6:41 
Well it's great that we have a dll error that can mean ♥♥♥♥♥♥♥♥♥. :steamhappy:
Sinsling 19. juli 2019 kl. 6:43 
Oprindeligt skrevet af Grumpy:

why not ask your IT guy - just wtf on that part
I dunno... some it guys... I've overheard calls. You dont want to know the people they hire these days.

Also I fail at reading error codes. :steamfacepalm:

Although are you positive an error code isn't built using these fault numbers? Searching for the full string does imply a hardware error. 🤔
Sidst redigeret af Sinsling; 19. juli 2019 kl. 6:46
Denny Crane 19. juli 2019 kl. 6:49 
1. My office IT guy does this because I sign his paycheck and he knows how to keep a job. Mind you this isn't in his job description but he understand office politics.
2. My office IT guy does admit when he doesn't know the answer and works with me to find a solution.
3. He's Indian and that's all his culture has been reduced to, so I have no doubt with his and your all's help we'll find a solution.
Denny Crane 19. juli 2019 kl. 6:52 
My office IT guy says that "reseating" things will require me (him) to be at my computer box. I'm on my mobile smart phone at the firm right now. I also have a client about to arrive soon so I will be unable to attempt the "reseating" and checking of my chips. That will have to wait until after the work day.
You all keep brain storming and read that computer code I pasted. Keep posting with ideas and work together. With your combined weight and brain power, I'm sure we'll get this.
Grumpy 19. juli 2019 kl. 7:01 
Oprindeligt skrevet af Denny Crane:
1. My office IT guy does this because I sign his paycheck and he knows how to keep a job. Mind you this isn't in his job description but he understand office politics.
2. My office IT guy does admit when he doesn't know the answer and works with me to find a solution.
3. He's Indian and that's all his culture has been reduced to, so I have no doubt with his and your all's help we'll find a solution.


Oprindeligt skrevet af Denny Crane:
My office IT guy says that "reseating" things will require me (him) to be at my computer box. I'm on my mobile smart phone at the firm right now. I also have a client about to arrive soon so I will be unable to attempt the "reseating" and checking of my chips. That will have to wait until after the work day.
You all keep brain storming and read that computer code I pasted. Keep posting with ideas and work together. With your combined weight and brain power, I'm sure we'll get this.

I have a much better idea, we go and enjoy our modded games and you stop trolling. your last 2 posts were too obvious.
Murky 19. juli 2019 kl. 7:04 
Thanks for sharing the error code. Sounds like a hardware problem but could very well be caused by a software.

I am no expert, but I would start by eliminating any software related faults since your IT guy cannot open up the pc:

> Start by checking if any of the hardware in your pc is missing a driver.
Control Panel > Hardware and Sound > Device Manager
Update any hardware with red or yellow exclamation mark

> Run a memory test using the inbuilt Windows Memory diagnostic tool
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools

Or download a program like memtest86 for indepth testing the memory
https://www.memtest86.com/

> Run a stress test with Prime95 or AIDA64
https://www.guru3d.com/files-details/prime95-download.html

> Download the lates BIOS for your motherboard (your IT guy should be able to help on this)
Sinsling 19. juli 2019 kl. 7:11 
I kinda suspected it from the start but I'm guessing you got tired of playing. That's disappointing.
StarlightRac 19. juli 2019 kl. 9:07 
even though he/she might be trolling, i like to say you guys should get gold star; will a lot of them. i'm impress, you are all will knowledgable(ms) and super helpful.
Sidst redigeret af StarlightRac; 19. juli 2019 kl. 9:11
SpeedFreak1972 19. juli 2019 kl. 10:03 
Oprindeligt skrevet af Denny Crane:
"Bug Check String" is empty on all fields.
"Caused by" = "hal.dll"
"Caused by Address" = "hal.dll+477e8"

this an odd one Hal is the hardware Abstraction layer what means that is the dll that forms a bridge between Hardware and OS ... From what I've read it can be corrupted however that would cause far more severe problems.

That said this is far beyond my expertise.
Sidst redigeret af SpeedFreak1972; 19. juli 2019 kl. 10:04
< >
Viser 31-45 af 51 kommentarer
Per side: 1530 50

Dato opslået: 19. juli 2019 kl. 4:56
Indlæg: 51