Jump to content

Nizzel

Member
  • Posts

    156
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About Nizzel

  • Birthday Sep 26, 1996

Profile Information

  • Gender
    Male
  • Location
    Denmark

Recent Profile Visitors

1,012 profile views
  1. Dude you are a life saver. i managed to get into my PC. pretty funny how its like an entire OS in itself when you boot up on Hirens. Now i disconnected my school from my account. i just gotta make a new account now and get everything over to that one i suppose
  2. I will give that a go. downloading it as i write this.
  3. So as it stands i am unable to log into my own pc i had my school email account linked up to my microsoft account i guess and was what i was using to log in. as it stands i graduated and the university terminated my account which makes me now unable to even log into my own machine If i try to log into my account it says this; "You can't sign in with this account. Try a different account." List of things i have tried: Booting into safe mode Booting into safe mode with networking (However the internet doesnt seem to actually load) Activating the hidden administrator account on windows using CMD (trying to log into this account just says this; Account has been disabled please see your system administrator Using the tool locksmith by booting up into a usb drive (doesnt seem like it does anything its a tool to change password for accounts) Adding accounts using CMD (cant log into them) Things i havent tried yet: Activating the guest account and trying to log into it Out of ideas thats why im here :EDIT: I have come to the conclusion that i dont think i have actually activated the administrator account. it seems the recovery CMD i have been using is just that. it can't change accounts that are on my harddrive. that would explain the whole X:Recovery directory it was in on the CMD window and also why it says it cant add the user to the local group. any ideas on how i would be able to do this properly?
  4. it seems that its the dual bios LED that is flashing. i tried clearing CMOS using the jbat1 jumper. this worked for a bit until it then just flashed slowly which means BIOS 2 has failed. however before it flashed quickly which means that BIOS 1 has failed. when both dont work it should have a solid light as far as i know. but it does seem that maybe both BIOS's are dead which means the motherboard is bricked. as far as i think anyways.
  5. As stated before. Yes it does not boot. The PC turns on but I get no screen showing.
  6. I don't think you get what I mean. It never gets that far. I literally can't get into bios
  7. But I can't even boot into BIOS. I don't think I would be able to update my bios
  8. As I said in the post I tried reinstalling ram. I can't boot the PC at all how would I update the BIOS?
  9. So my PC have been acting very strange as of late. sometimes i could not see my Raid 0 drives at all and sometimes i could. i was trying to fix this by going into the BIOS and changing the SATA mode. first i tried raid which it then did not boot up at all (i have raid configured in windows so maybe thats why) then i tried ACHI which well made me not able to boot up at all i cleared CMOS by clicking the button on my motherboard which did not work. i then tried taking out the CMOS battery which did not work either. My motherboard is blinking like crazy with the LED that is located quite low on the motherboard. i have tried the following things: Taking out the graphics card and booting up using another graphics card tried every RAM combination possible (even no RAM at all) disconnecting my raid drives no outside cables connected (other than power cable) Cleared CMOS by button and battery My system: i7 2600k 4.1Ghz 16gb corsair vengeance 1866mhz CL9 GTX 980ti 840 pro 256gb 2x WD black RAID 0 2TB total WD Green 1TB Cooler Master Silent Pro M 850W MSI P67A-GD65 Motherboard Windows 10 64bit Here is a video i have taken of the motherboard LED blinking https://www.youtube.com/watch?v=fzYjstTHh1M
  10. its probably just some safe measure to protect the card. when its unstable it will lock itself to a lower clock speed so it doesnt fail again. its because the overclocked failed before
  11. have you tried restarting? not even kidding but if your card was slightly unstable it might have locked itself to a lower clock speed? maybe check what its core clock is during the benchmarks?
  12. my 980ti only has one DVI port though so im not sure that would solve anything. but it wouldnt help much as none of my monitors actually have dvi so no
  13. my motherboard has no connection for that though ^^' but sound advice anyways. ye im wondering if its the adapters that are causing it thats why i also mentioned it in the post i did. i dont really have a choice in the matter though as these monitors dont support display port
  14. i have tried this. it fails. boots up with all 4 monitors being blank
×