Random crashes on new build

S

StymiedMike

Well-known member
Joined
Sep 25, 2016
Posts
94
I recently started using a newly built Windows 10 PC. It only has Thunderbird 78 & Firefox 92 on it.

Several times a day Thunderbird would open & freeze to a blank white screen which said "Not responding" in the upper left corner. The only way to close it is to power off the PC. A few times Firefox also locked up but not recently. Again, these are the only 2 programs on the PC.

I ran sfc /scannow which indicated it was repairing/replacing files. Everything worked great for 5 days, but then TB froze 3 times within an hour. It cannot be closed in task manager or using taskkill. The PC has to be powered off.

Last night I restored a drive image. TB & FF worked OK for 24 hours. I probably opened TB 25-30 times. But then TB opened & froze to a blank screen & "Not responding" again.

Also, right after I did the image restore I opened File Explorer & it opened & froze to a blank white screen and "Not responding". First time I saw File Explorer do that. This would seem to indicate the problem is not with TB or FF.

Is there anything in Event Viewer that could indicate what is wrong? I created a dump file in Task Manager before I powered off the PC. Might there be something in there that would indicate the problem?

Any help would be appreciated.
Thanks
 
This morning I restored an earlier image than I previously did. This version did not have FF or TB on it. I thought it had an earlier version of Windows 10 on it which means Win10 would need to get updated, but that wasn't the case. I did install a fresh copy of FF & TB and so far they're working but I'm not counting on that to last.

I presume there's no crash data since an image was restored. But hen it crashes I'll follow the instructions you posted.
 
As previously mentioned, Thunderbird & Firefox randomly freeze & don't respond. This happened once with File Explorer. Yesterday was a new problem but may be related. I could not access TB email or use FF because the bookmarks were not accessible. Yet everything was working a couple hours earlier. I have both of their profiles on the D: drive.

I rebooted the PC and the D drive did not show up in File Explorer or Disk Management. I shut down the PC & did a cold re-boot. I message came in large text on the lower half of the screen but it disappeared before I could read the whole thing. Within a minute everything came back up & running normally & the D: was now there.

Almost the same thing happened a month ago. Back then I could not copy to the D: drive. Rebooting indicated it disappeared. Another reboot gave me the large text error message & everything worked after that. Except for the random TB & FF freezes and the one time where File Explore froze.

Here's the Speccy link and the SysnativeFileCollectionApp.zip is attached.
http://speccy.piriform.com/results/Pk0GQcpJunxVQqqZZfhutLl

PC has an ASRock B365M Pro4 mobo, Intel I5-9400 CPU, 16 GB RAM (2 x 8 G.Skill RipjawsV) & a Samsung 500GB EVO 970+ M.2 for the C: drive. Corsair CX430 CPU, no video card. I built the PC last year but didn't start using it until about a month ago when I installed a Samsung 1TB EVO 970+ M.2 drive for the D: storage drive.

I did contact ASRock & they said these Samsung drives are good to use with that mobo.

Windows is 20H2 and restored with an image a day ago. The only programs that I installed are TB, FF and AOMEO backupper.

About a week ago I ran sfc /scannow & it said it repaired/replaced some files & the PC worked OK for 5 days which is the longest it has worked without have TB or FF lock up. I have to power off the PC in order to close out of the programs.

Before I restored an Image I did have Samsung Magician installed & ran SMART and everything was OK. Both drive temperatures were about 35°C.

I don't know if the D: drive is defective or if Windows just forgets it's there.

Is the large text error message from Windows or BIOS?

Any help would be greatly appreciated.
Thanks.
 

Attachments

Can you operate your system without the D drive and if you do are there still problems?

Can you try the D: drive in another system?

These simple tests might help you determine if the D: drive is faulty. Don't forget it could also be the cables or connectors that are not working correctly, make sure that you are using good quality cables with the locking mechanism that holds them in place.
 
I also did an analysis of the crash dump and specifically looked at the events leading up to the crash. The data suggest that there are problems with the drive, possibly related to powering up the drive and allocating input/output queues. Note the comment (which I have put in bold) that the device failed. These are summarised below:

Rich (BB code): 
3: kd> .load pde;!dpx
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
Start memory scan  : 0xffffc089efc4eca8 ($csp)
End memory scan    : 0xffffc089efc50000 (Kernel Stack Base)

               rsp : 0xffffc089efc4eca8 : 0xfffff80133609169 : nt!KiBugCheckDispatch+0x69
               r11 : 0xffffc089efc4ede8 : 0xfffff80133605469 : nt!KiPageFault+0x469
               r15 : 0xffffc682fddc9278 :  !du "stornvme"
0xffffc089efc4eca8 : 0xfffff80133609169 : nt!KiBugCheckDispatch+0x69
0xffffc089efc4ecd0 : 0xfffff80136c6ba12 : storport!StorpMarkDeviceFailed+0x57a
0xffffc089efc4ed98 : 0xfffff801334f3f1f : nt!KeQueryPerformanceCounter+0x5f
0xffffc089efc4eda8 : 0xfffff801334f3f1f : nt!KeQueryPerformanceCounter+0x5f
0xffffc089efc4ede0 : 0xffffc682fddc9278 :  !du "stornvme"
0xffffc089efc4ede8 : 0xfffff80133605469 : nt!KiPageFault+0x469
0xffffc089efc4edf0 : 0xffffc682fd38a3f0 :  Trap @ ffffc089efc4edf0
0xffffc089efc4eec8 : 0xfffff8013347b43f : nt!PsGetCurrentServerSiloGlobals+0x3f
0xffffc089efc4eed8 : 0xfffff801335d2558 : nt!write_string+0x48
0xffffc089efc4eef8 : 0xfffff80136c36b7c : storport!RaidAdapterReleaseInterruptLock+0x50
0xffffc089efc4ef08 : 0xfffff801335d2445 : nt!output_l+0x819
0xffffc089efc4ef28 : 0xfffff80136c5ba2c : storport!RaidAdapterGetFirstUnit+0xa4
0xffffc089efc4ef58 : 0xfffff80136c6ba12 : storport!StorpMarkDeviceFailed+0x57a
0xffffc089efc4efa0 : 0xfffff80136d0f788 :  !du ""Allocate IO queues failed""
0xffffc089efc4efb8 : 0xfffff801335f91f4 : nt!KiInterruptDispatchNoLockNoEtw+0x44
0xffffc089efc4f018 : 0xfffff801335631ff : nt!WdHwpWritePortUShort+0xf
0xffffc089efc4f048 : 0xfffff80136d0f788 :  !du ""Allocate IO queues failed""
0xffffc089efc4f068 : 0xfffff801335f91f4 : nt!KiInterruptDispatchNoLockNoEtw+0x44
0xffffc089efc4f080 : 0xffffc682fddc9278 :  !du "stornvme"
0xffffc089efc4f128 : 0xfffff80136c98000 : storport!WPP_GLOBAL_Control
0xffffc089efc4f138 : 0xfffff80136c6725c : storport!StorDelayExecution+0xdc
0xffffc089efc4f148 : 0xfffff80136d08c90 : stornvme!NVMeLogTelemetryWaitForCmdComplete+0x30
0xffffc089efc4f178 : 0xfffff80136c3dd81 : storport!StorPortExtendedFunction+0xb1
0xffffc089efc4f200 : 0xffffc089efc4f340 : 0xfffff80136c98000 : storport!WPP_GLOBAL_Control
0xffffc089efc4f230 : 0xfffff80136d0f788 :  !du ""Allocate IO queues failed""
0xffffc089efc4f248 : 0xfffff80136d00000 : stornvme!DiagGeneric+0x98
0xffffc089efc4f2c0 : 0xffffc089efc4f340 : 0xfffff80136c98000 : storport!WPP_GLOBAL_Control
0xffffc089efc4f2d8 : 0xfffff80136cfca16 : stornvme!NVMeControllerInitPart2+0x226
0xffffc089efc4f308 : 0xfffff80136d0f788 :  !du ""Allocate IO queues failed""
0xffffc089efc4f340 : 0xfffff80136c98000 : storport!WPP_GLOBAL_Control
0xffffc089efc4f358 : 0xfffff80136cfce0c : stornvme!NVMeControllerPowerUp+0x54
0xffffc089efc4f388 : 0xfffff80136cf4bc4 : stornvme!NVMeHwAdapterControl+0x134
0xffffc089efc4f418 : 0xfffff80136c405cd : storport!RaCallMiniportAdapterControl+0x25
0xffffc089efc4f448 : 0xfffff80136c6d937 : storport!RaidAdapterSendPowerToMiniport+0x6b
0xffffc089efc4f4d8 : 0xfffff8013348507e : nt!IopfCompleteRequest+0x11e
0xffffc089efc4f550 : 0xffffc089efc4f5a0 : 0xfffff80136983002 : pci!WPP_RECORDER_INITIALIZED+0x2
0xffffc089efc4f558 : 0xfffff8013695cd12 : pci!PciProgramInterruptResource+0x122
0xffffc089efc4f5a0 : 0xfffff80136983002 : pci!WPP_RECORDER_INITIALIZED+0x2
0xffffc089efc4f5c8 : 0xfffff80133484f47 : nt!IofCompleteRequest+0x17
0xffffc089efc4f5d8 : 0xffffc089efc4f600 : 0xfffff80136983000 : pci!WPP_RECORDER_INITIALIZED
0xffffc089efc4f5f8 : 0xfffff80136952280 : pci!PciPowerUpDeviceTimerCallback+0x4d0
0xffffc089efc4f600 : 0xfffff80136983000 : pci!WPP_RECORDER_INITIALIZED
0xffffc089efc4f620 : 0xffffc683018e48b0 :  dt Wdf01000!FxPkgFdo
0xffffc089efc4f628 : 0xfffff801365b2836 : Wdf01000!FxThreadedEventQueue::QueueWorkItem+0x32
0xffffc089efc4f638 : 0xfffff801365aac7d : Wdf01000!FxIFR+0x1ed
0xffffc089efc4f6f8 : 0xfffff8013347ffe9 : nt!KiExpireTimer2+0x429
0xffffc089efc4f708 : 0xfffff80136951db0 : pci!PciPowerUpDeviceTimerCallback
0xffffc089efc4f710 : 0xfffff80136951db0 : pci!PciPowerUpDeviceTimerCallback
0xffffc089efc4f718 : 0xffffc089efc4fa30 : 0xfffff80136951db0 : pci!PciPowerUpDeviceTimerCallback
0xffffc089efc4f808 : 0xfffff8013347f825 : nt!KiTimer2Expiration+0x165
0xffffc089efc4f8c8 : 0xfffff80133499d14 : nt!KiRetireDpcList+0x874
0xffffc089efc4f9c8 : 0xfffff801335f9235 : nt!KiInterruptDispatchNoLockNoEtw+0x85
0xffffc089efc4fa20 : 0xfffff801365ba000 : Wdf01000!FxPowerIdleMachine::_PowerTimeoutDpcRoutine
0xffffc089efc4fa30 : 0xfffff80136951db0 : pci!PciPowerUpDeviceTimerCallback
0xffffc089efc4fb58 : 0xfffff801335fad3e : nt!KiIdleLoop+0x9e
0xffffc089efc4fb98 : 0xffffc089efc49000 :  !da ""KSE: KsepMatchInitCpuInfo failed. [0x%08x].""
 
philc43 said:
Can you operate your system without the D drive and if you do are there still problems?

Can you try the D: drive in another system?

These simple tests might help you determine if the D: drive is faulty. Don't forget it could also be the cables or connectors that are not working correctly, make sure that you are using good quality cables with the locking mechanism that holds them in place.
Click to expand...

Both drives are M.2 drives so there are no cables. I do not have another PC that has an M.2 slot.

However at one time I did put the Firefox profiles on the C: drive so it would all be on the C: drive and it still had a lockup.
 
StymiedMike said:
Are you referring to the D: drive that failed?
Click to expand...
I can't actually tell from the crash data which drive is being addressed. This is why I wanted you to remove the D: drive and see if it still happened.
 
I will do. I won't know right away if it's going to fail because sometimes it works OK all day. Or one time it worked 5 days. I was ready to install other programs when the problem occurred.

Do you think there's a possibility that since both drives are fast M.2 drives that's causing a problem? IOW they're sort of stumbling across each other?
 
I have now explored the Event log data and this confirms it is the D: drive. See the section below:

Code: 
2021-09-26T16:16:48.8760000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.8760000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.8760000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.8760000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.8760000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.8760000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.8920000Z        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume6.
           Failure status: A device which does not exist was specified.
           Device GUID: {87c89656-b6ab-7334-2078-22938cdc6255}
           Device manufacturer:
           Device model: Samsung SSD 970 EVO Plus 1TB
           Device revision: 3B2QEXM7
           Device serial number: 0025_3856_1150_7F0E.
           Bus type: NVMe
           Adapter serial number: S6S1NG0R620181K     _0006
   2021-09-26T16:16:48.9080000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.9210000Z        The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume6.
           Failure status: A device which does not exist was specified.
           Device GUID: {87c89656-b6ab-7334-2078-22938cdc6255}
           Device manufacturer:
           Device model: Samsung SSD 970 EVO Plus 1TB
           Device revision: 3B2QEXM7
           Device serial number: 0025_3856_1150_7F0E.
           Bus type: NVMe
           Adapter serial number: S6S1NG0R620181K     _0006
   2021-09-26T16:16:48.9080000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.9080000Z        An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
   2021-09-26T16:16:48.9080000Z        {Delayed Write Failed} Windows was unable to save all the data for the file D:\. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
 
Thanks philc43 -

This morning my wife had the same problem. She could not access TB, powered off the PC & turned it back on. When it came back on got a blue screen with big white letters and it was counting up, 20%. 30%, etc. When done she was able to access email.

Later she tried FF & got the message that the bookmarks were not available, etc. She left it at that. She was trying to quote the TB and FF message and they appeared to be the same as what I experienced.

Since she left the PC with FF not working, it displayed the same message I had experienced about no bookmarks or history. I looked in File Explorer and there was no D: drive. I powered off the PC. When turning back on I got the blue screen with big white letters. It did the counting up 20%, 30%, etc. and it displayed a URL to contact and something about "storport" or similar. It happened too quickly to get the exact spelling, but it's probably the same as you posted in message #6.

Now I have to decide if I want to return, exchange, try a different brand for the D: drive. Or just use a spinner HDD as originally planned. The only reason I went with an M.2 for the D: drive is I had gift card to use, the drive was on sale, & I figured why not.

Thanks again & I'll let you know what happens.
 

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

Back
Top