BSOD All the Time

I have a Lenovo T61 and I get BSODs all the time.
I have run Memtest86+ for 12 hrs. No errors.
sfc /scannow had no errors.
chkdsk had no errors.

BSOD on both Windows XP SP3 and Windows 7 Pro.
Errors about ntoskrnl.exe

Any advice? Hardware error? Bad MB/GPU or CPU?
I have run the Lenovo diagnostics without error.

 

hi
download Who Crashed which will give us a better idea.
what graphics card have you got and which drivers are you using.

 

Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 5/9/2010 7:51:34 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x84226, 0x3, 0x79316)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\050910-17971-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/9/2010 7:43:37 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41201, 0xFFFFF683FF7EF990, 0xA3200000842D2005, 0xFFFFFA800793A440)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\050910-14508-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/9/2010 7:39:11 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x855A2, 0x2, 0x847A1)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\050910-14726-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/9/2010 7:34:48 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF683FF78F668, 0x0, 0x0, 0xFFFFF80002AD21E2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\050910-14664-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/9/2010 7:28:16 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x3, 0xFFFFF8A0089C4E50, 0xFFFFF8A0089C4E50, 0xFFFFF8A0009C4E50)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\050910-14492-02.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/9/2010 7:21:07 PM your computer crashed
This was likely caused by the following module: cdrom.sys
Bugcheck code: 0x50 (0xFFFFF88001ACA994, 0x8, 0xFFFFF88001ACA994, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\050910-14258-01.dmp
file path: C:\Windows\system32\drivers\cdrom.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI CD-ROM Driver
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/9/2010 7:17:26 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xBE (0xFFFFF8A000D6C0D3, 0x8000000126D20121, 0xFFFFF8800B540620, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Dump file: C:\Windows\Minidump\050910-14492-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/9/2010 7:09:24 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ADA805, 0xFFFFF8800C146960, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\050910-15615-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/9/2010 7:01:00 PM your computer crashed
This was likely caused by the following module: ci.dll
Bugcheck code: 0xBE (0xFFFFF88000D07B60, 0x3CC00000034EA101, 0xFFFFF88008D07830, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Dump file: C:\Windows\Minidump\050910-15958-01.dmp
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
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/9/2010 6:42:26 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x15D21, 0x0, 0x15D61)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\050910-14352-02.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/9/2010 6:31:30 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002FD29E8, 0xFFFFF88002FD2250, 0xFFFFF880012FB4F2)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\050910-17862-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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/9/2010 6:05:16 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BB590D, 0xFFFFF8800BA896A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\050910-14430-02.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/9/2010 5:48:53 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF683FF7A28A0, 0x0, 0x0, 0xFFFFF80002A971E2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\050910-15288-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/9/2010 5:45:16 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006940B30, 0xFFFFFA8006940E10, 0xFFFFF80002D91540)
Error: CRITICAL_OBJECT_TERMINATION
Dump file: C:\Windows\Minidump\050910-14352-01.dmp
file path: C:\Windows\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
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/9/2010 2:44:18 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF683FF7A8C88, 0x0, 0x0, 0xFFFFF80002ADF1E2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\050910-14461-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/9/2010 2:14:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFFC7D9A9ABDA8, 0x0, 0xFFFFF80002BD0C07, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\050910-14430-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/9/2010 2:11:52 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF68000C00098, 0xA0A00000A5AC1825, 0xFFFFF680000069C0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\050910-15522-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/9/2010 2:10:34 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x403, 0xFFFFF680000175F0, 0xEF70000005047867, 0xFFFFF6FD40006238)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\050910-14554-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 Sat 5/8/2010 2:51:32 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009552618, 0xFFFFF88009551E80, 0xFFFFF80002AFD687)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\050810-15194-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 Sat 5/8/2010 1:12:10 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF95FD895DDB9, 0x8, 0xFFFFF95FD895DDB9, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\050810-17082-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 Sat 5/8/2010 1:11:09 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x85D5B, 0x2, 0x85D4D)
Error: PFN_LIST_CORRUPT
Dump file: C:\Windows\Minidump\050810-22978-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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

21 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

are you trying to run readyboost or anything like that, have a usb memory drive plugged in full time, page space on something other than %systemdrive%??

And are ALL and I mean ALL of your drivers completely up to date, designed for Win7, etc, etc.

 

What newsposter said.
ntoskrnl.exe is responsible for various system services such as hardware virtualization, process and memory management, etc.
So, try what newsposter suggested.

 

Hmm, notice that the OP said he has the same behavior in both WinXP and Win7, which are two entirely different OS. There's probably not a single driver that's the same between the two. Given that situation, it's almost certain that we are dealing with a hardware issue here. Of course, what is really puzzling is that none of the diagnostics finds anything wrong.

How frequent are these BSODs? Any specific programs that are running when the BSODs occur? Can you swap out your memory modules (maybe borrow a set from a different computer) and see if this has any effect? Really poking around in the dark here.

 

Yep. I did not have time to read the whole therad when I postet my previous post. So, that was the reason why I gave general information. But I agree with you, it looks like an hardware issue.
I don't think this is going to be easy to figure out as you said, but that is why we are here on NBR!

 

And if YOU read the first part of my response I'm asking generic questions that apply to any recent msft OS.

 

I do usually have an SDHC card in the card reader.
I'll take it out and see if it improves.
There is no specific program that I am running when it BSODs. All my apps of the same version work on other computers.
Another symptom is that Firefox and Kaspersky Internet Security 2010 crashes a lot.