Computer Freeze - Hard Reboot Required

L

Lunddal

Member
Joined
Jun 30, 2020
Posts
8
Hello Everyone,

I found this website by doing a search on google for my problem.
Sometimes the computer just freezes and I am stuck at whatever I had going on, on my screen.

I am able to do nothing at all besides to do a hard restart of the computer.

Going through your forums I found a diagnostic tool which I have used - I have attached the Zip file to this thread.

I did a memory check already but it came out with no issues.
I honestly thought it was my memory because I feel like I have had some issues with them where for example my computer wouldn't boot but switching the memory helped.

I hope any of you can help.
 

Attachments

Just a side note.

This problem occurs sometimes and not always.
I had it 2 times shortly after each other tonight but Tomorrow I might not have the problem before in a couple of days.
 
MrPepka said:
Update BIOS - Support For B360-A PRO | Motherboard - The world leader in motherboard design | MSI Global
Click to expand...

Why are you telling people to update their BIOS all the time as a first response? That's silly. BIOS updates really aren't necessary unless they fix something that is broken or if the user wants a feature that may have been added in an update.

Code: 
3: kd> .cxr ffff800d06bac3a0
rax=0000000000003b89 rbx=0000000000000001 rcx=ffff868ab87a1010
rdx=0000000000000001 rsi=000000002a4cb2c7 rdi=0000000000000001
rip=fffff80138abc846 rsp=ffff800d06bacd90 rbp=0000000000000003
r8=0000000000003b89  r9=ffff868ab87a1010 r10=fffff801200a0f20
r11=0000000000000001 r12=0000000000000001 r13=ffff868a90842870
r14=fffffb287903e310 r15=0000000000000003
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
dxgkrnl!CFlipToken::TraceStateChanged+0x86:
fffff801`38abc846 498bcd          mov     rcx,r13

There was an exception, specifically an access violation that occurred in the DirectX function while it was doing some graphics-related work. There was an attempt to move r13 to the rcx register, but that's where the access violation hit.

Code: 
3: kd> !pte ffff868ab87a1010
                                           VA ffff868ab87a1010
PXE at FFFFE371B8DC6868    PPE at FFFFE371B8D0D150    PDE at FFFFE371A1A2AE18    PTE at FFFFE343455C3D08
Unable to get PXE FFFFE371B8DC6868

We can't get the status of the rcx register's contents because it's only a minidump, so not much to go on. I presume it's invalid memory though and that's why the exception occurred.

I'd first try a complete uninstall of your nvidia drivers, restarting, and then a reinstall of the latest nvidia video card drivers for your system so we can either see if it fixes it or at the very least rule out video drivers.
 
Patrick said:
Why are you telling people to update their BIOS all the time as a first response? That's silly. BIOS updates really aren't necessary unless they fix something that is broken or if the user wants a feature that may have been added in an update.
Click to expand...
Well, but BIOS updates can also improve the compatibility of the motherboard with the graphics card
 
Patrick said:
Why are you telling people to update their BIOS all the time as a first response? That's silly. BIOS updates really aren't necessary unless they fix something that is broken or if the user wants a feature that may have been added in an update.

Code: 
3: kd> .cxr ffff800d06bac3a0
rax=0000000000003b89 rbx=0000000000000001 rcx=ffff868ab87a1010
rdx=0000000000000001 rsi=000000002a4cb2c7 rdi=0000000000000001
rip=fffff80138abc846 rsp=ffff800d06bacd90 rbp=0000000000000003
r8=0000000000003b89  r9=ffff868ab87a1010 r10=fffff801200a0f20
r11=0000000000000001 r12=0000000000000001 r13=ffff868a90842870
r14=fffffb287903e310 r15=0000000000000003
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
dxgkrnl!CFlipToken::TraceStateChanged+0x86:
fffff801`38abc846 498bcd          mov     rcx,r13

There was an exception, specifically an access violation that occurred in the DirectX function while it was doing some graphics-related work. There was an attempt to move r13 to the rcx register, but that's where the access violation hit.

Code: 
3: kd> !pte ffff868ab87a1010
                                           VA ffff868ab87a1010
PXE at FFFFE371B8DC6868    PPE at FFFFE371B8D0D150    PDE at FFFFE371A1A2AE18    PTE at FFFFE343455C3D08
Unable to get PXE FFFFE371B8DC6868

We can't get the status of the rcx register's contents because it's only a minidump, so not much to go on. I presume it's invalid memory though and that's why the exception occurred.

I'd first try a complete uninstall of your nvidia drivers, restarting, and then a reinstall of the latest nvidia video card drivers for your system so we can either see if it fixes it or at the very least rule out video drivers.
Click to expand...

I did a FULL format c: of my computer.
I disassembled the computer and gave it a thorough cleaning aswell.
Updated ALL drivers including chipset and everything through Driver Booster.
Installed the newest driver for my GPU through Nvidia website.

It has been running flawlessly for throughout the weekend - but I just had a freeze once again where I had to push on hold the power button to shut it down and boot it back up again.

I will run a check once again - hopefully you can see what the problem might be.

Personally I am suspecting my memory or motherboard - mostly my memory.

Brb with a new diagnostic.
 
xilolee said:
That wasn't a good idea.
It could suggest older drivers (if not bad ones).
Click to expand...

What?
I was on the impression that Driver Booster was fairly good - waste of money I guess?

Will update the chipset drivers etc. from the manufacturers website.

But I don't reckon that is the main issue though.
 
AHCI-DRIVER-BOOSTER.png

As an example, it would change my updated AHCI driver (10.0.19041.1, MS driver; that's the latest windows version) with an older one: 1.3.1.276 (from AMD), dated 19 March 2015.
 
Are you using the following ram model?

F4-3200C16D-16GTZR
Trident Z RGB DDR4-3200MHz CL16-18-18-38 - 1.35V - 16GB (2x8GB)

If yes, try to increase the dram frequency to 2666 (value taken from intel i5-8600K webpage).
Currently it seems it's set to 2133.
And today there's a new GeForce Game Ready Driver: 451.67 WHQL.
 
Last edited:
xilolee said:
Are you using the following ram model?

F4-3200C16D-16GTZR
Trident Z RGB DDR4-3200MHz CL16-18-18-38 - 1.35V - 16GB (2x8GB)

If yes, try to increase the dram frequency to 2666 (value taken from intel i5-8600K webpage).
Currently it seems it's set to 2133.
And today there's a new GeForce Game Ready Driver: 451.67 WHQL.
Click to expand...

That is the ram I am using, yes.

I am working in The Netherlands atm but I will try this when I get back home! :)

I've just increased the mhz from 800 to 2166 before I left for work (It seemed like it was the max i could go to).
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top