Windows 10: BSOD Windows 10 1703 When creating system image

The last bsod in the logs was 6/9/2017.
Were there any bsod while using Windows driver verifier?

 

It appears there have been an unexpected shutdown 2 days ago, I don't assume you're aware of it?
Code: Event[4194]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-06-10T02:07:30.224 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-NGQE08I Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote]

 

Hi zbook

(On the first day of the two days while running verifier)
There where a couple but the wierd thing is when it bsod those two times i was watching a episode on vlc player and when the blue screen came up it ended the blue screen really quick it was that quick i couldn't even see the error code.
This wasn't like the other times when it sits there for say 10 - 15 seconds collecting data and then reboots.

(Second day)
Watched about 6 episodes on vlc and it was perfectly fine.

 

Hi Axe0

No sorry didn't know about that one just the stuff i mentioned to zbook in my last post.

I just don't understand why they are so random and why it will not create a system image without bsod.

 

When using windows driver verifier please turn off automatic reboot so that you can view the stop code. Most often the stop code is driver verifier detected violation. More important though is that it may display the misbehaving driver with *.sys.
Whenever you experience a bsod using windows driver verifier please record the misbehaving driver and post into the forum.

See this link to uncheck automatic restart:
BSOD Finding and fixing them - Microsoft Community

The last bsod in the log was 6/4/2017.
Please update your initial zip log or post a new log for the bsod while using windows driver verifier.

 

If driver verifier didn't catch a driver, no BSOD occured. It isn't useful to run driver verifier again since there have been multiple attempts to run driver verifier hoping it would crash the system.

Based on the chkdsk logs, run follow tests on each partition / drive.







Diagnostics Test

HDD TEST
*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*Arrow Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
*Arrow Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

 

The last bsod minidump was on 6/7. The last 3 dumps indicated memory. The memory has passed the memtest86+. It seems like there were only a small number of non-Microsoft drivers that were checked during runs of windows driver verifier. If you continue to have bsod and if the HD and chkdsk don't yield the malfunctioning hardware or misbehaving driver another run of windows driver verifier testing all non-Microsoft drivers may provide information. Please keep us informed about any new bsod as you are performing HD tune and chkdsk.

 

Hi guys sorry for the late reply these took a while plus i had 2 Bsod while on desktop updated logs below.

Just done the the hard drives tests these are the results images below thanks again Axe0,Zbook.
Attachment 139405 Attachment 139406 Attachment 139407

Attachment 139408 Attachment 139409 Attachment 139410

Attachment 139411 Attachment 139412 Attachment 139413

Attachment 139414 Attachment 139415 Attachment 139416

Attachment 139417 Attachment 139418 Attachment 139419

Attachment 139420 Attachment 139476 Attachment 139421

 

Code: BugCheck 1000007E, {ffffffffc0000005, fffff802ab711c50, ffffda8179416678, ffffda8179415eb0} Probably caused by : memory_corruption[/quote] Code: BugCheck 1000007E, {ffffffffc0000005, fffff803250f8c50, ffffde80f103c678, ffffde80f103beb0} Probably caused by : memory_corruption[/quote] Code: BugCheck 1000007E, {ffffffffc0000005, fffff8037cc87c50, ffffc680a0b946b8, ffffc680a0b93ef0} Probably caused by : memory_corruption[/quote] Was the memtest you had ran memtest or memtest86+?
With 3/3 new bsod minidumps in 2 days that were memory lets make another test of the memory.
Please use memtest86+


Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.
Memtest86+ - Advanced Memory Diagnostic Tool

On the 1500GB drive run chkdsk /x /f /r (this may take many hours, plan to run overnight)

 

What case do you have?
The HDD temps may be a risk, it could result in physical damage.


Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

 

Hi guys

Axe0 i have a cooler master cosmos 1 case i will fill the specs of my computer in later tonight or tomorrow i have to go out in a mo.

Zbook i will run memtest86+ over night sry it was the other memtest i ran first didn't realise there where two.

On the 1500GB drive run chkdsk /x /f /r
I tried this in admin comand promt i put g where the x is but it says invalid parameter - /g

 

When you open file explorer you can view the drive letter assigned to each drive. For the chkdsk syntax if the problematic drive is g use this command in administrative command prompt: chkdsk G: /x /f /r

 

/f is a parameter that is already included twice....
I am wondering zbook, what is the reason for suggesting /f /r and /x whilst I've been trying to explain this a few times.

Just run chkdsk G: /r /x

 

The syntax allow both to be used to get the same result. It's out of habit.
If /r has it disregard the /f switch then its the same. If /f makes it run the same process again that its consuming unnecessary time. I was not able to find that information and understand your comment.
/r Locates bad sectors and recovers readable information. The disk must be locked. /r includes the functionality of /f, with the additional analysis of physical disk errors.
/x Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated. /x also includes the functionality of /f.

 

Hi guys

Have run memtest again so that will be about 12 passes with both memtests and 0 errors.
Attachment 139586

I have took both seagate drives out of the system for now to see if it is ok for a while as i was transfering a couple of files from the one of them drives to my 4tb hitachi one and it bsod again twice.

Ive updated system spec also.

updated logs below.

Thanks again Axe0,Zbook.

.