AMD 7950 BSOD

History of this computer is as follows:

Bought all the parts on PC Part Picker, watched my good friend build, test it, and package it up for shipping all live on twitch. 

Have had BSOD from day 1.  Recently reset it. (reinstalled windows). Left everything default which means all the bloatware is intact.

I didnt want to start turning everything off until I got the problem fixed.  I have attached all the required files and links. 

Please save my sanity and try to find anything that would be causing my problems?  Thank you so much for your time!! 

http://speccy.piriform.com/results/AucEVj8UE0jcBdO1A5GUJyb

Same culprit in each of the three dmps storahci.sys the incorrect set up information addresses this.

Couple of things there but the two most important are explained below;

The computer has not been set up properly, see my canned explanation below;

The RAM is not appropriate for your CPU, AMD state here up to 5200MHz/MT/s and if you have EXPO/XMP enabled the RAM will get auto OCd past what the CPU can handle and the PC will become unstable.

Well this would explain why it seemed to have gotten worse after I did the reset on it.  Just a quick reminder please, where is it that i stop windows from updating drivers? Thank you so much for you quick response, I will let you know how it goes either way!!

**Also I dont have anything overclocked in my system atm.

Edited by eVeville, 16 January 2024 - 02:57 PM.

In answer to your question How to disable automatic driver install on Windows 11

Couple of other suggestions;

IRestore the MBs default factory settings in the BIOS, they are sometimes listed as one of the following " factory defaults" "most stable" or on newer boards "optimized" please note that if you have both the "most stable" and the "optimized" options in the BIOS you should choose the most stable" option as in this instance the "optimized" settings are a form of overclocking that can cause instability.  

Save the new settings, restart and make sure that fast boot is disabled, if not disable it, save/exit, restart and test.

Just wondering why you picked up a M/B that is already 2yrs old and leaves 2-3 yrs left of Support (below).

You Motherboard Support Page with Bios and Drivers : https://www.msi.com/Motherboard/PRO-X670-P-WIFI/support

Further on the ram.  Speccy reports 63gig of ram and not 64gig.

I would think possible Speccy has misreported the total but would suggest download CPU-Z to make sure of the total. While there grab HWMonitor excellent tool.

Would also suggest test the ram with Memtest86+ https://www.memtest.org/ to test and confirm if any damage to the ram.  If there is would hope bought ram in matched pairs

and have the packaging to RMA them if have to. Test 1 stick at a time.  See Manual for slots to use, can download from the Support URL if need to.

If bought in matched pairs then have to send 2 back at a time

Note : there is no info in Speccy as to maker of ram and other details that would have helped you.  Not a good sign. (not looked at Dump files for info)

Further to drivers some info for you; roll back driver : https://www.windowscentral.com/how-roll-back-device-driver-windows-10 /11

and stop specific drivers updates/: https://www.howtogeek.com/263851/how-to-prevent-windows-from-automatically-updating-specific-drivers/

Would also suggest stopping anything in BIOS from speeding up the boot. example ASUS Fast Boot for the same reasons as below :

Stop MS Fast Start : https://www.windowscentral.com/how-disable-windows-10-fast-startup /11 and WHY !!!

Let us know how your making out.

Thank you for taking you time to try and help me.

Heres the link to CPU-Z Validator on my PC.

https://valid.x86.fr/8az5cg

I already tested my ram, both together and individually.  Everything came back fine.  I already turned off windows updating and Dont have anything overclocked.

I will turn off fast startup and recheck for anything that could be speeding things up.

Ill update once I have new info. 

Thanks again.

Notwithstanding the advice above, the dumps, which are identical, clearly show that the problem is with the 2TB Samsung 870 QVO SSD.

The bugcheck in all three dumps is a 0x9F with argument 1 set to 0x3. This indicates that a device has failed to complete a power transition within an expected time The dump gives us the address of the IRP managing the power transition (in argument 4) and the device address of the device having problems (in argument 2)...

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffb102f4ff1050, Physical Device Object of the stack
Arg3: ffffde8790b1f178, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffb102ff99fa70, The blocked IRP

Displaying the blocked IRP shows us what driver(s) were failing to complete...

10: kd> !irp ffffb102ff99fa70
Irp is active with 6 stacks 3 is current (= 0xffffb102ff99fbd0)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffb102f4ff1050 00000000 fffff8006b4e8510-ffffb102ff9c5590 Success Error Cancel pending
           \Driver\storahci    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffb102ff9c5050 00000000 fffff8006a3aec60-00000000 Success Error Cancel pending
           \Driver\disk    partmgr!PmPowerCompletion
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffb102ff6669a0 00000000 fffff80065b2cf80-ffffb102ff99f2d8 Success Error Cancel pending
           \Driver\partmgr    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffb102ff99f2d8    

            Args: 00000000 00000000 00000000 00000000

At the very bottom there are the stroachi.sys and partmgrt.sys drivers, both of which are Microsoft drivers and so they are not at fault. They do however indicate that the problem lay with a power transition (note that both are power related) for a storage device.

The device object address shows us the devobj structure that Windows uses to manage this device

10: kd> !devobj ffffb102f4ff1050
Device object (ffffb102f4ff1050) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\storahci DriverObject ffffb102f4fd5d30
Current Irp 00000000 RefCount 0 Type 00000007 Flags 00001050
SecurityDescriptor ffffe0850c71a8e0 DevExt ffffb102f4ff11a0 DevObjExt ffffb102f4ff27a0 DevNode ffffb102f4fb9420
ExtensionFlags (0000000000)  
Characteristics (0x00000180)  FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffb102ff9c5050 \Driver\disk
Device queue is not busy.

The key data in the for our purposes is the address of the device node (the DevNode) which describes that actual device. Displaying the DevNode gives...

10: kd> !devnode ffffb102f4fb9420
DevNode 0xffffb102f4fb9420 for PDO 0xffffb102f4ff1050
  Parent 0xffffb102f4f61a20   Sibling 0000000000   Child 0000000000   
  InstancePath is "SCSI\Disk&Ven_Samsung&Prod_SSD_870_QVO_2TB\7&2ff5684&0&000000"
  ServiceName is "disk"
  State = DeviceNodeStarted (0x30a)
  Previous State = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[10] = DeviceNodeStarted (0x30a)
  StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[08] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[07] = DeviceNodeStarted (0x30a)
  StateHistory[06] = DeviceNodeStartPostWork (0x309)
  StateHistory[05] = DeviceNodeStartCompletion (0x308)
  StateHistory[04] = DeviceNodeStartPending (0x307)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x306)
  StateHistory[02] = DeviceNodeDriversAdded (0x305)
  StateHistory[01] = DeviceNodeInitialized (0x304)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x0)
  StateHistory[14] = Unknown State (0x0)
  StateHistory[13] = Unknown State (0x0)
  Flags (0x24000130)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_NO_RESOURCE_REQUIRED, DNF_NO_LOWER_DEVICE_FILTERS,
                      DNF_NO_UPPER_DEVICE_FILTERS
  CapabilityFlags (0x00402180)  SilentInstall, RawDeviceOK,
                                WakeFromD3
                                Unknown flags 0x00400000

The InstancePath near the top shows that the device is a Samsung&Prod_SSD_870_QVO_2TB. At the bottom you can see in the CapabilityFlags that the device is capable of 'WakeFromD3' The D3 state is a low power state (D0 is the normal running state) so the device should be able to complete this power transition.

I would check that the SSD is properly connected, especially the power connector - at both ends. Check the SATA connector at both ends too. This could also be chipset driver related, as mentioned above.

TBH I would take it back to the builder and ask them to fix it.

 

Edited by ubuysa, 17 January 2024 - 03:07 AM.

TBH I would take it back to the builder and ask them to fix it.

 

ubuysa,

Unfortunately the parts were assembled by a friend of eVeville who as I mentioned in my reply # 2 has not done so correctly, not one system driver has been installed so no wonder the OP has had problems, the MBs chipset has no way of being able to properly communicate with any of the hardware.

Unfortunately the parts were assembled by a friend of eVeville who as I mentioned in my reply # 2 has not done so correctly, not one system driver has been installed so no wonder the OP has had problems, the MBs chipset has no way of being able to properly communicate with any of the hardware.

Yes, that's a very good point. However, I wanted to provide the OP with some hard evidence from the dumps that the PC has a real problem. It could indeed by driver related (and probably is) but having hard proof that all is not well from a dump is better evidence to take to the builder than "the people at BleepingComputer say it's not been built properly".
 

Hope you don`t think that I was questioning your words of wisdom ubuysa as it was not intentional, I was merely mentioning the fact that there was no warranty claim or professional tech available to put things right.

Fwiw, I build and repair computers and you never ever hand over a computer that has not had the drivers correctly installed and Windows fully updated, any BSOD after that you ask experts like yourself for help.

Sorry I havent been able to respond until now.  I will have time tonight to work on my computer, I did however double check my bios and turned off fast boot.  Also wanted to mention that the Hard Drive in question is actually the old boot drive for my previous system, I did not format it before using it in this new system, but the system is booting from the new drive.  Could that be causing any problems? Would just formating the drive maybe help? Also the friend that build this system lives about 2000 miles from me so its not something he can help me with unfortunately.  

I am alittle confused now as to what steps to take to try and fix things now?

Edited by eVeville, 18 January 2024 - 08:27 PM.

Hi, In reality your friend is not needed.   You can do anything that is required.

Yes the old boot drive can confuse Windows and result with problems due to it being a previous boot drive.  You should move your stuff off of it and then format it out and delete the boot partition that is on the drive.

In perfect world you would format your C : Drive and then install Windows, disconnecting from the internet and installing your Chipset Drivers, SATA Drivers followed by lesser stuff with Audio last.  With reboots in between.

Your get those things : From your Motherboard Support Page with Bios and Drivers : https://www.msi.com/Motherboard/PRO-X670-P-WIFI/support

You say you checked the BIOS that does not mean you updated it.

Running : Version: 1.90   Date:  6/8/2023   Current Release : 7D67v1E5(Beta version)   Date : 2024-01-05

Which Updates : - AGESA ComboPI 1.1.0.1 updated.   

The update is very important for the Processor.  As well people are saying improved boot times.

EDIT : Windows 11 Download Page : https://www.microsoft.com/en-us/software-download/windows11

Edited by Pkshadow, 18 January 2024 - 09:47 PM.

Ok should I update the bios after I reinstall windows? I guess it wouldnt really matter since the bios loads before windows, but I want to make sure I do everything right.

If the computer is stable then yes.  If the computer has a option in Bios to stick it on USB and shove it into a Dedicated Rear I/O USB Port that does not require for the system to have started just plugged in and power to the PSU then yes.

I would suggest downloading your manual from the Support URL if do not have a paper book and read about how to do your Bios Update as there is a possible 3 ways to do it.

Watch the Video off your Support Page : https://www.msi.com/Motherboard/PRO-X670-P-WIFI/support on the BIOS Tab.

Ok, Thank you so much for the quick response.  I just noticed on the MSI website that the 2 first options to download are both "Beta" am I correct in saying that I should download the first NON Beta option for updating the bios?

Edited by eVeville, 19 January 2024 - 05:57 AM.