Question I'm getting BSODs on an Asus computer, but no dump files are created ?

[ubuysa]

Run the Sysnative file collection app again and upload the new output zip file.

 

[SabbathFan]

Run the Sysnative file collection app again and upload the new output zip file.

Hello. My computer blue screened again, even though I updated my NVIDIA drivers. Here is the zip file:
https://www.dropbox.com/scl/fi/h6s4...ey=fv2p2cwiilzwjgkftqkr3yyhr&st=21sr9x1f&dl=0

 

[ubuysa]

Well again, you said your system blue screened but the logs don't confirm that. I see the kernel 41 error, indicating that Windows didn't shutdown properly, but no evidence of a BSOD.

Would you please do the following...

1. Enter the command sysdm.cpl into the Run command box.
2. Click the Advanced tab of the window that opens.
3. Click the bottom Settings button.
4. Check that the Write an event to the system log IS checked.
5. Also uncheck Automatically restart. This will allow you to see the error message - you'll then have to manually reboot.

Since you're seeing 'blue screens' fairly often I'd also like you to try starting Windows in Safe Mode. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

The usefulness of Safe Mode is that because it's a stripped-down system consisting only of Microsoft services and drivers it's very stable, so if you get BSODs or crashes in Safe Mode you have a hardware problem. On the other hand, if it's stable in Safe Mode then your problem is with a third-party driver or service that wasn't loaded in Safe Mode. There is another technique we can use in that case to locate the problem service or driver.

 

[SabbathFan]

Well again, you said your system blue screened but the logs don't confirm that. I see the kernel 41 error, indicating that Windows didn't shutdown properly, but no evidence of a BSOD.

Would you please do the following...

1. Enter the command sysdm.cpl into the Run command box.
2. Click the Advanced tab of the window that opens.
3. Click the bottom Settings button.
4. Check that the Write an event to the system log IS checked.
5. Also uncheck Automatically restart. This will allow you to see the error message - you'll then have to manually reboot.

Since you're seeing 'blue screens' fairly often I'd also like you to try starting Windows in Safe Mode. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

The usefulness of Safe Mode is that because it's a stripped-down system consisting only of Microsoft services and drivers it's very stable, so if you get BSODs or crashes in Safe Mode you have a hardware problem. On the other hand, if it's stable in Safe Mode then your problem is with a third-party driver or service that wasn't loaded in Safe Mode. There is another technique we can use in that case to locate the problem service or driver.

I decided to run Memtest86 again, and it also found no errors.

 

[ubuysa]

Ok, in addition to the changes I suggested earlier, let's stress your CPU and see whether that is glitchy. This test will make your CPU run hot, so first give the insides and all dust filters a clean so that the PC cooling is working well. Also, for this test, ensure that there is plenty of air around the CPU so it can cool itself properly, so if it's stuffed in a corner move it out so it's clear all around. This test will not harm your CPU as long as you run it as instructed below.

1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test.
4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp approaches or reaches 100°C (Tmax for your CPU), then stop Prime95 and let us know what happened.

Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.

Let us know what that reveals.

 

[SabbathFan]

Ok, in addition to the changes I suggested earlier, let's stress your CPU and see whether that is glitchy. This test will make your CPU run hot, so first give the insides and all dust filters a clean so that the PC cooling is working well. Also, for this test, ensure that there is plenty of air around the CPU so it can cool itself properly, so if it's stuffed in a corner move it out so it's clear all around. This test will not harm your CPU as long as you run it as instructed below.

1. Download Prime95 and a CPU temperature monitor (CoreTemp will do).
2. Keep the temperature monitor running all the time you run Prime95. Your CPU will get hot!
3. Run each of the three Prime95 tests (smallFFTs, largeFFTs, and Blend) one after the other for a minimum of 1 hour per test.
4. If Prime95 generates error messages, if the system crashes/freezes/BSODs, or if your CPU temp approaches or reaches 100°C (Tmax for your CPU), then stop Prime95 and let us know what happened.

Note that a properly cooled and stable CPU should be able to run all Prime95 tests pretty much indefinitely.

FYI: The small FFT test stresses the CPU more than RAM. The large FFT test stresses RAM more than the CPU. The Blend test is a mixture of the two.

Let us know what that reveals.

Just tried Prime95, and temperature typically stayed at around 70°C, no errors and no crashes or BSODs. Each test lasted for about an hour.

 

[ubuysa]

It's not your CPU then.

Did you uncheck the 'Automatically restart' box in the sysdm.cpl dialog like I asked?

We know your CPU is good and we're pretty sure your RAM is good too, so let's see whether we can catch a misbehaving driver. Sometimes a bad driver can cause a 0x124 BSOD, they can certainly cause 0x154 BSODs, so I'm going to get you to enable Driver Verifier...

Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

To enable Driver Verifier do the following:

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

These are high-level Microsoft drivers that manage lower-level third-party drivers that we otherwise wouldn't be able to trap. That's why they're included.

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running for 48 hours, use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past. If Windows doesn't automatically reboot after each BSOD then just reboot as normal and continue testing. The Driver Verifier generated BSODs are these...

• 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
• 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
• 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
• 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
• 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
• 0xE6: DRIVER_VERIFIER_DMA_VIOLATION

If you see any of these BSOD types then you can disable Driver Verifier early because you'll have caught a misbehaving driver.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query. If drivers are listed then it's enabled, if no drivers are listed then it's not.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up if you like, or not as you choose. Upload the file(s) to the cloud with a link to it/them here (be sure to make it public).

 

[SabbathFan]

It's not your CPU then.

Did you uncheck the 'Automatically restart' box in the sysdm.cpl dialog like I asked?

We know your CPU is good and we're pretty sure your RAM is good too, so let's see whether we can catch a misbehaving driver. Sometimes a bad driver can cause a 0x124 BSOD, they can certainly cause 0x154 BSODs, so I'm going to get you to enable Driver Verifier...

Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

To enable Driver Verifier do the following:

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

These are high-level Microsoft drivers that manage lower-level third-party drivers that we otherwise wouldn't be able to trap. That's why they're included.

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running for 48 hours, use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past. If Windows doesn't automatically reboot after each BSOD then just reboot as normal and continue testing. The Driver Verifier generated BSODs are these...

• 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
• 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
• 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
• 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
• 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
• 0xE6: DRIVER_VERIFIER_DMA_VIOLATION

If you see any of these BSOD types then you can disable Driver Verifier early because you'll have caught a misbehaving driver.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query. If drivers are listed then it's enabled, if no drivers are listed then it's not.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up if you like, or not as you choose. Upload the file(s) to the cloud with a link to it/them here (be sure to make it public).

I have unchecked "Automatically restart" in the sysdm.ccl, and I'll give Driver Verifier a try later.

 

[SabbathFan]

It's not your CPU then.

Did you uncheck the 'Automatically restart' box in the sysdm.cpl dialog like I asked?

We know your CPU is good and we're pretty sure your RAM is good too, so let's see whether we can catch a misbehaving driver. Sometimes a bad driver can cause a 0x124 BSOD, they can certainly cause 0x154 BSODs, so I'm going to get you to enable Driver Verifier...

Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

To enable Driver Verifier do the following:

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

These are high-level Microsoft drivers that manage lower-level third-party drivers that we otherwise wouldn't be able to trap. That's why they're included.

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running for 48 hours, use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past. If Windows doesn't automatically reboot after each BSOD then just reboot as normal and continue testing. The Driver Verifier generated BSODs are these...

• 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
• 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
• 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
• 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
• 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
• 0xE6: DRIVER_VERIFIER_DMA_VIOLATION

If you see any of these BSOD types then you can disable Driver Verifier early because you'll have caught a misbehaving driver.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query. If drivers are listed then it's enabled, if no drivers are listed then it's not.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up if you like, or not as you choose. Upload the file(s) to the cloud with a link to it/them here (be sure to make it public).

Hello there. I ran Driver Verifier and I got the DRIVER_VERIFIER_DETECTED_VIOLATION BSOD in the end. Here is one of the dump files it created.
091124-16078-01.dmp

 

[ubuysa]

If you have more Driver Verifier triggered dumps lease upload those too, it's possible it's trapped more than one driver.

In that one dump Driver Verifier trapped the AsIO3.sys driver, a component of Armory Crate. The driver illegally referenced a user-mode handle whilst running in kernel mode, hence the Driver Verifier BSOD. The version you have installed may have been superseded.....

4: kd> lmDvmAsIO3
Browse full module list
start             end                 module name
fffff801`4ab80000 fffff801`4ab8f000   AsIO3    T (no symbols)           
    Loaded symbol image file: AsIO3.sys
    Image path: \??\C:\Windows\system32\drivers\AsIO3.sys
    Image name: AsIO3.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Wed Nov 22 11:07:00 2023 (655DC4B4)
    CheckSum:         000114F9
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

If you must run Armory Crate then look for an update on your Asus motherboard website. TBH I would uninstall Armory Crate completely, it doesn't have a particularly good reputation for stability.

 

[SabbathFan]

If you have more Driver Verifier triggered dumps lease upload those too, it's possible it's trapped more than one driver.

In that one dump Driver Verifier trapped the AsIO3.sys driver, a component of Armory Crate. The driver illegally referenced a user-mode handle whilst running in kernel mode, hence the Driver Verifier BSOD. The version you have installed may have been superseded.....

4: kd> lmDvmAsIO3
Browse full module list
start             end                 module name
fffff801`4ab80000 fffff801`4ab8f000   AsIO3    T (no symbols)        
    Loaded symbol image file: AsIO3.sys
    Image path: \??\C:\Windows\system32\drivers\AsIO3.sys
    Image name: AsIO3.sys
    Browse all global symbols  functions  data  Symbol Reload
    Timestamp:        Wed Nov 22 11:07:00 2023 (655DC4B4)
    CheckSum:         000114F9
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

If you must run Armory Crate then look for an update on your Asus motherboard website. TBH I would uninstall Armory Crate completely, it doesn't have a particularly good reputation for stability.

This is the only other dump file I have. BTW, I have uninstalled Armoury Crate.
091124-16171-01.dmp

 

[ubuysa]

That second dump is the same as the first. That gives me more confidence that Armory Crate was the cause.

 

[SabbathFan]

That second dump is the same as the first. That gives me more confidence that Armory Crate was the cause.

I have now removed AsusCertService from my computer. I hope it fixes the BSOD issue I've been having for almost nine months. If I'm still getting the UNEXPECTED_STORE_EXCEPTION BSOD, I will report back to you.

 

[SabbathFan]

That second dump is the same as the first. That gives me more confidence that Armory Crate was the cause.

Hello. I got a BSOD, but this time with the CRITICAL_PROCESS_DIED error code. Yes, I have uninstalled Armoury Crate, including the very driver that was known to be causing problems.

 

[ubuysa]

Ah, a CRITICAL_PROCESS_DIED bugcheck is most usually caused by faulty hardware. Can you please run the Sysnative file collection app again and upload the new output.

 

[SabbathFan]

Ah, a CRITICAL_PROCESS_DIED bugcheck is most usually caused by faulty hardware. Can you please run the Sysnative file collection app again and upload the new output.

Here it is.
https://www.dropbox.com/scl/fi/h6s4...ey=fv2p2cwiilzwjgkftqkr3yyhr&st=h5hrvozc&dl=0

 

[ubuysa]

You need to run the Sysnative app again and get a NEW output file. The one you uploaded looks like the one I've already seen, there is no 0xEF bugcheck dump in there.

 

[SabbathFan]

You need to run the Sysnative app again and get a NEW output file. The one you uploaded looks like the one I've already seen, there is no 0xEF bugcheck dump in there.

Is this it? BTW, I removed Armoury Crate and AsusCertService off my computer and still got the UNEXPECTED_STORE_EXCEPTION BSOD.
https://www.dropbox.com/scl/fi/hq2k...ey=ukv2bei5inhcgplvgkxde1o23&st=kxixp6hx&dl=0

 

[ubuysa]

No, the latest dump in there is dated 11th Sept, but the CRITICAL_PROCESS_DIED BSOD you most recently had was on the 24th.

 

[SabbathFan]

No, the latest dump in there is dated 11th Sept, but the CRITICAL_PROCESS_DIED BSOD you most recently had was on the 24th.

So looks like it didn't create a dump. However, I got an UNEXPECTED_STORE_EXCEPTION BSOD, even though I uninstalled Armoury Crate and AsusCertService.

 

[ubuysa]

Can you try starting Windows in Safe Mode please and see whether it BSODs. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

The usefulness of Safe Mode is that because it's a stripped-down system consisting only of Microsoft services and drivers it's very stable, so if you get BSODs or crashes in Safe Mode you have a hardware problem. We really need to see at this point whether this is hardware related (it looks as though it may be).

 

[SabbathFan]

Can you try starting Windows in Safe Mode please and see whether it BSODs. In Safe Mode a stripped-down Windows system is loaded, with only critical services and drivers loaded. Typically no third-party drivers are loaded. This does mean that you won't be able to do any useful work in Safe Mode, or play games, and many of your devices may not work properly (or at all) because their drivers have not been loaded. Your display will be low resolution for example, because you'll be using only the Windows basic display driver.

The usefulness of Safe Mode is that because it's a stripped-down system consisting only of Microsoft services and drivers it's very stable, so if you get BSODs or crashes in Safe Mode you have a hardware problem. We really need to see at this point whether this is hardware related (it looks as though it may be).

Do you think I should uninstall any of these? At least three of them are Armoury Crate.

https://imgur.com/a/a1KVetR

View: https://imgur.com/a/a1KVetR

 

[ubuysa]

I cant see that image, I'm getting an imgur.com is at capacity message. However, Armory Crete is know to be a tad flaky and if you can do without it then it's best to fully uninstall it.

Is it stable in Safe Mode?