Blue Screen of death, pls. help

[freshbuilder]

I would like to take a moment to apologize for the exuberantly long post and posting it here since I don't know exactly what's wrong with my rig and thought I'd post it here.

I have spent a ton of money on my desktop and I'm really scared as this hasn't even lasted a year yet. Long story short, there are times when I suddenly lose my internet connection even if my USB that catches my router's signal (sorry no idea what it's called) and shows full bars for internet connection and so forth. My USB internet thing is attached to a 5 ft. long USB connection that has this signal booster thing. Now when I try to take away my USB (either from the extension or yanking out the extension itself) my desktop produces this sound like its having a seizure or something.

This is when I get a blue screen of death and my desktop automatically reboots on its own. When the desktop a pop up appears telling me that it can check for a solution and so forth, which isn't really helping. Anyway, I checked the more details thing and this has happened to me about three times already and I've taken it upon myself to copy paste the stuff that's written on it. Hopefully someone here can give me an idea of what this problem is about.

The 1st log

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 44
BCP1: FFFFFA800B9EEC60
BCP2: 0000000000000EAE
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\011613-21138-01.dmp
C:\Users\XXXXXX\AppData\Local\Temp\WER-30872-0.sysdata.xml

Second

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 44
BCP1: FFFFFA800A0CC470
BCP2: 0000000000000EAE
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\011613-17425-01.dmp
C:\Users\XXXXX\AppData\Local\Temp\WER-33025-0.sysdata.xml

Third

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 44
BCP1: FFFFFA8009FBE8B0
BCP2: 0000000000000EAE
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\011613-24663-01.dmp
C:\Users\XXXXX\AppData\Local\Temp\WER-46347-0.sysdata.xml


Follow up questions that I hope will get answers:

Why is this happening and how can I fix it?

Is this a serious issue that can potentially harm my hardware?

As I haven't tried it yet, will turning off my desktop whenever my internet turns off be a good way of getting my net back up without resulting in a blue screen of death?

BTW I don't know if this will be helpful but my internet dongle thing is a linksys Cisco WUSB54GC ver. 3

Motherboard: Asrock z68 Extreme 7 gen 3
GPU: Sapphire 7950 HD 3GB OC
CPU Intel i5-2500k
Ram: Couple of red 4GB corsairs, forgot the model and I think i threw away the box.
Hard Drive: WD 500 GB blue
My mouse is a Razer Naga and my Keyboard is just plain except it has extra buttons like sound, mute, shutdown and so forth.

 

[gamerk316]

Wow, this is an unusual one:

The MULTIPLE_IRP_COMPLETE_REQUESTS bug check has a value of 0x00000044. This indicates that a driver has tried to requested an IRP be completed that is already complete.

So almost certainly a driver. I'd make sure your ethernet drivers are all up to date.

Even MSFT is VERY pessimistic in regards to this BSOD:

This is a tough bug to find because the simplest case -- a driver that attempted to complete its own packet twice -- is usually not the source of the problem. More likely, two separate drivers each believe that they own the packet, and each has attempted to complete it. The first request succeeds, and the second fails, resulting in this bug check.

Tracking down which drivers in the system caused the error is difficult, because the trail of the first driver has been covered by the second. However, the driver stack for the current request can be found by examining the device object fields in each of the stack locations.

For now, make sure all your drivers are up to date. Not much more you can do then that.

 

[Scott_D_Bowen]

Could be advanced malware malfunctioning too.

 

[johnbl]

it does sound like a bug in a Ethernet driver. you can download a debug program like "whocrashed" and it will look at your debug file or you can put your memory dump on the cloud and someone can take a quick look at it. gameerk316 is correct in that your solution is most likely to update your Ethernet driver.

 

[gamerk316]

Just thinking out loud; running 'SFC /scannow' from the command window probably couldn't hurt either.

 

[diablo34life]

interesting