Jump to content
Come try out our new Arcade we just put up, new games added weekly. Link at the top of the website ×

BSOD


tinmann

Recommended Posts


  • Member ID:  3821
  • Group:  *** Clan Members
  • Followers:  17
  • Topic Count:  8
  • Topics Per Day:  0.00
  • Content Count:  158
  • Content Per Day:  0.04
  • Reputation:   52
  • Achievement Points:  1050
  • Solved Content:  0
  • Days Won:  0
  • Joined:  10/20/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/20/1972
  • Device:  Windows

I had a system crash in the middle of a game last night and got the BSOD but didn't catch the number. it only flashed it for about 2 seconds.

this system never crashed before but it did hang up a couple times in the past week.

is there a way to find out what it was?

im running windows 7

any help would be great

Link to comment
Share on other sites

Awards


  • Member ID:  5785
  • Group:  ***- Inactive Clan Members
  • Followers:  7
  • Topic Count:  8
  • Topics Per Day:  0.00
  • Content Count:  172
  • Content Per Day:  0.04
  • Reputation:   74
  • Achievement Points:  1098
  • Solved Content:  0
  • Days Won:  0
  • Joined:  02/27/13
  • Status:  Offline
  • Last Seen:  
  • Birthday:  01/01/1970
  • Device:  Windows

Hmm. My rig also has the same crash once in a while during game. My is wind7, the best way to see what causes it is click 

Window-Control Panel- Action Center-Maintenance-View Reliability History.

My gpu sometimes runs out of vram and crashes.

Link to comment
Share on other sites

Awards


  • Member ID:  3821
  • Group:  *** Clan Members
  • Followers:  17
  • Topic Count:  8
  • Topics Per Day:  0.00
  • Content Count:  158
  • Content Per Day:  0.04
  • Reputation:   52
  • Achievement Points:  1050
  • Solved Content:  0
  • Days Won:  0
  • Joined:  10/20/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/20/1972
  • Device:  Windows

thanks rookido.. I will check into that

Link to comment
Share on other sites

Awards


  • Member ID:  808
  • Group:  **- Inactive Registered Users
  • Followers:  2
  • Topic Count:  7
  • Topics Per Day:  0.00
  • Content Count:  36
  • Content Per Day:  0.01
  • Reputation:   31
  • Achievement Points:  292
  • Solved Content:  0
  • Days Won:  0
  • Joined:  11/29/09
  • Status:  Offline
  • Last Seen:  
  • Birthday:  08/24/1966
  • Device:  Windows

I use BlueScreenView. It's a free utility

 

http://www.nirsoft.net/utils/blue_screen_view.html

Link to comment
Share on other sites



  • Member ID:  87
  • Group:  ***- Inactive Clan Members
  • Followers:  57
  • Topic Count:  98
  • Topics Per Day:  0.02
  • Content Count:  3789
  • Content Per Day:  0.70
  • Reputation:   3589
  • Achievement Points:  27249
  • Solved Content:  0
  • Days Won:  7
  • Joined:  09/02/09
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/02/1871

i just smoke another bowl and laugh at my computer seems to help me :shock:

Link to comment
Share on other sites



  • Member ID:  87
  • Group:  ***- Inactive Clan Members
  • Followers:  57
  • Topic Count:  98
  • Topics Per Day:  0.02
  • Content Count:  3789
  • Content Per Day:  0.70
  • Reputation:   3589
  • Achievement Points:  27249
  • Solved Content:  0
  • Days Won:  7
  • Joined:  09/02/09
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/02/1871

make sure your not over heating check fans when was the last time you cleaned your computer?

Link to comment
Share on other sites



  • Member ID:  389
  • Group:  *** Clan Members
  • Followers:  45
  • Topic Count:  296
  • Topics Per Day:  0.06
  • Content Count:  4480
  • Content Per Day:  0.84
  • Reputation:   3643
  • Achievement Points:  36586
  • Solved Content:  0
  • Days Won:  40
  • Joined:  09/14/09
  • Status:  Offline
  • Last Seen:  
  • Birthday:  01/01/1970
  • Device:  Windows

this on a laptop or tower ?

 

HDD failling

Link to comment
Share on other sites



  • Member ID:  3189
  • Group:  *** Clan Members
  • Followers:  94
  • Topic Count:  355
  • Topics Per Day:  0.08
  • Content Count:  5234
  • Content Per Day:  1.17
  • Reputation:   11106
  • Achievement Points:  48754
  • Solved Content:  0
  • Days Won:  112
  • Joined:  02/11/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  12/24/1957
  • Device:  Windows

You do not need a 3rd party viewer to see what went wrong.  Simply open the Windows Event Viewer (run eventvwr.msc) and click into the "Windows Logs" area and start scanning for errors at the date and time of the BSOD.  They will be obvious.

 

The reason you are not able to read the BSOD because the system reboots too fast is because you have Automatic Restart on System Failure enabled, which it is by default.  To turn it off so you can actually get a look at the BSOD screen:

 

Go into the Control Panel and start the System app (or right click on Computer in the Start menu and select Properties.) 

 

Select Advanced System Settings from the selections on the left sidebar (this places you in the System Properties dialog on the Advanced tab.)

 

Under the Startup and Recovery section, click the Settings button.

 

Uncheck Automatically Restart.

 

If you do this, you will need to force a restart yourself whenever you get a BSOD.

Edited by djMot
Link to comment
Share on other sites



  • Member ID:  3003
  • Group:  *** Clan Members
  • Followers:  26
  • Topic Count:  36
  • Topics Per Day:  0.01
  • Content Count:  419
  • Content Per Day:  0.09
  • Reputation:   348
  • Achievement Points:  3598
  • Solved Content:  0
  • Days Won:  0
  • Joined:  11/21/11
  • Status:  Offline
  • Last Seen:  
  • Birthday:  03/17/1979
  • Device:  Windows

I have found that most BSOD lately have been because of a failing memory stick.  Windows has a built in memory test to find out which one is bad. Or you can pull all but one stick out and reboot and play around for a while and see if you get BSOD.  Repeat using each memory stick by itself until the bad one is found.  If not a memory stick be sure to turn off all overclocked items and return them to stock specs and overclock only one item at a time.  Also check for dust bunnies that can cause cooling problems.  Also you can check the power supply for failures as well. Good luck.

Link to comment
Share on other sites



  • Member ID:  3821
  • Group:  *** Clan Members
  • Followers:  17
  • Topic Count:  8
  • Topics Per Day:  0.00
  • Content Count:  158
  • Content Per Day:  0.04
  • Reputation:   52
  • Achievement Points:  1050
  • Solved Content:  0
  • Days Won:  0
  • Joined:  10/20/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/20/1972
  • Device:  Windows

make sure your not over heating check fans when was the last time you cleaned your computer?

 

its all clean and the fans are running. I clean it out every month

 

make sure your not over heating check fans when was the last time you cleaned your computer?

 

 

this on a laptop or tower ?

 

HDD failing

 

everything appears to be fine with the hard drives and it is a tower with lots of air movement 

Link to comment
Share on other sites

Awards


  • Member ID:  3821
  • Group:  *** Clan Members
  • Followers:  17
  • Topic Count:  8
  • Topics Per Day:  0.00
  • Content Count:  158
  • Content Per Day:  0.04
  • Reputation:   52
  • Achievement Points:  1050
  • Solved Content:  0
  • Days Won:  0
  • Joined:  10/20/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/20/1972
  • Device:  Windows

You do not need a 3rd party viewer to see what went wrong.  Simply open the Windows Event Viewer (run eventvwr.msc) and click into the "Windows Logs" area and start scanning for errors at the date and time of the BSOD.  They will be obvious.

 

The reason you are not able to read the BSOD because the system reboots too fast is because you have Automatic Restart on System Failure enabled, which it is by default.  To turn it off so you can actually get a look at the BSOD screen:

 

Go into the Control Panel and start the System app (or right click on Computer in the Start menu and select Properties.) 

 

Select Advanced System Settings from the selections on the left sidebar (this places you in the System Properties dialog on the Advanced tab.)

 

Under the Startup and Recovery section, click the Settings button.

 

Uncheck Automatically Restart.

 

If you do this, you will need to force a restart yourself whenever you get a BSOD.

thanks dj  I found that setting. I always like to find out what the code means and then fix it.

fortunately this was the first time this system ever crashed and its almost 3 years old

Link to comment
Share on other sites

Awards


  • Member ID:  3821
  • Group:  *** Clan Members
  • Followers:  17
  • Topic Count:  8
  • Topics Per Day:  0.00
  • Content Count:  158
  • Content Per Day:  0.04
  • Reputation:   52
  • Achievement Points:  1050
  • Solved Content:  0
  • Days Won:  0
  • Joined:  10/20/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/20/1972
  • Device:  Windows

I have found that most BSOD lately have been because of a failing memory stick.  Windows has a built in memory test to find out which one is bad. Or you can pull all but one stick out and reboot and play around for a while and see if you get BSOD.  Repeat using each memory stick by itself until the bad one is found.  If not a memory stick be sure to turn off all overclocked items and return them to stock specs and overclock only one item at a time.  Also check for dust bunnies that can cause cooling problems.  Also you can check the power supply for failures as well. Good luck.

im gonna try the memory just to be sure but it only happened once(so far)

I don't have anything O.C.ed .... I will have to pick a day to shut down and start playing with it!lol

Link to comment
Share on other sites

Awards


  • Member ID:  3189
  • Group:  *** Clan Members
  • Followers:  94
  • Topic Count:  355
  • Topics Per Day:  0.08
  • Content Count:  5234
  • Content Per Day:  1.17
  • Reputation:   11106
  • Achievement Points:  48754
  • Solved Content:  0
  • Days Won:  112
  • Joined:  02/11/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  12/24/1957
  • Device:  Windows

 

You do not need a 3rd party viewer to see what went wrong.  Simply open the Windows Event Viewer (run eventvwr.msc) and click into the "Windows Logs" area and start scanning for errors at the date and time of the BSOD.  They will be obvious.

 

The reason you are not able to read the BSOD because the system reboots too fast is because you have Automatic Restart on System Failure enabled, which it is by default.  To turn it off so you can actually get a look at the BSOD screen:

 

Go into the Control Panel and start the System app (or right click on Computer in the Start menu and select Properties.) 

 

Select Advanced System Settings from the selections on the left sidebar (this places you in the System Properties dialog on the Advanced tab.)

 

Under the Startup and Recovery section, click the Settings button.

 

Uncheck Automatically Restart.

 

If you do this, you will need to force a restart yourself whenever you get a BSOD.

thanks dj  I found that setting. I always like to find out what the code means and then fix it.

fortunately this was the first time this system ever crashed and its almost 3 years old

 

Be aware that a fluke BSOD is possible.  A gamma ray just happens to pierce the heart of your processor at just the wrong moment and flips just the wrong bit... or whatever.  Only become nervous when it seems like a chronic issue.  A second time in as many days would have me worried, but not once in a blue moon.

 

Did the system logs tell you anything?  They should have.

Link to comment
Share on other sites



  • Member ID:  2114
  • Group:  **- Inactive Registered Users
  • Followers:  13
  • Topic Count:  30
  • Topics Per Day:  0.01
  • Content Count:  233
  • Content Per Day:  0.05
  • Reputation:   66
  • Achievement Points:  1574
  • Solved Content:  0
  • Days Won:  0
  • Joined:  01/09/11
  • Status:  Offline
  • Last Seen:  
  • Birthday:  06/28/1966

Before you start dissecting your system and OS - try checking your memory (RAM) sticks.  I repair a lot of computers and that is a VERY common cause of BSOD.

Link to comment
Share on other sites



  • Member ID:  2114
  • Group:  **- Inactive Registered Users
  • Followers:  13
  • Topic Count:  30
  • Topics Per Day:  0.01
  • Content Count:  233
  • Content Per Day:  0.05
  • Reputation:   66
  • Achievement Points:  1574
  • Solved Content:  0
  • Days Won:  0
  • Joined:  01/09/11
  • Status:  Offline
  • Last Seen:  
  • Birthday:  06/28/1966

sorry - Sgt. Twinkie already advised you of that.

Link to comment
Share on other sites



  • Member ID:  3821
  • Group:  *** Clan Members
  • Followers:  17
  • Topic Count:  8
  • Topics Per Day:  0.00
  • Content Count:  158
  • Content Per Day:  0.04
  • Reputation:   52
  • Achievement Points:  1050
  • Solved Content:  0
  • Days Won:  0
  • Joined:  10/20/12
  • Status:  Offline
  • Last Seen:  
  • Birthday:  04/20/1972
  • Device:  Windows

i did notice a window update a day before it started and just for giggles i restored it... it hasn't lagged or crashed since but i will keep an eye on it.... see what happens from here

Link to comment
Share on other sites

Awards

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.