Windows 7: BSOD after win7 updates, ntoskrnl.exe+253d0

Hello and welcome :) .
The dumps are showing driver issues but apart from two separate dumps showing
activity of an nVidia (before the update to the beta driver) and a very old iaStor driver,

Code:

0: kd> lmvm iastor
Browse full module list
start             end                 module name
fffff880`0104c000 fffff880`01168000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: \SystemRoot\system32\DRIVERS\iaStor.sys
    Image name: iaStor.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Jun 05 04:53:40 2009

they aren't concise about a single driver.
Now, if the RAM is brand new I would hold off on testing it and focusing on Driver Verifier for now.
Please enable Driver Verifier.

Arc said:

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Please enable driver verifier following this TUTORIAL | But using these settings:

1. Go to Start and type in "verifier" (without the quotes) and press Enter
2. Select "Create custom settings (for code developers)" and click "Next"
3. Select "Select individual settings from a full list" and click "Next"
4. Select everything EXCEPT FOR "Low Resource Simulation", "Force Pending I/O Requests", "IRP Logging" and click "Next"
5. Select "Select driver names from a list" and click "Next"
6. Then select all drivers NOT provided by Microsoft, Unknown, or Macrovision and click "Next"
7. Select "Finish" on the next page.

Post back with a couple of DV enabled crashes :) .

Thanks for the update :) .
Keep it enabled for 48 hours ,while normally using the PC (as if it wasn't enabled), or until a few crashes occur.

Thanks for the feedback :) .
The dumps point to a potential HDD hardware error.

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: fffff6fc00022ff8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000001f02ea860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff800045ff4c0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Code:

ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

Code:

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
3990 errors : !nt (fffff800045ff000-fffff800045fffff)

Other bugchecks were 0xF4 which are usually attributed to storage.

Please test the HDD.
Please post a picture of disk managment.

• Disk Management - Post a Screen Capture Image

   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.

Post back with the results, based upon them we need to determine our next action :) .

Thanks for the feedback :) .
The CHKDSK looks good as well as you said that the drive passed the seatools tests.
In that case I would remove intel rapid storage.

Arc said:

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features.
Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Then I would scan for corrupt files as 3990 errors is not right at all,
I would follow that with a MEMtest86+.

• Follow this tutorial on how to use the SFC/ SCANNOW tool in Windows.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.
Post back with the results :) .