[SOLVED] Getting Random BSOD in new build and I cant figure out the reason

[farazk86]

So not exactly a new build, but a build of old parts lying around. I had the following components lying around and decided to build a system from it:

AMD A4-6320
Gigabyte GA-F2A78M-DS2
4GB DDR3 RAM
500GB HDD
300W PSU
Cheap case

So I connected all of the above together and the only hiccup in all this was the PSU and motherboard compatibility. The PSU has a 4pin CPU power pin whereas the motherboard has a 8 pin connector.

I searched these forums for this and the general answers were to go ahead with the build as for around 100W CPU's the 8pin is recommended. My CPU is 65W so I figured it should be alright. Went ahead with the build and it started up without any problems.

Windows installed just fine as well and all drivers and software worked. But I would randomly get BSOD with a different error code every time, first was "IRQL less or something.." and then it was "Page fault in non paged area" etc.

I got a BSOD while doing a windows update.

for the page fault in non paged area I followed this page: https://www.tomshardware.com/uk/news/how-to-fix-page-fault-error-windows-10,36234.html and the chkdsk scan is stuck on 10% for the past hour.

I know for a fact that the HDD and the RAM and PSU are working, as these are from my previous build. I also ran a memory diagnostic scan to ensure RAM was fine and it came back with no errors.

So as of now, I cannot figure out the reason for the BSOD's and my only guess would be the 4pin 8pin problem between the CPU and PSU.

Would this be the reason? I'm happy to buy a molex to 4 pin adapter for this (but how can it struggle with a 65W CPU?), or can the reason be a faulty motherboard?

I also ensured BIOS is updated to latest version of F6e.

Any suggestions on how to pin point the exact problem?

Thank you

 

[onespeedbiker]

The chkdisk stalling can mean chkdisk is a lot of corruption which may take hours to repair. "If you run CHKDSK /r and get stuck on Windows 10, probably there are plenty of data need to be recovered and lots of bad sectors needing repair. Therefore, it is normal that several hours even a day is required. Let it run overnight if you feel it is repairing something."
https://www.diskpart.com/windows-10/chkdsk-windows-10-stuck-3889.html. You may want to run chkdisk without a parameter which will list the issues but not try to repair the. You might also attach the hdd to another computer to run chkdisk to see if its the hdd or PC that is the problem.

In the long run clean install may be the only answer https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/ What PSU are you using?

 

[farazk86]

The chkdisk stalling can mean chkdisk is a lot of corruption which may take hours to repair. "If you run CHKDSK /r and get stuck on Windows 10, probably there are plenty of data need to be recovered and lots of bad sectors needing repair. Therefore, it is normal that several hours even a day is required. Let it run overnight if you feel it is repairing something."
https://www.diskpart.com/windows-10/chkdsk-windows-10-stuck-3889.html. You may want to run chkdisk without a parameter which will list the issues but not try to repair the. You might also attach the hdd to another computer to run chkdisk to see if its the hdd or PC that is the problem.

In the long run clean install may be the only answer https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/ What PSU are you using?

Hi, the chkdsk /r /f has been running for about 4 hours now and its still at 10%. I cant even exit as if I reset the system, the chkdsk starts again. So I have no other option other than to wait.

And this HDD was in active use before this, I had it full of data in another system of mine and formatted it for this system, deleted partition at Windows installation and let Windows create the partitions for me. Dont know why it might be the HDD having bad sectors?

This is a clean install, installed windows just this morning on a freshly partitioned HDD.

My PSU is a HiPro 300W. Model HP-D3057F3P

 

[farazk86]

The chkdisk stalling can mean chkdisk is a lot of corruption which may take hours to repair. "If you run CHKDSK /r and get stuck on Windows 10, probably there are plenty of data need to be recovered and lots of bad sectors needing repair. Therefore, it is normal that several hours even a day is required. Let it run overnight if you feel it is repairing something."
https://www.diskpart.com/windows-10/chkdsk-windows-10-stuck-3889.html. You may want to run chkdisk without a parameter which will list the issues but not try to repair the. You might also attach the hdd to another computer to run chkdisk to see if its the hdd or PC that is the problem.

In the long run clean install may be the only answer https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/ What PSU are you using?

Hi, just to post an update.. chkdsk just finished and it said it could not complete successfully and produced the following log file:

Startup Repair diagnosis and repair log
---------------------------
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = D:\Windows
AutoChk Run = 1
Number of root causes = 1

Test Performed: 
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed: 
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 125 ms

Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 1188 ms

Test Performed: 
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed: 
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 78 ms

Test Performed: 
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 657 ms

Test Performed: 
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed: 
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Root cause found: 
---------------------------
Boot critical file d:\boot\resources\custom\bootres.dll is corrupt.

Repair action: File repair
Result: Failed. Error code =  0x2
Time taken = 3437 ms

---------------------------
---------------------------

 

[onespeedbiker]

Here is your problem.
Boot critical file d:\boot\resources\custom\bootres.dll is corrupt IOW somewhere in your install something went wrong.

This link has a number of fixes to repair bootres.dll (often this results in you not being able to boot)
https://answers.microsoft.com/en-us...to-start/bcf8503c-1b39-4827-9734-a64fef725d0f

Again, while you properly did a clean install, something went wrong that was probably a one time incident, so hopefully what ever the issue it won't be repeated with another clean install.

 

[Colif]

perhaps make sure you have the last BIOS as it might help as well.

generally, a clean install is fastest way to fix bootres.dll errors... I have found.

 

[farazk86]

Thanks for the replies. So, as suggested I did a fresh install. Deleted current partition and let Windows create
the necessary new partitions at install time.

And when Windows was installed, as I plugged in my Wifi dongle in USB I got another BSOD, this time with the stop code: SYSTEM_SERVICE_EXCEPTION

What may be causing all this?

 

[Colif]

Is wifi your only internet?

Windows needs new drivers and updates after the install so its possible the BSOD caused by stock drivers. If you were plugging dongle in to update PC, can you use ethernet instead? Once drivers updated the BSOD might be fixed?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

 

[farazk86]

Is wifi your only internet?

Windows needs new drivers and updates after the install so its possible the BSOD caused by stock drivers. If you were plugging dongle in to update PC, can you use ethernet instead? Once drivers updated the BSOD might be fixed?

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

Thanks, I did as you suggested and I eventually got another BSOD.
The minidump folder had 2 dump files, so I uploaded both:

https://filebin.net/tz76ue50pug7d3ny

Thanks for helping out

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://faerielongearedowl.htmlpasta.com/

File information:	022720-24406-01.dmp (Feb 26 2020 - 18:44:46)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: SearchUI.exe)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 04 Sec(s)

File information:	022620-21375-01.dmp (Feb 26 2020 - 18:43:16)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	ntkrnlmp.exe (Process: svchost.exe)
Uptime:	0 Day(s), 1 Hour(s), 10 Min(s), and 41 Sec(s)

Comment: The overclocking driver "AODDriver2.sys" was found on your system. (AMD Overdrive)

Possible Motherboard page: https://www.gigabyte.com/Motherboard/GA-F2A78M-DS2-rev-30/support#support-dl
I'm not positive that this is the correct revision of your F2A78M-DS2 motherboard, but it matches up with the BIOS versions listed on the page. It appears you have the latest BIOS already installed.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

results for error 1 are very strange

fffffc06954e62a8 fffff80312ae95dd : 000000000000001e ffffffffc0000005 fffff80312b370e6 0000000000000000 : nt!KeBugCheckEx
fffffc06954e62b0 fffff80312bd4942 : fefefefefefefefe fefefefefefefefe fefefefefefefefe fefefefefefefefe : nt!KiDispatchException+0x58d
fffffc06954e6960 fffff80312bd109c : fefefefefefefefe fefefefefefefefe fefefefefefefefe fefefefefefefefe : nt!KiExceptionDispatch+0xc2
fffffc06954e6b40 fffff80312b370e6 : fefefefefefefefe fefefefefefefefe fefefefefefefefe fefefefefefefefe : nt!KiGeneralProtectionFault+0x2dc
fffffc06954e6cd0 fefefefefefefefe : fefefefefefefefe fefefefefefefefe fefefefefefefefe fefefefefefefefe : nt!MiRaisedIrqlFault+0x5e
fffffc06954e6cd8 fefefefefefefefe : fefefefefefefefe fefefefefefefefe fefefefefefefefe fefefefefefefefe : 0xfefefefefefefefe fffffc06954e6ce0 fefefefefefefefe : fefefefefefefefe fefefefefefefefe fefefefefefefefe 0000000000000000 : 0xfefefefefefefefe
fffffc06954e6ce8 fefefefefefefefe : fefefefefefefefe fefefefefefefefe 0000000000000000 fffff80312a84f86 : 0xfefefefefefefefe fffffc06954e6cf0 fefefefefefefefe : fefefefefefefefe 0000000000000000 fffff80312a84f86 0000000000000010 : 0xfefefefefefefefe
fffffc06954e6cf8 fefefefefefefefe : 0000000000000000 fffff80312a84f86 0000000000000010 fefefefefefefefe : 0xfefefefefefefefe fffffc06954e6d00 0000000000000000 : fffff80312a84f86 0000000000000010 fefefefefefefefe fffffc06954e6e10 : 0xfefefefefefefefe

what is fefefefe as system sure likes to say it.

this is what 2nd shows

ffff8407c490e0d8 fffff803e2c7f2b9 : 0000000000000050 fffffcafc0466828 0000000000000000 ffff8407c490e390 : nt!KeBugCheckEx
ffff8407c490e0e0 fffff803e2c76d88 : ffff880028001e00 0000000000000000 ffff800000000000 ffffc5e2f178bc58 : nt!MiSystemFault+0xcf9
ffff8407c490e220 fffff803e2dc33da : ffff9f0014216001 000000000000417e 0000000000008000 fffffcafc0466000 : nt!MmAccessFault+0x1f8
ffff8407c490e390 fffff803e2c4f4f7 : fffffcafc0466000 fffff804f611e100 0000000000080100 0000000000004000 : nt!KiPageFault+0x31a
ffff8407c490e520 fffff803e30debf7 : ffffcb8bf1781b40 fffff80300007fff ffffcb8bf1781700 ffffcb8beffff8e8 : nt!RtlFindClearBits+0xb7
ffff8407c490e580 fffff803e30dfe4d : ffff8407c490e700 ffffcb8beffff580 0000000000010000 0000000000000000 : nt!MiFindEmptyAddressRange+0x117
ffff8407c490e600 fffff803e30df7fe : ffffcb8beeb35010 ffff8407c490e900 ffff8407c490ea38 ffff8407c490ea48 : nt!MiMapViewOfDataSection+0x40d
ffff8407c490e770 fffff803e30c3145 : ffff8407c490ea38 ffff8407c490e9e8 ffff88852f31c2e0 0000000000000001 : nt!MiMapViewOfSection+0x30e
ffff8407c490e8c0 fffff803e30c2b82 : 0000000000000000 ffff88852bc81c50 0000000000000000 0000000000010000 : nt!MmMapSecureViewOfSection+0x9d
ffff8407c490e980 fffff803e30a6a27 : 0000000000000000 0000000000000000 0000000000004000 0000000000000000 : nt!AlpcpCreateView+0xfe
ffff8407c490ea30 fffff803e30a6d40 : 0000000000000000 ffff8407c490eb80 0000000000000001 ffff8407c490eb80 : nt!AlpcpCreateSectionView+0x87
ffff8407c490ea80 fffff803e2dc6343 : ffffcb8bf1781700 0000000000000002 0000000000000000 0000000000000000 : nt!NtAlpcCreateSectionView+0x130
ffff8407c490eb00 00007ffaf392ae24 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
000000ae2cdfe718 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`f392ae24

which is far more normal...

from what i can tell fefefefe is caused by heap corruption. It could also be a lack of drivers since you only have 5 installed. One being over drive...
Feb 11 2014 AODDriver2.sys !!! AMD Overdrive driver http://support.amd.com/
May 28 2015 netr28ux.sys Ralink Wireless Adapter driver https://www.mediatek.com/
Nov 04 2015 atikmdag.sys ATI Radeon Kernel Mode driver
Nov 04 2015 atikmpag.sys ATI video card driver
Oct 05 2016 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/

have you gone to the website of your motherboard and installed any of the chipset drivers? Or sound?
https://www.gigabyte.com/Motherboard/GA-F2A78M-DS2-rev-30/support#support-dl-driver-chipset (assuming Gardenman guessed model right)

 

[farazk86]

Thanks for the replies guys. I dont think Ive ever done any overclocking and I dont know why the overclocking driver is on there? As its just windows default drivers, the ones that come with Windows update.

I have made sure to use the latest drivers by clicking update drivers from device manager. But I have not used the motherboard website.

One thing I noticed on the website, is that the BIOS version I am using F6e is listed as a BETA BIOS there. Could this be the reason? its not a stable BIOS?

Regarding drivers, I thought it was best to rely on Windows to keep lates drivers as motherboard manufacturers stop updating their drivers for old equipment.

So what can I do to fix this?

Thanks again

 

[Colif]

I think your BIOS is fine. What likely happened was it was released around the time gigabyte had stopped supporting motherboard and it never came out of beta. I have the same thing on my board, Asus released BIOS for it after their support period had expired and the BIOS are beta there too. from 4 years ago.

Windows update only looks at the WIndows update catalog and if the makers of drivers don't give them newer versions, it can't see anything newer. ITs often a good idea to check there after install. although on a 5 year old PC there might not be much missing. Chipset drivers will help windows see what board has and might avoid the 1st weird error.

 

[farazk86]

I think your BIOS is fine. What likely happened was it was released around the time gigabyte had stopped supporting motherboard and it never came out of beta. I have the same thing on my board, Asus released BIOS for it after their support period had expired and the BIOS are beta there too. from 4 years ago.

Windows update only looks at the WIndows update catalog and if the makers of drivers don't give them newer versions, it can't see anything newer. ITs often a good idea to check there after install. although on a 5 year old PC there might not be much missing. Chipset drivers will help windows see what board has and might avoid the 1st weird error.

Thanks, I'll do that. I noticed that there are 3 versions of the same motherboard, I have version 3.0 BIOS, but I cant tell the difference between the three, even the compare page shows the same specs: https://www.gigabyte.com/Comparison/Result/2?pids=5335,4876

Is it possible that I installed the bios of the wrong revision of the board?

 

[farazk86]

Here is the CPU-z information, is that helps?

 

[Colif]

have you looked at motherboard itself? they often stencil the name of the motherboard on them and it may show which revision you have.

its strange to me they are virtually identical. all except bios versions. Main difference in overview is that the description of the 3.2 mentions - GIGABYTE Ultra Durable™ motherboards use high quality Nippon Chemicon ARE series audio capacitors. These professional audio capacitors deliver the highest quality sound resolution and sound expansion to create the most realistic sound effects for user experience.

That appears to be main difference between both. Better audio capacitors

how long have you had PC? that might tell you which you have as the 3.2 didn't exist before January 2015

you could run speccy, looking at it here it shows revision number - https://www.ccleaner.com/speccy/download - although it may not show much more than cpuZ, worth a try.

Its likely that if you had flashed wrong bios to wrong board, BSOD would be the least of your problems. It is likely more destructive. The boards seem identical to me.

 

[farazk86]

have you looked at motherboard itself? they often stencil the name of the motherboard on them and it may show which revision you have.

its strange to me they are virtually identical. all except bios versions. Main difference in overview is that the description of the 3.2 mentions - GIGABYTE Ultra Durable™ motherboards use high quality Nippon Chemicon ARE series audio capacitors. These professional audio capacitors deliver the highest quality sound resolution and sound expansion to create the most realistic sound effects for user experience.

That appears to be main difference between both. Better audio capacitors

how long have you had PC? that might tell you which you have as the 3.2 didn't exist before January 2015

you could run speccy, looking at it here it shows revision number - https://www.ccleaner.com/speccy/download - although it may not show much more than cpuZ, worth a try.

Its likely that if you had flashed wrong bios to wrong board, BSOD would be the least of your problems. It is likely more destructive. The boards seem identical to me.

Hi,

So after contacting Gigabyte, they told me where the revision number on the motherboard may be written and my board version is indeed rev 3.0, so the bios is correct.

But I installed the chipset driver and the BSOD's did not happen again for a few hours.

Happy with the progress, I decided to stress test my PC just to be sure, so I ran HeavyLoad for a bit and after about 5 minutes in the PC froze with some random horizontal lines on screen. and after that the computer kept freezing again.

I also got a couple more BSOD's, one just now and one a couple days earlier, I have attached both of them below:

Does this indicate the reason for my problems?

https://filebin.net/hrf34y1o1yx39pwj

Many thanks for helping me out so far

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://untimberedbedlingtonterrier.htmlpasta.com/

File information:	030420-26312-01.dmp (Mar 3 2020 - 18:42:42)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	ntkrnlmp.exe (Process: Speccy64.exe)
Uptime:	0 Day(s), 0 Hour(s), 29 Min(s), and 40 Sec(s)

File information:	030120-32421-01.dmp (Mar 1 2020 - 13:40:07)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: MicrosoftEdge.)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 07 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[clementttttttt]

Did you run sfc /scannow?

 

[farazk86]

Did you run sfc /scannow?

Hi, I did run sfc /scannow before and uploaded the report above, then it was determined that I had a corrupted windows installation. Which I formatted and reinstalled

 

[Colif]

The wifi card is running WIn 8 drivers. Its a 802.11n speed adapter card, given AC replaced it 5 years ago and I think there is faster now, it could be cause of BSOD. Have you tried without the wifi card?

you only have 6 drivers running and the 2 dumps are saying cause is a driver, so it has to be one of them
Feb 11 2014 AODDriver2.sys !!! AMD Overdrive driver http://support.amd.com/
May 07 2015 usbfilter.sys AMD USB Filter driver
May 28 2015 netr28ux.sys Ralink Wireless Adapter driver https://www.mediatek.com/
Nov 04 2015 atikmdag.sys ATI Radeon Kernel Mode driver
Nov 04 2015 atikmpag.sys ATI video card driver
Apr 24 2017 cpuz143_x64.sys CPUID driver
May 24 2019 rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/

it could be the AMD drivers but some of those likely actually came with windows so its hard to say, and you did update chipset drivers already (?)

I was going to ask about Radeon drivers but I see they for onboard - https://www.cnet.com/products/amd-a4-6320-3-8-ghz-processor-ad6320okhlbox/