Constant BSOD after previous problems

[Jwoodall92]

Hi all,

Around 5 days ago now I installed a new CPU fan, went to start my PC back up but got no display, I then tried all the obvious things such as resetting the battery and then resetting BIO's to factory defaults but nothing worked, I then remembered that back when I first built the PC I had to change the RAM timings due to me purchasing the wrong sticks of RAM so I did so and the PC started up, however after 2 or so minutes of being on the desktop I received a BSOD. I then decided to reformat and reinstall Windows 7 just to save messing around really as I already had everything backed up however the problem still persisted. I have tried to install the drivers for my graphics card but it literally doesnt let me. It says installation succesful but then they arent actually installed, I have no clue what on earth the problem is. I have also ran a error check on the HD and left Windows Memory Diagnostic running for a good hour or so.

The computer seems to BSOD more often when under stress, for example I managed to download a game (BSOD are much less frequent now that I've reinstalled Windows and reformatted) and I loaded it up, however after around roughly 30 seconds I had another BSOD. This is as far as I've gotten really, I hope someone can help me out here..

 

[Jwoodall92]

Bump.

 

[Jwoodall92]

88 views and no replies..

 

[writhziden]

Hi all,

Around 5 days ago now I installed a new CPU fan, went to start my PC back up but got no display, I then tried all the obvious things such as resetting the battery and then resetting BIO's to factory defaults but nothing worked, I then remembered that back when I first built the PC I had to change the RAM timings due to me purchasing the wrong sticks of RAM so I did so and the PC started up, however after 2 or so minutes of being on the desktop I received a BSOD. I then decided to reformat and reinstall Windows 7 just to save messing around really as I already had everything backed up however the problem still persisted.

Looking into it, give me a few minutes...

You had five memory related blue screens, one hard drive related, and a system related, but these are three months old and probably not relevant. When you reinstalled Windows, did you do a full format or quick format? You may want to try a full format to clean up any bad sectors on the hard drive if you did not do so before.

See http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html to create new minidmp files for future issues.


I am not understanding how five days ago you could reinstall Windows and still have three month old dmp files... Something odd here.

 

[writhziden]

An option if you do not want to do a full format, run an http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html, and type:
chkdsk /r c:
chkdsk /r d:
etc. for all drives with system files and program files

When asked if you would like to schedule them to run when Windows is restarted, hit the Y key.

 

[Jwoodall92]

Hi all,

Around 5 days ago now I installed a new CPU fan, went to start my PC back up but got no display, I then tried all the obvious things such as resetting the battery and then resetting BIO's to factory defaults but nothing worked, I then remembered that back when I first built the PC I had to change the RAM timings due to me purchasing the wrong sticks of RAM so I did so and the PC started up, however after 2 or so minutes of being on the desktop I received a BSOD. I then decided to reformat and reinstall Windows 7 just to save messing around really as I already had everything backed up however the problem still persisted.

Looking into it, give me a few minutes...

You had five memory related blue screens, one hard drive related, and a system related, but these are three months old and probably not relevant. When you reinstalled Windows, did you do a full format or quick format? You may want to try a full format to clean up any bad sectors on the hard drive if you did not do so before.

See http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html to create new minidmp files for future issues.


I am not understanding how five days ago you could reinstall Windows and still have three month old dmp files... Something odd here.

It was a full format but there was 2 partitions of the hard drive, didnt think much of it at the time as one was something like 499gb, and the other something like 100mb. Honestly not sure where these 3 month old dumps have come from, maybe a problem with the computers clock after the reformat?

So just to confirm I have no BSOD's for today? If not how close together are the timings on these blue screens? If they are all in the space of a few days im almost certain its the ones from today, something must be wrong with the date set on the pc.

Im in bed on my laptop now but ill do this minidmp thing tommorow for sure.

Thanks man.

 

[writhziden]

It was a full format but there was 2 partitions of the hard drive, didnt think much of it at the time as one was something like 499gb, and the other something like 100mb. Honestly not sure where these 3 month old dumps have come from, maybe a problem with the computers clock after the reformat?

So just to confirm I have no BSOD's for today? If not how close together are the timings on these blue screens? If they are all in the space of a few days im almost certain its the ones from today, something must be wrong with the date set on the pc.

Im in bed on my laptop now but ill do this minidmp thing tommorow for sure.

Thanks man.

The BSODs were all in one day, and all within about five hours of each other, so probably not from recent problems. Also, you will have to wait for two or three blue screens AFTER setting up the minidmps to be created before posting them on here.

 

[Jwoodall92]

It was a full format but there was 2 partitions of the hard drive, didnt think much of it at the time as one was something like 499gb, and the other something like 100mb. Honestly not sure where these 3 month old dumps have come from, maybe a problem with the computers clock after the reformat?

So just to confirm I have no BSOD's for today? If not how close together are the timings on these blue screens? If they are all in the space of a few days im almost certain its the ones from today, something must be wrong with the date set on the pc.

Im in bed on my laptop now but ill do this minidmp thing tommorow for sure.

Thanks man.

The BSODs were all in one day, and all within about five hours of each other, so probably not from recent problems. Also, you will have to wait for two or three blue screens AFTER setting up the minidmps to be created before posting them on here.

Just checked and as suspected the clock on the PC is set to 14/09/2011, so the ones your looking at must be the ones from yesterday. I just havent set the time and date since the reinstallation of windows.

 

[writhziden]

Just checked and as suspected the clock on the PC is set to 14/09/2011, so the ones your looking at must be the ones from yesterday. I just havent set the time and date since the reinstallation of windows.

That is odd that it is that far off. Anyway, in regards to your blue screens, a few things you can try...

1. Shut down and turn off your computer.
2. Unplug the power from the wall/surge protector.
3. Hold down the power button for 30 seconds to close the circuit and drain capacitors.
4. Remove the computer case and then remove all components from the motherboard (graphics card, memory modules, etc. except CPU and CPU fan).
5. Get a can of air and blow the dust out of all slots and off all components, including the ones you have removed.
6. Reseat all peripherals into the motherboard.
7. Put the case back on.
8. Plug the power back in for the computer.
9. Start your computer up.
10. Go into the BIOS and reset to Defaults to reset the CMOS
11. Fix your RAM timings to the most stable timings
12. Save and exit the BIOS and start your computer normally.

Post back if the above makes a difference. If not, I have a few other things we can test.

 

[writhziden]

such as resetting the battery and then resetting BIO's to factory defaults but nothing worked,

Was this the CMOS battery that you reset? That may explain your time issue.

 

[Jwoodall92]

It was a full format but there was 2 partitions of the hard drive, didnt think much of it at the time as one was something like 499gb, and the other something like 100mb. Honestly not sure where these 3 month old dumps have come from, maybe a problem with the computers clock after the reformat?

So just to confirm I have no BSOD's for today? If not how close together are the timings on these blue screens? If they are all in the space of a few days im almost certain its the ones from today, something must be wrong with the date set on the pc.

Im in bed on my laptop now but ill do this minidmp thing tommorow for sure.

Thanks man.

The BSODs were all in one day, and all within about five hours of each other, so probably not from recent problems. Also, you will have to wait for two or three blue screens AFTER setting up the minidmps to be created before posting them on here.

Just done all the above, however after resetting BIO's to fail-safe defaults I also had to underclock the processor to 2.64ghz down from what auto set it to (3.80ghz) as well as the RAM timings otherwise it was just stuck on a loop (getting to the black screen where the 4 coloured orbs joined together ton form the windows logo on the black background).

Been on desktop now for around 2 minutes, ill report back if I get any more BSOD.

 

[Jwoodall92]

Just checked and as suspected the clock on the PC is set to 14/09/2011, so the ones your looking at must be the ones from yesterday. I just havent set the time and date since the reinstallation of windows.

That is odd that it is that far off. Anyway, in regards to your blue screens, a few things you can try...

1. Shut down and turn off your computer.
2. Unplug the power from the wall/surge protector.
3. Hold down the power button for 30 seconds to close the circuit and drain capacitors.
4. Remove the computer case and then remove all components from the motherboard (graphics card, memory modules, etc. except CPU and CPU fan).
5. Get a can of air and blow the dust out of all slots and off all components, including the ones you have removed.
6. Reseat all peripherals into the motherboard.
7. Put the case back on.
8. Plug the power back in for the computer.
9. Start your computer up.
10. Go into the BIOS and reset to Defaults to reset the CMOS
11. Fix your RAM timings to the most stable timings
12. Save and exit the BIOS and start your computer normally.

Post back if the above makes a difference. If not, I have a few other things we can test.

Yep, just started up a game and as expected after about 2 minutes of being in the menu's it gave me a BSOD and restarted.

 

[Jwoodall92]

Heres an update with a new health report and 2 new BSOD's

 

[writhziden]

As many of your blue screen errors are due to memory, run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial.

Let it run for 7 passes.

Also, even if it does not find any errors, try changing memory configurations and running Windows and games to see if the problem stops: use one memory module at a time in different slots to find any bad slots/modules. If a memory module and slot work together, that module and that slot are good. Test other modules in the good slot, and test the good memory in other slots to determine bad modules/slots.

 

[writhziden]

You have also received two system based blue screens related to your processor. Given that you are having to underclock your processor, this may be related. You may have to change processor settings to determine what provides the most stability. Additionally, you may want to check your temperatures to see if your blue screens are temperature related. To do so, download and install HWiNFO64 Download. You may have to install it multiple times before it runs; the installation seems to be a little buggy. That software will monitor temperatures of your CPU and GPU and possibly other components if they have temperature sensors. You can track changes using the logging function to create a .csv file that opens in excel. If you want to, you can post the log .csv file on here (or zip it if it is too big to upload) for us to take a look at.

 

[Jwoodall92]

Heres the .csv
I didnt run it for too long, I was going to start a game so that you could see the temperatures maybe spike if thats the problem but then realised you have to stop the logging for it to create the document.. I didnt experience any BSOD's whilst it was running.

 

[writhziden]

Heres the .csv
I didnt run it for too long, I was going to start a game so that you could see the temperatures maybe spike if thats the problem but then realised you have to stop the logging for it to create the document.. I didnt experience any BSOD's whilst it was running.

You shouldn't need to stop the logging for it to create the document. When I run it, it creates the document in realtime.

Temperatures look good for that set. See what happens if you Blue Screen.

 

[Jwoodall92]

As many of your blue screen errors are due to memory, run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial.

Let it run for 7 passes.

Also, even if it does not find any errors, try changing memory configurations and running Windows and games to see if the problem stops: use one memory module at a time in different slots to find any bad slots/modules. If a memory module and slot work together, that module and that slot are good. Test other modules in the good slot, and test the good memory in other slots to determine bad modules/slots.

As I mentioned in the original post I did run the windows memory diagnostic tool for 2 hours or so and received absolutely no errors. Is there still any point in running memtest? I have no DVD+R's about so i'll have to buy a new pack if I need it.

 

[Jwoodall92]

Heres the .csv
I didnt run it for too long, I was going to start a game so that you could see the temperatures maybe spike if thats the problem but then realised you have to stop the logging for it to create the document.. I didnt experience any BSOD's whilst it was running.

You shouldn't need to stop the logging for it to create the document. When I run it, it creates the document in realtime.

Ok, ill run another one now and also try and run the game and see if we can see any correlation in the temperature and the BSOD.

 

[writhziden]

As many of your blue screen errors are due to memory, run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial.

Let it run for 7 passes.

Also, even if it does not find any errors, try changing memory configurations and running Windows and games to see if the problem stops: use one memory module at a time in different slots to find any bad slots/modules. If a memory module and slot work together, that module and that slot are good. Test other modules in the good slot, and test the good memory in other slots to determine bad modules/slots.

As I mentioned in the original post I did run the windows memory diagnostic tool for 2 hours or so and received absolutely no errors. Is there still any point in running memtest? I have no DVD+R's about so i'll have to buy a new pack if I need it.

Memtest does a thorough test for more passes. Two hours of testing generally is not enough to find memory issues. Many people run for 24 hours to get a better idea of how well the memory works.