B
Brokko_
Since about 3-4 weeks I have been getting BSOD's (almost) every time I start up my system. They vary in message but most of them are things like MEMORY_MANAGEMENT or ISQL or some others I can't remember. Using a blue screen viewer I have come to the conclusion that it is always 1 file that the error is coming from:
I have ran a diskcheck on my main disk, reinstalled windows, ran memtest86+, updated all my drivers and ran driver verifier.
The last one gave me more of a clue to what was going on. It put me in a bluescreen loop which wasn't a huge deal as I could boot into safe mode and then see what the issue was. The first issue was a virtual bus driver that was apparently automatically installed once I had plugged in my controller, which caused driver verifier to crash. So now I tested the system more with trying to boot up again and I still had the blue screens. So I ran driver verifier again, now leading to the following file (which was also shown on the BSOD itself):
Again ntoskrnl.exe and this time Wdf01000.sys. The problem now is that I cannot find any particular issue or fix related to this file. It is all the general: use a restore point or do this or that. Without actually knowing what the issue is. Is there any way to find out what is causing this (/which driver)?
As a note: I have all my chipset drivers installed from my motherboard manufacturer, and a legitimate copy of Windows 10 Educational.
Continue reading...
| Filename | Address In Stack | From Address | To Address | Size | Time Stamp | Time String |
|---|---|---|---|---|---|---|
| ntoskrnl.exe | ntoskrnl.exe+34ccaa | fffff806`4ee00000 | fffff806`4fe46000 | 0x01046000 | 0x64ebcc57 | 27/08/2023 23:21:11 |
I have ran a diskcheck on my main disk, reinstalled windows, ran memtest86+, updated all my drivers and ran driver verifier.
The last one gave me more of a clue to what was going on. It put me in a bluescreen loop which wasn't a huge deal as I could boot into safe mode and then see what the issue was. The first issue was a virtual bus driver that was apparently automatically installed once I had plugged in my controller, which caused driver verifier to crash. So now I tested the system more with trying to boot up again and I still had the blue screens. So I ran driver verifier again, now leading to the following file (which was also shown on the BSOD itself):
| Filename | Address In Stack | From Address | To Address | Size | Time Stamp | Time String | Product Name | File Description | File Version | Company | Full Path |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ntoskrnl.exe | ntoskrnl.exe+9cde34 | fffff802`6ec10000 | fffff802`6fc56000 | 0x01046000 | 0x64ebcc57 | 27/08/2023 23:21:11 | |||||
| Wdf01000.sys | Wdf01000.sys+a710 | fffff802`702b0000 | fffff802`70381000 | 0x000d1000 | 0xa9a9d36e | 14/03/2060 09:40:14 |
Again ntoskrnl.exe and this time Wdf01000.sys. The problem now is that I cannot find any particular issue or fix related to this file. It is all the general: use a restore point or do this or that. Without actually knowing what the issue is. Is there any way to find out what is causing this (/which driver)?
As a note: I have all my chipset drivers installed from my motherboard manufacturer, and a legitimate copy of Windows 10 Educational.
Continue reading...