BSoD playing majority of games Kernal_Data_Inpage_Error e.g.BF3/Skyrim

Welcome to SF :) .

All of the bugchecks are the same STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
with a second parameter of, 0xC000009D - DEVICE_NOT_CONNECTED.

Code:

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: fffff6fb80000000
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 000000007642d880
Arg4: fffff70000000000

Present in the dump is a known BSOD in Windows 7.

Code:

0xfffff880033af2f8 : 0xfffff800032f2e15 : nt!IoPageRead+0x255
0xfffff880033af388 : 0xfffff800032f291f : nt!MiIssueHardFault+0x28b
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
0xfffff880033af5b8 : 0xfffff800032c9cee : nt!KiPageFault+0x16e
0xfffff880033af648 : 0xfffff800032cea8a : nt!KiSwapContext+0x7a
0xfffff880033af678 : 0xfffff800032b8883 : nt!MmCreateKernelStack+0x83
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
0xfffff880033af6c8 : 0xfffff800033ffd0e : nt!ExAllocatePoolWithTag+0xfe
0xfffff880033af728 : 0xfffff800035df2e0 : nt!MiFindEmptyAddressRange+0xd0
0xfffff880033af778 : 0xfffff800032abd9a : nt!ExAllocatePoolWithTagPriority+0x4a
0xfffff880033af8a8 : 0xfffff800032da6f2 : nt!IoSetCompletionRoutineEx+0x52
0xfffff880033af8b8 : 0xfffff88000e14c52 : Wdf01000!FxObject::DisposeChildrenWorker+0x2fa
0xfffff880033af8e0 : 0xfffff88000e10df0 : Wdf01000!FxIoTarget::_RequestCompletionRoutine
0xfffff880033af8e8 : 0xfffff88000e13787 : Wdf01000!FxIoTarget::SubmitLocked+0x47f
0xfffff880033af928 : 0xfffff800032d766a : nt!IoReuseIrp+0x3a
0xfffff880033af958 : 0xfffff800032cae53 : nt!KiSystemServiceCopyEnd+0x13
0xfffff880033af998 : 0xfffff88000ea0ba0 : Wdf01000!FxWmiIrpHandler::m_WmiDispatchTable+0x7d0
0xfffff880033af9a8 : 0xfffff88000e14ebf : Wdf01000!FxObject::PerformEarlyDisposeWorkerAndUnlock+0xfb
0xfffff880033af9c8 : 0xfffff88000e11045 : Wdf01000!FxRequest::Release+0x65
0xfffff880033afa18 : 0xfffff800032cea8a : nt!KiSwapContext+0x7a
0xfffff880033afb28 : 0xfffff800034712d8 : nt!ExWorkerQueue+0x58
0xfffff880033afb38 : 0xfffff800032c7410 : nt!KiServiceLinkage
0xfffff880033afb50 : 0xfffff880033afb68 : 0xfffff800036fea23 : nt!ExRaiseHardError+0xe3
0xfffff880033afb58 : 0xfffff800032c15f2 : nt!KiCommitThreadWait+0x1d2
0xfffff880033afb68 : 0xfffff800036fea23 : nt!ExRaiseHardError+0xe3
0xfffff880033afbc0 : 0xfffff880033afce0 : 0xfffff800034d08c0 : nt!IopHardError
0xfffff880033afbc8 : 0xfffff800034712d8 : nt!ExWorkerQueue+0x58
0xfffff880033afc08 : 0xfffff88001a54bb4 : cdrom!RequestSetupMcnSyncIrp
0xfffff880033afc18 : 0xfffff88001a54bb4 : cdrom!RequestSetupMcnSyncIrp
0xfffff880033afc48 : 0xfffff800034d08c0 : nt!IopHardError
0xfffff880033afc68 : 0xfffff800036ff293 : nt!IopHardErrorThread+0x73
0xfffff880033afc98 : 0xfffff880033afcb8 : 0xfffff800035c2101 : nt!ObpWaitForMultipleObjects+0x42b
0xfffff880033afca8 : 0xfffff800032d5261 : nt!ExpWorkerThread+0x111
0xfffff880033afcb0 : 0xfffff800036ff220 : nt!IopHardErrorThread
0xfffff880033afcb8 : 0xfffff800035c2101 : nt!ObpWaitForMultipleObjects+0x42b
0xfffff880033afcc8 : 0xfffff800034712d8 : nt!ExWorkerQueue+0x58
0xfffff880033afcd0 : 0xfffff880033afce0 : 0xfffff800034d08c0 : nt!IopHardError
0xfffff880033afce0 : 0xfffff800034d08c0 : nt!IopHardError
0xfffff880033afd20 : 0xfffff800032d5150 : nt!ExpWorkerThread
0xfffff880033afd38 : 0xfffff800035682ea : nt!PspSystemThreadStartup+0x5a
0xfffff880033afd78 : 0xfffff800032bc8e6 : nt!KxStartSystemThread+0x16

• Driver Reference Table - sptd.sys
• Driver Reference Table - dtsoftbus01.sys

Please remove DAEMON Tools, then follow the quote below to verify and delete
any remnants of the driver that may have been left behind.

Code:

Start Menu\Programs\DAEMON Tools Lite

Arc said:

Download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

Open up the case and re-seat the HDD connections, on the motherboard as well as on the drive itself.

• SATA Data & SATA-Power.

I advise testing the Hard-Drive.

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fx key.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Reset your Page File:

1. Start Menu> Run >type control.exe system
and press the Enter key.
A windows will open and on the Left hand side you will see Advanced system settings, click it.



2. Next click on the Advanced tab and Settings which correspond to the Performance section;



3. Then the Advanced tab once more and click on the Change button;



4. Untick the checkbox next to Automatically manage paging file size for all drives;



5. Select No paging file and Click on the Set button;


6. Confirm all the windows.

7. Restart the PC.

8. Reverse the procedure, by following steps 1-3, only this time select System managed size
and click the Set button;



9. Recheck the box next to Automatically manage paging file size for all drives
and exit the windows by clicking the OK button;



10. Confirm all of the remaining windows by click the OK button
and restart once again to take affect.


Keep us informed :) .

Upload the new files following Blue Screen of Death (BSOD) Posting Instructions.

Did you complete all that was requested?

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check- Scroll down to OPTION TWO of the tutorial and use the /R switch in the CHKDSK command | chkdsk C: /R.
2. Then Post the Disk Check results following | This Tutorial.
3. Once back in Windows, download Crystal Disk Info and post a screenshot (multiple shots if you have more than one drive).
4. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
5. If SeaTools for DOS is unable to recognize your HDD:
6. Visit HDDdiag and follow the instructions | Or follow the instructions below.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fx key.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

Arc said:

Re-seat the sata and power.

Let us know the results.

OK, I'll wait for your next post :) .

I'm going to try the seatools now... here are the newer files etc. etc.

ps. Thanks so much for helping!!


ADDED: I cannot use SeaTools because I get Error 15: file missing or something along those lines

It's my pleasure :) .

The dump is the same as before.

Code:

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

Where are the results of the disk check and disk info requested in post #5?
Try swapping Sata-ports, Sata Data cables, Sata-Power cables.
Did you try and create the seatools bootable USB on a different thumb-drive / CD ?

Also you have some incredibly old drivers!

Code:

hardlock.sys Thu Nov 30 19:12:07 2006
hamachi.sys  Thu Nov 30 22:24:52 2006
aksdf.sys    Wed Dec 13 19:09:32 2006

• Driver Reference Table - hardlock.sys
• Driver Reference Table - hamachi.sys
• Driver Reference Table - aksdf.sys

Please remove or update.