Where does the BSOD come from when trying to write to the hard drive?

Question

System administration

Hello. No experience in system administration.
I have Windows Server 2008 R2 at work. There is a raid HP P2000. On the server, a 4.2 TB disk is visible in the disks. It is divided into 2 volumes - 1 TB and 2.8 TB. The second volume is shared over the network, it is the main repository of documents. The first volume is not particularly used. When working with the second volume (over the network and directly from the server), a BSOD almost always crashes with error 0x0000007F. I thought the problem was in one of the hard drives, all the more or less suspicious ones were replaced. The problem remains. I have no experience as an administrator, I don’t know where to dig. I will be grateful for advice!

Answer 1

babyflowercry , so RAID has nothing to do with it at all! After all, a colleague provided a link - it says that such an error gets out due to a stack exhaustion error when working over a network via the SMB protocol. When you share a volume, this is the protocol you use. The problem is that initially I dug in the wrong place. RAID is also needed in order to minimize the impact of disk problems on the stability of the system, and even a complete disk failure should not cause a BSOD in any way, rather, a failure of the RAID controller can. In your case, the reason is a bug in the implementation of the protocol, which is treated elementarily - by installing an update! The update number is in the article. In general, for good, you need to install all the updates - you never know what other hidden bugs will be cured.