Error Code 0xc0000185 on Startup!

[GodlyHallows]

Hey guys! So, about 3 months ago, I built my first rig!

It runs steady, and I have had little to no problems before now.

 

It seems that I after a while of downtime get the errorcode 0xc0000185 on startup. Simply rebooting it seems to help, and the pattern seems to be:

1. Start up get the bluescreen

2. Restart, motherboard dont want to load properly (stops before BIOS it seems)

3. Restart again, and everything works smoothly.

 

I have yet to encounter that bluescreen when the computer is turned on.

Now, from what I gather, 0xc0000185 seems to be contact to media related? I have no CD-reader.

 

Does anyone have any tips as to what to check/look for?

[JefferyD90]

GodlyHallows, on 23 Nov 2015 - 02:24 AM, said:GodlyHallows, on 23 Nov 2015 - 02:24 AM, said:

Hey guys! So, about 3 months ago, I built my first rig!

It runs steady, and I have had little to no problems before now.

 

It seems that I after a while of downtime get the errorcode 0xc0000185 on startup. Simply rebooting it seems to help, and the pattern seems to be:

1. Start up get the bluescreen

2. Restart, motherboard dont want to load properly (stops before BIOS it seems)

3. Restart again, and everything works smoothly.

 

I have yet to encounter that bluescreen when the computer is turned on.

Now, from what I gather, 0xc0000185 seems to be contact to media related? I have no CD-reader.

 

Does anyone have any tips as to what to check/look for?

http://www.eightforums.com/bsod-crashes-debugging/32490-bsod-error-code-0xc0000185.html

That's a good starting point.

 

But pretty much everything points to doing a clean install of Windows.  Please follow the guide that is linked in my signature.

[GodlyHallows]

http://www.eightforums.com/bsod-crashes-debugging/32490-bsod-error-code-0xc0000185.html

That's a good starting point.

 

But pretty much everything points to doing a clean install of Windows.  Please follow the guide that is linked in my signature.

 

So you would recommend a clean install?

Can the error be rooted in me having a pirated copy of Windows (pirated Win 8.1, legit update to Win 10)? If so, why has the error not showed before?

 

Thanks,

T

[JefferyD90]

GodlyHallows, on 23 Nov 2015 - 03:06 AM, said:

So you would recommend a clean install?

Can the error be rooted in me having a pirated copy of Windows (pirated Win 8.1, legit update to Win 10)? If so, why has the error not showed before?

 

Thanks,

T

First off, pirated software is awful anyways.  at least 75% of the time the software that is pirated has something slipped into it.

 

Just image being a legitimate buyer of Windows.  You just paid $100 or so for a copy of Windows, you install it, and understand that it is illegal to share it with anyone.  Would you put a copy of your ISO up on a torrent website, use your own resources to seed it (probably at least 10 times), and provide a crack or key for everyone?  It just doesn't happen.  I would highly recommend biting the bullet, buying a copy of Windows (or at least downloading the ISO from Microsoft and installing it then after 30 days deal with the reduced functionality) and installing it KNOWING that everything is legit.

 

But I do digress, I highly suggest that it is probably related to some 3rd party software of yours that has modified or edited a core part of Windows.  Without more information, of which I wouldn't even know where to start (actually you would start with event viewer) I couldn't suggest anything other than a clean install of your OS.

[GodlyHallows]

First off, pirated software is awful anyways.  at least 75% of the time the software that is pirated has something slipped into it.

 

Just image being a legitimate buyer of Windows.  You just paid $100 or so for a copy of Windows, you install it, and understand that it is illegal to share it with anyone.  Would you put a copy of your ISO up on a torrent website, use your own resources to seed it (probably at least 10 times), and provide a crack or key for everyone?  It just doesn't happen.  I would highly recommend biting the bullet, buying a copy of Windows (or at least downloading the ISO from Microsoft and installing it then after 30 days deal with the reduced functionality) and installing it KNOWING that everything is legit.

 

But I do digress, I highly suggest that it is probably related to some 3rd party software of yours that has modified or edited a core part of Windows.  Without more information, of which I wouldn't even know where to start (actually you would start with event viewer) I couldn't suggest anything other than a clean install of your OS.

 

 

Found out what the problem was, for future reference. It was a bit less complicated than feared, and I feel a bit stupid.

Turned out to actually be a USB stick with bootable windows on it that caused the problem on boot, not quite sure why as my boot order has USB long down the list, but beh. I had recently plugged it in to check what was on it, and forgot to take it out, and so the errors began! 

 

Thanks for the tips though!