|
|
|
This thread is locked; no one can reply to it.
|
1
2
|
| Random computer freezes and bsods shitstorm after clean install Win 7 |
|
Joachim Arting
Member #13,584
September 2011
|
Hey guys. I'm kinda pissed right now, which is a rare thing. 2 Days ago, I decided to format my comp for no particular reason, just felt like it. After this event a whole shitstorm of freezes have occurred. Happens at random, for no obvious reason. Yesterday, I got a bluescreen too, for no obvious reason while playing a game. Today, it's just gotten worse. I get constant bluescreens or freezes and I'm starting to get really frustrated. I have goolged, but I haven't found a single solution to my problem. What's most frustrating is that I didn't have any of these problems before reformatting, so I don't see how this can be a RAM issue as many have proposed. I have tried resetting the BIOS defaults and even tightening the motherboard screws. BIOS is the latest version, same for the graphics drivers etc. Can someone PLEASE help me ------------------------------------------------------------------------------- |
|
Arthur Kalliokoski
Second in Command
February 2005
 |
Run off a live CD for a few hours, if everythings fine, your windows install must be the problem. They all watch too much MSNBC... they get ideas. |
|
Joachim Arting
Member #13,584
September 2011
|
Arthur Kalliokoski said: Run off a live CD for a few hours, if everythings fine, your windows install must be the problem. Thanks for the quick response. How would I do that? ------------------------------------------------------------------------------- |
|
Arthur Kalliokoski
Second in Command
February 2005
|
Download one of these, burn it to a CD (or DVD if it's too big for a CD) and set your BIOS to boot off the CD/DVD first, then reboot with the CD still in the drive. In that list on the webpage, try one of the Desktop types in the Purpose column so you can actually do stuff. I bet everybody's going to say to use Ubuntu, but I've had problems with those too, from not detecting the monitor correctly (too high a resolution for the monitor to handle, so it doesn't display) to not detecting wireless devices correctly. [EDIT] I totally forgot about the possibility of using a USB stick instead of a DVD. They all watch too much MSNBC... they get ideas. |
|
Thomas Fjellstrom
Member #476
June 2000
 |
I'd also attempt a memtest86+ run. HalfBakedBeaver said: What's most frustrating is that I didn't have any of these problems before reformatting, so I don't see how this can be a RAM issue as many have proposed. It could just be bad luck. But I'm hesitant to claim it for sure is a ram problem. But it doesn't hurt to run the tests. Another possible issue is drivers. Try making sure you have the latest drivers from the manufacturers of your hardware, like the motherboard+chipset (ie: amd, nvidia, intel), NIC, Video Card, Sound, etc. -- |
|
Crazy Photon
Member #2,588
July 2002
 |
I agree with Tomasu that it can be a driver issue. Perhaps Windows Update tried to update your video drivers while playing a game, so it may have left something in a corrupted state. Try also with safe mode and see if it hangs. ----- |
|
Joachim Arting
Member #13,584
September 2011
|
Thomas Fjellstrom said: I'd also attempt a memtest86+ run. Passed, no errors. Quote: Another possible issue is drivers.
Chipset is up to date. I haven't tried Arthurs suggestion yet though. My old man thought I should check the hdd for physical errors via the windows tool or just simply do another clean install of Windows. Any other suggestions? ------------------------------------------------------------------------------- |
|
Thomas Fjellstrom
Member #476
June 2000
|
S.M.A.R.T. test on the harddrive. Maybe check for issues with the drivers you have installed? I'm not sure hard drives would normally cause bluescreens. See if you can't write down the error code windows gives you the next time it bluescreens, and google that. -- |
|
Arthur Kalliokoski
Second in Command
February 2005
|
Thomas Fjellstrom said: I'm not sure hard drives would normally cause bluescreens. Ring 0 code is certainly on the disk, if not data in the swapfile. They all watch too much MSNBC... they get ideas. |
|
Thomas Fjellstrom
Member #476
June 2000
|
If the OS is already running, it probably isn't related to ring0 code, as I'd expect to stay cached in memory if its important. Swap is a possibility, if data is corrupted, or the disk takes too long to respond to the OS, apps can/will hang while the OS is waiting. And there might be crashes because of it. -- |
|
bamccaig
Member #7,536
July 2006
 |
Bluescreen certainly sounds hardware related. Either bad drivers or hardware failure, I'd guess. The drivers seem more likely. It might not hurt to attempt to reinstall the graphics drivers (you'll probably be better off getting the drivers directly from the graphics card vendor instead of using Windows Update). I don't imagine that it should be possible for Windows Update to corrupt itself, but then I wouldn't be surprised either... If all else fails, format and reinstall Windows, and this time to be safe just let the updates go before you start actually using the system. Try your luck with that. Also, make sure you put decent anti-virus software on early. AVG Free, Avast! Free Edition, and Microsoft Security Essentials are all relatively well regarded [or at least have been] (and all free). None of them are perfect, but they're still way better than paid-for software. -- acc.js | al4anim - Allegro 4 Animation library | Allegro 5 VS/NuGet Guide | Allegro.cc Mockup | Allegro.cc <code> Tag | Allegro 4 Timer Example (w/ Semaphores) | Allegro 5 "Winpkg" (MSVC readme) | Bambot | Blog | C++ STL Container Flowchart | Castopulence Software | Check Return Values | Derail? | Is This A Discussion? Flow Chart | Filesystem Hierarchy Standard | Clean Code Talks - Global State and Singletons | How To Use Header Files | GNU/Linux (Debian, Fedora, Gentoo) | rot (rot13, rot47, rotN) | Streaming |
|
Edgar Reynaldo
Major Reynaldo
May 2007
 |
You interrupted the computer while it was updating. You probably left the computer in an unusable state. The computer will appear to stall like that during the update process, it's just poorly designed software. You just have to let it run next time. Start over. Format, install, update. And don't turn it off in the middle of stuff! My Website! | EAGLE GUI Library Demos | My Deviant Art Gallery | Spiraloid Preview | A4 FontMaker | Skyline! (Missile Defense) Eagle and Allegro 5 binaries | Older Allegro 4 and 5 binaries | Allegro 5 compile guide |
|
Thomas Fjellstrom
Member #476
June 2000
|
Edgar Reynaldo said: You interrupted the computer while it was updating. You probably left the computer in an unusable state. The computer will appear to stall like that during the update process, it's just poorly designed software. You just have to let it run next time. Start over. Format, install, update. And don't turn it off in the middle of stuff! I have never noticed a windows update process freeze the entire OS outside of it doing the bits it has to do on reboot. But yeah, it may be messed up after that freeze. -- |
|
Joachim Arting
Member #13,584
September 2011
|
bamccaig said: The drivers seem more likely. It might not hurt to attempt to reinstall the graphics drivers (you'll probably be better off getting the drivers directly from the graphics card vendor instead of using Windows Update) I did get the graphics drivers directly from AMD, It was the first thing I downloaded. Quote: Also, make sure you put decent anti-virus software on early. AVG Free, Avast! Free Edition, and Microsoft Security Essentials are all relatively well regarded [or at least have been] (and all free). None of them are perfect, but they're still way better than paid-for software. Got MSE right after the AMD drivers. Edgar Reynaldo said: You interrupted the computer while it was updating. And don't turn it off in the middle of stuff!
I did not turn it off myself Ran a full harddrive scan today, don't know what it's called in the english version but the one where you right click the drive > properties > Tools > <insert name here> ------------------------------------------------------------------------------- |
|
jhuuskon
Member #302
April 2000
 |
Occasionally updates to the display driver freeze the display for a few seconds. Another good way to to get Windows running so slowly that it seems to be frozen at times is trying to use the computer when the RAID controller is rebuilding a RAID array[1]. During RAID rebuild system calls and deferred procedure calls take full seconds to complete (in contrast to microseconds under normal conditions) and that delay makes programs behave in interesting ways. Trying to install a metric fuckton of updates while the rebuild is in progress is simple way to fuck up your OS. References
You don't deserve my sig. |
|
Joachim Arting
Member #13,584
September 2011
|
Yesterday I decided to remove one of my RAM sticks, to see if this was the cause of the problem, but It crashed once again. I'm hoping to say that the problem is solved, although I have not a single clue about why. I'll update if it crashes again ------------------------------------------------------------------------------- |
|
Arthur Kalliokoski
Second in Command
February 2005
|
Sometimes the connectors can corrode, and taking the stuff apart and putting it back together again fixes that. They all watch too much MSNBC... they get ideas. |
|
Joachim Arting
Member #13,584
September 2011
|
Seriously... Just read your post Arthur, then I got a bluescreen again... ------------------------------------------------------------------------------- |
|
Arthur Kalliokoski
Second in Command
February 2005
|
Isn't there some sort of message on this bluescreen? What does it say? And IIRC, there are logfiles for the Admin to look over that should say something about the cause of a bluescreen. They all watch too much MSNBC... they get ideas. |
|
bamccaig
Member #7,536
July 2006
|
Yes, try to write down every bit of detail you can from the bluescreen(s). They should give you a hint what parts of the system are failing. It's also possible that you just have hardware that isn't seated quite properly and inevitably a bad connection is made which Windows can only see as asplosion. It might be worth removing all detachable hardware and reseating everything if you're comfortable doing this. Take care to make sure everything is seated good. That might resolve your problems. -- acc.js | al4anim - Allegro 4 Animation library | Allegro 5 VS/NuGet Guide | Allegro.cc Mockup | Allegro.cc <code> Tag | Allegro 4 Timer Example (w/ Semaphores) | Allegro 5 "Winpkg" (MSVC readme) | Bambot | Blog | C++ STL Container Flowchart | Castopulence Software | Check Return Values | Derail? | Is This A Discussion? Flow Chart | Filesystem Hierarchy Standard | Clean Code Talks - Global State and Singletons | How To Use Header Files | GNU/Linux (Debian, Fedora, Gentoo) | rot (rot13, rot47, rotN) | Streaming |
|
Samuel Henderson
Member #3,757
August 2003
 |
Yeah googling the BSOD Message and error code can sometimes help you pinpoint whether the error is in the hardware or in some level of software. ================================================= |
|
Don Freeman
Member #5,110
October 2004
 |
Most (if not all) chipset providers say to update their drivers first and THEN install graphics card drivers. Maybe reinstall your graphics driver again. It could be you had a corrupt spot on the dvd when you installed. I had that happen to me with XP. Installed everything clean and had random issues here and there, come to find out...it was something bad on the dvd (original, had dirty spot or was scratched...I can't remember exactly now). Windows SHOULD have picked that up during the copy operation of the install, but apparently not. -- |
|
Joachim Arting
Member #13,584
September 2011
|
Don Freeman said: It could be you had a corrupt spot on the dvd when you installed
I didn't use the cd, I downloaded the latest driver directly. All the bsod error codes have been 1053, but that's all I remember ------------------------------------------------------------------------------- |
|
Thomas Fjellstrom
Member #476
June 2000
|
HalfBakedBeaver said: I didn't use the cd, I downloaded the latest driver directly. I think he meant the OS. Quote: All the bsod error codes have been 1053, but that's all I remember Look for the ALL_CAPS_STRING and the 0xHEXCODE and search for those. -- |
|
Joachim Arting
Member #13,584
September 2011
|
This is wierd. ------------------------------------------------------------------------------- |
|
|
1
2
|
Good luck bud. I would probably do:
