Assumption: Your a developer who understand how to debug. If you're a consumer then all I can say is it is probably a bad driver but without looking at the dump there is no way to tell.
The HAL is for hardware interaction. So it is either a hardware issue or a driver issue. Unfortunately given just that screenshot we have no way of
knowing. Given the bug check code it seems to be this which leads me to believe it is a bad driver. If you load this up in windbg then it should show you the module and call stack which will quickly narrow down the driver that is potentially causing the issue.
Of course if this machine was fine for a while and you updated something and things started breaking then that is where I'd start.
today i received 3rd BSOD. it is like 2nd
Caused by driver: volmgrx.sys
Crash address: ntoskrnl.exe+1b8ad0
windbg result is here
can you help me?
Looks like a storage driver problem. I see Intel in the list. You could have a bad drive or driver. I recommend you run tests on your drive to eliminate hardware issues. If none are found then report the issue to Intel and see what they say. Of course I'm assuming you're running the right/latest drivers for your storage.
i installed last solidigm storage tool and update firmware. server uptime is 10 days
last uptime before bsod was 7 days
uptime almost 14 days
Sign in to comment