System Crashes

[Half Life]

Hi guys, 

A few weeks ago my system starts crashes regulary, some times BSOD or just frezze. The problems started when I change my motherboard, I bought an Aorus Z390 Pro WiFi, the only changed that I do when I change the mother board was reinstall the OS. I downloaded the windows media creation tool and download the ISO this month.

 

How looks when the system works normally.

 

 

 

 

How looks when system frezze.

 

 

 

And the BSOD...

 

 

I reinstalled ALL drivers but the problem still.

[Boinbo]

6 minutes ago, Half Life said:

Hi guys, 

A few weeks ago my system starts crashes regulary, some times BSOD or just frezze. The problems started when I change my motherboard, I bought an Aorus Z390 Pro WiFi, the only changed that I do when I change the mother board was reinstall the OS. I downloaded the windows media creation tool and download the ISO this month.

 

How looks when the system works normally.

 

 

 

 

How looks when system frezze.

 

 

 

And the BSOD...

 

 

I reinstalled ALL drivers but the problem still.

What is your whole system? Could you list it in PcPartPicker?

[Half Life]

27 minutes ago, Boinbo said:

What is your whole system? Could you list it in PcPartPicker?

Sure!

https://pcpartpicker.com/list/3kxLzY

[DisguisedMonkey]

1 hour ago, Half Life said:

Sure!

https://pcpartpicker.com/list/3kxLzY

No graphics card?

 

1000W PSU for just an i5?

[DisguisedMonkey]

1 hour ago, Half Life said:

Sure!

https://pcpartpicker.com/list/3kxLzY

Do you have an overclock applied aswell? If you do restore BIOS overclocking settings to default and see if it continues crashing.

[Half Life]

2 hours ago, DisguisedMonkey said:

No graphics card?

 

1000W PSU for just an i5?

Not yet. 

 

Haha it was on discount, same price that 600w. 

2 hours ago, DisguisedMonkey said:

Do you have an overclock applied aswell? If you do restore BIOS overclocking settings to default and see if it continues crashing.

I had and remove the settings, but no by restore. 

 

I'll try. 

[DisguisedMonkey]

14 hours ago, Half Life said:

Not yet. 

No problem was just wondering if you had taken one out.

14 hours ago, Half Life said:

 

Haha it was on discount, same price that 600w. 

I thought you had just gone extremely overkill but if it was the same price why not.

14 hours ago, Half Life said:

I had and remove the settings, but no by restore. 

 

I'll try. 

Did this fix anything?

[Half Life]

14 hours ago, DisguisedMonkey said:

No problem was just wondering if you had taken one out.

I thought you had just gone extremely overkill but if it was the same price why not.

Did this fix anything?

Well, I ran Prime95 on memory test and the system crash 27 min after, I can´t see the mensagge error, but on event viewer the error it's 0x0000000a (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffff804116a2232). And this it another one 0x00000139 (0x0000000000000004, 0xffff81808433f4f0, 0xffff81808433f448, 0x0000000000000000). 

 

And the MEMORY.DMP file

 

 

 

memory.txt

[Half Life]

Another thing, after the last crash I hear a little buzzer when the OS runs up, and too when I do something with the mice.

[DisguisedMonkey]

6 hours ago, Half Life said:

Well, I ran Prime95 on memory test and the system crash 27 min after, I can´t see the mensagge error, but on event viewer the error it's 0x0000000a (0x0000000000000010, 0x0000000000000002, 0x0000000000000000, 0xfffff804116a2232). And this it another one 0x00000139 (0x0000000000000004, 0xffff81808433f4f0, 0xffff81808433f448, 0x0000000000000000). 

 

And the MEMORY.DMP file

 

 

 

memory.txt

IRQL_NOT_LESS_OR_EQUAL is usually caused by conflicting memory locations if I recall correctly.

 

If you go to System Information > Hardware Resources > Conflicts/Sharing you will be able to see a list of conflicting memory addresses.

 

Another solution would be if you have a system restore point or image you could revert to. If you do I would suggest reverting back to this.

 

If not, a complete OS reinstall would be ideal. Just make sure you backup anything important.

[DoctorNick]

Clear CMOS. Enable XMP in bios.

The buzzing sound could indicate that the PC is not grounded (ths not an issue unless your motherboard is making contact with the case) I would pull out the motherboard and check and reseat the board.

[Half Life]

4 hours ago, DisguisedMonkey said:

IRQL_NOT_LESS_OR_EQUAL is usually caused by conflicting memory locations if I recall correctly.

 

If you go to System Information > Hardware Resources > Conflicts/Sharing you will be able to see a list of conflicting memory addresses.

 

Another solution would be if you have a system restore point or image you could revert to. If you do I would suggest reverting back to this.

 

If not, a complete OS reinstall would be ideal. Just make sure you backup anything important.

Actually, for the moment only have one ram stick on slot A1, and last night I change it to B1 and ran P95 on memory blend arround 4+ hours and no problems. Today I'll run P95 for more time and at the night I'll play to check. I hope it's just that if you use only one stick that you need to place in slot B1, because the manual only indicated the slots than you must use if you have two or four sticks.

 

4 hours ago, DoctorNick said:

Clear CMOS. Enable XMP in bios.

The buzzing sound could indicate that the PC is not grounded (ths not an issue unless your motherboard is making contact with the case) I would pull out the motherboard and check and reseat the board.

I change the speakers for a headset and the buzzing gone, the buzzing only hear when I use my USB speakers, I'll clean the CMOS and at the afternoon post the feedback. 

 

[Half Life]

Hi guys

Well, today I ran P95 10+ hours with the memory stick on B1 and no problem. But Gigabyte told me if I use one stick must be on A2, I did it but the system crashes again with this error: 0x0000003b (0x00000000c0000005, 0xffff83cc8194a2e2, 0xfffffb03ca726ce0, 0x0000000000000000). 

 

Do you think than the slots A maybe are faulty?

 

PD. The buzzing gone after clear CMOS.