Weird Random BSOD

I

Iron Lion

Member
Joined
Jan 28, 2020
Posts
10
Windows 10 64 Retail installed in October.
I9-9900K
Maximus XI Formula
Corsair Dominator Platinum RGB 32 GB (4 x 8 GB) DDR4 3200 MHz C16
Adata SX8200 Pro M.2-2280 2TB PCI Express 3.0 x4 NVMe Solid State Drive
Gigabyte GeForce RTX 2080 Ti XTREME WATERFORCE WB 11GB
Creative Sound BlasterAE-9
PSU 1200W Corsair
Self Made System

All parts were installed in october 2019 other than the PSU and BLU RAY they around 5 years old.


I have been working with Colif from town hardware sinve november, none of us can seem to figure out what is wrong. Heres the thread Question - Intermitent BSOD

More dumps: OneDrive
 

Attachments

Last edited by a moderator:
Hi Iron Lion,

Welcome to Sysnative!

Could you provide a list of options you have tried in order to solve the crashes? That would save us time.

I note you have a thread at TenForums where they suspect a CPU problem quite quickly because of 0x124.
Although I am a long-time member at TenForums as well, I disagree with them that it's a CPU problem based on the 0x124 crashes. What they're looking at, Toms Hardware as well, is an error record created by the CPU at the time of the crash and one of the important elements in it is
Rich (BB code): 
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffff9a0cbe1cb138
Section @ ffff9a0cbe1cb280
Offset : 600
Length : 272
Flags : 0x00000000
Severity : Fatal

Error : Unknown (Proc 5 Bank 0)
Status : 0xb200000000030005

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffdc8fa11dd138
Section @ ffffdc8fa11dd280
Offset : 600
Length : 272
Flags : 0x00000000
Severity : Fatal

Error : Unknown (Proc 14 Bank 0)
Status : 0xb200000000030005

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffc98334db8138
Section @ ffffc98334db8280
Offset : 600
Length : 272
Flags : 0x00000000
Severity : Fatal

Error : Unknown (Proc 6 Bank 0)
Status : 0xb200000000030005
Specifically, the colored parts. If the processors were at least the same, I might have gone the same route because then it's more likely that a core is bad but multiple 0x124 with each a different core is not likely to be the CPU in my experience.


The variety in crashes are also notable, I'll have a look at the Toms Hardware thread.
2020-01-28T05:13:23.001The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc98334db8028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fe1ab7d9-fb90-4b3d-b88a-86a55a396e7e.27
2020-01-23T02:04:33.817The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffdc8fa11dd028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a23287b8-b6ba-4fc2-84ca-cf891dab8c08.1001
2020-01-22T10:11:55.982The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff9a0cbe1cb028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 22a10403-886d-4b67-9c33-f7a2aa2e4a99.1199
2020-01-13T17:16:09.169The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffa000b5016100, 0x00000000000000ff, 0x0000000000000000, 0xfffff800495ceebc). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: acd87af0-e1a1-4674-86dc-e2b1cb9bf9fe.3284
2020-01-12T22:33:33.963The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8054a1ecd49, 0xffffa78248f5ea20, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 891beaa9-0b23-48c3-bc8e-7ec449cc7cc1.3438
2020-01-12T19:38:20.504The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff8e0e5b3f0060, 0xffff87079febf7b0, 0xffff8e0e627a78e0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 0c4797d4-c554-446f-8976-b4be69eb8a11.3606
2020-01-11T03:51:59.939The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff940dbcb8f028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 254c48a3-f8e5-412c-b798-66e2599e03e2.3827
2020-01-11T02:20:27.410The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd888f5f08028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c6f5fe6d-8fc2-4818-a7ee-335d29639ebd.3929
2020-01-10T23:47:35.740The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffba04ea7ec028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4780fc1f-8e98-442c-81a2-c09e070e81f6.4010
2020-01-10T02:35:58.124The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffcb82785a0028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c2cfd152-a7ac-4ec0-8dee-606b2c77435b.4181
2020-01-10T00:29:09.011The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000000, 0x0000000000000002, 0x0000000000000000, 0xfffff80727e49fff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 495d28ed-db1e-438d-a5ae-2e1bee0b464f.4277
2020-01-08T23:02:03.598The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000001, 0xfffff807673387be). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 4ea31d3c-02c2-4e51-b405-b2db4ddadb2c.4472
2020-01-07T08:13:31.537The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffdc08ca1a0028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: b0d20d38-0ca5-4292-9998-17d2d443dc74.4663
2020-01-06T20:22:10.010The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd40631fa8028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 5b40a45a-5032-4685-a442-f37bac909f72.4765
2020-01-06T07:40:42.893The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc1840bdc4028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 36d54f01-049d-45da-8ff3-a7bfe4fc09ca.4877
2020-01-05T07:48:02.820The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffb80282e23028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a274d8ab-2ce7-4623-83a7-55797be5d73a.5090
2020-01-05T03:15:04.807The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff80441173358). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: f5ba2d88-21c7-4dca-8c63-12cb58a6c0a1.5167
2020-01-04T02:11:19.368The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffda0c70619028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c8a2e56c-aaf8-4b1f-a19e-217e1e8e8792.5318
2019-12-29T20:02:44.280The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffb08c7f9a0028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: ebfa50e0-bbfb-47cb-8a4b-75f97ab5fa67.6086
2019-12-29T12:29:36.456The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff8012d7745a8, 0x0000000000000002, 0x0000000000000000, 0xfffff8016c2467c7). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 443a5147-f036-4e0a-a306-77f4a6ea1f3c.6173
2019-12-27T18:35:06.051The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffbd063b9d9028, 0x00000000b2000000, 0x0000000000000014). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: d59dae34-7a34-44ff-968f-bbfa55532869.6671
2019-12-23T05:33:44.345The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe7058a9b8028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: f85355bd-e7f3-46ed-b393-d896663c4b3c.7375
2019-12-22T00:54:20.712The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8027d7bffd6, 0xffffba8de2bf6030, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 89f5caf6-9a0b-4354-a264-90ba52d23353.7536
2019-12-21T10:16:30.806The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff8f0ebe276028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 82741bbd-5f89-4486-a051-12f8d7d09f6d.7681
2019-12-21T09:11:39.021The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffa5084b709028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a6e91950-51e6-4385-9abb-519324ef7ecb.7775
2019-12-20T21:05:52.301The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff870346819028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 07f6a146-1f39-4fd3-9ecf-ea67834d76a2.7941
2019-12-20T20:57:42.499The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc602bcfa0028, 0x00000000be000000, 0x0000000000800400). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 341ce7e6-e9fd-4791-a7b6-b4e458c03f45.8025
2019-12-20T20:13:30.077The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80403d73358, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: db0e8c96-a975-4f57-b5c3-8a74dd4ad9ed.8109
2019-12-19T20:12:13.752The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd989aabea028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 862f0956-ebb3-445c-b8d5-2925eb6435d8.8328
2019-12-18T06:31:03.209The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd183e2d3a028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: bad059d9-a795-40e1-9df1-7915c15eb1d5.8806
2019-12-09T07:45:07.027The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe40c3f3b4028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 07015811-21eb-4e7d-ab1a-a3df69275289.10108
2019-12-06T11:31:12.613The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc082895ed028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 875116ad-e47b-4082-bd28-761867d3aee1.10680
2019-12-05T21:47:29.303The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd9014fddb028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 5cb44968-783f-4cf3-b78d-b792e5e5fff2.10859
2019-12-04T05:52:22.326The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe502efbb9028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\Minidump\120419-9468-01.dmp. Report Id: 949b2bb0-4ac2-4dbb-9a95-06bc0f37644b.11472
2019-12-02T19:52:42.040The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc18beee2a028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\Minidump\120219-9187-01.dmp. Report Id: 65d8eaed-e7cf-4091-b8e9-88819efa13ed.11819
2019-11-29T06:39:39.827The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x000000000000000c, 0x0000000000000000, 0xffffa38041e80180, 0x000000000000000e). A dump was saved in: C:\Windows\Minidump\112919-10921-01.dmp. Report Id: 2432b8ba-6ba3-445b-a4b6-ace40bbf825f.12440
2019-11-26T02:44:17.422The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8027b373358, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\112619-9562-01.dmp. Report Id: d18dc505-3fa1-4c9f-9a44-d0a51867723d.13822
2019-11-10T13:07:25.137The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500, 0xfffff80725d73358). A dump was saved in: C:\Windows\Minidump\111019-8250-01.dmp. Report Id: d03c9a80-459f-41c8-ab31-542d52fbfee6.16188
2019-11-07T22:30:35.263The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc7049596a028, 0x00000000b2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: d2468434-a3b3-470b-b0bc-c52273da4e3a.16589
2019-11-07T22:08:03.670The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffd80f5ab3c028, 0x00000000f2000000, 0x0000000000030005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 2614c41c-f1ce-408e-a4c7-e8b506ce20be.16667
(Ps, the numbers in the right column reference the event ID in the event logs, I will remove them when I have some time)
 
Mostly read the TH thread and it seems they've been going back and forth with drivers and hardware.

Could you remove the XMP and use the default SPD settings while troubleshooting.


What I would do in your situation, a hardware stripdown starting with unnecessary hardware.
 
XMP? SPD?

We have tried Changing sound cards, changing from WI-FI to cable then back again, changing the power cable and surge protector,tried looking for windows errors, tried the usual tests that didnt show anything. Basicly everything other than Taking things apart and randomly RMA'ing stuff. Thats still the plan i just would like to know where to start for the best chances of getting the part that causing problems. Id love to be able to strip it down and try different parts, but i dont have any spares that i can try that will fit, plus if i take anything apart i have to fight through the massive custom watercooling loop. Toms hardware seems to leanign toward motherboard, so am now, more so from my pretty limited understanding of what you said. I was going to swap my PSU for a 1000w corsair i have lying around as its the only part i can do that with, i wanted to know if there was any point trying that or going straight to RMA's starting with my motherboard.


Thank you for you help so far.
 
One thing i have noticed that i forgot to mention, that i cant explain at all is: BSOD stop for 3 calendar days (regardless of up time), on the 3rd day after a power off at the PSU the bsod will start again.So if i hit the switch on the PSU (to change parts or cables) or if there is a power cut. It has happened twice after i noticed it first. So i have been able to replicate it twice since i noticed it first. Once i got the HWINFO log file near a BSOD for the guys at toms hardware i will try to replicate it a 3rd time.

Why 3 days?
 
While it's actually something different, SPD is commonly referred to when one implies the base speed, voltage, and timings at which RAM operates without any custom configurations.
SPD, Serial Presence Detect, is really a standardized way of accessing information about a RAM module, such as the speed, voltage, and timings.

XMP, Extreme Memory Profile, is something that allows someone to change the settings at which the RAM is to operate. These settings have been tested by the manufacturer and as such, it should normally be safe to apply them.
It's similar to manually changing the settings for the RAM to run at a higher speed like what many do with the CPU, but XMP largely made that process easier and safer.

In my opinion, XMP is basically overclocking, because the way I see it XMP allows for the RAM to operate at a faster speed than its base which in my books is overclocking.

I would suggest reading the user manual of your motherboard about XMP and the RAM settings, check out version E14120 at the support page if you don't speak Japanese or Chinese.

I am also leaning towards the motherboard, but I would like to ensure the XMP isn't causing any problems.


For the hardware stripdown, I would start by removing anything you don't need on a daily base. Examples: external drives, a headphone (if you're not a music producer), printer, USB adapters, ...


A random suggestion here for the 3 calendar days BSOD stop, check out Task Scheduler. A few years ago someone I was helping said that he/she checked Task Scheduler and found a task that was being triggered before each BSOD and disabling it solved the problem.
 
Ok, i cheked and XMP was off i had just set memory speed to the right speed 3200. I dont know much about the bios, i just set everything to auto and move on. I turned XMP on just to see if it helps. The ppl who made it probably know a lot more than i do, i have popular hardware so its probably been tested to death. One thing i noticed its says my ram is 3200 in one place in the bios but on the same screen it says in 1666. No idea whats thats about.

Theres no external drives, nothing usb that was plugeed into it before the problem started, its just my keyboard mouse, hub and Fingerpint reader. The hub and reader were installed after the BSOD started.Long after but i can yank them if it helps. Printer is conected over the network along with my nas. Its just the two tvs i use as screens,mouse,keyboard,hub, and fingerprint lock.

Cheked task sheduler and nothing stood out or matched up that i could see.

As for striping down the pc itself, its custom water cooled i have no air cooling stuff that fits, i have no spare parts that fit the board either. I was hoping some one could tell if it was software of what pice of hardware i need to RMA. Thats doesnt look likley at this point so what im asking first is is it worth me swaping my PSU and unpluging the blu ray which are the only old parts on my pc (my last pc they were in used to lock up and freeze a few times a day untill i did a hard reset and i never figured out whats wrong of fixed it) or do i just go straight to sending random parts back untill it works? Second if i do randomly RMA parts which one do i start with that gives me best chance of hitting the bad part first time? Im guessing motherboard.

Edit: looks like you edited my one drive link, but it leads to the older dump files. the most recent ones along with log files from HWINFO and Argus montior and a log fime from Autorun are in the folder above it. "Dump" not "Old"
 
Last edited:
One thing i noticed its says my ram is 3200 in one place in the bios but on the same screen it says in 1666. No idea whats thats about.
Click to expand...
DDR or Dual Data Rate.

Some programs, including the BIOS, show the speed of RAM, ~1600 in your case, in single data rate.
A single data rate means that with every clock cycle, a single transfer takes place. Dual is 2 transfers in a cycle allowing for the memory to be twice as fast.
1580284408667.png



Dumps from BSOD crashes are normally not able to tell us what part of hardware (if any) caused the crash because dumps and all the tools needed to analyze them are originally designed for developers. From time to time dumps can help us indicate what might have caused the crash with hardware, but we can never be 100% certain until proven as the past has shown.


Have you used the other PSU before without problems? Swapping a PSU would be useless if the other PSU isn't good.


Any hardware you don't need is not limited to external hardware, but could also be internal such as any drives used for storage only or a memory module if you have multiple or GPU for example.

The hub and reader were installed after the BSOD started.Long after but i can yank them if it helps
Click to expand...
Please do still disconnect them, it doesn't matter if they were installed after or before the BSODs started. It matters that the hardware is reduced to make it easier to pinpoint the cause.
 
Ok makes sense, i just grasping at straws or anyting i dont undertand.

I thought the psu was the problem with my last pc turned out i was wrong as swaping it didnt solve the problem and as i type that i realise if there somehting up with one i have in there now i would have had more and different probelms.

I cant pull my GPU because ill have no way to bridge the gap in the loop, i have 32gb of ram split between 4 memory modules do you want me to pull 3 of them? i did already run memtest and they come up fine after 4 runs. other than the sound card that we already tired swaping with a new one there nothing else in there other than fans that i can pull and still have it work at all.

This is why really starting to think send stuff back in order of llikleyhood is the only option i have left...
 
This is just my thoughts, but since it's possible you'd need to remove the custom cooling in order to RMA a part I would suggest you remove the custom cooling now and use a standard fan allowing for removal of more parts.

i have 32gb of ram split between 4 memory modules do you want me to pull 3 of them?
Click to expand...
Yes, everything that's not needed and can be removed including 3 of the modules.
 
Ok i just RMA's my motherboard to amazon, they were nice enough to send the new one first. It will be here on the 11. Lets hope i got it right, if didnt ill have go to the manufacturer for the rest because amazon wont be happy if i sent back a perfectly fine motherboard. So ill have to send the rest back to Corsair,Intel and Gigabyte i think the GPU is.

Maybe turning on XMP will work, maybe i set the memory settings wrong and this righted them.


Im kinda broke right now, and i would have to buy air cooler, bad timing as i cant reallyafford it right now.Thats why i just pulled the triger on the RMA all other free options have run out. Wish me luck and pray for me!

In case it doesnt work who whats to try and guess the odds on the next thing i should try sending back? CPU, RAM or GPU?
 
While I understand you'd like to know the next step in advance, it's not something we try to guess because in order to do that the result of the current step needs to be known.

Just to make you aware, while many may provide you with a complete step by step tutorial trying to cover nearly all possibilities, we don't do that unless we're fairly sure of the cause. Complete step by step tutorials may be beneficial for some, >90% of it really is useless for many.
 
Dw im not after step by step stuff. I hate those things on google. But because of the nature of this thing and my limited funds we are only going to guessing here from now on. If its still around after i swap out the motherboard,and god i hope not but if it is then we will be no closer to knowing whats wrong other than knowing its not the motherboard. So far i have 1 myabe two votes for cpu next from Toms Hardware. I have been reduced to using the same system those terrible singing shows on tv use to fix my pc. The part that gets the most votes gets changed next if the motheboard doesnt work. So go ahead and cast your vote, i wont hold you to it were are all guessing now. IT Repair by democracy!
 
I was exaggerating a little, but we cannot or should not judge based on the current information on what to do next before the results are there.
 
axe0 said:
This is just my thoughts, but since it's possible you'd need to remove the custom cooling in order to RMA a part I would suggest you remove the custom cooling now and use a standard fan allowing for removal of more parts.

Yes, everything that's not needed and can be removed including 3 of the modules.
Click to expand...
If it's a mem timing problem, trying that could only show a fuse have broken because 1200W is overkill and power lines should be stable enough.

I would want to ask if Windows is 100.000000% up-to-date and no update is manually forbidden, like the Specter/Meltdown patch, for exemple.
If desynch comes from the clock on the mobo, I'd suggest changing the battery aswell.
I'd like to know also if the electrical lines is good in this house : 1200W is such a toaster... + a fancy 150W / 300W screen I guess ? All on the same plug ? Anti-lightning plug I hope ? CPL in this house ?
Can you run Crystal info with so much BSOD also, just to check HDD's health ?
 
Last edited:
How old is cpuz148 ? I see it's v1.73 something on the web.
Is the history of this computer a total hardware swap but for the HDD, then windows and driver update ?
 
CoinCoin said:
If it's a mem timing problem, trying that could only show a fuse have broken because 1200W is overkill and power lines should be stable enough.

I would want to ask if Windows is 100.000000% up-to-date and no update is manually forbidden, like the Specter/Meltdown patch, for exemple.
If desynch comes from the clock on the mobo, I'd suggest changing the battery aswell.
I'd like to know also if the electrical lines is good in this house : 1200W is such a toaster... + a fancy 150W / 300W screen I guess ? All on the same plug ? Anti-lightning plug I hope ? CPL in this house ?
Can you run Crystal info with so much BSOD also, just to check HDD's health ?
Click to expand...


Im not sure what mem timings have to do with my PSU but then theres a lot i dont understand sorry. Strange you should mention it but the guy that conected the room im in to the rest of houses power was... well he wasnt exaclty legit, if the power was janky i would be totally unsuprised. But i have a lot of other stuff in here, and its all fine so i decided to try moving to another room last, it would be pretty dificult because i dont live in the rest of building its not mine, it would be for a test too because id have to get somone in to unjank the power. i have metnioned on toms hardware but no one seems overly worried.

Windows is 100% up to date with a clean install on a new SSD.

I Rma'd the motheboard so if that the problem it will be fixed.

The power may or may not be janky but desinged this room around my lifestyle, i had them put 6 double sockets in the wall for a totall of 12 plug sockets. The PC, my stereo and two different Tv's (50inch pan plasma and 35inch toshiba lcd) i use as screens (one for gaming/pc stuff one for movies from my pc)because i havent updated one yet are all in their own socket, all surge proteced.

What is CPL?

I cheked my ssd with crystal disk already its ok as far as i could tell

At this point its a total rebuild other than the blu ray and PSU they are about 5 years old.



MrPepka said:
Update:
BIOS - ROG MAXIMUS XI HERO Driver & Tools | Płyty główne | ASUS Polska
Click to expand...


I tried to do that already, before that bios came out, i updated to the one before it and it didnt help any, i dont see any reason why this update would help? Theres nothing in the notes for it that would sujest it would help? Unless its just a generic "try this" sujestion and while i very much aprciate you all help and and everyone else's here very much we way past generic stuff at this point. This has been going on since the 7th of december over at Toms Hardware, the thread is 7 pages long.
 
If you can, try an anti-ligthning plug (or better : an uninterruptible power supply).

The idea in this is if the electrical network is bad in your house, and if you're taking too much of a phase in your house, then anyone closing a light on the same phase would give a kick in your PSU. Anti-ligthning plugs prevents that (and UPS are even better : it's a big capacitor, they prevent power-off after fuse cuts. But with a 1200W PSU, they would prevent poweroff for what 2 minutes ?).

Usually, 1200W named PSU are allready doing this (especially Corsair), but I'm afraid there is a second effect.

Secodn effect is your system shouldn't use more than, say, 750W top, when playing the newest AAA games with all the fancy effects.

So what happens is you're asking the PSU to give stable signals at 60% load - which is the usually good stable load, but also ask the PSU to be stable when you're asking say 200W from your PSU when browsing the internet. At 15% load, I would say any PSU give crap unstable power signals. Especially if next-door-dude open and close his ligths.

(Keep in mind that what I say is highly hypothetical, mainly told to give or reject ideas).

-edit- 1200W + fancy TVs + more plugs on the same phase is huge. Don't show this to the fire insurance man because he will ask for a kitchen electricity network rigth there. So try your stuff in your kitchen plugs for a test ? (and don't make tea at the same time, fuse will explode).

CPL is internet through electrical network. Corsair (usually) knows now how to handle it, but 5 years ago, I don't know.
 
Last edited:
Power settings in Windows can tell the computer to use performance mode, which would makes you give $ to the electricity compagny also. That is a test you could make but I'm not sure it's reliable if you don't load the GPU. It may need the GPU to be set always on performance mode too and even there I'm not sure.
To know if it's working, all fans should make helicopter sounds.

I think that test is quite dumb though, because I don't understand perfectly how win10 manages power from PSU. I live by the philopsophy "it works, so don't touch" and never made that.
 

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

Back
Top