Constant Freezez/BSOD ntoskrnl.exe Crashing

Pretty much had these only the past week or so, everything was running fine untill i came home to a blue screen, ever since then things have been crashing and things have been shutting down unexpectedly. Usually skype would make the shutdown noise and then i'd recieve a bluescreen.

I used the program whocrashed to gather the infomation from the dump files left, Before it was just blue screening and was unable to write a memory file but i managed to fix that problem.

Here are the whocrashed Logs

On Wed 04/04/2012 09:17:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040412-32916-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80076FD2F0, 0xFFFFFA80076FD5D0, 0xFFFFF800045D75F0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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.



I've also tried using windows startup repair only to recieve a boot failure with the error code 0xc000000f "the boot selection failed because a required device is inaccessible"

1.Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

2.Run a Check Disk...

Disk Check

3.
* We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

* If you are overclocking STOP

* We could also use some system information, which you can get easily by running msinfo32. To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.

* You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to 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.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Please run System File Check. Option 2.

If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.

SFC /SCANNOW Command - System File Checker

Hey JMH! Just completed the scan and it did not find any integrity violations

Excellent.
Use your computer normally in the interim.

Upload any further DMP files for analysis.

Its already crashed 2 times since this post but hasn't gone to bluescreen, instead all my applications have shut down saying this error

The instruction at 0x0000000076CA584C referenced memory at 0x00000000076CA584C. The required data was not placed into memory because of an I/O error status of 0xc000000e

Click on OK to terminate the program.

Its really becoming a pain

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 Raid update its Driver.



Memtest.

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

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

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.

So, 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

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.

I have the same. Today, I turned on my Dell Leatitude E6400 (Windows 7 Professional x64 SP1) from hibernation and after few sec the BSOD appeared! (Because from my last session I had skype turned on) I restarted PC, turned on Skype (5.8), and again BSOD. So, I reinstall it, turned on -> BSOD. I dump file and have the same problem, like is desribed here. But I didn't install any new HW, so why???? But I decided to disable Integrated WebCam -> run Skype -> BSOD (so, it wasn't reason). I disabled Bluetooth and wifi (and used wired) -> run Skype -> BSOD. I unplug my wireless mouse -> run Skype -> BSOD.

But finally, I disabled ESET Smart Security 4 -> run Skype -> and now, it seems to be ok!!!!

In past, I tried to register java libraries or other steps, which are described in many forums, but nothing helps.

I hope, that upgrade to ESET Smart Security 5, will alow me to use antivir and firewall together with Skype...