Well, the header says it all. I've gotten this multiple times. When it
happened, I was running Firefox 2.x, Thunderbird, MediaMonkey, Zune X64,
mutorrent and that's it.
I managed to take a picture of it, because that's easier than writing
the stuff down by hand, so here are the codes that came with it (there
were like four or five).


0x0000000A, (0x000009710000007E, 0x000000000000002, 0x0000000000000001,
0xFFFFF8000020A6163)

Thanks for any help


--
Scottaz

Hi,

Have any unsigned drivers trying to run in your x64 system?

The error codes and message is only sufficient to confirm that it is a
driver error. Beyond that, it's not much good for isolating the cause. A
driver file is corrupt, missing, in conflict, or non-compliant with the
system. The problem is....which one? A dump file may tell us, set the
advanced system startup and recovery settings to create a small memory dump,
and the next time it happens send the newly created minixxxxxx-0x.dmp under
C:\Windows\Minidump to me at using a subject line of "per
req".

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"Scottaz" wrote in message
...

Well, the header says it all. I've gotten this multiple times. When it
happened, I was running Firefox 2.x, Thunderbird, MediaMonkey, Zune X64,
mutorrent and that's it.
I managed to take a picture of it, because that's easier than writing
the stuff down by hand, so here are the codes that came with it (there
were like four or five).


0x0000000A, (0x000009710000007E, 0x000000000000002, 0x0000000000000001,
0xFFFFF8000020A6163)

Thanks for any help


--
Scottaz