It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
General discussion (archive)Two BSOD in Two Weeks(24 posts)(24 posts)
(24 posts)
Pages:
1
2
This is my favourite topic
Posted March 10, 2014
Hey folks, just got my second BSOD from out of nowhere in the past two or three weeks (can't remember exactly how long ago last one was, but no more than two or three weeks ago).

Should I be worried?? I mean been gaming on this rig for almost two years and none, and then two in a couple of weeks doesn't sound good, but I dunno.

Sorry I didn't read all that stuff on it but if it helps any both times NOTHING was happening. Once the screen was on my Steam account, but no game was active and I wasn't actively doing anything and I look up and see a BSOD.

Now just now, no screen was up, still on my desktop, and I'm not touching it, have been sitting here at this laptop and I saw the screen change out of the corner of my eye and another BSOD.

Should I be worried, or chalk it up to random gremlins and wait and see if anything more comes of it?
Post edited March 10, 2014 by OldFatGuy
Posted March 10, 2014
yes you should be worried as it doesn't if there wasn't a problem.
You need to get the 0x0000 error code that will usually help define the problem.
Posted March 10, 2014
BSOD is never good and usually implies that something went really wrong in your system, how long ago since you did a fresh re-install of the OS?
Posted March 10, 2014
It's hard to say for sure. I'm not a tech support person, but computer savvy enough to have fixed Blue Screen problems of my own a few times in the past by opening the minidumps (the logs that Windows creates when a BSOD occurs) with BlueScreenView and trying to figure things out from there.
Posted March 10, 2014
Wait for another BSOD and reevaluate. Two BSODs in two years is nothing to be worried about for a home system.
Posted March 10, 2014
avatar
lugum: yes you should be worried as it doesn't if there wasn't a problem.
You need to get the 0x0000 error code that will usually help define the problem.
Okay, I'll try to catch it next time. But my memory sucks, and the screen doesn't stay up long before it restarts, so I'll try and write it down before it disappears but can't guarantee success of that.
Posted March 10, 2014
Get the aforementioned program. It will read the data from minidump folder, so you could locate the problem. Its fast and easy.
Posted March 10, 2014
You may want to try running a disk check. To schedule it follow the instructions here.

It will run the next time you restart your computer. Disk checks can take up to a couple hours to complete, depending on how many bad sectors there are on your drive.
Posted March 10, 2014
Checkdisk to locate the driver's error? Much luck.
Posted March 10, 2014
avatar
OldFatGuy: Hey folks, just got my second BSOD from out of nowhere in the past two or three weeks (can't remember exactly how long ago last one was, but no more than two or three weeks ago).

Should I be worried?? I mean been gaming on this rig for almost two years and none, and then two in a couple of weeks doesn't sound good, but I dunno.

Sorry I didn't read all that stuff on it but if it helps any both times NOTHING was happening. Once the screen was on my Steam account, but no game was active and I wasn't actively doing anything and I look up and see a BSOD.

Now just now, no screen was up, still on my desktop, and I'm not touching it, have been sitting here at this laptop and I saw the screen change out of the corner of my eye and another BSOD.

Should I be worried, or chalk it up to random gremlins and wait and see if anything more comes of it?
You might want to look into this free program called BlueScreenView. It will scan the minidump files that your computer creates and then tell you which error code was returned. Then you can do a search for the error code to see what went wrong.
Posted March 10, 2014
avatar
OldFatGuy: Okay, I'll try to catch it next time. But my memory sucks, and the screen doesn't stay up long before it restarts, so I'll try and write it down before it disappears but can't guarantee success of that.
Right-click on your My Computer icon and select Manage. Then go to Event Viewer > Windows Logs > System to find the error code.
Posted March 10, 2014
A BSOD can mean a lot. If it happens randomly... mhh... Have you installed any new hard- or software that's doing stuff in the background (looking for updates)? I installed a new webcam a couple of days ago and had three BSODs in 15 minutes. Whenever I switch the photo quality (Thanks God I don't need a webcam to take photos), I'll end up with that nice screen, telling me that something went terribly wrong. And some years ago I had some BSODs because a small part of my RAM was broken.

To find out what is causing the BSODs, get Blue Screen View (downloads are on the bottom of the page). Every BSOD creates a dump file. Blue Screen View can read those files and gives you a good overview with all the relevant information. Lots of numbers and codes to google where your problem is coming from.

edit: Just saw that AlKim already mentioned Blue Screen View :/
Post edited March 10, 2014 by real.geizterfahr
Posted March 10, 2014
avatar
OldFatGuy: Okay, I'll try to catch it next time. But my memory sucks, and the screen doesn't stay up long before it restarts, so I'll try and write it down before it disappears but can't guarantee success of that.
avatar
stg83: Right-click on your My Computer icon and select Manage. Then go to Event Viewer > Windows Logs > System to find the error code.
Well I tried both BlueScreenView and this and I'm just not sure what I'm looking at.

Under Bugcheck (on BlueScreenView) is has this code for both crashes, the one today and the one on 3/3 (guess it was one week ago)

0x0000009f

Then there about 8 or nine columns to the right with more codes, so not sure what you need.

On the one where I right clicked Computer (etc.) I can't find anything looking like that code in Lugum's post above.
Posted March 10, 2014
avatar
OldFatGuy: On the one where I right clicked Computer (etc.) I can't find anything looking like that code in Lugum's post above.
After going there you have to double click the event from the list with <span class="bold">Error</span> usually indicated by red.
Post edited March 10, 2014 by stg83
Posted March 10, 2014
avatar
OldFatGuy: Okay, I'll try to catch it next time. But my memory sucks, and the screen doesn't stay up long before it restarts, so I'll try and write it down before it disappears but can't guarantee success of that.
avatar
stg83: Right-click on your My Computer icon and select Manage. Then go to Event Viewer > Windows Logs > System to find the error code.
That gave me five columns, 1)Level, 2)Date and Time, 3) Source 4)Event ID and 5) Task Category

Level: Information
Date and Time : Today's date, a few minutes ago
Source: Service Control Manager
Event ID: 7036
Task Category: None

That's all I see on that whole screen, sorry.

OH Sorry, just saw your next post, sorry, my bad, I'll start looking for red letters
Post edited March 10, 2014 by OldFatGuy
Pages:
1
2
This is my favourite topic
Community
General discussion (archive)Two BSOD in Two Weeks(24 posts)(24 posts)
(24 posts)