BSODs at random times (no particular program used)

CaliByWayOfKS · 07 Jul 2017

Hello there,

On June 3rd, 2017 my Dell XPS got its first BSOD and I didn't think much of it due to the fact that the BSOD was so fast that I couldn't even catch what the particular error was. Unfortunately it has occured 11 more times since that day and the Windows 10 troubleshooters find no errors or etc.

*Each time the error occured I was either in the room not touching the computer and I saw it flash the BSOD or I was using a different program or just browsing the internet (chrome, itunes, microsoft excel, and etc).*

I then did some searching online and found that I could get some more potential information in the "event viewer" feature in Windows 10, which listed "Event 41, Kernel-Power, Task Category (63)". I then contacted Windows Support which first asked me if I was on a computer that was taken from Windows 8 to Windows 10, which I informed them no and that my computer started with Windows 10. After they did some searching based on what I told them I was informed my error was due to display drivers. So was told I needed to uninstall both of them and restart my computer and my problem would be fixed.

Unfortunately that didn't fix my issue, so they told me that the issue would be my power supply... since it wasn't plugged into the power supply when the error occurred that also was incorrect. They had me change a few settings in the power management settings and was told to observe over the weekend. However I just go the error again so I thought I would post here in case someone else might have any thoughts or etc.

Some other information would be that under "Event Viewer" I could click on the tab for details and this was what was listed below.

BugcheckCode 340
BugcheckParameter1 0xffffd4813198e000

The other BugcheckParameters only listed "0x0"

Hopefully someone may have some insight to what my issue is perhaps. I did the log collector, but on my screen I didn't have anything listed in the "mini dump files" as the video example did so I hope that doesn't cause an issue with potential trouble shooting (I haven't cleared anything or etc so everything should still be there).

Thanks in advance.

zbook · 07 Jul 2017

Code:

Dump file creation failed due to error during dump creation.

Code:

The IO operation at logical block address 0x654aac02 for Disk 1 (PDO name: \Device\00000070) failed due to a hardware error.

Code:

The IO operation at logical block address 0x654ab402 for Disk 1 (PDO name: \Device\00000070) failed due to a hardware error.

Code:

Dump file creation failed due to error during dump creation.

Code:

The driver detected a controller error on \Device\Harddisk1\DR1.

Code:

The driver detected a controller error on \Device\Harddisk1\DR2.

Code:

An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

In your logs there were numerous crashes.
There were no *.dmp files within the logs
There were numerous error codes within the logs displaying: Dump file creation failed due to error during dump creation.

Open administrative command prompt and type or copy and paste:

1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

2) sfc /scannow

3) dism /online /cleanup-image /restorehealth

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread

4) chkdsk /x /r (this may take many hours to run so plan to run this command overnight)
When it completes please post the results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

5) run on the SMART tests on your drive:
CrystalDiskInfo - Software - Crystal Dew World
http://www.hdtune.com/
Hard Disk Sentinel - HDD health and temperature monitoring
When the test has completed please use the Microsoft snipping tool to post images into the thread.

6) run Sea tools for windows in SMART, short and long generic tests and post results into the thread
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows

7) Check the current settings for memory dumps:
Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > use the Microsoft sniping tool and post an image into the thread

After you post the image please change the settings to:
check: write an event to the system log
uncheck: automatically restart
write debugging information: automatic memory dump
dump file: %SystemRoot%\MEMORY.DMP
check: overwrite any existing file
uncheck: disable automatic deletion of memory dumps when disk space is low

See this link: BSOD Finding and fixing them - Microsoft Community: BSOD Finding and fixing them - Microsoft Community

8) download and install Whocrashed: http://www.resplendence.com/whocrashed
Click: analyze
post any dump results into the thread
Click tools > crash dump test > type ACCEPT > see if a dump was created and analyzed and report results into the thread

CaliByWayOfKS · 07 Jul 2017

Question, for Step 5 is that any of those 3 particular links give you the SMART tests? I must admit I'm completely unfamiliar with what a SMART test is. Also what is the "Microsoft snipping tool" that I use for the images? Would just doing a screencap with print screen and then just editing down to just the size of the SMART test work as well?

Some of the above will go with Step 6, but I'm proceeding with the rest currently and hope to be finished and posting today.

zbook · 07 Jul 2017

There were 3 software options listed to run a SMART test on your drive. Pick one of them to run a free test in extensive or detailed fashion and post images into the thread.
For images you can use Microsoft paint or Microsoft snipping tool.

CaliByWayOfKS · 07 Jul 2017

Understood, I tried the HD Tune Pro link, but it never populates anything in the "health" tab (completely blank). I cannot even select items under the "info" tab either.

So I'm at a loss as to why it won't work.

CaliByWayOfKS · 07 Jul 2017

Windows 10 - Version 1703 - OS Build 15063.447

Windows PowerShellCopyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> winver
PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.

Windows PowerShellCopyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message

PS C:\WINDOWS\system32>

TimeCreated : 7/7/2017 2:58:23 PM
Message :

Checking file system on C: The type of the file system is NTFS. Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ... Cleaning up instance tags for file 0x664c. Cleaning up instance tags for file 0x1422f. 360192 file records processed. File verification completed. 6805 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ... 448652 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ... Cleaning up 4525 unused index entries from index $SII of file 0x9. Cleaning up 4525 unused index entries from index $SDH of file 0x9. Cleaning up 4525 unused security descriptors. CHKDSK is compacting the security descriptor stream Security descriptor verification completed. 44231 data files processed. CHKDSK is verifying Usn Journal... Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ... 360176 files processed. File data verification completed.
Stage 5: Looking for bad, free clusters ... 92174832 free clusters processed. Free space verification is complete. Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system. No further action is required.

486823213 KB total disk space.
117558724 KB in 182245 files.
120668 KB in 44234 indexes.
0 KB in bad sectors.
444489 KB in use by the system.
65536 KB occupied by the log file.
368699332 KB available on disk.
4096 bytes in each allocation unit.
121705803 total allocation units on disk.
92174833 allocation units available on disk.

Internal Info: 00 7f 05 00 48 74 03 00 7a 98 06 00 00 00 00 00 ....Ht..z....... 3e 07 00 00 85 00 00 00 00 00 00 00 00 00 00 00 >...............

Windows has finished checking your disk. Please wait while your computer restarts.

PS C:\WINDOWS\system32>

--------------- SeaTools for Windows v1.4.0.4 ---------------
7/7/2017 4:02:25 PM
Model Number: PM951 NVMe SAMSU
Serial Number: 8F67_B56
Firmware Revision: BXV7
Inquiry - Started 7/7/2017 4:02:25 PM
Short Generic - Started 7/7/2017 4:03:33 PM
Short Generic - Pass 7/7/2017 4:04:26 PM
Inquiry - Started 7/7/2017 4:05:38 PM
Vendor ID: NVMe Model Number: PM951 NVMe SAMSU
Serial Number: 8F67_B56
Firmware Revision: BXV7
Copyright: Drive Capacity: 512.11 GB / 476.94 GiB
Max LBA: 1000215215
Power-On Hours: 0
Drive Temperature (C/F): 1 / 34
WWN: 60025388F67B5614
Sector size (Logical/Physical): 512 / ----
Rotation rate: Solid State Drive
Form factor: Unknown
Specification Supported: SPC-4
Additional Specifications Supported:
Percentage Used Endurance Indicator (%): -1
Encryption Support: Not Supported
SCSI Firmware Release Number:
Servo RAM Release Number:
Servo ROM Release Number:
Servo RAM Release Date:
Servo ROM Release Date:
Hours Since Last DST: 0
Long Generic - Started 7/7/2017 4:06:23 PM
Long Generic - Pass 7/7/2017 4:28:20 PM
Short Generic - Started 7/7/2017 4:29:06 PM
Short Generic - Pass 7/7/2017 4:29:58 PM

zbook · 07 Jul 2017

Were you able to run the Sea Tools SMART test?

Chkdsk did some repairs: Correcting errors in the Volume Bitmap. Windows has made corrections to the file system.

Chose one of the other SMART software programs so that you have images and data that you save and use to follow trends over time.

Uncheck automatic restart so that you have time to view the windows bsod screen.

CaliByWayOfKS · 07 Jul 2017

Yes the Sea Tools is in the text above, but when I copy and pasted it all from a text file I saw it looked crazy so I was trying to readjust everything so that it was readable, but missed readjusting the Sea Tools part. Here it is again below.

--------------- SeaTools for Windows v1.4.0.4 ---------------
7/7/2017 4:02:25 PM
Model Number: PM951 NVMe SAMSU
Serial Number: 8F67_B56
Firmware Revision: BXV7
Inquiry - Started 7/7/2017 4:02:25 PM
Short Generic - Started 7/7/2017 4:03:33 PM
Short Generic - Pass 7/7/2017 4:04:26 PM
Inquiry - Started 7/7/2017 4:05:38 PM
Vendor ID: NVMe Model Number: PM951 NVMe SAMSU
Serial Number: 8F67_B56
Firmware Revision: BXV7
Copyright: Drive Capacity: 512.11 GB / 476.94 GiB
Max LBA: 1000215215
Power-On Hours: 0
Drive Temperature (C/F): 1 / 34
WWN: 60025388F67B5614
Sector size (Logical/Physical): 512 / ----
Rotation rate: Solid State Drive
Form factor: Unknown
Specification Supported: SPC-4
Additional Specifications Supported:
Percentage Used Endurance Indicator (%): -1
Encryption Support: Not Supported
SCSI Firmware Release Number:
Servo RAM Release Number:
Servo ROM Release Number:
Servo RAM Release Date:
Servo ROM Release Date:
Hours Since Last DST: 0
Long Generic - Started 7/7/2017 4:06:23 PM
Long Generic - Pass 7/7/2017 4:28:20 PM
Short Generic - Started 7/7/2017 4:29:06 PM
Short Generic - Pass 7/7/2017 4:29:58 PM

CaliByWayOfKS · 07 Jul 2017

After re-reading your question I notice you mention the SMART test again, I don't see that as an option unfortunately.

All I see is "basic tests" with "drive information", "short generic", and "long generic".

Here is the WhoCrashed info as well.

zbook · 07 Jul 2017

Attachment 142940

For whocrashed was that the analyze before or after the test bsod dump?