Bluescreen of death (critical_object_termination ntoskrnl.exe, Windows 7 64bit)

Toggle sidebar Toggle sidebar
B

Ben Facepalm

Reputable
Jun 5, 2015
4
0
4,510
For a few days I have BSOD which comes randomly after a while (30-40 minutes).

Informations about my system:
CPU: AMD Phenom II X6 1070T
GPU: NVIDIA GeForce GTX 680
NEW RAM: Corsair Vengeance 8GB (2x4GB) DDR3 1700MHz PC3 12800, CL9-9-9-24
OLD RAM: G. Skill 4GB (2x2GB) DDR3 1600MHz PC3 12800 CL7-8-7-24
Mainboard: ASUSTek Computer Inc.,model: M4A89TD PRO
Bios: American Megatrends Inc., version 0601, date 04/02/2010
SSD: M4-CT128M4SSD2 ATA
2xHDD RAID 0: AND 2+0 Stripe/Raid0 (I will find the exact name for the HDD later)

When do I get BSOD?
It happens randomly when I’m browsing web, play a game etc.
When I’m in a game the mouse starts to be slow, then it stops getting input - everything is frozen, but I can still hear and talk with my friends on teamspeak for a few moments and then the BSOD comes.
When I’m browsing web or I’m on Desktop my page is not loading anymore in Chrome and stops responding. My Taskbar disappears and becomes black. My mouse is loading and I can’t do anything except moving my mouse cursor. After a while (up to 2 minutes freeze) the BSOD appears.

What did I change recently before appearance of BSOD and what did I try to fix?
2 weeks ago I bought new Ram and it worked perfectly fine without any problem.
I accidentally activate ASUS CORE Unlocker by pressing ‘4’ on startup of the computer.
After the first BSOD, I immediately went into the BIOS and disabled ASUS CORE Unlocker.
Now I even reset my BIOS setup to default (except for Raid0 of course..).
Still having BSOD.
I tried to use my old Ram only with different slots and still BSOD.
I ran MemTest86 over night and had 6 passes.
Chkdsk C: /F /R had no problem.
Chkdsk F: /F /R stopped before it could finish due to BSOD…. (is there any way to do chkdsk F: without having to boot into Windows?).
I checked my cables, unplugged and replugged.

My MiniDump in a Zip:
Google Drive download

Bluescreenview
04e1c8a291ea8cc7a47b3a2b812eae8c.png
 
Solution
J
one of your memory dumps showed the cause of the corruption as an IO error while reading the wininit.exe image from disk. This can indicate a drive connection problem, check the drive cables (power and data) maybe update the SATA drivers for the motherboard from the motherboard vendor. Or change your SATA data connection for your drive to a different port or controller (use the slower primary controller rather than the faster secondary controller)
-------------
overall you will want to change your memory dump type to kernel because problems involving USB ports require kernel memory dumps to figure out. https://www.sophos.com/en-us/support/knowledgebase/111474.aspx you will also want to turn on verifier flags to force windows to look...
Sort by date Sort by votes
one of your memory dumps showed the cause of the corruption as an IO error while reading the wininit.exe image from disk. This can indicate a drive connection problem, check the drive cables (power and data) maybe update the SATA drivers for the motherboard from the motherboard vendor. Or change your SATA data connection for your drive to a different port or controller (use the slower primary controller rather than the faster secondary controller)
-------------
overall you will want to change your memory dump type to kernel because problems involving USB ports require kernel memory dumps to figure out. https://www.sophos.com/en-us/support/knowledgebase/111474.aspx you will also want to turn on verifier flags to force windows to look for drivers that are making common programming mistakes. Run cmd.exe as an admin then run
verifier.exe /standard /all
then reboot your system and wait for the next memory dump. it will be stored in c:\windows\memory.dmp

if windows driver verifier finds a driver that is making a mistake, it will bugcheck the system and name the driver.

use verifier.exe /reset
to turn off the verifier functions after you are done testing.
-------------
you will want to update your BIOS,
M4A89TD PRO :https://www.asus.com/Motherboards/M4A89TD_PROUSB3/HelpDesk_Download/

you are running mixed memory modules:
memory bank 0: F3-12800CL7-2GBRM0 2GB G.SKILL
memory bank 1: F3-12800CL7-2GBRM0 2GB G.SKILL
memory bank 2: CMZ8GX3M2A1600C9 4BG Corsair
memory bank 3: CMZ8GX3M2A1600C9 4BG Corsair
You will want to consult your motherboard manual and confirm that each pair is in the correct slots. Often you would want to put one set in slot 0 and 2 and the other in slot 1 and 3 to get them to pair correctly. (but check the manual) update the BIOS to get the best chance of the BIOS selecting the best primary and secondary memory timings. After, you do this you should run memtest86 to confirm your memory is working as expected.



-------------
bugcheck 0x124 WHEA_UNCORRECTABLE_ERROR
Error Type : Unknown error
reported from CORE 4 cache bank 1
system uptime 10seconds. (most likely the system rebooted)
--------------
bugcheck CRITICAL_OBJECT_TERMINATION (f4)
wininit.exe used a invalid memory address, I would confirm the actual binary is not corrupted on disk. start cmd.exe as an admin then run
sfc.exe /scannow

you have various suspect drivers that could be corrupting your system memory.
the most noteable being WinRing0x64.sys, but I have also seen corruption caused by the razer overlay driver \C:\Windows\system32\drivers\rzpmgrk.sys Thu Apr 17 12:36:12 2014
and Saitek Magic Bus drivers. Looks like you have 2 installed
\SystemRoot\system32\DRIVERS\SaiK1703.sys Thu Sep 20 03:03:56 2012
\SystemRoot\system32\DRIVERS\SaiU1703.sys Thu Sep 20 03:03:52 2012

you might also look to update:
Screaming Bee Audio Driver
\SystemRoot\system32\drivers\ScreamingBAudio64.sys Thu Jul 01 11:54:32 2010

your network driver is out of date:
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
\SystemRoot\system32\DRIVERS\Rt64win7.sys Tue Jun 12 07:00:29 2012
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

old network drivers tend to mess up nvidia graphics drivers that have shadowplay running, also causes problems for current virus scanners.

machine info:
BIOS Version 0601
BIOS Release Date 04/02/2010
Manufacturer ASUSTeK Computer INC.
Product M4A89TD PRO



 
Upvote 1 Downvote
Solution
Thanks a lot for replying! I thought no one would reply anymore.
I have one pair in slot 0 and 2 and the other pair of ram in slot 1 and 3. I also updated my Mainboard to the latest version already and also cleared my CMOS by removing the battery of the mainboard.

I will try to change my memory dump type and try out the verifier.

What should I do with the suspected drivers? If deinstall, how can I do so? In Device-manager I don't find all, I think..
I ran MemTest86 already one night with 6 passes... but I think I had only one pair of ram inside. I will try MemTest with both ram inside.

sfc.exe /scannow always stop at 70% because of Windowsresourceprotection (I don't know the english term, in German it was Windowsresourcenschutz).

I turned off Shadowplay and still have the problem.



 
Upvote 0 Downvote
So I did CHKDSK C: /R.
The first time there was an unkown error around 43%, phase 4 of 5.
The second time it didn't find any problem.
sfc /scannow still stops at 70% due to windows resource protection..
 
Upvote 0 Downvote
looks like the memory dump is not marked public I can not get to it.
you could run whocrashed.exe or bluescreenviewer.exe
and have one of those programs look at the memory dump and it should indicated the driver that is getting caught by verifier.



 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom