BSOD from ntoskrnl.exe and AC Adapter?

Derivative said:

Hey all, thanks for reading this if you do haha.

Is Windows 7 . . .
- x64
- Originally was Vista, but I installed Windows 7 on the laptop.

- Age of System: 1.5 years.
- Age of System: 1.4 years (I ran vista for a little bit before swapping to 7)
My laptop had been working fine and dandy until I came back from Minnesota to Florida, on the 22nd. I don't recall installing a lot of programs. I did install Mass Effect, not sure if that has a lot to do with it. Also some updated drivers for my graphics card, thinking I might downgrade the drivers (is that possible?).Somewhere along the lines, I started getting Blue Screen'd, not totally super frequent, but a couple times a day (I use my computer a lot).

I ran WhoCrashed, and I obtained this:

On Thu 12/30/2010 5:09:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123010-38173-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037DA477)
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.


On Thu 12/30/2010 5:09:21 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netw5v64.sys (netw5v64+0x5B7D)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037DA477)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5v64.sys Intel Corporation IRQL_NOT_LESS_OR_EQUAL




On Thu 12/30/2010 4:36:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\123010-42120-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003213477)
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.


On Wed 12/29/2010 5:37:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122910-34647-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037DD477)
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.


On Tue 12/28/2010 5:44:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122810-36036-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000320B477)
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.


On Tue 12/28/2010 3:04:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122710-25490-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003214477)
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.


On Tue 12/28/2010 12:16:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122710-27783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037EC477)
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.


On Mon 12/27/2010 9:26:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122710-51761-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037D6477)
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.


On Sun 12/26/2010 1:38:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122510-23150-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8000321A477)
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.


On Sun 12/26/2010 12:17:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122510-28267-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037E2477)
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.


On Fri 12/24/2010 3:40:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-30934-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0x30, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/24/2010 3:32:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-33493-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003216477)
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.


On Fri 12/24/2010 3:04:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-28314-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037F0477)
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.


On Fri 12/24/2010 1:19:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-23712-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003207477)
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.


On Fri 12/24/2010 1:04:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122310-29125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800037EB477)
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.


Conclusion
26 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

pneteth.sys (PdaNet Broadband Adapter Driver, June Fabrics Technology Inc.)

netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)

As you can see, the ntoskrnl.exe thing has been the cause of most of them. What do I do?

On a less important note, just today my computer started randomly shutting down without warning, just every light turns and the whole thing is off, then when I turn it on I get a problem with the AC Adapter (???) . I think this might have to do with overheating since my laptop was burning at the time (I should say that I had been playing a lot of Mass Effect before it happened)

tl;dr
I'm getting blue screen'd, details above, haven't really installed a lot of things barring Mass Effect and some drivers for graphics cards, ntoskrnl.exe seems to be the cause, what do I do?

Thanks again!

I am afraid who crashed is often incorrect. If ntkernl had crashed the system would not be able to re-start.

WE need the actual dmp files

If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
* Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.

Thank you for your reply!

I was too "quick and loose" and didn't read the appropriate procedure for this. My apologies!

I've attacehd the Minidump file as requested, as well as the files requested in the sticky. I couldn't upload the Perfmon as an html file for some reason.

EDIT: Nevermind, didn't zip up the Perfmon file haha. There, uploaded!

Just got another BSOD. Got motivated to bump this thread. Sorry. : (

Just bumpin'. Happy New Years everybody!