Vuze (azerus) shuts down my PC

[BuckeyeNation27]

and fuck....it just restarted.

 

[Dryden]

Have you tried looking at porn yet?

 

[Count Rugen]

and remember... this is for posterity, so be honest.

 

[sandgk]

In other words, only the naked truth - copies of any pictorial evidence must be submitted to the RR.

 

[BuckeyeNation27]

Are there any errors showing up on the App or system logs?

Error code 100000d1, parameter1 83000000, parameter2 00000002, parameter3 00000000, parameter4 f7870b98.

helpful?

 

[sandgk]

Error code 100000d1, parameter1 83000000, parameter2 00000002, parameter3 00000000, parameter4 f7870b98.

helpful?

Here's what someone else said on TechSpot:
The original question

zarathustra_
10-05-2006, 08:04 AM
Hi all,

I wonder if cpc2004's about? hehe

It's obvious to all that he has the necessary expertise here to decipher this:

Error code 100000d1, parameter1 00000400, parameter2 00000002, parameter3 00000000, parameter4 f9622a96.

It's from the event log directly after a BSoD. If any more information is required, of course I will be more than happy to oblige.

Thank you all in advance,

zarathustra...

The reply was:

howard_hopkinso
10-05-2006, 08:07 AM
A bugcheck of D1 means the following.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by faulty or mismatched RAM, or a damaged pagefile.

Go HERE (Before posting your minidumps, please read this - TechSpot OpenBoards) and follow the instructions.

If that doesn`t help, attach 5 or 6 of your latest minidumps to your next post.

Regards Howard :)

First thing the linked solution page (the one in the second quote block) says is run MemTest - you just might have bad RAM.

 

[Mike80]

Error code 100000d1, parameter1 83000000, parameter2 00000002, parameter3 00000000, parameter4 f7870b98.

helpful?

actually as Sandgk put out there, yes perhaps maybe kinda

I had a similar problem and it was a bad RAM stick. I don't have the exact error messages right now (it was last summer), but I was playing games when it decided to do it.

If you haven't already, back up your stuff that you can't lose.