Original title: ntoskrnl.exe BSOD - on 2 different fresh installs
I just did a new build with a fresh install of Windows 7 Home Premium and received a BSOD while I slept analyzed the dump file and it points to ntoskrnl.exe . As I stated this is a fresh install and I had the same issue with the last install which is why I
started throwing parts at the system to see if it was more of an internal component error. any ideas on how to fix this without the usual "reinstall" response
The dump file is as follows:
crash dump file: C:\Windows\Minidump\112812-29608-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0xFFFFFA500015C038, 0x2, 0x1, 0xFFFFF80002ADBFD4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA500015C038, 0x2, 0x1, 0xFFFFF80002ADBFD4)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
These are the two crash dumps received since the reinstall. Since I started getting these BSOD I have replaced the Memory, Motherboard and processor, video card ( nvidia and ati) and am really getting frustrated with what seems to be a microsoft problem.
any advice is greatly accepted.
Thanks