Solved New build experiencing BSOD with multiple drivers listed as cause

[Zeddakis]

I built a new PC this weekend and I have been getting frequent BSOD with my new build. I have filled in my system specs under my profile. Before I built the computer I went to each manufacturer’s website and made sure I had their most current drivers and Bios and I have done all Windows Updates. I have done no overclocking on the PC.

Most of the original BSOD I was getting on Saturday and Sunday listed the nvlddmkm.sys as the driver causing it. Based on that I did a clean install of the Nvidia GeForce driver, but this time used the 331.40 beta driver to see if that would fix it. Well I have not had a BSOD for that driver since, but I keep getting BSOD most of the time several times an hour. Though I did go almost 7 hours yesterday without one and then they started right back up with multiple crashes an hour. Most of the BSOD are happening during regular type activities like web browsing, watching online videos, and working in MS Office. I have not been able to game much, but it has never happened when gaming.

I have been watching my temps in hardware monitor all weekend just to make sure everything looked good. Below is what I am currently running and these are pretty consistent with what I have ran all weekend.

CPU Temps run between 31-42
HDD Temps run between 29-34
GPU Temps run between 29-34 for normal use and in the mid-50s when gaming
Sys Temps running in the mid to high 30s

I ran memtest86 and it passed.

Almost every time a different driver is listed as the cause when I look at the file in Blue Screen Viewer. Any help identifying the possible case would be greatly appreciated.

 

[koolkat77]

Welcome to the Forum.

Your dumps do come with a lot of different codes.

BugCheck 3B, {c0000005, fffff8000344058c, fffff880197fec10, 0} 
Probably caused by : win32k.sys ( win32k!DesktopAlloc+23 ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck D1, {0, 2, 0, fffff88001b5005f} 
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+4f ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 4E, {9a, 32e88f, 3, 0} 
Probably caused by : memory_corruption ( nt!MiBadRefCount+4f ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck A, {fffffa9a3e814040, 2, 0, fffff80003471b2e} 
Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+101ba ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 3B, {c0000005, fffff800034dfafe, fffff8800cdeabb0, 0} 
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 109, {a3a039d8a8e74b4f, b3b7465efb641ab5, fffff800033829fe, 1} 
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+3de ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 1E, {0, 0, 0, 0} 
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck D1, {0, 7, 0, fffff8800f54473b} 
Probably caused by : nvlddmkm.sys ( nvlddmkm+e773b ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
BugCheck 3B, {c000001d, fffff8800489f5ee, fffff8800f158dd0, 0} 
Probably caused by : hardware ( afd+495ee ) 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Let us get some drivers sorted first:

Drivers:-

NTIOLib_X64.sys Tue Nov 20 14:14:23 2012 (50AB3BDF)
MSI Afterburner driver (known BSOD issues with Windows) Also found to be a part of MSI Live Update 5
Driver Reference Table - NTIOLib_X64.sys

bflwfx64.sys Wed Feb 13 23:04:08 2013 (511BC788)
Bigfoot Networks Bandwidth Control Wireless NDIS Light Weight Filter driver
Driver Reference Table - bflwfx64.sys

Update these drivers to their latest driver version available. If not, uninstall them with revo:

Alpham264.sys Tue Mar 20 15:51:03 2007 (45FFAE87)
Ideazon ZBoard/Ideazon Fang MM USB HID driver
http://www.carrona.org/drivers/driver.php?id=Alpham264.sys

Alpham164.sys Mon Jul 23 13:57:03 2007 (46A45F4F)
Ideazon ZBoard/Ideazon ZBoard Fang MM USB HID
http://www.carrona.org/drivers/driver.php?id=Alpham164.sys

Please uninstall all MSI related software for testing purpose. Also remove Bigfoot Network software. It was directly blamed on one of your dump.

• Revo Uninstaller "Free"
  • Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software.
    • Link to download: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

• System File Checker
  • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    • Link to full tutorial: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
• Run Disk Check in Windows 7
  • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
    • Link to full tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

• Virus Check:
  • Make scans with these tools below:
    • TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
    • Online Virus Scanner Eset
• Application conflict:
  • Reduce the start-up items. This will help avoid software conflicts:
    • Remove Startup Programs in Windows 7
    • Clean Startup in Windows 7

Follow this-

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

nvlddmkm.sys        Fri Sep 27 11:45:06 2013 (52451B62) 
nvvad64v.sys        Tue Aug 20 17:29:10 2013 (52135306)

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results.

• Bitdefender is also contributing to your BSOD's. As a test I would recommend you uninstall it and use Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
  • Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
  • Help protect your PC with Microsoft Security Essentials
  • Malwarebytes Free

   Note

:info: Do not start the trial version of MalwareBytes

• Also take a look at: Good & Free System Security Combination

• Test and Diagnose RAM issues with MEMTEST86+
  • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
    • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Let us know the rsults.

BSOD BUGCHECK SUMMARY:

[FONT=Lucida Console]Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Wed Oct 16 20:34:51.695 2013 (UTC + 6:00) 
System Uptime: 0 days 0:35:57.476 
BugCheck 3B, {c0000005, fffff8000344058c, fffff880197fec10, 0} 
Probably caused by : win32k.sys ( win32k!DesktopAlloc+23 ) 
BUGCHECK_STR:  0x3B 
PROCESS_NAME:  explorer.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Wed Oct 16 19:58:03.121 2013 (UTC + 6:00) 
System Uptime: 0 days 1:24:20.902 
BugCheck D1, {0, 2, 0, fffff88001b5005f} 
Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+4f ) 
BUGCHECK_STR:  0xD1 
PROCESS_NAME:  System 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Wed Oct 16 18:32:51.216 2013 (UTC + 6:00) 
System Uptime: 0 days 0:41:44.013 
BugCheck 4E, {9a, 32e88f, 3, 0} 
Probably caused by : memory_corruption ( nt!MiBadRefCount+4f ) 
BUGCHECK_STR:  0x4E_9a 
PROCESS_NAME:  System 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Wed Oct 16 17:50:15.393 2013 (UTC + 6:00) 
System Uptime: 0 days 0:07:45.079 
BugCheck A, {fffffa9a3e814040, 2, 0, fffff80003471b2e} 
Probably caused by : tcpip.sys ( tcpip! ?? ::FNODOBFM::`string'+101ba ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  System 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Wed Oct 16 09:46:08.398 2013 (UTC + 6:00) 
System Uptime: 0 days 0:54:12.194 
BugCheck 3B, {c0000005, fffff800034dfafe, fffff8800cdeabb0, 0} 
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e ) 
BUGCHECK_STR:  0x3B 
PROCESS_NAME:  FastBootServic 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Wed Oct 16 05:26:59.392 2013 (UTC + 6:00) 
System Uptime: 0 days 1:09:43.173 
BugCheck 109, {a3a039d8a8e74b4f, b3b7465efb641ab5, fffff800033829fe, 1} 
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+3de ) 
BUGCHECK_STR:  0x109 
PROCESS_NAME:  System 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Wed Oct 16 04:16:52.740 2013 (UTC + 6:00) 
System Uptime: 0 days 0:07:15.537 
BugCheck 1E, {0, 0, 0, 0} 
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) 
BUGCHECK_STR:  0x1E 
PROCESS_NAME:  System 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Tue Oct 15 20:03:12.220 2013 (UTC + 6:00) 
System Uptime: 0 days 0:38:08.001 
BugCheck D1, {0, 7, 0, fffff8800f54473b} 
*** WARNING: Unable to verify timestamp for nvlddmkm.sys 
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys 
Probably caused by : nvlddmkm.sys ( nvlddmkm+e773b ) 
BUGCHECK_STR:  0xD1 
PROCESS_NAME:  System 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 
Debug session time: Tue Oct 15 19:24:40.217 2013 (UTC + 6:00) 
System Uptime: 0 days 0:18:49.013 
BugCheck 3B, {c000001d, fffff8800489f5ee, fffff8800f158dd0, 0} 
Probably caused by : hardware ( afd+495ee ) 
BUGCHECK_STR:  0x3B 
PROCESS_NAME:  KillerService. 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[Zeddakis]

Thanks for looking at my files and for the help.

I removed all the MSI software from my system as well as all the Bigfoot Killer network manager software and all drivers with the exception of the e22w7x64.sys driver which is my NIC driver.

I also uninstalled all the Ideazon software/drivers. In addition to that I uninstalled and unplugged my Logitech G13 gameboard and the Razer software for my mouse.

I removed all Nvidia software and drivers and did a clean install of the most current WHQL drivers and only installed the graphic driver, PhysX software, and the GeForce Experience software.

I removed a lot of the software that was loading on start-up to minimize the amount of programs loading then.

I ran a System File Checker scan and there were no issues.

I ran a Disk Check and there were no issues.

I uninstalled BitDefender and ran their separate uninstaller software to make sure I had everything removed. I then installed Microsoft Security Essentials and ran a full scan and everything was clean.

I ran Kaspersky’s Rootkit Removal Utility and it found nothing.

I ran MEMTEST86+ for 7 passes with no issues.

Then I starting playing some online videos and surfing the web to see what would happen and crashes started happening again. I have had 2 crashes this morning since completing all of the above the last few days. Attached are the files for those.

The only other thing I could try if it still looks to be network related is uninstall the NIC driver and disable the NIC in the BIOS and trying just surfing via my Wi-Fi for a while to see what happens.

Besides that any suggestions or ideas of what is still causing the BSODs?

 

[koolkat77]

Any system service, or a device driver, or the graphics driver to the memory, and the tests are needed to determine the actual cause.

• Enable Driver Verifier to see if it catches any misbehaving driver::tip: Driver Verifier - Enable and Disable
  1. :info: Using Driver Verifier to identify issues with Drivers

 

[Zeddakis]

OK, I ran the Driver Verifier. You will see two new dump files since my last post. Both happened yesterday. The one at 2:58:32 PM is a BSOD that happened while I was setting up the Driver Verifier to run. The one at 11:35:08 PM happened over night while I was letting the computer run while streaming videos to see if it would crash. There was one other time in between while I was running Driver Verifier that the computer froze up, but it did not cause a BSOD, so no dump file was generated. I just had to hit restart and force the computer to reboot.

Thanks!

 

[Arc]

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.

Let us know the results.
_________________________________________________________

BugCheck A, {1, 2, 1, fffff80003541e6f}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
-----------------------------------------------------------
BugCheck 50, {fffff88009d98760, 1, fffff88001d6f332, 1}


Could not read faulting driver name
Probably caused by : afd.sys ( afd!AfdFastIoDeviceControl+1322 )

Followup: MachineOwner
---------

 

[Zeddakis]

Stress test the Graphics Card using Furmark.

Ran stress test for 20 minutes with no issues. The max temp on GPU 1 was 86°C and on GPU 2 it was 81°C.

Benchmark Results:
SCORE:1351 points (22 FPS, 60000 ms)
Max GPU Temp: 86°C
Resolution: 5760x1080 (W) - AA:0 samples
FPS: min:22, max:24, avg:22 - OPTIONS: XB FX DynBkg

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.

eXtreme Power Supply Calculator gave me the following:

Minimum PSU Wattage: 770 Watts
Recommended Wattage: 820 Watts

My system has a CORSAIR HX850 850W 80 PLUS GOLD Certified.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage.

I have been running my PC for several hours this morning. Below is a screenshot from Hardware Monitor.

Upload a screenshot of the summery tab of Speccy.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.

I have not done any overclocking on the system and BIOS is set to default.

Thanks!

 

[Arc]

All are fine.

Your GPU does not support the earlier drivers, and hence you need to wait for another driver update from nvidia.

Otherwise, apparently there is no issue that is visible at this point (If it is not a corrupt board/BIOS).

 

[Zeddakis]

OK, the board has dual BIOS, so I can switch to the other one and see how that goes.

Thanks!

 

[Zeddakis]

OK, I switched to the 2nd BIOS about 18 hours ago and just left it at the version it shipped with and so far no BSOD. I steamed over 7 hours of video yesterday, played some games, and let it run all night with a few programs running. So far so good! I am going to let it run today while I am at work, but hopefully it is working fine now and the issue was with the BIOS. Thanks again guys for all your help.

 

[Arc]

Observe the situation over a bit of more time (at least over an week). If it goes stable for that time, it will be good.

And report us back, after one week or occurrence of the next BSOD, whichever is earlier

 

[Zeddakis]

I'll let you know in a week how it is going unless I have a BSOD before then, but it ran all day today while I was a work with no issues.

 

[Arc]

Ah! That's a sort of good news

 

[Zeddakis]

OK, it has been over a week now and no BSOD, since I switched over to the other BIOS. Looks like either there was an issue with the one version of the BIOS or something happened to it when I updated it to the newest version. I am going to just keep using the second BIOS and the version it shipped with for now.

Thanks to everyone on here for your help.

 

[Arc]

You are welcome mate

Let us know for any further issue.