BSOD while Win7 64-Bit is idle or various times (BCCode: 7a)

I have been having blue screens for a couple months now and have been trying to figure out why. The BSOD varies but typically was the STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL.

They started after I got better compatible RAM (went from 4Gb to 8Gb) so I have went back to the 4Gb. But the RAM tested out fine (7 passes each stick with MemTest 86+ no problems) and I have gotten a blue screen again yesterday. It was STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 4105

Additional information about the problem:
BCCode: 7a
BCP1: FFFFF6FC40008690
BCP2: FFFFFFFFC0000185
BCP3: 0000000108289860
BCP4: FFFFF880010D293C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Hello kabo0m.

Hum this might be a problem, on HP's support site there isn't an option for selecting Windows 7 so drivers might become an issue especially when the required driver is for the SATA controller.

You could also try and use HP's identify drivers tools and see if it would pick up anything needed:

Automatically Find HP Updates

Cheers, Boris :)

BorisTheAnimal said:

Hello kabo0m.

Hum this might be a problem, on HP's support site there isn't an option for selecting Windows 7 so drivers might become an issue especially when the required driver is for the SATA controller.

You could also try and use HP's identify drivers tools and see if it would pick up anything needed:

Automatically Find HP Updates

Cheers, Boris :)

Thanks. Trying that now. Is that what caused the Blue Screen?

Is that what caused the Blue Screen?

Not exactly (apologies for bumping in).

I have analysed the dump, because I couldn't recall the exact error status codes from the 0x7A that leads to hard drive problems but it seems my guess is correct.
Below I have marked a few things red, it means that there are problems with reading data from the hard drive what could be caused by a few things

1. The drivers of the IDE controller is outdated/corrupted
2. The hard drive is failing
3. The cable needs replacement
4. The connection on the motherboard is the problem in which you would have to get a new motherboard.

Further there is also some corruption with a system driver.
Please follow below suggestions and let us know what the results of the tests are.

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.

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc40008690, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 0000000108289860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880010d293c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)




CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
    fffff880010d2000-fffff880010d2007  8 bytes - ataport!DeviceAtaPassThroughIoctl+1a0
	[ 85 4a 08 75 b3 83 7a 0c:00 00 00 00 00 00 00 00 ]
    fffff880010d2009-fffff880010d2010  8 bytes - ataport!DeviceAtaPassThroughIoctl+1a9 (+0x09)
	[ 74 ad 81 7a 0c e0 a5 01:00 00 00 00 00 00 00 00 ]
    fffff880010d2012-fffff880010d2047  54 bytes - ataport!DeviceAtaPassThroughIoctl+1b2 (+0x09)
	[ 77 a4 3b f7 76 10 2b f7:00 00 00 00 00 00 00 00 ]
    fffff880010d204b-fffff880010d2090  70 bytes - ataport!DeviceAtaPassThroughIoctl+1eb (+0x39)
	[ 48 8b d3 e8 4d 50 ff ff:00 00 00 00 00 00 00 00 ]
    fffff880010d2093-fffff880010d209c  10 bytes - ataport!DeviceAtaPassThroughIoctl+233 (+0x48)
	[ 0f 87 1f ff ff ff 41 b8:00 00 00 00 00 00 00 00 ]
    fffff880010d209f-fffff880010d20ae  16 bytes - ataport!DeviceAtaPassThroughIoctl+23f (+0x0c)
	[ 8b c2 c1 ea 0c 41 23 c8:00 00 00 00 00 00 00 00 ]
    fffff880010d20b1-fffff880010d20ba  10 bytes - ataport!DeviceAtaPassThroughIoctl+251 (+0x12)
	[ c1 e9 0c 03 ca 41 3b 8e:00 00 00 00 00 00 00 00 ]
    fffff880010d20bd-fffff880010d20d6  26 bytes - ataport!DeviceAtaPassThroughIoctl+25d (+0x0c)
	[ 0f 87 f5 fe ff ff 33 c9:00 00 00 00 00 00 00 00 ]
    fffff880010d20d9-fffff880010d20dc  4 bytes - ataport!DeviceAtaPassThroughIoctl+279 (+0x1c)
	[ c0 e9 55 01:00 00 00 00 ]
    fffff880010d20df-fffff880010d20e2  4 bytes - ataport!DeviceAtaPassThroughIoctl+27f (+0x06)
	[ 4c 89 b8 80:00 00 00 00 ]
    fffff880010d20e6-fffff880010d2137  82 bytes - ataport!DeviceAtaPassThroughIoctl+286 (+0x07)
	[ 4c 89 70 08 4c 89 70 10:00 00 00 00 00 00 00 00 ]
    fffff880010d213a-fffff880010d213c  3 bytes - ataport!DeviceAtaPassThroughIoctl+2da (+0x54)
	[ c0 e9 e4:00 00 00 ]
    fffff880010d2140-fffff880010d2150  17 bytes - ataport!DeviceAtaPassThroughIoctl+2e0 (+0x06)
	[ 4c 8b 64 24 30 4c 8b c6:00 00 00 00 00 00 00 00 ]
    fffff880010d2153-fffff880010d215a  8 bytes - ataport!DeviceAtaPassThroughIoctl+2f3 (+0x13)
	[ 41 3b c6 8b d8 0f 8c c6:00 00 00 00 00 00 00 00 ]
    fffff880010d215e-fffff880010d2178  27 bytes - ataport!DeviceAtaPassThroughIoctl+2fe (+0x0b)
	[ 48 8b d6 49 8b cf e8 9b:00 00 00 00 00 00 00 00 ]
    fffff880010d217b-fffff880010d2184  10 bytes - ataport!DeviceAtaPassThroughIoctl+31b (+0x1d)
	[ 24 5f 3c 03 75 12 8a 86:00 00 00 00 00 00 00 00 ]
    fffff880010d2187-fffff880010d218d  7 bytes - ataport!DeviceAtaPassThroughIoctl+327 (+0x0c)
	[ 88 47 2e 8a 86 ec 03:00 00 00 00 00 00 00 ]
    fffff880010d2190-fffff880010d2197  8 bytes - ataport!DeviceAtaPassThroughIoctl+330 (+0x09)
	[ 88 47 28 48 8b 86 18 04:00 00 00 00 00 00 00 00 ]
    fffff880010d219a-fffff880010d21a2  9 bytes - ataport!DeviceAtaPassThroughIoctl+33a (+0x0a)
	[ 49 3b c6 74 1f 80 be f1:00 00 00 00 00 00 00 00 ]
    fffff880010d21a5-fffff880010d21a9  5 bytes - ataport!DeviceAtaPassThroughIoctl+345 (+0x0b)
	[ 10 72 16 48 8b:00 00 00 00 00 ]
    fffff880010d21ab-fffff880010d21b3  9 bytes - ataport!DeviceAtaPassThroughIoctl+34b (+0x06)
	[ 48 89 47 28 48 8b 86 18:00 00 00 00 00 00 00 00 ]
    fffff880010d21b6-fffff880010d21c7  18 bytes - ataport!DeviceAtaPassThroughIoctl+356 (+0x0b)
	[ 48 8b 48 08 48 89 4f 20:00 00 00 00 00 00 00 00 ]
    fffff880010d21c9 - ataport!DeviceAtaPassThroughIoctl+369 (+0x13)
	[ 04:00 ]
    fffff880010d21cc-fffff880010d2205  58 bytes - ataport!DeviceAtaPassThroughIoctl+36c (+0x03)
	[ 89 47 08 41 80 fd 01 74:00 00 00 00 00 00 00 00 ]
    fffff880010d2209-fffff880010d2241  57 bytes - ataport!DeviceAtaPassThroughIoctl+3a9 (+0x3d)
	[ 48 8b cb e8 8f 4e ff ff:00 00 00 00 00 00 00 00 ]
    fffff880010d2244-fffff880010d2285  66 bytes - ataport!DeviceAtaPassThroughIoctl+3e4 (+0x3b)
	[ 49 3b ce 74 08 33 d2 ff:00 00 00 00 00 00 00 00 ]
    fffff880010d2288-fffff880010d2292  11 bytes - ataport!IdeInitAtaPassThroughIrb+24 (+0x44)
	[ 48 8b fa 48 8b e9 45 88:00 00 00 00 00 00 00 00 ]
    fffff880010d2295-fffff880010d2298  4 bytes - ataport!IdeInitAtaPassThroughIrb+31 (+0x0d)
	[ 8a 81 58 04:00 00 00 00 ]
    fffff880010d229b-fffff880010d229f  5 bytes - ataport!IdeInitAtaPassThroughIrb+37 (+0x06)
	[ 41 88 80 ee 03:00 00 00 00 00 ]
    fffff880010d22a2-fffff880010d22a5  4 bytes - ataport!IdeInitAtaPassThroughIrb+3e (+0x07)
	[ 8a 81 59 04:00 00 00 00 ]
    fffff880010d22a8-fffff880010d22ac  5 bytes - ataport!IdeInitAtaPassThroughIrb+44 (+0x06)
	[ 41 88 80 ef 03:00 00 00 00 00 ]
    fffff880010d22af-fffff880010d22b6  8 bytes - ataport!IdeInitAtaPassThroughIrb+4b (+0x07)
	[ 8b 42 0c 41 89 80 fc 03:00 00 00 00 00 00 00 00 ]
    fffff880010d22b9-fffff880010d22c3  11 bytes - ataport!IdeInitAtaPassThroughIrb+55 (+0x0a)
	[ f6 42 02 02 74 08 41 83:00 00 00 00 00 00 00 00 ]
    fffff880010d22c6-fffff880010d22d2  13 bytes - ataport!IdeInitAtaPassThroughIrb+62 (+0x0d)
	[ 40 f6 42 02 04 74 09 41:00 00 00 00 00 00 00 00 ]
    fffff880010d22d5-fffff880010d22e0  12 bytes - ataport!IdeInitAtaPassThroughIrb+71 (+0x0f)
	[ 07 f6 42 02 08 74 08 41:00 00 00 00 00 00 00 00 ]
    fffff880010d22e3-fffff880010d22ee  12 bytes - ataport!IdeInitAtaPassThroughIrb+7f (+0x0e)
	[ 08 f6 42 02 20 75 08 41:00 00 00 00 00 00 00 00 ]
    fffff880010d22f1-fffff880010d22fc  12 bytes - ataport!IdeInitAtaPassThroughIrb+8d (+0x0e)
	[ 10 f6 42 02 01 74 0a 41:00 00 00 00 00 00 00 00 ]
    fffff880010d22ff-fffff880010d2306  8 bytes - ataport!IdeInitAtaPassThroughIrb+9b (+0x0e)
	[ 01 eb 08 41 83 a0 f8 03:00 00 00 00 00 00 00 00 ]
    fffff880010d2309-fffff880010d2314  12 bytes - ataport!IdeInitAtaPassThroughIrb+a5 (+0x0a)
	[ fe f6 42 02 10 74 08 41:00 00 00 00 00 00 00 00 ]
    fffff880010d2317-fffff880010d231c  6 bytes - ataport!IdeInitAtaPassThroughIrb+b3 (+0x0e)
	[ 02 41 83 88 f8 03:00 00 00 00 00 00 ]
    fffff880010d231f-fffff880010d2321  3 bytes - ataport!IdeInitAtaPassThroughIrb+bb (+0x08)
	[ 20 ba 12:00 00 00 ]
    fffff880010d2325-fffff880010d2329  5 bytes - ataport!IdeInitAtaPassThroughIrb+c1 (+0x06)
	[ 41 c6 80 f1 03:00 00 00 00 00 ]
    fffff880010d232c-fffff880010d2340  21 bytes - ataport!IdeInitAtaPassThroughIrb+c8 (+0x07)
	[ 12 8d 4a f2 41 b8 49 64:00 00 00 00 00 00 00 00 ]
    fffff880010d2343-fffff880010d2349  7 bytes - ataport!IdeInitAtaPassThroughIrb+df (+0x17)
	[ 48 3b c6 75 0a be 9a:00 00 00 00 00 00 00 ]
    fffff880010d234c-fffff880010d234e  3 bytes - ataport!IdeInitAtaPassThroughIrb+e8 (+0x09)
	[ c0 e9 b1:00 00 00 ]
    fffff880010d2352-fffff880010d2358  7 bytes - ataport!IdeInitAtaPassThroughIrb+ee (+0x06)
	[ 8b 47 28 89 83 30 04:00 00 00 00 00 00 00 ]
    fffff880010d235b-fffff880010d2363  9 bytes - ataport!IdeInitAtaPassThroughIrb+f7 (+0x09)
	[ 0f b7 47 2c 66 89 83 34:00 00 00 00 00 00 00 00 ]
    fffff880010d2366-fffff880010d236c  7 bytes - ataport!IdeInitAtaPassThroughIrb+102 (+0x0b)
	[ 8a 47 2e 88 83 36 04:00 00 00 00 00 00 00 ]
    fffff880010d236f-fffff880010d2372  4 bytes - ataport!IdeInitAtaPassThroughIrb+10b (+0x09)
	[ 80 a3 35 04:00 00 00 00 ]
    fffff880010d2375-fffff880010d2379  5 bytes - ataport!IdeInitAtaPassThroughIrb+111 (+0x06)
	[ 4f 80 bd 58 04:00 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3591 errors : !ataport (fffff880010d2000-fffff880010d2fff)

axe0 said:

Below I have marked a few things red, it means that there are problems with reading data from the hard drive what could be caused by a few things

1. The drivers of the IDE controller is outdated/corrupted
2. The hard drive is failing
3. The cable needs replacement
4. The connection on the motherboard is the problem in which you would have to get a new motherboard.

Further there is also some corruption with a system driver.

Everyone had suspected the motherboard but now I see the hard drive could be the issue as well???

Okay I tested HDD C where Windows is installed (the 320Gb) and this was the result:

HD Tune Pro: WDC WD3200AAKS-75L9A0 Error Scan

Scanned data : 319 gB
Damaged Blocks : 0.0 %
Elapsed Time : 1:09:19
1 Error at 93467 MB (LBA 191421870)

HD Tune Pro: WDC WD3200AAKS-75L9A0 Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 200 200 51 198 ok
(03) Spin Up Time 140 137 21 3975 ok
(04) Start/Stop Count 98 98 0 2009 ok
(05) Reallocated Sector Count 200 200 140 0 ok
(07) Seek Error Rate 100 253 0 0 ok
(09) Power On Hours Count 26 26 0 54370 ok
(0A) Spin Retry Count 100 100 0 0 ok
(0B) Calibration Retry Count 100 100 0 0 ok
(0C) Power Cycle Count 100 100 0 360 ok
(C0) Unsafe Shutdown Count 200 200 0 159 ok
(C1) Load Cycle Count 200 200 0 2004 ok
(C2) Temperature 112 88 0 31 ok
(C4) Reallocated Event Count 200 200 0 0 ok
(C5) Current Pending Sector 200 200 0 1 warning
(C6) Offline Uncorrectable 200 200 0 1 ok
(C7) Interface CRC Error Count 200 200 0 4 attention
(C8) Write Error Rate 200 200 0 1 ok
(F0) Head Flying Hours 38 38 0 45657 ok
(F1) Unknown Attribute 200 200 0 70463916612 ok
(F2) Unknown Attribute 200 200 0 123022700045 ok

Health Status : warning

HD Tune Pro: WDC WD3200AAKS-75L9A0 Benchmark

Test capacity: full

Read transfer rate
Transfer Rate Minimum : 5.6 MB/s
Transfer Rate Maximum : 99.0 MB/s
Transfer Rate Average : 78.5 MB/s
Access Time : 16.0 ms
Burst Rate : 170.0 MB/s
CPU Usage : 7.4%

Previous test with SeaDos also had issues with C.

I had ran it before posting in this thread:

The C drive failed on a short test:

--------------- SeaTools for Windows v1.4.0.4 ---------------
2/26/16 7:44:16 PM
Model Number: WDC WD3200AAKS-75L9A0
Serial Number: WD-WMAV21414266
Firmware Revision: 01.03E01
Short DST - Started 2/26/16 7:44:16 PM
Short DST - FAIL 2/26/16 7:50:58 PM
Long Generic - Started 2/26/16 7:52:53 PM

And the sfc/scannow I will do next. What is the difference between that and chkdsk?

An advice, don't ask for help on different forums. That could cause 2 suggestions to collide against each other what may make things only worse.

System File Checker scans the system files and in case it finds them it'll try to repair them what may take a few tries sometimes.
Check disk scans the partition for bad sectors and if it finds them, depending on the commands given, it marks them as bad so the system won't use them anymore. However a bad sector usually relates to a hard drive that soon completely fails so check disk is a temporary solution.

Oh okay.. should I do both sfc/scannow and chkdsk?

Yes please :)

BorisTheAnimal said:

Yes please :)

First test:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

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.

C:\Windows\system32>

2nd test .. starting it now

I did the ChkDsk while I was not home so I had to look in the Event Viewer to grab it for you.

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

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

CHKDSK is verifying files (stage 1 of 5)...
259072 file records processed. File verification completed.
745 large file records processed. 0 bad file records processed. 2 EA records processed. 47 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
315426 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
259072 file SDs/SIDs processed. Cleaning up 58 unused index entries from index $SII of file 0x9.
Cleaning up 58 unused index entries from index $SDH of file 0x9.
Cleaning up 58 unused security descriptors.
Security descriptor verification completed.
28178 data files processed. CHKDSK is verifying Usn Journal...
34172096 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
259056 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
55154367 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

312466431 KB total disk space.
91367308 KB in 144107 files.
111788 KB in 28179 indexes.
4 KB in bad sectors.
369863 KB in use by the system.
65536 KB occupied by the log file.
220617468 KB available on disk.

4096 bytes in each allocation unit.
78116607 total allocation units on disk.
55154367 allocation units available on disk.

Internal Info:
00 f4 03 00 09 a1 02 00 52 f5 04 00 00 00 00 00 ........R.......
70 5f 00 00 2f 00 00 00 00 00 00 00 00 00 00 00 p_../...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

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