BSOD Issues

Quote Monsterkiller

Thanks(0)

Quote

Topic: BSOD Issues
Posted: 21 Feb 2020 at 4:38am

Hello,

is there a solution for your problem? Got the same issues.

Regards

Rodney5

Newbie

Joined: 24 Sep 2019
Status: Offline
Points: 1

Post Options

Quote Rodney5

Thanks(0)

Quote

Posted: 24 Sep 2019 at 5:16pm

BSoDs can be caused by poorly written device drivers or malfunctioning hardware, such as faulty memory, power supply issues, overheating of components, or hardware running beyond its specification limits. In the Windows 9x era, incompatible DLLs or bugs in the operating system kernel could also cause BSoDs.

Valentine

Newbie

Joined: 29 May 2019
Status: Offline
Points: 6

Post Options

Thanks(0)

Quote

Posted: 03 Jun 2019 at 11:55am

It seems I was unable to get previous BSOD logs but I could grab this. I don't recall this BSOD during this time it must have happened after I started my computer and left.

This is the System/Application Logs, I personally think I didn't find anything out of the ordinary but I've posted them here just to be sure.

Valentine

Newbie

Joined: 29 May 2019
Status: Offline
Points: 6

Post Options

Thanks(0)

Quote

Posted: 03 Jun 2019 at 11:40am

Xaltar wrote:

The debug code that is displayed last and remains on the display is the one that indicates where the problem lies. If the codes all clear and the system then boots then there is not problem, if a code sticks and the system halts, that is when you have a problem and the code will give you an idea as to where.

Make sure your RAM is installed in slots A2 and B2 and that it is properly seated. Code 55 typically means the RAM was not detected. Before you go to all the trouble of getting different RAM, make sure it isn't something simple like the RAM not being fully inserted.

The DEBUG code only happens after a blue screen. Sometimes I'm able to boot perfectly fine and stay fine for a day or two. My RAM is within A2 and B2 and is properly seated, I've checked multiple times by taking it out and putting it in firmly. The 7F debug code is the most common one that I get, only the 55 will appear once in a while after failing to boot multiple times.

Event4101 wrote:

I noticed you used the word "lately" which seems to hint that everything had been working fine until just recently, when the BSOD started to appear.

Just about all BSODs will provide a stop code along with a set of four, eight character, hexadecimal codes that can provide additional insight into what went wrong. You might want to take notice of those codes and then refer to this web page for how to interpret that information for additional clues to what went wrong.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management

Searching the Windows "System" or "Application" event logs for the time just before the BSOD appeared might also provide you with some clues to the problem. You can also use a utility program like BlueScreenView to help analyze the Windows crash dump file that is often written to the hard drive when a BSOD occurs.

http://www.nirsoft.net/utils/blue_screen_view.html

You didn't mention what version of Windows you are using, but be aware that Windows 10 has a habit of installing new hardware drivers as part of the automatic patch/update process. New hardware drivers can be buggy, or encounter unforeseen compatibility issues, which often result in memory corruption or memory violation errors, that then lead to the surprise BSOD. You may want to review the Windows Update installation log to see if any updated drivers were recently installed without your direct knowledge.

Running a memory test like memtest86, or the built-in Windows memory diagnostic tool, is also a decent way to tell if there is a memory related hardware problems, versus a potential driver problem. It does seem like you ran a memory test that returned no errors, once again making me suspicious that your problem may not be related to a failing component.

It appears you are using a Corsair 8GBx2 dual channel memory kit. Something you might want to try would be to run on a single stick of memory to see if the problem disappears. Try one memory stick and then the other, and maybe try different memory slots. See if the problem follows a specific memory stick or is related to a specific memory slot. It is also possible for hardware to develop problems as components heat-up. So notice if things tend to crash after the computer has been powered-on for a while, or maybe during some hard use, such a gaming.

Another troubleshooting technique would be to remove all add-on components and run the computer in the most basic, stripped-down, bios defaults, configuration. That could help to isolate the problem to an external USB device, a third-party graphics card, an add-on SATA controller, a changed bios setting, etc, etc, etc.

Anyway, that is my two cents in 500 words or less. :)

I am using Windows 10 Education, I have reinstalled windows three times and installed drivers manually via the ASRock APP shop. There is no hexadecimal stop code I can see, since it just says this - https://imgur.com/a/9HpEiEz

I will be sure to use the blue screen view and view the system/application event logs to see if I can find anything before the bsod.

Should I run another memtest86?

I've tried multiple times with single stick both different ones and in different slots. The BSODs usually happen when I'm not playing video games but browsing something on chrome or chatting in discord. The latest one was on windows boot.

BIOS defaults seem to cause most of the BSODing, then after I changed to an XMP profile it became less likely to BSOD and I was finally able to boot into windows.

I've decided to purchase the F4-3200C16D-16GTZR (since it is on the QVL list) and refund the CMR16GX4M2D3000C16 in place to see if it is the RAM issue. hopefully, it was... If it isn't then it's most likely the Motherboard or CPU because the 1080ti was used in my previous build perfectly fine.

I really appreciate the time being taken to help me guys, thank you!

Event4101

Newbie

Joined: 23 Jan 2018
Status: Offline
Points: 27

Post Options

Quote Event4101

Thanks(0)

Quote

Posted: 03 Jun 2019 at 5:50am

I noticed you used the word "lately" which seems to hint that everything had been working fine until just recently, when the BSOD started to appear.

Just about all BSODs will provide a stop code along with a set of four, eight character, hexadecimal codes that can provide additional insight into what went wrong. You might want to take notice of those codes and then refer to this web page for how to interpret that information for additional clues to what went wrong.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management

Searching the Windows "System" or "Application" event logs for the time just before the BSOD appeared might also provide you with some clues to the problem. You can also use a utility program like BlueScreenView to help analyze the Windows crash dump file that is often written to the hard drive when a BSOD occurs.

http://www.nirsoft.net/utils/blue_screen_view.html

You didn't mention what version of Windows you are using, but be aware that Windows 10 has a habit of installing new hardware drivers as part of the automatic patch/update process. New hardware drivers can be buggy, or encounter unforeseen compatibility issues, which often result in memory corruption or memory violation errors, that then lead to the surprise BSOD. You may want to review the Windows Update installation log to see if any updated drivers were recently installed without your direct knowledge.

Running a memory test like memtest86, or the built-in Windows memory diagnostic tool, is also a decent way to tell if there is a memory related hardware problems, versus a potential driver problem. It does seem like you ran a memory test that returned no errors, once again making me suspicious that your problem may not be related to a failing component.

It appears you are using a Corsair 8GBx2 dual channel memory kit. Something you might want to try would be to run on a single stick of memory to see if the problem disappears. Try one memory stick and then the other, and maybe try different memory slots. See if the problem follows a specific memory stick or is related to a specific memory slot. It is also possible for hardware to develop problems as components heat-up. So notice if things tend to crash after the computer has been powered-on for a while, or maybe during some hard use, such a gaming.

Another troubleshooting technique would be to remove all add-on components and run the computer in the most basic, stripped-down, bios defaults, configuration. That could help to isolate the problem to an external USB device, a third-party graphics card, an add-on SATA controller, a changed bios setting, etc, etc, etc.

Anyway, that is my two cents in 500 words or less. :)

Xaltar

Moderator Group

Joined: 16 May 2015
Location: Europe
Status: Online
Points: 26903

Post Options

Quote Xaltar

Thanks(0)

Quote

Posted: 03 Jun 2019 at 5:44am

The debug code that is displayed last and remains on the display is the one that indicates where the problem lies. If the codes all clear and the system then boots then there is not problem, if a code sticks and the system halts, that is when you have a problem and the code will give you an idea as to where.

Make sure your RAM is installed in slots A2 and B2 and that it is properly seated. Code 55 typically means the RAM was not detected. Before you go to all the trouble of getting different RAM, make sure it isn't something simple like the RAM not being fully inserted.

Valentine

Newbie

Joined: 29 May 2019
Status: Offline
Points: 6

Post Options

Thanks(0)

Quote

Posted: 03 Jun 2019 at 12:28am

badbri wrote:

That could be the reason. What does the BIOS say when you load the SPD ?
At 2666 (not overclocked for any 300 series motherboard) good ram will be at 15-15-15-35 1.2v @ 2666Mhz.
I suggest G.SKILL ram, F4-3000C15D-16GTZ would be a good choice if you want 3000Mhz or if you do not want to overclock above 2666 then RipJaws F4-2666C15D-16GVR. Both are designed for low CAS at rated speed and are on the QVL list.

Thanks for the reply, I really appreciate the help. Is the "F4-3000C16D-16GTZR" fine to buy? Since I personally want RGB but it doesn't show up on the QVL list cause of the "R" at the end.

The BSOD error I get is "Stop code:MEMORY_MANAGEMENT" So I assumed it was RAM related but when I did a 14 hour RAM test it came up with 8 passes and thought it could be motherboard related since someone had a similar issue and changed the board to fix it. But I'm not sure cause sometimes my motherboard boots with code 7F, A2, AND 55 sometimes. Which seem to be hardware related to the RAM.

badbri

Groupie

Joined: 20 Feb 2018
Location: USA
Status: Offline
Points: 415

Post Options

Quote badbri

Thanks(0)

Quote

Posted: 30 May 2019 at 10:27am

That could be the reason. What does the BIOS say when you load the SPD ?
At 2666 (not overclocked for any 300 series motherboard) good ram will be at 15-15-15-35 1.2v @ 2666Mhz.
I suggest G.SKILL ram, F4-3000C15D-16GTZ would be a good choice if you want 3000Mhz or if you do not want to overclock above 2666 then RipJaws F4-2666C15D-16GVR. Both are designed for low CAS at rated speed and are on the QVL list.

https://www.passmark.com/baselines/V9/display.php?id=99573335296

Valentine

Newbie

Joined: 29 May 2019
Status: Offline
Points: 6

Post Options