BSOD while running CPU intensive programs - Bug Check Code 0x00000124

[Vir Gnarus]

Latest crashdump I see is from August 21, and it reports another internal CPU timer issue during use of video encoding/decoding with Handbrake. The problem is that the report you gave us doesn't seem most recent: the syslog, for example has entries only up to August 18. Can you generate a new report with crashdumps? Thanks.

- Isaac

 

[russifer]

Vir,
Ok I generated another one...I thought I got them all last time but hopefully this one is ok. Please let me know.

Thanks,
Russ

 

[Vir Gnarus]

Ok, it appears neither a crashdump nor an event log entry is being created for these crashes, which either means this is happening very early during Windows startup, or some I/O failure between your disk and memory.

 

[russifer]

Vir,
I think there is an event log entry being created. I attached a screenshot of my Event Viewer. The crash only happens soon after Windows boots when I'm running the verifier program. Every other time it's occurred when I'm encoding video with Handbrake. So if it's an I/O failure between disk and memory, how do you think I should proceed? Does this mean it may not be the CPU?

Thanks,
Russ

 

[Vir Gnarus]

Notice the latest instance was from yesterday? That's what I meant. It hasn't reported anything from the crash experienced when turning Driver Verifier on.

There may be a driver problem or some other issue manifesting when Driver Verifier is activated, but there's a good possibility it is not involved with what you've been experiencing consistently.

If you can at least write down on the blue screen caused by Driver Verifier, or take a snapshot of it with a camera or whatever, that would be better than being completely in the dark. We'll need the name of the actual bugcheck experienced, the 4 parameters (numbers in parentheses), and name of any driver mentioned (such as "Probably caused by:" or something) if present. If you can mention if it states that crashdump creation was complete or is hung up or anything like that, that'd be great.

Just so you know, you may need to turn off Automatic Restart on crash. Do this by typing "Advanced system settings" in Start Menu, go to Startup & Recovery settings, and uncheck "Automatically restart". Save settings and restart. Then turn on Driver Verifier, set it up and restart again.

If your system reboots without a blue screen despite having unchecked this, then you are suffering from a major power failure, which can be caused by a short circuit, or a bad power supply.

 

[russifer]

Vir,
I'm sorry, I don't think I was being clear. I didn't run the verifier today - I ran it before I began this thread, so the "081812-16208-01.dmp" file that's in all of the zip files was created when I tried testing with verifier. The system does have a blue screen when unchecking "Automatically Restart" in Startup & Recovery settings.

Let me know if this works for you, otherwise I can set it up to run again and re-generate the files.

Thanks,
Russ

 

[Vir Gnarus]

What I'd like done is Verifier to be ran again and capture another blue screen to discover if anything has changed since you disabled the ASUS services and uninstalled the applications.

 

[russifer]

Vir,
I've been running verfiier for a while, and attempting to get a BSOD. I encoded video yesterday for about 8 hours straight, and didn't get any BSOD. Previously when I had ran verifier, about a minute into booting into Windows it would BSOD, even without me starting any programs. Now it seems to be running fine. I attached two screenshots of my verifier settings. I wonder whether stopping some of those services a few days ago did the trick? What are your thoughts?

Thanks,
Russ

 

[Vir Gnarus]

You stated that it crashed again after you turned off the survives though, yes?

What concerns me is that those drivers for the ASUS mobo utilies are still present in the list of loaded drivers (asio.sys, asupio.sys, etc). I personally would be wary about removing them manually, but if you wanna try, you should set a restore point, then go into Safe Mode and go into /Windows/System32 and rename their extension from .sys to like .sysBAK or whatever. They may be in /Windows/System32/drivers so check there too.

Another option is to use Driver Sweeper on em. However, I still highly recommend you make a system restore point first before doing so. Still, Driver Sweeper can be more thorough than just manually removing the drivers themselves.

 

[russifer]

It did crash once after I turned off all the services, but what I didn't do after turning them off was restart my computer, and I wonder if maybe restarting cleared out anything that may have been left behind by the services being on?

I'm thinking I may leave the verifier settings on for a few more days, try encoding lots of video, and see if it crashes again. If it does, I'll make a system restore and run Driver Sweeper.

What do you think?

Thanks,
Russ

 

[Vir Gnarus]

I still recommend removing them regardless whether or not it crashes again, just because they're loaded and are eventually going to cause issues in the long run even if they so happen not too now. But other than that, yeah keep up with DV and Handbrake and see how things go.

 

[russifer]

Hi Vir,
So I have some updates to share. I had verifier running for a couple of days, and I encoded video for 10 hours straight yesterday, with no issues at all. Then this morning I tried opening this program that I use to convert VHS to DVD (honestech VHS to DVD 5.0 Deluxe) and after opening it would immediately BSOD. I was able to reproduce it every time I opened the program (did it 4 times). I then turned verifier off, and now I can open the program with no issue at all. Is this something to be concerned about, or do you think it's just that verifier is stress testing certain drivers and opening this program conflicts with it? I attached a new zip file with new diagnostics.

I think what I'm going to do today is keep verifier off and run encoding all day to see if I get a BSOD.

Thanks,
Russ

 

[Vir Gnarus]

This is happening because the software is resurrecting an old ATI TV card driver (emBDA64.sys; dated 2007) that does not comply to Windows 7 driver coding practices, and is performing an illegitimate operation that will no doubt cause some form of corruption. While Windows 7 regularly does not panic about this behavior because its system checks aren't that stringent, Driver Verifier established a check that does catch this bad behavior and will crash the system as a result.

As for the driver itself, I cannot seem to get much info about it other than this thread and the description below from the Driver Reference Table site I use often:

Driver Description: USB 28xx OEM Filter (TV Card) ATI chipset
Driver Update Site: Driver

Beyond that, I cannot help you as I'm not familiar with TV cards nor this specific program you're using. If you can find some update to this driver that'd probably be your best option, but for now, not sure.