Solved Experiencing BSoD Randomly

[patch1334]

Hello,

I have been getting blue screen on this PC about once a week for the past 3 weeks. Any help to find out a possible cause would be much appreciated:

PC specs

Model: HP EliteDesk 800 G1
CPU: Intel i5 2GHz
RAM: 4GB
HDD: 500GB Sata

I've attached the ZIP file from DM Collector.
Thanks in advance!

 

[axe0]

1 of the crashes was unable to create a dump file.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 7 tutorial

Event[45068]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2016-01-29T13:47:55.000
  Event ID: 1005
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: ABE1123.global.ad
  Description: 
[COLOR="Red"]Unable to produce a minidump file from the full dump file[/COLOR].

The saved dump is a 0x7A, pointing to hard drive problems

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

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

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

I/O errors

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
[COLOR="red"]If the error status is [U]0xC000000E[/U], 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.[/COLOR]
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c04607b0, lock type that was held (value 1,2,3, or PTE address)
Arg2: [COLOR="Red"]c000000e[/COLOR], [COLOR="red"]error status (normally i/o status code)[/COLOR]
Arg3: 2db77860, current process (virtual address for lock type 3, or PTE)
Arg4: 8c0f6223, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

NTFS corruption

CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
    8c0f6000-8c0f65d6  1495 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+d17
	[ 81 fa 03 07 00 00 74 13:d2 2a a8 05 28 5b ac 0d ]
    8c0f65d8-8c0f66ce  247 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+12ef (+0x5d8)
	[ e9 72 ed ff ff 8d 41 08:84 3c 79 20 62 d9 06 1f ]
    8c0f66d0-8c0f670a  59 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+13e7 (+0xf8)
	[ d1 eb 12 3b 50 04 73 1a:88 a8 76 22 02 cb 48 10 ]
    8c0f670c-8c0f685c  337 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+1423 (+0x3c)
	[ e9 d8 f1 ff ff 83 c3 08:d6 e5 5e 01 4e bc 0d 14 ]
    8c0f685e-8c0f6a43  486 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+1575 (+0x152)
	[ 50 08 83 c2 18 3b fa 76:7a 13 00 cf e3 04 3e f1 ]
    8c0f6a45-8c0f6ac0  124 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+175b (+0x1e7)
	[ 53 ff 75 10 ff 75 0c ff:9e 6c 08 c4 52 62 18 ee ]
    8c0f6ac2-8c0f6bce  269 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+17d8 (+0x7d)
	[ 10 eb 02 33 d2 81 fa 04:cb 0f 94 44 0c 11 16 43 ]
    8c0f6bd0-8c0f6be4  21 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+18e6 (+0x10e)
	[ 3b 41 0c 7f 11 0f 8c c7:a0 7d 73 17 5e 97 bd 0d ]
    8c0f6be6-8c0f6c40  91 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+18fc (+0x16)
	[ 8d 45 dc 50 53 51 ff 75:4b 01 aa 0a 67 02 d2 2c ]
    8c0f6c42-8c0f6c81  64 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+1958 (+0x5c)
	[ 7d 24 72 de 3b d0 0f 85:41 1d 16 06 40 06 c8 5e ]
    8c0f6c83-8c0f6dd2  336 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+1999 (+0x41)
	[ 08 74 0e 0f b7 59 08 03:10 40 3a ca 17 ba 17 c0 ]
    8c0f6dd4-8c0f6e46  115 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+1aea (+0x151)
	[ 8b 55 14 3b 42 1c 73 15:e8 31 4f 07 b8 9d 41 1f ]
    8c0f6e48-8c0f6eee  167 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+1b5e (+0x74)
	[ 50 ff 15 5c a6 04 8c 89:f0 40 3e 0c 86 68 d2 11 ]
    8c0f6ef0-8c0f6fff  272 bytes - [COLOR="red"]Ntfs[/COLOR]!DoAction+1c06 (+0xa8)
	[ 00 75 6a 03 c1 0f b7 48:04 ab ca 12 8c 16 4a 21 ]
4083 errors : !Ntfs (8c0f6000-8c0f6fff)

 

[patch1334]

Hi,

Appreciate the support. I've now carried out the tests below:

SeaTools (All 3 tests passed successfully)
Chkdsk (Log attached)
HDTune (Screenshots below)

From what I can see, the tests don't seem to show any major failures. Could this relate to an OS file system issue?
Thanks

HDTune Error Scan

HDTune Health

HDTune Benchmark

 

[axe0]

Keep me posted on the situation

Windows has made corrections to the file system.

 

[patch1334]

Perfect, didn't notice that - thanks axe0. I'll mark this as Solved if there isn't another BSOD in the next week or so