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: I could use some help with debugging NTOSKRNL.EXE

29 Jun 2011   #1
BrutalForce

Windows 7 x64
 
 
I could use some help with debugging NTOSKRNL.EXE

I tried debugging this on my own, but with little success (obviously don't know what I am doing. Best as I can tell its related to a NTOSKRNL.EXE which google tells me is a keyboard issue.

Can anyone help me please?

I get random blue screens with a bad pool caller? Prior to this there was no real system action. Afterwards I updated all my drivers and Windows updates and I still got a blue screen.

Attachment 162312


My System SpecsSystem Spec
.
29 Jun 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by BrutalForce View Post
I tried debugging this on my own, but with little success (obviously don't know what I am doing. Best as I can tell its related to a NTOSKRNL.EXE which google tells me is a keyboard issue.

Can anyone help me please?

I get random blue screens with a bad pool caller? Prior to this there was no real system action. Afterwards I updated all my drivers and Windows updates and I still got a blue screen.

Attachment 162312

These both were related to a memory exception caused by an un-named driver. Please do the following


1-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.


Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



2-Driver verifier


Quote:
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
3-Update the old drivers listed below
Code:
hotcore3.sys    10/27/2006 9:40:50 AM        fffff880`00dc7000    fffff880`00dd3000    0x0000c000    0x45420c62                        
regi.sys    4/16/2007 11:19:10 AM        fffff880`09539000    fffff880`09541000    0x00008000    0x462393ee                        
yk62x64.sys    2/23/2009 11:02:27 AM        fffff880`10b2f000    fffff880`10b92000    0x00063000    0x49a2ba83                        
mcdbus.sys    2/24/2009 6:34:07 AM        fffff880`02c0f000    fffff880`02c4b880    0x0003c880    0x49a3cd1f                        
LUsbFilt.Sys    6/17/2009 12:49:46 PM        fffff880`04b61000    fffff880`04b71000    0x00010000    0x4a391eaa                        
AsUpIO.sys    7/5/2009 10:21:38 PM        fffff880`041b4000    fffff880`041ba000    0x00006000    0x4a515fb2

How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
My System SpecsSystem Spec
29 Jun 2011   #3
BrutalForce

Windows 7 x64
 
 

Thank you for the quick response. I will begin diagnostics tomorrow. Thank you. I will report back with my results.
My System SpecsSystem Spec
.

05 Jul 2011   #4
BrutalForce

Windows 7 x64
 
 

Ok, I ran 10 passes of memtest86 on each stick (2) No errors.

I did the driver verifier and my computer would crash in both Windows Normal and Safe Mode.

I had to keep rolling back with restore, so I am including a new minidump for further help. I also uninstalled all old software in hopes that one of those drivers would be the culprit, but so far no luck. AVG would not properly uninstall (something with the installation), so I will try that too.

Please help. I am very frustrated and really want to avoid having to reformat.
My System SpecsSystem Spec
Reply

 I could use some help with debugging NTOSKRNL.EXE




Thread Tools




Similar help and support threads
Thread Forum
ntoskrnl.exe (Bad Pool Header) BSOD Debugging Help Request
Hi and a very happy and prosperous 2013 to everybody, I'm at my wits' end trying to figure out ntoskrnl.exe (Bad Pool Header) BSODs I'm having and cannot pinpoint to a program, driver or else. I've attached herein as advised the SF_DD_MM_YYYY.zip file and the minidumps files for your review....
BSOD Help and Support
BSOD frequent, tried debugging, but Ntoskrnl.exe error
Hi all, my computer has been running great. just last week, it started randomly producing the BSOD. I have several dump files. I've tried analyzing them with WinDbg but I get nothing but errors: Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2 can someone analyze my...
BSOD Help and Support
Thread Gone - Debugging
I posted up in the crashes and debugging forum yesterday and included a zip of my BSOD dump logs thread gone, any reason? i've had no notification i can see?? thanks Ben
Chillout Room
Need help debugging CBS.log
Hi, I did sfc scan today and ran into some trouble. CMD output was: Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete.
BSOD Help and Support
debugging help
Hi People, first post here, can anyone help me with this mini dump file i don't know how to fix my windows symbols so thought it would be easier to ask for help. been having a few BSOD lately. I'm running win 7 ultimate x64 retail
BSOD Help and Support
new to debugging
Hi please help me...im trying to view my DMP file with kernell debugger and a black dos screen flashes really quick but goes away..so i cant view anything ..Please help me cuz i want to find out what is wrong with my computer. Here are the bluescreens.
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 12:09.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App