Ehssan Shamoradi
New Member
- Joined
- May 11, 2014
- Messages
- 7
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {18, 2, 1, fffff8011d970181}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {ffffe001350b11fb, 1, fffff801434ce076, 2}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+166 )
Followup: MachineOwner
Thanks for that, I'll remove it initially and see what happens. Is it best to just uninstall the driver from device manager or is there a cleaner method? It would've been installed by my 2Tb WD external HDD.
So how likely do you think a hardware fault is? I'd be pretty angry if that was the case considering they've (PC Specialist) done a full rebuild and had it back three times. To elaborate on the issue there is no trigger to the BSODs, they are pretty random, can occur when just browsing online for example. I sometimes go up to around 10 days without issue. The system is also otherwise stable and fast although I annoyingly can't do a system restore because of this error: - "an unspecified error occurred during system restore (0x80070005)". I've been told the most likely fix for this is to turn off antivirus but the problem persists even with Windows Defender turned off.
Thanks for your time
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {18, 2, 1, fffff8011d970181}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {18, 2, 1, fffff8011d970181}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption