Windows 10: Different BSoDs on New PC Build

I built a PC specifically to play No Man's Sky, and it seemed to be working fine. There was a couple of BSoDs before, but I updated all the drivers, and it seemed to be ok. I turned it on today and I'm getting all kinds of BSoDs.

DRIVER_OVERRAN_STACK_BUFFER
ATTEMPTED_TO_WRITE_READONLY_MEMORY
CUSTOM_ERROR
IRQL_NOT_LESS_THAN_EQUAL
SYSTEM_THREAD_NOT_HANDLED_M
KMODE_EXCEPTION_NOT_HANDLED
and another one I can't recall

Sometimes it would happen shortly after rebooting, without me doing anything, other times it would be while browsing the web, attempting to launch a program or play a game. The timing isn't consistent either. Sometimes it'll crash as soon as I launch a game, other times I can play for an hour before it crashes.

I've tried updating all of my drivers, running virus and malware scans, cleanup and defragging, I found some corrupted .Net files, but the .Net repair tool did nothing, and removing .Net with the cleanup tool and reinstalling it didn't help at all. I'm really hoping it's something simple, and that I'll be able to play without issues, but I feel like there's something seriously wrong, and I don't know what to do. Google is very little help other than leading me here. Hopefully I've uploaded what you guys need to help. Thanks.

Attachment 95380

:)

 

Repeated BSODs on new PC Build...

These are called BCC124 and are related to hardware. Read how to diagnose and

hopefully to fix them in this wiki

BugCheck Code 124

 

Repeated BSODs on new PC Build...

Hello all,

I am still battling this problem with this PC build months later. I tried to run an automatic repair, but this did not seem to fix the problem. I found an article online with suggestions to repair a faulty windows installation. I used the Win install
disk to access the command prompt and used system file checker (sfc) command to try find and repair any errors in system files. That did not work.

Then I re-installed the OS (Win 7 64 Pro) by using system upgrade from the Install Windows prompts from the Win install disk. Still no success. After the re-install, the system ran for several (maybe 10) days with no problems, then back to daily (or so)
BSODs. The issue still seems to be centered around hal.dll.:

==================================================

Dump File : 050416-5335-01.dmp

Crash Time : 5/4/2016 6:59:30 PM

Bug Check String :

Bug Check Code : 0x00000124

Parameter 1 : 00000000`00000000

Parameter 2 : fffffa80`0d6ce028

Parameter 3 : 00000000`bf800000

Parameter 4 : 00000000`00200401

Caused By Driver : hal.dll

Caused By Address : hal.dll+12a3b

File Description : Hardware Abstraction Layer DLL

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)

Processor : x64

Crash Address : ntoskrnl.exe+70380

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\Windows\Minidump\050416-5335-01.dmp

Processors Count : 8

Major Version : 15

Minor Version : 7601

Dump File Size : 282,088

Dump File Time : 5/4/2016 7:00:46 PM

==================================================

I have checked all of the hardware, drivers, etc., and have not found any faults yet.

Any ideas would be appreciated.

Thanks,

-M

 

Hi Kittau,

Welcome to the 10forums *Smile

Please update the BIOS to the newest version from ASUS
M5A78L-M LX PLUS | Motherboards | ASUS Global







Diagnostics Test

System File Check
Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of SFC and post it.
Code: Event[2162]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2016-08-10T11:48:21.938 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Micah-PC Description: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.[/quote]

 

I've tried downloading the BIOS updates there before, but it's just a ROM file and I don't know how to use that. As soon as I upgraded to Windows 10, I went into the device manager and went down the list and manually attempted to update the driver for everything on the list. There was only a couple that needed an update. I don't know if the BIOS can be upgraded from there or not. Also, in the manual for my motherboard, it says to go into the BIOS menu and set an IRQ for my graphics card once I install it, but my GPU didn't say anything about that. Again, I've never worked with anything in the BIOS menu, so I have no idea what to do in there, or if it's even necessary. I'm worried I'll screw it up and make it worse.

I'll try the next step you have posted here and hopefully something good will happen. I apologize for my ignorance when it comes to this stuff. I've tried googling answers and I just get tons of different answers for the same problem, and most of what I'm finding pertains to Windows 7 anyway.

 

Put it on a USB, boot into the BIOS and follow part 2.1.2 from the user manual.

The IRQ assigment is simply to prevent possible conflicts when PCI cards use shared slots, if necessary, I do not think it is something to worry about *Smile
If you do worry about it, assign IRQ 18 to the graphics card and it should be fine.

 

So I ran the scan once, and it said it detected some corrupted files and fixed them successfully, but upon restarting the PC, I got another BSoD as it was loading Windows. (Where it loads before the screen comes up where you input your password.)

Attachment 95548

Also I went into BIOS menu after it rebooted again and it was running version 1501 of the BIOS. I don't know if that info will help at all. I didn't see anywhere in there to upgrade from that menu.

After running the scan a second time, it said there were corrupted files that couldn't be fixed. Hopefully this is the right log. I couldn't find %systemroot%\Logs\CBS, but I did find a text doc in Windows/Logs/CBS.

Attachment 95556

 

Lets first get Windows corruption gone & BIOS up to date *Smile

%systemroot%\Logs\CBS & [/COLOR] Windows/Logs/CBS are pretty much the same, when you enter %systemroot% in the addressbalk or in search you come in the Windows folder *Smile
%systemroot% is not a folder.

It looks like you have a problem with the Calibri font.
Please follow this post, download the tool and run it as administrator.
If you do NOT have any media, download it from my Onedrive and mount the ISO *Arrow Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Code: 2016-08-11 11:52:39, Info CSI 000054ec Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-calibri_31bf3856ad364e35_10.0.10586.0_none_772bc5a59a1bbfac\calibri.ttf do not match actual file [l:11]"calibri.ttf" : Found: {l:32 0F5tr0bRnJyr8/P/PqIZ6daBLcb5hvmhVMvWNNQyM/8=} Expected: {l:32 cCb11IKDRhZS7tFDFoJYk3G37mk2FzbZsI65uQ+kU4s=} 2016-08-11 11:52:39, Info CSI 000054ed [SR] Cannot repair member file [l:11]"calibri.ttf" of Microsoft-Windows-Font-TrueType-Calibri, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2016-08-11 11:52:39, Info CSI 000054ee@2016/8/11:18:52:39.742 Primitive installers committed for repair 2016-08-11 11:52:39, Info CSI 000054ef Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-calibri_31bf3856ad364e35_10.0.10586.0_none_772bc5a59a1bbfac\calibri.ttf do not match actual file [l:11]"calibri.ttf" : Found: {l:32 0F5tr0bRnJyr8/P/PqIZ6daBLcb5hvmhVMvWNNQyM/8=} Expected: {l:32 cCb11IKDRhZS7tFDFoJYk3G37mk2FzbZsI65uQ+kU4s=} 2016-08-11 11:52:39, Info CSI 000054f0 [SR] Cannot repair member file [l:11]"calibri.ttf" of Microsoft-Windows-Font-TrueType-Calibri, version 10.0.10586.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2016-08-11 11:52:39, Info CSI 000054f1 [SR] This component was referenced by [l:110]"Microsoft-OneCore-Fonts-UAPFonts-Package~31bf3856ad364e35~amd64~~10.0.10586.0.56951adcca9881af795c737cd0e80e3c" 2016-08-11 11:52:39, Info CSI 000054f2 Hashes for file member \??\C:\WINDOWS\fonts\calibri.ttf do not match actual file [l:11]"calibri.ttf" : Found: {l:32 0F5tr0bRnJyr8/P/PqIZ6daBLcb5hvmhVMvWNNQyM/8=} Expected: {l:32 cCb11IKDRhZS7tFDFoJYk3G37mk2FzbZsI65uQ+kU4s=} 2016-08-11 11:52:39, Info CSI 000054f3 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-font-truetype-calibri_31bf3856ad364e35_10.0.10586.0_none_772bc5a59a1bbfac\calibri.ttf do not match actual file [l:11]"calibri.ttf" : Found: {l:32 0F5tr0bRnJyr8/P/PqIZ6daBLcb5hvmhVMvWNNQyM/8=} Expected: {l:32 cCb11IKDRhZS7tFDFoJYk3G37mk2FzbZsI65uQ+kU4s=} 2016-08-11 11:52:39, Info CSI 000054f4 [SR] Could not reproject corrupted file [l:20 ml:21]"\??\C:\WINDOWS\fonts"\[l:11]"calibri.ttf"; source file in store is also corrupted 2016-08-11 11:52:39, Info CSI 000054f5@2016/8/11:18:52:39.836 Primitive installers committed for repair[/quote]

 

Bios update successful! Thanks for the help on that. Do I need to do the sfc scans again now?

 

Not yet, please first make sure that you follow my post #6 *Smile

 

Sorry, I really need to refresh the thread before I reply lol. I just extracted the file to C:/ and got another Stack Buffer BSoD. Waiting for it to reboot.

 

You could do the part of the Windows corruption fix possibly in safe mode *Smile

 

Step 2 says to right click Image Health and click unblock in properties, but I don't see a block/unblock option.

Also: http://www.microsoft.com/en-us/softw...load/techbench seems to be missing.

 

I added a download link for the media of my onedrive *Wink

If you don't see any box to vink for unblocking then you don't need to.

 

Ok I ran Image health, option 1 and it came up with no corruption or missing files or anything.