Windows 10: BSOD Random times when computer unattended.

Sorry, missed your post zbook, I couldntdownload the dm beta, when i clicked on link i get:Invalid Attachment specified. If you followed a valid link, please notify the administrator

 

Hi Zbook
I have ran the all the tests but the memory test, I ran that last time and went past 8 passes and didnt take a photo, will run it again now, in the meantime, I took all the pics in the zip file, everything should be here even the DM beta (finally managed to find it). But please keep in mind that I found out my comp does not do memory dumps for some reason. I used who crashed and crashed my PC but nothing came out. in the event viewer i get:
Volmrg: Dump file creation failed due to error during dump creation.

I have pics of all the attached above *Smile Thank you once again

 

1) Chkdsk /x /f /r C: displayed:

Correcting errors in the master file table's (MFT) BITMAP attribute.

Windows has made corrections to the file system.

2) When available post chkdsk /x /f /r on the other partitions.

3) Open device manager > click view > click show hidden devices > expand all rows > post images of any row with a yellow triangle and black exclamation mark or unknown device

4) Check and re-seat cables for all drives.

5) Read these links on Windows driver verifier: (do not use the tool until it is communicated in the thread)
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

6) Create a brand new restore point
7) Backup any important files to another drive or to the cloud

8) Run Sea tools for windows on each drive using SMART, and long generic tests:

How to use SeaTools for Windows
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows | Seagate Support
http://www.seagate.com/support/downloads/seatools/
Boot SeaTools off of a USB Drive | nowhereLAN

Report the results into the thread.

9) The upper portion of the Virtual Memory windows was cut off. Please re-post displaying the uppermost box.

 

Hi Zbook

Thank you for being patient with me, and thank you for all your help so far:

1) Do i need to do anything for this step or is this for my own information ? Is that a good thing?
2) I have disconnected all other drives yesterday, and the BSOD still happens, do i still need to do chkdsk on my other drives?
3) I have completed this step, do i need to show you screenshot, no yellow triangle and black exclamation marks or unknown devices.
4) I have opened my PC, took apart my graphics card, cleaned it, cleaned PCI slot, added new thermal paste, reseated all cables, nothing seems loose. But it was good to do it.
5) Will read those now, I will not use them until you tell me too
6) created restore point (14/4/18 12:28pm NZD time)
7) have nothing to backup as this is a new installation (ready to do anything at this stage)
8) have installed seatools, will start running it now, do i need to do it for all the drives as I can disconnect the others.
Edit: Ran the smart test - passed Long generic test - passed *Smile 1:10pm NZD Time

9) Apologies, have attached a pic for virtual memory now,

Edit: Shall i run the driver verfier now?
Also, googling the error in eventviewer right before my critical error:
File System Filter 'npsvctrig' (10.0, ‎2070‎-‎05‎-‎06T02:38:28.000000000Z) has successfully loaded and registered with Filter Manager.
People are saying its a hardware error.
I have changed powersupply, still same error, I will change videocardtonight with my mate, all else fails then it must be either CPU or Motherboard. (positive that the ram passed but will run it again tonight).

I am really hoping its a driver error

Again, thank you so much for your time.

 

Chkdsk /x /f /r corrected problems with the drive file system. If these types of problems are not fixed there can be problems related to the problematic files. This can include problems with booting.

When possible, especially on HD it is your best interest to perform chkdsk /x /f /r on all drives to scan, fix and restore any drive file system problems. This can be accomplished is most cases by running the command overnight.

Windows driver verifier will repetitively produce BSOD until all misbehaving drivers are fixed or until the tool is turned off.
After each BSOD run the beta log collector to collect new files.
And search for a memory dump file: C:\Windows\memory.dmp > zip > post a share link into the thread

For each dump you should see a windows with : ( and bugcheck. Sometimes a misbehaving driver may displayed in the form *.sys. If you see a misbehaving driver please record it and post it into the thread.

To turn off or recover from Windows driver verifier you will need to use the Windows advanced troubleshooting menu. There are 3 different methods:
1) startup options (not startup repair) > restart > select #6 safe mode with command prompt > type:
verifier /reset
2) command prompt > administrator: X:\windows\system32\cmd.exe > X:\Sources> type:
verifier /bootmode resetonbootfail
3) system restore

The methods to be used to turn off Windows driver verifier should be used in the order above and only advance to the next step if the prior step failed. Using system restore often leads to a loss of the dump file and little progress is made in the troubleshooting.

There may be computer sluggishness or slow boots when using Windows driver verifier. If there are significant problems the test settings can be modified.

Use this link for the customized test settings:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

Use this link for the methods to turn off Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials


Code: Event[790]: Log Name: System Source: volmgr Date: 2018-04-13T22:35:54.462 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Dump file creation failed due to error during dump creation. Event[1259]: Log Name: System Source: volmgr Date: 2018-04-14T16:21:16.259 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Dump file creation failed due to error during dump creation. Event[1329]: Log Name: System Source: volmgr Date: 2018-04-14T18:11:14.680 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Dump file creation failed due to error during dump creation. Event[1628]: Log Name: System Source: volmgr Date: 2018-04-14T21:01:35.712 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Dump file creation failed due to error during dump creation. Event[1697]: Log Name: System Source: volmgr Date: 2018-04-15T00:26:25.212 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Dump file creation failed due to error during dump creation. Event[1784]: Log Name: System Source: volmgr Date: 2018-04-15T08:32:51.290 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Dump file creation failed due to error during dump creation. Event[756]: Log Name: System Source: Disk Date: 2018-04-13T21:38:04.761 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[757]: Log Name: System Source: Disk Date: 2018-04-13T21:38:04.761 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[758]: Log Name: System Source: Disk Date: 2018-04-13T21:38:04.761 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[759]: Log Name: System Source: Disk Date: 2018-04-13T21:38:08.767 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[760]: Log Name: System Source: Disk Date: 2018-04-13T21:38:08.767 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[761]: Log Name: System Source: Disk Date: 2018-04-13T21:38:08.767 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[762]: Log Name: System Source: Disk Date: 2018-04-13T21:38:12.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[763]: Log Name: System Source: Disk Date: 2018-04-13T21:38:12.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[764]: Log Name: System Source: Disk Date: 2018-04-13T21:38:12.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[765]: Log Name: System Source: Disk Date: 2018-04-13T21:38:16.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[766]: Log Name: System Source: Disk Date: 2018-04-13T21:38:16.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[767]: Log Name: System Source: Disk Date: 2018-04-13T21:38:16.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[845]: Log Name: System Source: Disk Date: 2018-04-14T00:18:27.923 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk7\DR7, is not ready for access yet. Event[846]: Log Name: System Source: Disk Date: 2018-04-14T00:18:27.941 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk8\DR8, is not ready for access yet. Event[847]: Log Name: System Source: Disk Date: 2018-04-14T00:18:33.009 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk7\DR7, is not ready for access yet. Event[848]: Log Name: System Source: Disk Date: 2018-04-14T00:18:33.026 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk8\DR8, is not ready for access yet. Event[849]: Log Name: System Source: Disk Date: 2018-04-14T00:18:38.072 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk7\DR7, is not ready for access yet. Event[850]: Log Name: System Source: Disk Date: 2018-04-14T00:18:38.088 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk8\DR8, is not ready for access yet. Event[851]: Log Name: System Source: Disk Date: 2018-04-14T00:18:43.137 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk7\DR7, is not ready for access yet. Event[852]: Log Name: System Source: Disk Date: 2018-04-14T00:18:43.153 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk8\DR8, is not ready for access yet. Event[853]: Log Name: System Source: Disk Date: 2018-04-14T00:18:48.196 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk7\DR7, is not ready for access yet. Event[854]: Log Name: System Source: Disk Date: 2018-04-14T00:18:48.212 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk8\DR8, is not ready for access yet. Event[855]: Log Name: System Source: atapi Date: 2018-04-14T00:18:53.259 Event ID: 143 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The storage device produced an internal dump. Event[856]: Log Name: System Source: Disk Date: 2018-04-14T00:18:53.259 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk7\DR7, is not ready for access yet. Event[857]: Log Name: System Source: Disk Date: 2018-04-14T00:18:53.260 Event ID: 157 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Disk 7 has been surprise removed. Event[858]: Log Name: System Source: atapi Date: 2018-04-14T00:18:53.276 Event ID: 143 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The storage device produced an internal dump. Event[859]: Log Name: System Source: Disk Date: 2018-04-14T00:18:53.276 Event ID: 15 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The device, \Device\Harddisk8\DR8, is not ready for access yet. Event[860]: Log Name: System Source: Disk Date: 2018-04-14T00:18:53.709 Event ID: 157 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: Disk 8 has been surprise removed. Event[756]: Log Name: System Source: Disk Date: 2018-04-13T21:38:04.761 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[757]: Log Name: System Source: Disk Date: 2018-04-13T21:38:04.761 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[758]: Log Name: System Source: Disk Date: 2018-04-13T21:38:04.761 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[759]: Log Name: System Source: Disk Date: 2018-04-13T21:38:08.767 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[760]: Log Name: System Source: Disk Date: 2018-04-13T21:38:08.767 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[761]: Log Name: System Source: Disk Date: 2018-04-13T21:38:08.767 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[762]: Log Name: System Source: Disk Date: 2018-04-13T21:38:12.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[763]: Log Name: System Source: Disk Date: 2018-04-13T21:38:12.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[764]: Log Name: System Source: Disk Date: 2018-04-13T21:38:12.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[765]: Log Name: System Source: Disk Date: 2018-04-13T21:38:16.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried. Event[766]: Log Name: System Source: Disk Date: 2018-04-13T21:38:16.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried. Event[767]: Log Name: System Source: Disk Date: 2018-04-13T21:38:16.806 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Ayman-PC Description: The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried. Event[991]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-04-14T08:39:26.730 Event ID: 21 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: Ayman-PC Description: A corrected hardware error has occurred. Component: AMD Northbridge Error Source: Corrected Machine Check Error Type: 28 Processor APIC ID: 0 The details view of this entry contains further information.[/quote]

 

Hey mate, good news, its been 2 days without any freezes. I have no idea what might of sorted it out, will keep this post open for now and mark it when its 1 week steady. It might be the "Correcting errors in the master file table's (MFT) BITMAP attribute."

 

There were problems creating dump files.
Using Windows driver verifier may create BSOD dump files and find misbehaving drivers.
If there are no BSOD with Windows driver verifier in use for 48 hours that would be useful in evaluating the drivers.
It would be useful to have some mini dumps or memory dump files to debug as there were driver problems reported in the logs.

 

I will use driver verifier, spoke too soon too. Was watching an anime online and comp just froze (with a weird buzzing noise from the sound coming from the PC speakers), no BSOD as well, had to restart so got an error 41. Its frustrating, I have no idea why my computer is not creating a minidump or a dump or why there is no BSOD.

 

Hi guys

Have ran driver verifier, immediatly got a IRP stack overflow error and then got a BSOD everytime before window starts, went back to my restore point beforehand as I could not start windows again. Now, i have uploaded the crash dump because finally it gave me one. Furthermore, the crashes seem to happen 1 hour or 2 hours exactly after computer is put on idle (keep in mind that the power mode is on performance). attached is the log colllector beta 2

 

Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > zip > post a one drive or drop box share link into the thread
So far there has only been 1 mini dump file for debugging with Windows driver verifier.
Please post multiple dump files.
Using system restore often leads to a loss of the dump file.
What happens with startup options?
What happens with bootmode?


The misbehaving driver identified in the debugging was: covefs.sys
Name Covecube Disk Enumerator
Manufacturer Covecube Inc.
PNP Device ID ROOT\SCSIADAPTER\0000
Driver c:\windows\system32\drivers\covefs_disk.sys (2.0.61.0, 55.10 KB (56,424 bytes), 29/09/2017 12:00 AM)

Please update the Covecube drivers:

Code: covefs CoveFS \??\c:\windows\system32\drivers\covefs.sys File System Driver Yes System Running OK Ignore No Yes[/quote] Code: covefsdisk CoveFSDisk c:\windows\system32\drivers\covefs_disk.sys Kernel Driver Yes Manual Running OK Normal No Yes[/quote]

 

Ok, drivepool (software using this driver) has already been updated to the newest build. I have 1 new minidump (Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.) but the others have been wiped, but whocrashed has managed to catch them (please note, I have taken out my graphics card, used DDU in safe mode to uninstall the drive, now trying out a nvidia based card, but it crashed before I could install the drive):

Crash Dump Analysis
Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump
C:\Windows\LiveKernelReports

On Wed 25/04/2018 1:52:20 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042518-24296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0xD1 (0xFFFFF803B5AC23DF, 0x2, 0x8, 0xFFFFF803B5AC23DF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 25/04/2018 1:52:20 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x83D9)
Bugcheck code: 0xD1 (0xFFFFF803B5AC23DF, 0x2, 0x8, 0xFFFFF803B5AC23DF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 25/04/2018 9:34:05 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\win32kbase.sys-20180425-0934.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoUnregisterShutdownNotification+0xBBE)
Bugcheck code: 0x164 (0xF, 0xFFFFC78310A18700, 0xF, 0x0)
Error: WIN32K_CRITICAL_FAILURE
Bug check description: This indicates that Win32k has encountered a critical failure. This may be caused by your graphics driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 25/04/2018 9:34:05 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\win32kbase.sys\win32kbase.sys-20180425-0934.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x425B4E)
Bugcheck code: 0x164 (0xF, 0xFFFFC78310A18700, 0xF, 0x0)
Error: WIN32K_CRITICAL_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Win32k has encountered a critical failure. This may be caused by your graphics driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

For all BSOD please run the beta log collector so that all log files are updated with each BSOD dump file.
Open file explorer > this PC > C: > in the right upper corner search for C:Windowsmemory.dmp > zip > post a one drive or drop box share link into this thread.

Commands are run on the mini and memory dumps. This provides deeper debugging than Whocrashed. This little that can done with a txt file unless it displays a misbehaving driver but often the misbehaving drivers are found using the commands. So it is important to have the files for the debugging.

Covecube Disk Enumerator software and its drivers (covefs_disk.sys, covefs.sys) were not in our driver database. Sometimes we submit drivers to update the database. What information do you have for the software and drivers?

 

oh sorry, all done *Smile

I have changed graphics card completly as well

 

See if you can find this memory dump file > zip > post into the thread using one drive or drop box:
Crash dump found at C:\Windows\MEMORY.DMP
Creation date: 04/25/2018 13:54:57
Size on disk: 583 MB


Code: 24/04/2018 8:43 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 35 P2: ffffc2020e0c6c10 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\042418-22906-01.dmp \\?\C:\Windows\TEMP\WER-94250-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9371.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9382.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER93B2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_35_2d789d2275c5d137844152ea6f543da11e651e31_00000000_cab_03e993bf Analysis symbol: Rechecking for solution: 0 Report Id: 28a086b5-2ac5-4651-aa7a-e390d0f5a0aa Report Status: 4 Hashed bucket:25/04/2018 1:55 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: d1 P2: fffff803b5ac23df P3: 2 P4: 8 P5: fffff803b5ac23df P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\042518-24296-01.dmp \\?\C:\Windows\TEMP\WER-75359-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36EA.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36EB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER370C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_844d4af59f821be335678899505732d2d228e510_00000000_cab_03b93709 Analysis symbol: Rechecking for solution: 0 Report Id: 40941a2d-c067-424e-bc8d-2dbe5afe7e89 Report Status: 4 Hashed bucket:[/quote] Code: 24/04/2018 8:43 AM Windows Error Reporting Fault bucket 0x35_VRF_disk!DiskDeviceControl, type 0 Event Name: BlueScreen Response: Not available Cab Id: 536b71c3-1bb1-417e-8842-1651f3fc4ee5 Problem signature: P1: 35 P2: ffffc2020e0c6c10 P3: 0 P4: 0 P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\042418-22906-01.dmp \\?\C:\Windows\TEMP\WER-94250-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9371.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9382.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER93B2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_35_2d789d2275c5d137844152ea6f543da11e651e31_00000000_cab_33a1de74 Analysis symbol: Rechecking for solution: 0 Report Id: 28a086b5-2ac5-4651-aa7a-e390d0f5a0aa Report Status: 268435456 Hashed bucket:[/quote] Code: 25/04/2018 1:56 AM Windows Error Reporting Fault bucket AV_CODE_AV_BAD_IP_nt!KiRemoveTimer2, type 0 Event Name: BlueScreen Response: Not available Cab Id: f5d46853-98a5-436c-992d-3ea2dc3d4610 Problem signature: P1: d1 P2: fffff803b5ac23df P3: 2 P4: 8 P5: fffff803b5ac23df P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\042518-24296-01.dmp \\?\C:\Windows\TEMP\WER-75359-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36EA.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36EB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER370C.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_844d4af59f821be335678899505732d2d228e510_00000000_cab_1f69847d Analysis symbol: Rechecking for solution: 0 Report Id: 40941a2d-c067-424e-bc8d-2dbe5afe7e89 Report Status: 268435456 Hashed bucket:25/04/2018 1:56 AM Windows Error Reporting Fault bucket LKD_0x164_win32kbase!HMUnlockObjectInternal, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 54f9dffd-feda-44e0-a13c-e5b4329ee10a Problem signature: P1: 164 P2: f P3: ffffc78310a18700 P4: f P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\LiveKernelReports\win32kbase.sys\win32kbase.sys-20180425-0934.dmp \\?\C:\Windows\TEMP\WER-75359-0.sysdata.xml \\?\C:\Windows\LiveKernelReports\win32kbase.sys-20180425-0934.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER368C.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36AB.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36CB.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_164_efd78b181ed04e50c6a0a67a9eeabd66868d7f2d_00000000_cab_1f695d6d Analysis symbol: Rechecking for solution: 0 Report Id: e55b4a20-80bb-4e39-876f-cf648a4a3e0a Report Status: 268435456 Hashed bucket:[/quote]

 

Ahhh, sorry, found it, here it is: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.