Windows 7 x64 BSOD ntoskrnl.exe

I have a Dell studio laptop with an i7-820 processor, 4GB DDR3-1333 Samsung Ram, dual booted with Ubuntu 10.04 x64 and Windows 7 x64. I have remformated this laptop many times for various reasons, mostly playing around with different multi boot OSs. No matter how I have my drive partitioned, or how many OSs I have installed I always get random BSOD. I have minidump enabled if needed. If this is hardware I really need to get it back to dell before my warranty runs out, I just dread calling their tech support if so. In the event log it appears to point to ntoskrnl.exe. I also ran the program "WhoCrashed.exe ", below are the recent BSODs since my last format. If anyone could help it would be greatly appreciated. Thanks in advanced. Here is the whocrashed report:



On Wed 6/23/2010 1:26:37 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD0, 0x2, 0x1, 0xFFFFF80002E7F2B0)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\062310-16411-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 6/11/2010 7:54:36 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xBE (0xFFFFF88001095AE0, 0x3BBA121, 0xFFFFF8800B9F8A50, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Dump file: C:\Windows\Minidump\061110-28376-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 6/11/2010 8:07:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002FA6A92)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\061110-27580-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 5/30/2010 6:06:33 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xF80060, 0x2, 0x1, 0xFFFFF80002EDF2B0)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\053010-53648-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 5/30/2010 5:57:32 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x780024, 0x2, 0x1, 0xFFFFF80002E962B0)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\053010-42167-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

 

Also if you are wondering why all the crazy times, I do network mtc on an off shift due to customer impact. Thanks again.

 

If it crashes even after reloading Windows & in Linux too, it looks like a hardware & not a software/driver issue.

Check your RAM for starters.

 

Linux does not crash.