Thread stuck in device driver

zbook thanks for your quick reply

Yes I plan to use the AMD gpu for gaming i play prototype csgo and such so i need that gpu and will need for at lease 6 months until i get a new laptop

next question = Why in this world it was misbehaving after 5 years of usage on the same drivers.. i admit that i was updating and downgrading it couple of times but it was just misunderstanding on my part after resetting windows after it was misbehaving during that 5 years time period
until the SSD was to arrive like it was just a coincidence that the reseller arrived at that day ..

UPDATE: i have installed the unifl catalyst 16.2.1 drivers which are signed by karl sabo

WISH ME LUCK !!Attachment 394361Attachment 394362
i will attach the screenshot of the drivers

- - - Updated - - -

PCkarma said:

guys please help me out on this one as i have to use this laptop in my college which is going to start in 15 days
i am really frustated with this as such i may have not followed some procedures so please tell me if I have and next steps

I have a Dell Vostro 3550 Laptop bough in 2011/12 , my father bought it
it has
CPU=intel i3 - 2330M
GPU=intel hd 3000 & AMD RADEON 7650M 1gb vram (as it shows in gpuz,SIV and other gpu info tools)
Windows 2004 build 19041.1
not able to install 22h2 feature update(idk why?)

I never got this error until it started on 25/07/2023 IST timing
first i was running hard drive (i do not know the build it was running no but was 2004 for sure)
and it happened .. THREAD STUCK IN DEVICE DRIVER

and on the same day the SSD that i bought arrived so I cloned(by thinking that it might be just random bsod happens sometimes) C:\ and boot section which was leading to
the VIDEO TDR FAILURE ERROR
reason = atikmpag.sys
I uninstalled gpu driver using DDU in safe mode
and installed again using dell drivers

which did not resolve it

so then i completely formatted C:\ and installed 2004 build 19041.1 fresh from media creation usb

it was fine until AMD driver got installed and when i restarted again it showed
the error THREAD STUCK IN DEVICE DRIVER
i again did the tedious task of trying some other versions of driver which did not work for me

i will upload my V2 log that i took in safe boot , although i don't know if it will help in safe boot

Also it can be AMD 6630M processor as it matches up with my gpu's core and memory frequency
also it says on notebook check that it came with 6630M and i reside in india so i don't know if there might be some regional stuff
and you can see in the driver photos that is 6600M and 6700M series chip
Review Dell Vostro 3550 Notebook - NotebookCheck.net Reviews
AMD Radeon HD 6630M - NotebookCheck.net Tech

Continue in safe mode continuously for 24 to 48 hours and for any BSOD post a new V2 share link into the newest post.

PCkarma said:

zbook thanks for your quick reply

Yes I plan to use the AMD gpu for gaming i play prototype csgo and such so i need that gpu and will need for at lease 6 months until i get a new laptop

next question = Why in this world it was misbehaving after 5 years of usage on the same drivers.. i admit that i was updating and downgrading it couple of times but it was just misunderstanding on my part after resetting windows after it was misbehaving during that 5 years time period
until the SSD was to arrive like it was just a coincidence that the reseller arrived at that day ..

UPDATE: i have installed the unifl catalyst 16.2.1 drivers which are signed by karl sabo

WISH ME LUCK !!Attachment 394361Attachment 394362
i will attach the screenshot of the drivers

- - - Updated - - -



Also it can be AMD 6630M processor as it matches up with my gpu's core and memory frequency
also it says on notebook check that it came with 6630M and i reside in india so i don't know if there might be some regional stuff
and you can see in the driver photos that is 6600M and 6700M series chip
Review Dell Vostro 3550 Notebook - NotebookCheck.net Reviews
AMD Radeon HD 6630M - NotebookCheck.net Tech

Ok so installing that driver gave me an VIDEO TDR FAILURE
what failed : atikmpag.sys
error
gained nothing but bad luck

- - - Updated - - -

zbook said:

Continue in safe mode continuously for 24 to 48 hours and for any BSOD post a new V2 share link into the newest post.

I will do so

The computer may have malfunctioning hardware.

Please continue in safe mode continuously for 24 to 48 hours and for any BSOD post a new V2 share link into the newest post.

Where did you download the AMD GPU drivers from? Karl Sabo is a very odd digital signer name, I would expect with a large organisation that it would be the company name rather than - potentially - the lead developer's name. I noticed that you had a strange process running at the time of the crash called MMLoadDrvPXDiscrete?

From what I can see in your Stop 0xEA bugchecks, one of your threads is continuously waiting on a dispatcher object to become signaled, which it seems to eventually do, albeit after a long time and therefore leads to the Stop 0xEA.

- - - Updated - - -

Win10Warlord said:

I noticed that you had a strange process running at the time of the crash called MMLoadDrvPXDiscrete?

It looks like a legitimate AMD process from what I can find. I would ensure that you have the latest stable AMD drivers from either your motherboard support page or from the AMD support site. However, Stop 0xEAs are usually always hardware related.

Are you able to disable the AMD Radeon graphics card and just use the Intel HD 3000 integrated GPU? This should reveal whether it's a problem with the AMD graphics card.

ubuysa said:

Are you able to disable the AMD Radeon graphics card and just use the Intel HD 3000 integrated GPU? This should reveal whether it's a problem with the AMD graphics card.

yes it works but when i restart it becomes a low resolution video

- - - Updated - - -

Win10Warlord said:

Where did you download the AMD GPU drivers from? Karl Sabo is a very odd digital signer name, I would expect with a large organisation that it would be the company name rather than - potentially - the lead developer's name. I noticed that you had a strange process running at the time of the crash called MMLoadDrvPXDiscrete?

From what I can see in your Stop 0xEA bugchecks, one of your threads is continuously waiting on a dispatcher object to become signaled, which it seems to eventually do, albeit after a long time and therefore leads to the Stop 0xEA.

- - - Updated - - -



It looks like a legitimate AMD process from what I can find. I would ensure that you have the latest stable AMD drivers from either your motherboard support page or from the AMD support site. However, Stop 0xEAs are usually always hardware related.

As I stated that I now have installed one of he UNIFL drivers that are for this particular chipset
even after that it is not runnning well and the stop code changed from
Thread stuck to Video tdr failure

Could you please provide the latest dump files using the V2 collection tool? The best option at the moment would be to use the just the iGPU and then wait until you have another crash. It seems that they're quite frequent from what you have mentioned.