Solved Ntoskrnl bsod

[sharonross]

Hi Folks
Any help with the following will be greatly appreciated. We get random BSOD which to my untrained eye seem to relate back to ntoskrnl.exe. Unfortunately the problem is not consistant in that we cannot cause the BSOD and hence finding a solution has been difficult.

Memmory diagnostics has run overnight with no problem all drivers are up to date is there anything else I can do before my Husband tries a reinstall of the OS

 

[zigzag3143]

Hi Folks
Any help with the following will be greatly appreciated. We get random BSOD which to my untrained eye seem to relate back to ntoskrnl.exe. Unfortunately the problem is not consistant in that we cannot cause the BSOD and hence finding a solution has been difficult.

Memmory diagnostics has run overnight with no problem all drivers are up to date is there anything else I can do before my Husband tries a reinstall of the OS

Almost universally blamed on memory management


Memory corruption probably caused by a driver. please run these two tests



1-Memtest.

*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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

2-Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[sharonross]

Thanks for the quick response. I have already tried the memmory test and that was fine . I am currently running the driver verifier as suggested for over 48 hours and still no crash. Is there any harm if i run this permanently?

 

[BrutalForce]

I will throw this out there, are your BSOD Ntoskrnl.exe with random driver faults?

If so, I recommend running Prime95 and seeing if this will crash your system. If it does then double check your Heatsink/Fan. Where possible open the side of the case to rule out overheating problems. If it does it could be your processor. I tracked down Ntoskrnl BSODs after almost a month and a half of swapping parts to the Processor.

Edit: Yeah, I just downloaded your DMP files and looked and they look just like mine did. Multiple random crashes, but ntoskrnl was always involved.

My processor was a i7 860 (remember this series has an on board memory controller).

If you too have a iX XXX, Check and make sure your memory voltage is set to 1.5V (Any higher is not recommended by Intel and they will be sure and tell you that). Make sure the RAM is set to 1066 or 1333, but not higher. Again, Intel will tell you they don't support above this. (YES I KNOW YOUR RAM AND MOTHERBOARD MIGHT, BUT INTEL DOESN'T).

After doing that run Prime95 and monitor your CPU temperature with RealTemp. If you can crash your computer with P95 Blend or Small FFTs, then I am sad to say you have the same problem I did. Your processor will need to be replaced.

 

[karlsnooks]

Thanks for the quick response. I have already tried the memmory test and that was fine . I am currently running the driver verifier as suggested for over 48 hours and still no crash. Is there any harm if i run this permanently?

No.

Is the system running well now?

 

[sharonross]

spoke too soon. had 3 bsod today i attach dump file I do have i7 860 and the voltage is 1.5 and speed is 1066

 

[BrutalForce]

Run Prime95 to see if it will crash or lock up on you.

You can download it here. Prime95 (64bit) - 25.11 Download - EXTREME Overclocking

If it locks up or crashes, then you most likely will need a processor. You seem to have the same problem I was having.

Mine started out intermittent, and after about a month I was crashing almost hourly, and then it would barely start up.

 

[sharonross]

Do I keep the driver verifier going while I run prime95

 

[BrutalForce]

It doesn't matter. Try with and without. Either way, if prime doesn't lock it up right away, then try again as the BSODs get more frequent.

Also monitor the temperature with RealTemp, the temperatures (if running stock, should not really exceed 70 degrees Celcius) if they do, then I would double check your heat sink and fan.

 

[sharonross]

Running prime 95 now temps are 88,85,81,83. Been running for 10 minutes and still no crash how long should I wait

It's been running for 30 minutes with no crashes. I turned off verified and still can't get it to crash hopefully this means it's not the processor?

 

[BrutalForce]

Temps still seem w/in range. Fans look ok/clean? Like I said, mine started out intermittent and got exponentially worse. If you have another i3/5/7 you could try swapping it out, otherwise you will have to wait until it gets worse or you can duplicate the crash on demand. Regardless you sound like you are having my identical problem. Check out my last thread for details.

 

[karlsnooks]

Sharon,
Will take a look at latest .dmp files later.

If you only run one and only one program at a time, no matter what that program is, does the problem still surface.

 

[sharonross]

I don't think it matters. For example at least 2 of yesterday's crashes were while I was away from the pc and I think all programs barring windows 7 were closed.
Sunday and Monday the pc was on permanently while running driver verified. And it didn't crash at one stage I opened at least 5 programs.
Yesterday we had to turn the pc off and unplug and when turned back on again we started gettig the bsods while verified was running

 

[karlsnooks]

Sharon,

I think you will find this thread interesting since you asacpi.sys file is from 2005.

http://www.sevenforums.com/crashes-debugging/131226-bsod-ks-sys-please-help.html

 

[sharonross]

I have now updated the asacpi.sys file. Now we just have to wait and see.

 

[zigzag3143]

I have now updated the asacpi.sys file. Now we just have to wait and see.

Good job and good luck

 

[sharonross]

I spoke too soon. Its crashed again. Ive attached the file

 

[karlsnooks]

update your wacomm software/drivers

 

[sharonross]

thanks for the suggestions
Wacomm driver now upto date
so again we play the waiting game

 

[zigzag3143]

I spoke too soon. Its crashed again. Ive attached the file

33 of 50 crashes directly point to memory corruption the rest indirectly.

Memory corruption probably caused by a driver. please run these two tests



1-Memtest.

*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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

2-Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html