BSOD while converting vid file to DVD, dxgkrnl.sys

bullfights · 18 May 2014

I was using ConvertX2DVD to convert a MP4 vid to DVD so my son can watch it. I use this program most conversions to dvd. I then switched inputs and checked the TV for a recording, then after about 10 minutes I switched back to the PC and found it with BSOD, with a dxgkrnl.sys file as the culprit.

I serached online and read about DirectX updates but tried one and already installed latest. My Vid Drivers are up to date, not sure what else.

"Re previous BSODs, I have yet to check RAM but will do memtest tonight, just got back from Mexico trip and been busy."

attached is SF file

Arc · 19 May 2014

Hi bullfights.

A variety of bugcheck codes are there ... not only while using ConvertXtoDVD, but also other times too.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.
_______________________________

Code:

BugCheck 50, {fffff8a022038008, 1, fffff88013cf5804, 2}


Could not read faulting driver name
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::DestroyDevice+1b8 )

Followup: MachineOwner
---------

Code:

BugCheck A, {fffffa000ec53c83, 2, 0, fffff800046d7733}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )

Followup: MachineOwner
---------

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880051ccd0b, fffff88003176a18, fffff88003176270}

Probably caused by : vpchbus.sys ( vpchbus!XPartWaitDpcWorkItem+c7 )

Followup: MachineOwner
---------

bullfights · 28 May 2014

I was testing the RAM this morning with MEMTEST, and got two errors after ten minutes, see attached image.

I stopped the test and continued working on other things, I have 16gb so maybe tonight I will go on to the other option of finding out which one is bad.

Haven't tried other tests yet.

Arc · 29 May 2014

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.

It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.

It is a motherboard issue. The particular slot is bad.

If a particular RAM module is found to be bad, change it, with the exactly matching specs of the existing ones (or you may change the entire kit; it is up to you). But if a RAM slot is bad, that is a motherboard's failure. Dont use that slot anymore.

bullfights · 29 May 2014

Yeah thats the next step, will have to wait until I get back home from work tomorrow night or Friday morning. I live in Mexico and work in Port of LA.

Thanks

bullfights · 11 Sep 2014

Just a quick update: I ran into some BSOD's a couple days ago, every restart (reboot) flared one up, even trying to get into safe mode. So I decided to check the RAM again with memtest+ and sure enough the same two erros popped up. So I started to check the slots and ram, when I decided to take the PC apart and clean it up, it was filthy dirty to say the least.

After thoroughly cleaning all the dust bunnies I put it back together and went thru another memtest, I left it on all night and in the morning came back to a *Test completed, no errors found*, it was not all the way complete.

I am attaching the photo I took of the competed test, though it wasnt 100% finished, it was 29%. Also including this mornings BSOD if that says anything lemme know.

I am going to start another memtest right now, since I have to reboot, dvd burning program quit working but dvd recording still going....

Thanks

Gerry

Arc · 11 Sep 2014

Run memtest86+ for 8 consecutive passes to decide about its health.

bullfights · 11 Sep 2014

So after it says pass complete, have it re run again 8 times?

Arc · 12 Sep 2014

Pass complete means a single pass is complete. You are supposed to run such 8 continuous passes.

bullfights · 12 Sep 2014

Ok I will give it another go when I get back home, thanks

BSOD while converting vid file to DVD, dxgkrnl.sys

BSOD while converting vid file to DVD, dxgkrnl.sys

update, new bsod, memtest+