AAO25.com
Community => The Lounge => Hardware/Software => Topic started by: Koden on Tuesday, July 12, 2016, 08:52:06 AM
-
Well, I had a pesky Nvidia gtx 660 getting dusty in a corner, so I felt like swapping the old 9600gt I had in a desktop pc build with it (also swapped a ram module while I was at it). Mind you, both the ram and the card are working (they come from another rig). Swapped the hardware, booted up the pc...booted up fine, but once the Windows loading screen appears, I get a BSOD (and it also flashes out damn quick).
I tried swapping back to the older hardware it used to run with, but nothing. It just does the same thing. Also tried to clear the CMOS (admittedly wouldn't work if its a bsod, I guess).
So, I got no clue -_-' I was worried drivers could create issues but I never had issues like this, if that is the case (besides, both the new and the old one are Nvidia cards).
P.s. system specs:
Intel g1620 (yap, don't ask)
Asus h61m-k mainboard
Antec psu (380watts one, I guess its an Earthwatts model)
-
Well, I had a pesky Nvidia gtx 660 getting dusty in a corner, so I felt like swapping the old 9600gt I had in a desktop pc build with it (also swapped a ram module while I was at it). Mind you, both the ram and the card are working (they come from another rig). Swapped the hardware, booted up the pc...booted up fine, but once the Windows loading screen appears, I get a BSOD (and it also flashes out damn quick).
I tried swapping back to the older hardware it used to run with, but nothing. It just does the same thing. Also tried to clear the CMOS (admittedly wouldn't work if its a bsod, I guess).
So, I got no clue -_-' I was worried drivers could create issues but I never had issues like this, if that is the case (besides, both the new and the old one are Nvidia cards).
Press F8 before windows load, when a "-" blinks in the upper left corner.
-
Press F8 before windows load, when a "-" blinks in the upper left corner.
Doesn't that just shows the start up options? I've already tried the default windows start up and repair tho, and it's not able the fix the issue (whatever issue that is).
-
Doesn't that just shows the start up options? I've already tried the default windows start up and repair tho, and it's not able the fix the issue (whatever issue that is).
Can you get into SAFE MODE?
Try to pass a white eraser in the RAM and GPU contacts, re plug PSU cables.
-
Can you get into SAFE MODE?
Try to pass a white eraser in the RAM and GPU contacts, re plug PSU cables.
I tried to start it on safe mode, but it requires the startup repair which doesn't get through. About the eraser, I get what you mean, but the hardware was working fine before, why would they stop or make for issues all of a sudden just because of a swap?
-
I tried to start it on safe mode, but it requires the startup repair which doesn't get through. About the eraser, I get what you mean, but the hardware was working fine before, why would they stop or make for issues all of a sudden just because of a swap?
Shit happens ^^, can you get an Ubuntu or any other live cd/usb? if the system starts, then your PC should be fine. But try unplugging all the stuff from the mobo, clean and re install it, sometimes it is just how you placed the stuff, even if you have did it correctly.
-
Shit happens ^^, can you get an Ubuntu or any other live cd/usb? if the system starts, then your PC should be fine. But try unplugging all the stuff from the mobo, clean and re install it.
Well I have Ubuntu on another partition, I tried to fire it up and what I get is an mbr error...which probably means the mbr is corrupted. I guess I'll have a fun time looking around for the windows installation disk to launch a repair command from it...
-
Well I have Ubuntu on another partition, I tried to fire it up and what I get is an mbr error...which probably means the mbr is corrupted. I guess I'll have a fun time looking around for the windows installation disk to launch a repair command from it...
You are So lucky, corrupted MBR because of a BSOD :) You can always download an ISO and run it from a USB drive as well.
https://neosmart.net/wiki/fix-mbr/ (https://neosmart.net/wiki/fix-mbr/)
http://www.thewindowsclub.com/repair-master-boot-record-mbr-windows (http://www.thewindowsclub.com/repair-master-boot-record-mbr-windows)
-
If you have earlier windows than 8, F8 brings up startup menu IF it works until that. Then go to safe mode command prompt, type in bootrec /fixmbr. It should fix mbr problems. You can also do bootrec /fixboot and sfc /scannow.
-
Put your old hardware back in first. Does it work? If yes, then run this:
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html)
Remove any drivers, shut off the computer, swap parts and try again.
If that doesn't work then you'll have to repair the Windows installation. Without messing with command prompt, you can usually get away with a system restore from a Windows installation disc/thumb drive. If you need an installation disc, I'd suggest torrenting one, preferably a MSFL version. That will be a pure install, straight from Microsoft. There's no problem downloading it. It's only illegal if you install it with an already used serial key or bypass the activation. You're just using it for repair.
I'd almost wager that the issue lies in the memory you swapped over. Perhaps the timing/speed is different between the two computers. Resetting the BIOS might fix it but in some cases not, it may not be running at the speed/timing/voltage it needs to. I've personally swapped Nvidia graphics cards in and out of different models and didn't have an issue. The "proper" way is to clean the old drivers out first and do a clean install on the new drivers from Nvidia, not the manufacturer.
-
Put your old hardware back in first. Does it work? If yes, then run this:
http://www.guru3d.com/files-details/display-driver-uninstaller-download.html (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html)
Remove any drivers, shut off the computer, swap parts and try again.
If that doesn't work then you'll have to repair the Windows installation. Without messing with command prompt, you can usually get away with a system restore from a Windows installation disc/thumb drive. If you need an installation disc, I'd suggest torrenting one, preferably a MSFL version. That will be a pure install, straight from Microsoft. There's no problem downloading it. It's only illegal if you install it with an already used serial key or bypass the activation. You're just using it for repair.
I'd almost wager that the issue lies in the memory you swapped over. Perhaps the timing/speed is different between the two computers. Resetting the BIOS might fix it but in some cases not, it may not be running at the speed/timing/voltage it needs to. I've personally swapped Nvidia graphics cards in and out of different models and didn't have an issue. The "proper" way is to clean the old drivers out first and do a clean install on the new drivers from Nvidia, not the manufacturer.
As I wrote above, putting back the older hardware didn't work. Ill have to try with a system restore from the installation disk. I still wonder what was wrong with the ram module (cause the card is perfectly fine) to make for a bsod...can't believe the motherboard is that picky.
-
So could you get to safe mode cmd? You should try what I told, it is safe and saved many situations with mbr problems. Gfx driver could be that it needs to be uninstalled, as corrupt ones can cause bsod.
-
Try to recover the MBR/bott sector first, better than overwriting all Windows updates ^^, Sometimes mobos are pricky.
-
As I wrote above, putting back the older hardware didn't work. Ill have to try with a system restore from the installation disk. I still wonder what was wrong with the ram module (cause the card is perfectly fine) to make for a bsod...can't believe the motherboard is that picky.
That's what I get for not having my morning coffee yet.
Restore is likely your best bet without having to get all technical and nerdy in the command prompt. Start simple, work up from there.
It's hard to know exactly what happened without knowing what the BSOD is.
I recently had a laptop that got totally fucked over by a virus, destroyed the BCD and hard drive partitions. I finally pulled the STOP code out of the BSOD and researched for a while until I came across this lengthy fix:
http://triplescomputers.com/blog/casestudies/stop-error-0x0000007b-0xfffff880009a98e8-0xffffffffc000000d-0x0000000000000000-0x0000000000000000/ (http://triplescomputers.com/blog/casestudies/stop-error-0x0000007b-0xfffff880009a98e8-0xffffffffc000000d-0x0000000000000000-0x0000000000000000/)
That took care of it. Hopefully you don't have to go that far :)
-
That's what I get for not having my morning coffee yet.
Restore is likely your best bet without having to get all technical and nerdy in the command prompt. Start simple, work up from there.
It's hard to know exactly what happened without knowing what the BSOD is.
I recently had a laptop that got totally fucked over by a virus, destroyed the BCD and hard drive partitions. I finally pulled the STOP code out of the BSOD and researched for a while until I came across this lengthy fix:
http://triplescomputers.com/blog/casestudies/stop-error-0x0000007b-0xfffff880009a98e8-0xffffffffc000000d-0x0000000000000000-0x0000000000000000/ (http://triplescomputers.com/blog/casestudies/stop-error-0x0000007b-0xfffff880009a98e8-0xffffffffc000000d-0x0000000000000000-0x0000000000000000/)
That took care of it. Hopefully you don't have to go that far :)
Im repeating myself, but I still recommend to give a try to cmd :)
Its not tricky and it doesnt need technician to do it, if you know the simple commands. I wrote three commands that he should try, theres no danger with them. It either fixes mbr and boot sector or not, and then scans for corrupted system files and tries to fix them. Its quicker and more simple than full recover. Done it dozens of times.
Bcd can sometimes be more tricky, but not much that either.
-
Puthin if you have a patition free with no inportand software in it. A sec booteble O.S meaby de than you can work on your comp, to solf isue . Its an idear if i understand well you cant get back in your windows. And for later a sec. Acc on your comp helps to somtimes if virus is in. Good luck.
-
Im repeating myself, but I still recommend to give a try to cmd :)
Its not tricky and it doesnt need technician to do it, if you know the simple commands. I wrote three commands that he should try, theres no danger with them. It either fixes mbr and boot sector or not, and then scans for corrupted system files and tries to fix them. Its quicker and more simple than full recover. Done it dozens of times.
Bcd can sometimes be more tricky, but not much that either.
I tried to start it safe mode and cmd but it would just restart without even loading so I guess that's not gonna happen. I also tried to run a win7 installation disk I had around to run the repair tool, but i think it says its not the same version (which is likely). The thing is probably complicated by having an initial startup loader (with 3 options: "older window system", win7 and ubuntu) and another one after the "older win system" one which lets you choose between Xp and Ubuntu (I don't even remember why the OS menu loader is made like that). I figured ill check the error codes tomorrow (took a video, the screen was literally flashing away in a fraction of a second).
-
Aren't you using GRUB as bootloader?
-
Yeah I was thinking also as he mentioned Linux. Do you get into grub or directly windows loading? If you anyhow find a working boot dvd for your version (even to get cmd up), do the mbr fix and fixboot, but also then grub needs to be fixed if you want to get again to Linux, and that can be done through your distros live cd/dvd.
-
Well, i checked the bsod codes today, it was a rather "simple" issue, while restarting after swapping the new hardware in i entered the bios and used the default values which also included AHCI, setting it back to IDE of course solved the issue.
These were the BSOD codes.
STOP: 0X0000007B (0xF78d2524,0XC0000034,0X00000000, 0X00000000)
-
Oh yes, if you have installed windows with that old setting, you cant use the new. Good that its solved now!
-
I didn't mention it in the previous post, but the ram module and the gtx660 are now happily in (including the pain of having to update drivers on 2 OSs because parents still use WinXp...gawd). Not exactly a gaming rig, more like an experiment to see how much of a bottleneck the g1620 will be. It performs similarly to an Intel e8500, just a bit better, with a lower tdp.
http://www.cpubenchmark.net/cpu.php?cpu=Intel+Celeron+G1620+%40+2.70GHz (http://www.cpubenchmark.net/cpu.php?cpu=Intel+Celeron+G1620+%40+2.70GHz)
-
Oh yes, if you have installed windows with that old setting, you cant use the new. Good that its solved now!
You actually can and it's pretty easy;
http://support.microsoft.com/kb/922976 (http://support.microsoft.com/kb/922976)
-
You actually can and it's pretty easy;
http://support.microsoft.com/kb/922976 (http://support.microsoft.com/kb/922976)
Thank you! This we didnt study in school nor did I study myself. Seems that MS support person was wrong in this, once I called them about different issue and support guy was thinking audibly, and then he said if Windows is installed with ide/ahci, it cannot be changed.. but of course it could, as well as you can prepare windows for putting it into a wim and installing to another pc. Well, always theres something new to learn :)
-
Thank you! This we didnt study in school nor did I study myself. Seems that MS support person was wrong in this, once I called them about different issue and support guy was thinking audibly, and then he said if Windows is installed with ide/ahci, it cannot be changed.. but of course it could, as well as you can prepare windows for putting it into a wim and installing to another pc. Well, always theres something new to learn :)
So many things are possible that tech support people may not know about them. This is why I prefer a Google approach rather than seeking support from a single person. I've found far more tricks of the trade on Google than I ever learned in classes or from actual tech support people.
I will warn you, the above procedure doesn't work 100% of the time. I had a stubborn OEM computer that I tried it on and it would never switch over to AHCI. It might have worked with a re-install of Windows but it wasn't worth it. It's only really worth it when you have a SSD.
-
I modified the topic title to reflect the status ^_^ it's very happily and silently running, playing R6 Siege right now, smooth enough too (at the lowest setting obviously).
-
Pics plz
-
What'd you do to fix it?
-
Well, i checked the bsod codes today, it was a rather "simple" issue, while restarting after swapping the new hardware in i entered the bios and used the default values which also included AHCI, setting it back to IDE of course solved the issue.
These were the BSOD codes.
STOP: 0X0000007B (0xF78d2524,0XC0000034,0X00000000, 0X00000000)
-
Oh, that was the whole issue? I thought that was just one piece of the puzzle or something Koden tried to fix the issue.
-
Oh, that was the whole issue? I thought that was just one piece of the puzzle or something Koden tried to fix the issue.
I'm not entirely sure, but I assumed it was all by "that solved the issue". That and the fact that he's referring to the BSOD codes in the past.
-
Yep that was the only issue.
Pics plz
From the top: global, startup, entrance, pool room, garden. Left to right for lower - average - peak fps.
http://i.imgur.com/URTACHO.jpg (http://i.imgur.com/URTACHO.jpg)
-
Koden, when I'm done being addicted to Pokemon Go, let's play some R6s together as well :)
-
Koden, when I'm done being addicted to Pokemon Go, let's play some R6s together as well :)
Yeah! But...pokemon Go? :S
-
Yeah! But...pokemon Go? :S
TRIGGERED
Koden:
PPL say its working now, lets try (cross fingers)
http://www.apkmirror.com/apk/niantic-inc/pokemon-go/pokemon-go-0-29-2-release/pokemon-go-0-29-2-android-apk-download/download/ (http://www.apkmirror.com/apk/niantic-inc/pokemon-go/pokemon-go-0-29-2-release/pokemon-go-0-29-2-android-apk-download/download/)