>>101574781
>it begins

>>101574781
>he doesn't know

My i9 14900KS blue screens somewhat often (once every other week). Seems like a very unstable processor

I'm on a 2012 craptop because I'm poor :D

File: 1708789574575076.png (374 KB, 814x550)

374 KB PNG

>>101574833
>seems like

File: ab55ae593e36bc16261426f1e(...).jpg (64 KB, 694x718)

64 KB JPG

>MFW I'm an AMD master race member
It feels good, lads.

>>101574860
You're a goober.

>>101574781
The degradation has begun...

File: 1710828539294037.gif (1.44 MB, 300x284)

1.44 MB GIF

>>101574860
>AMD master race
based
>tranime
cringe

upgrade to 12900k

>>101574781
>>101574833
Get a refund
If you want to understand how bad the problem is, analyze the .dmp files it creates upon crashing.
>>101574860
Of course that Shamiko would use AMD

>>101574781
It's going to get worst anon.

>>101574991
Where do I find the .dmp files?

>>101574833
every intel processor starting from skylake is like that. It crashes randomly until it is fixed by intel.
I would recommend to check bios updates for your motherboard. I fixed one of my old machines with it.
instead of blue screening it just freezes for a second now :D

>>101575050
Yeah I updated the bios but still get BSODs.

File: 1719666201829975.gif (224 KB, 128x128)

224 KB GIF

ITS OVER

File: ryzen.jpg (524 KB, 1080x1080)

524 KB JPG

>>101575038
search your hard drive with *.dmp
you'll need windbg
the process goes, you open the dmp file with it, then type !analyze -v in the console then copypaste the EIP/RIP register's content in the disassembly view to know what instruction crashed, you compare the instruction with the error type and parameter to know if the CPU is faulty.
if you got illegal instruction on a valid x86 instruction it's over for your CPU, it has degraded probably a lot
if you get write access violation on an instruction that doesn't write to memory, your cpu has started degrading
otherwise if you get access violation but the second parameter of the exception is a low value or seemingly garbage value, check the instruction and its operands manually, if the exception address doesn't match the register state at all then you got yourself a certified authentic 14900KEK crash, otherwise it's a bug or the CPU crashed in a way that can't be easily be differentiated from a bug.
(sometimes it crashes in another unique way, it depends on your cpu, also this doesn't work the same way with some programs if they use a custom exception handler)

>>101574907
anime website

>>101574907
my brother in mook you're using the weeb site.

File: 14867850267099.jpg (26 KB, 345x452)

26 KB JPG

>>101574781
>not using GeForce Now

File: IMG_9263.jpg (43 KB, 640x480)

43 KB JPG

>>101574781
Your cpu is on borrowed time, like picrel.

File: IMG_9265.jpg (26 KB, 400x440)

26 KB JPG

>>101574781
The curse...