The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
We now return to our regularly scheduled PA Forums. Please let me (Hahnsoo1) know if something isn't working. The Holiday Forum will remain up until January 10, 2025.
Potential software related blue screen
The_SpaniardIt's never lupinesIrvine, CaliforniaRegistered Userregular
I just moved and my computer is now blue screening on startup. It's home built, cable managed to hell and was working fine before the short trip. While in transit it was in the original case box with styrofoam, and secured so the box would not move around. I have opened the case and all connections look secure and nothing is loose. I can get as far as the login screen, login and then about a min or two into the desktop loading it craps out on me. Safe mode works fine, so this leads me to believe it's software related.
So what do you guys think? Forgive the brevity, I'm typing this on a borrowed iPad.
What does the BSOD say? Does it happen in safe mode?
Make sure that everything inside the box is still seated properly.
e: You can also download Ubuntu Live and burn it to a disc and load from that. If you can keep your computer on in Linux without it crashing then it's Windows related and I'd probably end up doing a repair install on it.
You should remove and reseat the RAM and any cards. No matter how much or how well you packed it, things shake.
And BSODs are extremely indicative of hardware issues. For instance, every single BSOD i had in the last 5 years were RAM or HDD related. I
Trying Linux can help, but it won't eliminate hardware causes at all. My last system HDD was fucked up, but Linux booted fine because, well, it never even touched the System HDD.
The only way to be sure is taking out all cards and RAM sticks and them putting them back.
What does the BSOD say? Does it happen in safe mode?
Make sure that everything inside the box is still seated properly.
e: You can also download Ubuntu Live and burn it to a disc and load from that. If you can keep your computer on in Linux without it crashing then it's Windows related and I'd probably end up doing a repair install on it.
No it does not happen in safe mode, I'm making this post in safe mode right now while I back up documents in case this is a worst case scenario.
Safe mode probably doesn't really "use" all the hardware parts. Even if what you're facing is indeed a pure software BSOD, it wouldn't hurt to reseat the hardware in order to eliminate that possibility. That's the essence of troubleshooting, doing tests that actually eliminate possibilities. RAM sticks need only to shake a tiny bit to start creating problems. Out, in, and they're nice little guys again.
Also try disabling the "restart" when a system failure so you can find out what is giving you issues.
(In Windows 7: Start -> (Right Click Computer) -> Properties -> Advanced System Settings -> Advanced Tab -> (Startup and Recovery Section) Settings... -> Uncheck Automatically Restart)
This way if it causes the BSOD again then you can actually write down the STOP message. Or you could find the .dmp file and upload it somewhere so we could use windbg to see the issue. Whichever you feel comfortable with.
0
The_SpaniardIt's never lupinesIrvine, CaliforniaRegistered Userregular
This morning I jiggled a bunch of components again just to check if they are loose or not. Then I pulled and re-seated the RAM. Still BSOD. I'm going to run a harddisk check when I get home from work and see if maybe a bad sector is screwing everything up.
Spaniard, during the bluescreen you should get a message, please post the ALLCAPS part of the message at the top, and the first error code that starts with 0x (for example 0x000000a0) this will give me a very good idea of what the issue is. If you dont get the bluescreen but get a little window on next reboot with a BUGCHECK code in it, copy that and paste it into the thread.
Otherwise were all just shooting at the dark.
0
The_SpaniardIt's never lupinesIrvine, CaliforniaRegistered Userregular
Crapfortunately I leave for Europe tomorrow morning, so as much as it puts my teeth on edge the computer is going to have to wait it'll I get back. Yay for moving, packing for a trip right in the middle of that move, and your computer breaking all at once. We'll reconvene in two weeks, thanks for the help so far.
Posts
Tried once, more recent point, failed. Tried the furthest back I could possibly go and got an MpSigStub.exe error and failed restore.
Edit: Third attempt, successful restore, still blue screened.
Make sure that everything inside the box is still seated properly.
e: You can also download Ubuntu Live and burn it to a disc and load from that. If you can keep your computer on in Linux without it crashing then it's Windows related and I'd probably end up doing a repair install on it.
And BSODs are extremely indicative of hardware issues. For instance, every single BSOD i had in the last 5 years were RAM or HDD related. I
Trying Linux can help, but it won't eliminate hardware causes at all. My last system HDD was fucked up, but Linux booted fine because, well, it never even touched the System HDD.
The only way to be sure is taking out all cards and RAM sticks and them putting them back.
No it does not happen in safe mode, I'm making this post in safe mode right now while I back up documents in case this is a worst case scenario.
Also try disabling the "restart" when a system failure so you can find out what is giving you issues.
(In Windows 7: Start -> (Right Click Computer) -> Properties -> Advanced System Settings -> Advanced Tab -> (Startup and Recovery Section) Settings... -> Uncheck Automatically Restart)
This way if it causes the BSOD again then you can actually write down the STOP message. Or you could find the .dmp file and upload it somewhere so we could use windbg to see the issue. Whichever you feel comfortable with.
e: I realize that it could also be the video card, but I don't really think there's a good video card testing program... But I could be wrong.
Otherwise were all just shooting at the dark.
Technical information:
*** STOP: 0x000000D1 (0x0000000000FFFFF8, 0x0000000000000002, 0x000000000000000, 0xFFFFF88010F9274C)
*** EtronXHCI,sys - Adress FFFFF88010F9274C Base at FFFFF88010F8B000, Datestamp 4d67ec38
I hope I got it all right.
http://download.gigabyte.us/FileList/Driver/motherboard_driver_etron_usb3.exe
Here ya go.
Well one good turn deserves another, and that's why I offered. I also know him RL, so it's not like I can welch. :winky: