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: Blue screen, "probably" it's ntoskrnl.exe


28 May 2012   #1

Windows 7 Ultimate x64
 
 
Blue screen, "probably" it's ntoskrnl.exe

I changed my windows twice,my system becomes too slow, and Blue screens still appearing from time to time, especially every time i closed yahoo messenger, it's code 0x00000076 and sometimes 0x00000116.


My Windows: Windows ultimate x64 "from 1.5 month"
original version
Hard age: about 4 years "i formatted it 2 month ago"
i changed my power Supply recently also


Note: i'm egyptian so my english language and terminology is not so good , hope helping

My System SpecsSystem Spec
.

28 May 2012   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

> Kaspersky is a frequent cause of BSOD's.
I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloa...vremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows


>
Quote:
Re a 0x116
"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps CPUID - System & hardware benchmark, monitoring, reporting
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
My System SpecsSystem Spec
28 May 2012   #3

Windows 7 Ultimate x64
 
 

u mean the only problem from Kaspersky so i have to delete it !!


and what about ntoskrnl.exe,


&: if i changed the overall windows with another version and another anti virus program , would BSOD will stop forever ?


Finally: from what u analyzed is there any problem with my hardware ( like bad sectors) or mother board, or even in the temperature system ?!


very very appreciated ,
My System SpecsSystem Spec
.


28 May 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Did you read the link JMH gave for the STOP 0x116: VIDEO_TDR_ERROR troubleshooting?
My System SpecsSystem Spec
28 May 2012   #5
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Madozz,
Unfortunately we are not magicians who can make your problems disappear immediately.

Your DMP's were analysed & you were given the troubleshooting methods required.
Have you read & tried all that was put in Post 2?

{As I note Mike suggested above too.}

My System SpecsSystem Spec
29 May 2012   #6

Windows 7 Ultimate x64
 
 

i'm so sorry, if you noticed i wrote that my terminology in IT isn't so good, a lot of words i can't understand in the last quotation, hope u broaden your minds.


i did what u told me JMH, but another different blue screen start to appear >
My System SpecsSystem Spec
29 May 2012   #7
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Yahoo Messenger is listed in your analysis a few times.
Please follow the below instructions
.


These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.




Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.


RAM - Test with Memtest86+






Driver Verifier

Quote:
Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

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/Windows 7 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"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.


If you are using win 8 add these

- Concurrency Stress Test
- DDI compliance checking

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.


Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)


Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
06 Jun 2012   #8

Windows 7 Ultimate x64
 
 

(Loading ...........................) that's the only screen i had for 6 hours when i booted from Memtest86 CD , P.S: i'm 64 bit,mercury,
My System SpecsSystem Spec
06 Jun 2012   #9

Windows 7 Home Premium 64 Bit
 
 

Try running Memtest86+ with your hard disk removed. The hard disk can sometimes interfere with Memtest86+ running. If that does not work, try a hardware stripdown and test each module individually.

warning   Warning
Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!


Strip down your system to run only the bare essentials: one RAM module, the CPU, motherboard, one hard disk, one graphics card (or use onboard graphics if you have it), keyboard, mouse, and one monitor. See how the system behaves by running Windows for twice as long as it typically takes for you to get a crash. If it is stable, add one piece of hardware back at a time until you get crashes again. Take notes of what hardware you add and how the system responds to the hardware changes.

As you add and remove hardware, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
Once these steps have been followed, it is safe to remove and replace components within your computer.
My System SpecsSystem Spec
Reply

 Blue screen, "probably" it's ntoskrnl.exe




Thread Tools



Similar help and support threads for2: Blue screen, "probably" it's ntoskrnl.exe
Thread Forum
Blue screen on start up with "unexpected shut down" message BSOD Help and Support
Multiple crashing - "STOP: 0x000000F4", blue screen with white script. BSOD Help and Support
blue screen "power state failure" BSOD Help and Support
Solved B320 with frequent "blue screen" crashing BSOD Help and Support
Blue Screen of Death "ntoskrnl.exe" BSOD Help and Support
Post Blue Screen-- Primary Partition became "unformatted" & unbootable Hardware & Devices
"Black screen of death", Blue's cousin 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 03:33 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33