BSOD starting after a random amount of time

Roolek

Roolek

Well-known member
Joined
Dec 12, 2020
Posts
45
  • A brief description of your problem (but you can also include the steps you tried) BSOD started after PC in fine working condition after 7 months of building an entirely new setup, I've fresh installed Windows, had the GPU RMA'd and sent back as not faulty, having some success dropping down to 2 RAM sticks instead of 4, 2 seems to increase the interval between issues, but nothing fixed
  • System Manufacturer? Varying manufacturers of parts, ASUS Crosshair 8 wifi mobo, MSI 3080, Corsair dominator RAM
  • Laptop or Desktop? Desktop
  • Exact model number (if laptop, check label on bottom)
  • OS ? (Windows 10, 8.1, 8, 7, Vista) Windows 10
  • x86 (32bit) or x64 (64bit)? x64
  • (Only for Vista, Windows 7) Service pack?
  • What was original installed OS on system? Windows
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Retail
  • Age of system? (hardware) 7 Months except PSU which is new
  • Age of OS installation? Completed a fresh install 2 days ago from when this started
  • Have you re-installed the OS? Yes
  • CPU Ryzen 9 5900X
  • RAM (brand, EXACT model, what slots are you using?) Corsair Dominator Platinum RGB 32 GB (4 x 8 GB) DDR4 3600 MHz C18
  • Video Card MSI 3080
  • MotherBoard - (if NOT a laptop) ROG CROSSHAIR VIII HERO (WI-FI) (AM4)
  • Power Supply - brand & wattage (if laptop, skip this one) Corsair HX1000
  • Is driver verifier enabled or disabled? Enabled
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Used malwarebytes and got nothing back
  • Are you using proxy, vpn, ipfilters or similar software? No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
  • Are you currently under/overclocking? Are there overclocking software installed on your system? No
 
Last edited:
It seems all the crashes are Stop 0x124; the issue is very likely to be hardware related unfortunately. I suspect that RAM is the main culprit, but let's run MemTest86 for 8 passes (will require two runs) to check - Test RAM with PassMark MemTest86
 
As I know that will take a long time, I have swapped all the RAM out for some older, but tried and tested RAM from a previous build for now just to see, if it crashes again then I'll do memtest on the original ram
 
That will do and probably the better option to be honest. Please let us know how it goes.
 
Rich (BB code): 
10: kd> !pte ffffce81`65345200
                                           VA ffffce8165345200
PXE at FFFFF5FAFD7EBCE8    PPE at FFFFF5FAFD79D028    PDE at FFFFF5FAF3A05948    PTE at FFFFF5E740B29A28
contains 0A0000082B22A863  contains 0A0000082B22B863  contains 0A000001C7452863  contains 00000001E49EF880
pfn 82b22a    ---DA--KWEV  pfn 82b22b    ---DA--KWEV  pfn 1c7452    ---DA--KWEV  not valid
                                                                                  Transition: 1e49ef
                                                                                  Protect: 4 - ReadWrite

Rich (BB code): 
10: kd> !irql
Debugger saved IRQL for processor 0xa -- 2 (DISPATCH_LEVEL)

The latest crash appears to be have due to an illegal page fault and the address appears to be not completely borked either; let's run Driver Verifier for now with the recommended settings, which can be found here - Driver Verifier - BSOD related - Windows 10, 8.1, 8, 7 + Vista
 
Didn't get a blue screen this crash, everything froze up, sound stuttered then it just reset, have ran the collection don't know if it will capture that
 

Attachments

Rich (BB code): 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffe00802a09748, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80e6d38ee50, address which referenced memory

Rich (BB code): 
3: kd> !pte ffffe00802a09748
                                           VA ffffe00802a09748
PXE at FFFFA552A954AE00    PPE at FFFFA552A95C0100    PDE at FFFFA552B80200A8    PTE at FFFFA57004015048
contains 0A0000082B22B863  contains 0A00000296766863  contains 0A00000810D2C863  contains 0000000810DF4880
pfn 82b22b    ---DA--KWEV  pfn 296766    ---DA--KWEV  pfn 810d2c    ---DA--KWEV  not valid
                                                                                  Transition: 810df4
                                                                                  Protect: 4 - ReadWrite

Rich (BB code): 
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffce0d06b05428, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80ed781ee50, address which referenced memory

Rich (BB code): 
10: kd> !pte ffffce0d06b05428
                                           VA ffffce0d06b05428
PXE at FFFFB1D8EC763CE0    PPE at FFFFB1D8EC79C1A0    PDE at FFFFB1D8F38341A8    PTE at FFFFB1E706835828
contains 0A0000082B22B863  contains 0A00000133F12863  contains 0A000001C721F863  contains 000000021D675880
pfn 82b22b    ---DA--KWEV  pfn 133f12    ---DA--KWEV  pfn 1c721f    ---DA--KWEV  not valid
                                                                                  Transition: 21d675
                                                                                  Protect: 4 - ReadWrite

Both of the crashes are almost identical to each other and the same cause as the last crash. This would certainly seem to be driver issue in my opinion. I'm just not sure which one.

Please remove Driver Booster 8; I would not recommend installing any drivers which it offers. At the moment, I would suggest checking for any available updates for network adapter from Intel - Intel® Driver & Support Assistant

I couldn't see anything, but do you have any third-party network security programs installed?
 
Had 2 drivers to update from that Intel page, a bluetooth and a wifi driver

I haven't had driver booster installed on this fresh install of Windows, not sure where that is showing?

No third party network security programs
 
Roolek said:
I haven't had driver booster installed on this fresh install of Windows, not sure where that is showing?
Click to expand...
Apparently it's still installed? It should be present on the Start Menu.

It appear to be the exact same crash, at least they've all be consistent with each other, which would certainly pinpoint the issue to something software related. Could you please check the following directory and then upload a zipped version of the dump file? You'll need to upload it to a file sharing site such as Google Drive since it will be too large to attach to a forum post.

Rich (BB code): 
%systemroot%\MEMORY.DMP
 
Driver booster doesnt show on my start menu, under control panel to remove or when I search, not really sure what to do there?

MEMORY.rar
For the file
 
I'm surprised that Driver Verifier hasn't managed to find any violations, especially since the Force IRQL Checks is designed specifically for this kind of problem. It does seem that your version of MBAM has an active network security component and therefore I would recommend that you remove MBAM using the official removal tool - https://support.malwarebytes.com/hc...warebytes-using-the-Malwarebytes-Support-Tool

Afterwards, let's see if the system crashes again.
 
Roolek said:
Driver booster doesnt show on my start menu, under control panel to remove or when I search, not really sure what to do there?
Click to expand...
If you look at the Sysnative log collection folder which you attached, for some reason, the Msinfo32.nfo file has listed under Software Environment > Program Groups?
 
You could try using Revo uninstaller, it has a free trial version which you can use, but make sure you untick any additional programs it may want to install. I haven't used it in years so I'm not sure if they've added anything, I think CCleaner now tries or did try to bundle a third-party program with it? Otherwise I wouldn't worry too much about Driver Booster, it was more of a general suggestion.
 
If its not an issue, I'd rather leave it for now and just try get stable, will update as I get more crashes, or hopefully not
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top