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 because of tdx.sys and ntoskrnl.exe, code 0x000000c5

24 Apr 2012   #1

Windows 7 Home Premium 64 Bit
 
 
BSOD because of tdx.sys and ntoskrnl.exe, code 0x000000c5

I wasn't really doing anything when it happened. I ran a memory check, checked for updates to my network driver, and did various Malware scans, but none of these seemed to find any problems, so I'm at a loss ATM. Dump files are attached.

My System:
Intel(R) Core(TM) i3 CPU M 380 @ 2.53GHz
Sony Corporation VAIO
BIOS Date: 09/23/09 11:58:43 Ver: 08.00.10
4.00 GB Memory 3.67 GB Usable
HDD: (1) SAMSUNG HN-M500MBB (2) Ricoh SD/MMC Disk Device
Intel(R) HD Graphics
Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1

My System SpecsSystem Spec
.

24 Apr 2012   #2

Win 8 Release candidate 8400
 
 


These crashes were caused by memory corruption/exception (Cx05) probably your Avast.

I would remove and replace Avast with MSE and then run the 2 tests below.
Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows



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" 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 JGriff2 & Usasma.
Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)
My System SpecsSystem Spec
Reply

 BSOD because of tdx.sys and ntoskrnl.exe, code 0x000000c5





Thread Tools



Similar help and support threads for2: BSOD because of tdx.sys and ntoskrnl.exe, code 0x000000c5
Thread Forum
BSOD ntoskrnl.exe, HDAudBus.sys bugcheck code 0x00000050 BSOD Help and Support
DRIVER CORRUPTED EXPOOL 0x000000c5 ntoskrnl.exe BSOD Help and Support
Solved BSOD error code Help NTOSKRNL.EXE AND NCIP.SYS BSOD Help and Support
BAD_POOL_HEADER at ntoskrnl.exe+70040 BSOD, error code 0x00000019. BSOD Help and Support
BSOD, ntoskrnl.exe, error code 0x9F BSOD Help and Support
BSOD - BC Code 7f, ntoskrnl.exe BSOD Help and Support
BSOD code 44 caused by ntoskrnl, any ideas? 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 08:56 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