New
#11
Can't seem to find that driver anywhere.
Look around here Alpha Networks Inc.
But you might have to contact them.
Alpha Networks Inc.
Can't seem to find that driver anywhere.
Look around here Alpha Networks Inc.
But you might have to contact them.
Alpha Networks Inc.
Alright
So I sent an email regarding the driver to ALPHA Networks
And I did everything you instructed, Arc, except for the BIOS update and the ALPHA Networks driver
Everything was fine on the first day
But the BSOD struck again on the second day
With a different STOP error than before (I think)
Intel graphics driver again
Try another version? May be the that one earlier than the installed one? The installed one is of 31st July.Code:fffff880`07c25368 fffff880`04a7bcccUnable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys igdkmd64+0x3cccc fffff880`07c25370 fffffa80`057f87d0 fffff880`07c25378 fffff880`04588f76 dxgmms1!VidSchDdiNotifyInterrupt+0x9e fffff880`07c25380 fffffa80`0008cdfa fffff880`07c25388 fffff880`04ad13c5 igdkmd64+0x923c5 fffff880`07c25390 fffffa80`05b95000 fffff880`07c25398 fffff880`04c49ceb igdkmd64+0x20aceb
I downgraded my graphics driver
But I got another BSOD a few hours afterwards
Description here: Driver Reference Table - NisDrvWFP.sys.Code:fffff880`024b7638 fffff880`02a0f0d7Unable to load image \SystemRoot\system32\DRIVERS\NisDrvWFP.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for NisDrvWFP.sys *** ERROR: Module load completed but symbols could not be loaded for NisDrvWFP.sys NisDrvWFP+0xf0d7
All those are network related crash. At this point, I may suggest you to not use the Alpha network that use.
Alright
Thank you so much for your help
I reinstalled my network drivers
And it's been a week without any BSODs
This has never happened before
So I'm willing to mark my case as solved
Once again, thank you very much for your help.
Just when I thought everything was fine
The BSOD struck again
Is this related to something new?
Or is it the same problem as before?
Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
InformationWhy Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.
How Can we know that DV is enabled:
It will make the system bit of slow, laggy.
WarningBefore enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.
If there is no points, make a System Restore Point manually before enabling DV.
Let us know the results, with the subsequent crash dumps, if any.Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.
I ran Driver Verifier for around 4 hours, with my computer freezing twice during the test
However, I didn't get any minidumps for either of the times when my computer froze.