BSoD 1-2 minutes after Windows 7 starts (home prem64)

Hello jambon316, Welcome to SF

The dump file you posted states error code 0x7A BSOD Index

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc4003cb08, ffffffffc0000185, 2dc5bbe0, fffff88007961000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff6fc4003cb08, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000002dc5bbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88007961000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
 
ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR:  0x7a_c0000185
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from fffff80002b32438 to fffff80002abef00
STACK_TEXT:  
fffff880`0311d888 fffff800`02b32438 : 00000000`0000007a fffff6fc`4003cb08 ffffffff`c0000185 00000000`2dc5bbe0 : nt!KeBugCheckEx
fffff880`0311d890 fffff800`02ab0d8b : fffffa80`0d96f650 fffff880`0311d9c0 fffff800`02c4a440 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34cde
fffff880`0311d970 fffff800`02ad9da4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`02acd1ed : nt!MiIssueHardFault+0x28b
fffff880`0311da00 fffff800`02ab3848 : 00000000`00000001 fffff6fc`4003cae0 fffffa80`05d92300 00000000`00000000 : nt!MmAccessFault+0x11c4
fffff880`0311db60 fffff800`02ab3a34 : fffffa80`0c5249e0 00000000`00000001 fffffa80`00000000 fffff800`02ab1c5b : nt!MiInPageSingleKernelStack+0x134
fffff880`0311dc70 fffff800`02ab39cf : 00000000`00000000 00000000`00000001 fffffa80`018a9040 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`0311dcd0 fffff800`02ab366c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`018a9000 : nt!KiInSwapKernelStacks+0x1f
fffff880`0311dd00 fffff800`02d62166 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`0311dd40 fffff800`02a9d486 : fffff800`02c37e80 fffffa80`018cbb60 fffff800`02c45c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0311dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34cde
fffff800`02b32438 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34cde
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
Followup: MachineOwner
---------

If you look at the highlighted text it appears to be pointing to a disk problem
I would recommend running HDD diagnostic software to check for errors
Windows based test Disk Check
Bootable test Hard Drive Diagnostic Procedure

Hi Jamie,

In addition to the suggestions posted by 'Pauly', you may also try the following steps:
- Download and install updates and device drivers for your computer from Windows Update
- Scan your computer for viruses

You may find the following web article from 'Microsoft' useful: Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR (Windows Debuggers)

'Pauly' has shared a comprehensive list of custom 'Hard drive' diagnostics; you may also use the Dell's on-board diagnostics (PSA - Pre-Boot System Assessment), if needed: http://dell.to/OUGnqT
- Power off the laptop
- Power it back on and at Dell splash screen, repeatedly tap 'F 12 key'
- Use arrow keys on the keyboard to highlight 'Diagnostics' option and tap 'Enter'
- Capture the error message, if any

To analyse the error, click the following link: https://www5.nohold.net/Dell/Loginr....d=2591&login=1

Hope this helps. Do reply with the findings; glad to assist

No harm in trying if disk will still read then should work, worst case it may import an error and you start again nothing lost
IMO though i always recommend a Clean Install Windows 7 or Clean Reinstall - Factory OEM Windows 7 to give you the best running system without any factory bloatware

Hi Jamie,

The 'error code' 2000-0146 may occur either due to 'software corruption' or due to a 'bad hard drive'. Basic diagnostics (Pre-Boot System Assessment) does not test the 'hard drive' if this error is indicated. I recommend you to run the DST-Short / Long test for advanced diagnosis. DST-Short (or DST-Long) from '32bit Dell Diagnostics' may help us to determine if the previous error has been corrected.

You may also run the 'hardware diagnostics' again and continue testing even after you reach the 2000-0146 error message. You may get prompted with the following options:
- Select 'Test System'
- Select 'Custom Test'
- Drill down to the hard drive in question, select 'SMART Short Self Test'
- Click 'Run Tests'

Please refer to the following web article for detailed information on '32 bit Dell Diagnostics utility': How to Run the Dell 32-bit Diagnostics Utility | Dell

For detailed steps on 'Custom Test' on 'Hard Drive', you may also find the following video useful: Video Support Center
(Note: The Interface / test environment in the video may slightly vary from what you have in your laptop)

If the 'Custom Test' produces an error message, analyse it using the link that I shared in my previous post. If the system is still covered under warranty and needs a part replacement, please share the system 'Service Tag' and 'Account Holder name' with me (only in a personal message). I may arrange a 'service call' for 'repairs / part replacement' if needed.

If no hardware issue is detected, you may re install a 'fresh copy of Windows' in the system; it should fix it. (Please ensure that you backup all personal data before performing a fresh Windows Reinstall; it leads to data loss)

Hope this helps. Do reply with the findings; glad to assist.