New
#1
BSOD at unrelated times
Hi there,
My BSOD will happen very randomly and doesn't appear to have any sort of correlation between what I was doing and when the crash happened. I've included the .zip file from the "Grab All" function on the SF Diagonostic Tool as well as my own .zip file that includes the crash reports that Windows generates each time I arrive at the desktop after crashing (just something I've copied over into simple .txt files). My system specifications are also updated on my forum profile. If this is enough information, please have at it! I will include some background information below, however, if you're interested in that as well.
-----It started giving me a BSOD approximately about two to three months ago. As I stated previously, I don't believe there to be any correlation between what I'm doing and when the crash happens, but I do play the online game EverQuest quite often and have encountered the crash mostly when playing the game and trying to zone between different areas/maps. However, this is most likely just because of how often I play the game; I have crashed just as many times while simply browsing the internet when the game wasn't even opened in the background.-----
If I was playing my game, it would freeze up during the zoning phase and produce the BSOD. If I was doing something else, such as browsing random internet sites (random forums, GMail, etc.), the system would lag up quite heavily for a very brief two to three seconds (at most), the mouse would lag up very heavily (sometimes skipping from one side of the screen to the other when trying to move it during this lagging phase) and then freeze up entirely. If the BSOD was displayed, it would always read:
Originally, it would never, ever collect the dump data and it would still be sitting at the BSOD at the "Collecting data for crash dump . . ." step even after being let go overnight. It never would progress any further and I would just hard boot the computer, arrive back at my desktop and that would be that as if nothing ever happened.A clock interrupt was not received on a secondary processor within the allocated time interval.
Finally, about three weeks ago I took it to a computer shop because when the BSOD happened, it did not start up afterward as it would normally. I hard booted and instead of loading Windows, it presented me with the Windows Startup Repair Utility and told me that there was an uncorrectable issue and that I should contact my system administrator.
The computer shop told me that there was 48KB of "bad sector" on my hard drive and that it would have to be replaced. They also said this was likely the issue of my crashing. However, ten minutes after getting it home, it froze yet again while just checking random internet gaming forums. The difference this time, however, was that it actually started collected crash dumps at the BSOD and producing error reports upon arriving back at the desktop.
I've checked (endlessly) on every single Google search I can possibly word. Every single result I find basically tells me not to overclock or dual boot, and to try removing any memory/RAM that was not factory installed. None of this applies to my laptop. There was one forum post that recommended to try updated BIOS, but unfortunately that didn't solve the issue either.
That's about all of the detail that I can recall, but if more is needed please just say so and I'll do my best to provide anything I can. I thank everyone in advance for their time, it's greatly appreciated! I really would rather fix this instead of going with an entirely new system; hopefully that's an option!
Quote
. If you or anyone else has any other suggestions, please do post away! I'm willing to try everything and anything to be able to avoid having to drop a lot of money on a new system!