No, there is no printer or printer driver installed...

Any idea why this EA minidump always appear after the 8E BSOD?

>>>
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
<<<
Bugcheck code is usually caused by graphical device driver, video card or ram problem.

cpc2004 can you break that paragraph up a bit!

I didn't read it

Fresh minidumps to be analyzed.

It is always like that in this order. First, the BSOD with 8E error, than restart and a minidump with the 8E error is generated, restart again and the minidump with EA error is generated.

Inside the 2 new MiniDumps: (I have included all info)

----------------------------

Thanks..

What I understood was that the 2 problems (8E and EA) were probably caused by the IGP PCI Express video driver, even the 8E (pci.sys). That explains why these 2 problems always happens together.

What Do you think?

Originally Posted by cpc2004

Sounds like the best advice

Strange Temporary solution. I don´t know if this is the solution, but so far no more 8E and EA BSODs. I slowed down the video hardware acceleration in Windows advanced graphics properties (troubleshoot tab). Do you think this has probably something to do with my BSODs?

Still points to Video card memory or drivers
Did you try any older versions

No I didn´t. I´ll run my system with the current drivers and configuration. If no more problems occurs I´ll keep the current settings.

Can be noticable in some games.

But if all your programs and games work, then I suppose keep the setting (until another BSOD <-- hopefully never)

Yeah, hopefully never...

I don´t know if this will afect games, cause it is only 2D acceleration (cursor and drawing) I slowed down. Ran some benchmarks and only 2D scores were slower...

I´ll report here if the problems returns...

Bad news. BSOD 8E and EA returned as soon as I exit Dungeon Siege2 game. The two together as always. Uninstalled all Intel Graphics driver. Ran Drivercleaner, cleaned registry, etc... Installed Original Dell driver. Lets see.

One every strange thing is that the 2D Passmark scores lowered a lot, but the 3D Passmark score were higher.

Finally

Please report back with results

OK, I´ll update the thread...

Do you have any idea why these two BSODs always happens together? What 8E BSOD (pci.sys) has to do with EA BSOD (igxpdv32.dll)? Do they have a "connection" between the two?

Thanks

OK Kimsland, after two weeks that I changed my video driver back to the Dell version no more BSODs or any problems. Not a single lockup. Thanks everyone for the posts and help...

Thanks for the update