Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD from ntoskrnl.exe and AC Adapter?

30 Dec 2010   #1
Derivative

Windows 7 64 Bit Professional
 
 
BSOD from ntoskrnl.exe and AC Adapter?

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 it hints that ntoskrnl.exe 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!



My System SpecsSystem Spec
.
30 Dec 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Derivative View Post
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:
Quote:
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.
My System SpecsSystem Spec
30 Dec 2010   #3
Derivative

Windows 7 64 Bit Professional
 
 

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!
My System SpecsSystem Spec
.

30 Dec 2010   #4
Derivative

Windows 7 64 Bit Professional
 
 

Just got another BSOD. Got motivated to bump this thread. Sorry. : (
My System SpecsSystem Spec
31 Dec 2010   #5
Derivative

Windows 7 64 Bit Professional
 
 

Just bumpin'. Happy New Years everybody!
My System SpecsSystem Spec
Reply

 BSOD from ntoskrnl.exe and AC Adapter?




Thread Tools




Similar help and support threads
Thread Forum
0x00000124 ntoskrnl.exe ntoskrnl.exe+4a63cc BSOD Error runninganygame
i keep getting BSOD when playing game new graphics i dont know where to start when its comes to BSOD stuff 110414-10576-01.dmp 11/4/2014 10:48:39 PM 0x00000124 00000000`00000000 fffffa80`0af318f8 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+4a63cc ...
BSOD Help and Support
BSOD Address:ntoskrnl.exe+75bc0; dxgmms1.sys,ntoskrnl.exe,Ntfs.sys
Hi, to make things easier for you,below is the Bug Check String, Driver, and crash address SYSTEM_SERVICE_EXCEPTION___dxgmms1.sys___ntoskrnl.exe+75bc0 MEMORY_MANAGEMENT_______ntoskrnl.exe____ntoskrnl.exe+75bc0 SYSTEM_SERVICE_EXCEPTION___ntoskrnl.exe____ntoskrnl.exe+75bc0...
BSOD Help and Support
BSOD when goes sleep, ntoskrnl.exe+e96d2/ntoskrnl.exe+81e7a
When I put my pc in sleep mode it often crashes: the screen goes normally in sleep mode, but the pc continues to stay awake for several minutes than BSOD & restart or BSOD & shut off. Thanks to BlueScreenView I found what is seemingly the guilty process, but I don't know what to do now. Thanks...
BSOD Help and Support
Ntoskrnl.exe bsod after wireless adapter install
Sigh. After attempting to install a netgear dual band wireless usb adapter, I began to have repeated bsod's - about every 20 minutes. I uninstalled the adapter, but bsod has continued to occur. In safe mode (which I am in now) - no bsod. Here is the problem report: Problem signature: ...
BSOD Help and Support
BSOD ntoskrnl.exe , All the Time !! Crash Address ntoskrnl.exe+80640
Jan 2014 //------------------------------------------- How to Solve : 1- I've uninstalled my windows and recover my laptop with recovery DVD to it's original factory state.(original windows :)) 2- Never installed Norton internet security again , I'm using Microsoft Security Essentials now. 3-...
BSOD Help and Support
Random BSOD Reporting ntoskrnl.exe+75c40 & ntoskrnl.exe+7efc0
I'm getting random Blue Screens and can't figure out why. I'm not running any hardcore programs. I'm mostly just using Microsoft Office and Firefox. The BSOD's seem to happen when I'm in Outlook, Excel or Firefox. Haven't been able to determine exactly which at the time as I'm moving back and...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 07:54.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App