BSOD - randomly occurred, 0xf4 and ntoskrnl.exe

[xerxes]

First off I wanna say thank you guys so much in advance. Having just recently discovered this forum, I'm still in awe of the wealth of knowledge on here as well as how quickly and effectively people seem to respond. Quite comforting to say the least! So here's my BSOD issue (the zipped dumpfile is attached too):

Bug Check String: CRITICAL_OBJECT_TERMINATION
Bug Check Code: 0x000000f4
Parameter 1: 00000000`00000003
Parameter 2: fffffa80`07df0b30
Parameter 3: fffffa80`07df0e10
Parameter 4: fffff800`02b928b0
Caused by Driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+7cc40

I was away from my computer when it happened, but it was idle at the time with no applications open to my knowledge. I rebooted without any problems and my system seems to be stable now, but I would like to see if I can prevent this from happening in the future. I recently got a new SSD (corsair force gt - 120GB SATA3) to use as a system disk, and since faultwire said a 0xf4 error is possibly an issue with the boot drive, I'm wondering if that may be the case. My system specs are as follows:

OS: Windows 7 ultimate x64
MOBO: Asus p7h55-m pro
CPU: Intel core i3 540
RAM: RipjawsX 8GB ddr3 oc'd@ 1600MHz
GPU: integrated graphics on cpu
SSD/HDD: Corsair Force GT 120GB Solid State, WD Black 1TB, WD Green 2TB

Once thing I have read about pertaining to the Corsair force gt SSD is the firmware. The drive is only a week old and came with v1.3 firmware - some people have experienced issues with v1.3 and corsair did release a v1.4 along with a pdf explaining how to update your firmware, however, they explicitly stated only to do so if you were having issues or hangups. Essentially it said if you were not getting problems then don't flash your firmware and stick with 1.3. Now I'm not even sure it's the SSD at fault, but I figured it was worth a mention. Also, I like cheese.

Thanks guys for your time! Hopefully yall can lend some clarity to the issue. Much appreciated.

 

[Britt]

Sadly, the f4 BSOD code can mean a variety of things. In my experience, that is the most common error code that windows gives you when it really doesn't know what the problem is. But at least it gave you a file name to work with. ntoskrnl.exe is a core windows file for many services.

Questions: How old is your hardware? Did you buy your components brand new? Have you had blue screens in the past? Has your pc had any viruses/malware on it?

These tips will probably bring up zilch results, but it's worth a shot:

Try running a virus scanner if you suspect any malware on your system. Best ones are:

SUPERAntiSpyware.com | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
Malwarebytes : Free anti-malware, anti-virus and spyware removal download

You can try running some diagnostics on your drives, if you haven't already.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html

You can also try running memtest, but I don't think the ram is at fault here.

In addition, make sure all your drivers for your hardware are up to date. You can check for updates by going to the Start button > type "devmgmt.msc" without the quotations into the search box > locate your hardware on the left side of the window, expand it by clicking the small arrow next to the hardware's icon, and right-click the entry and select Update Driver Software.

Has the PC blue screened again since you last posted? Another thing I've had in my experience are just single random blue screens that happen only once and never again. Your BSOD might have just been a fluke, but I wouldn't bet the house on it just yet.

EDIT: Another thing I forgot to ask. Do you have any other hardware attached to your system? USB devices? etc.

EDIT PART DEUX: According to your dump file, the probable cause of your bsod was from wininit.exe. I don't know if this does a lot of good though, as the file is another core windows file; it contains a group of many more services and commands for windows, comprising of both third and non-third party processes. However, if you keep getting blue screens and they all point to the same file, then I suspect a non-third party windows driver MAY be at work here.

 

[xerxes]

Britt,

Thanks a bunch for responding. Let me first answer the questions you've posed. My hardware is around 6 months old - it's my most recent HTPC build - and all components were purchased new. I've had bluescreens in the past, but they were due to a bad memory module (i stupidly neglected to memtest my ram when i got it, and one stick ended up having 65k errors). The ram has since been upgraded, the hardrive wiped, and I've had a fresh OS install on my SSD. I also memtested my new ram and 4-5 passes cleared on each with 0 errors. I have not received any more BSODs thus far, fortunately enough. And with regard to usb devices - my htpc case has a card reader and some usb/1394 ports connected via two onboard usb cables, but there are no peripheral devices actually plugged in to them.

I use MSE as my av software, and I ran both quick and full scans and everything came out clean. Do you think I should re-run with MWB? I ran disk check and again, no problems. I did, however, run sfc and it returned the message that integrity violations were found I filtered the CBS log and looked at the sfcdetails and found this:

2011-09-27 23:00:43, Info                  CSI    000002a2 [SR] Beginning Verify and Repair transaction
2011-09-27 23:00:43, Info                  CSI    000002a4 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-09-27 23:00:48, Info                  CSI    000002a6 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2011-09-27 23:00:48, Info                  CSI    000002a7 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2011-09-27 23:00:48, Info                  CSI    000002aa [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
2011-09-27 23:00:55, Info                  CSI    000002ac [SR] Verify complete

So this has piqued my interest now, because it seems to be a problem quite a few other people have experienced. What the heck is this iassdo.dll.mui file and how could it have gotten corrupt I wonder. I searched these forums as well as google, and they all have received this issue at different times with different BCCodes. I'm wondering whether I should try and extract the file from my installation dvd and replace the corrupt one? Most people just kinda suggested the catchall repair install, which I would like to avoid doing atm, but am obviously not opposed to it if it's necessary. So, I default to you guys/girls. What do you think that iassdo.dll.mui corruption could be and how might I go about fixing it?

Once again, I very much appreciate your help Britt. Hopefully you, or another experiencing this issue, could shed some light on it! Thanks!

 

[Britt]

Hmm, I suppose you could try replacing the file with a non-corrupted version, but I'm 50/50 on if it would help. I'd recommend backing up any important files before doing so though, just in case the pc decides to blow up (I overestimate, but you never know...).

If that doesn't work, then a repair install would probably be the best thing to do. From what I've read, that method usually resolves the issue.

Keep me posted.

 

[panais]

Hi xerxes.

Please update your Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities
ASUSTeK Computer Inc. -Support- Drivers and Download

The driver is very old from 28-Mar-05 and old drivers in many cases give bsod.

My two cents.