BSODS

[superbarnie]

Okay, i just installed SPEEDFAN.

The temperatures are:
GPU: 41C
HD0: 40C
Temp1: 48C
Core0: 45C
Core1: 46C
Core2: 48C
Core3: 49C

This is while my computer is pretty much idle. Only Chrome running atm.

[the86d]

There is a CD typically called MRI, it is apparently what GeekSquad is issued for troubleshooting, and includes a test of pretty much everything just by hitting enter. A torrent/ISO can be found if you look on the sea of information, and is bootable. I understand that this takes about an hour to run all tests (aside from HDD, and this is the major long test depending on drive size). This might be an option, as I do not know of anything opens source/free that digs that deep.

Does windows try to research the problem for you when it comes back up?

Are there clips on the HDD's SATA connectors holding them firmly in place?

I think this might be an ISO of something that is included on that MRI called the drive fitness test: https://www1.hgst.com/hdd/support/do...2_v416_b00.iso to test the drive...

I think we are all just throwing out ideas, but booting to and running diags from that MRI HAS been useful in some cases such as this... I hear.

Edit: Just out of curiosity, can we get a screen-scrape (just the area of the screen in question) of all stuff running by your clock after you show all icons and notifications on the taskbar?

"chkdsk /f" as admin to verify there are no errors with files on the drive, bad sectors in swap/data area (it will require a reboot after you answer yes? I usually do this after a clean install of Windows and after all Windows updates compete and it will usually correct issues with the MFT, almost every time.

Did you blow the grills/fans out from both directions and make sure to not cover any fan vents/fan exhaust areas while it is running?

Maybe running something that uses 100%-ish CPU would tell you if it was a heat issue quickly with speedfan running? Do fans get loud/fast a lot?

A coworker actually had a similar problem, and his issue was that there was a blanket of cat-fur and dust on the inside grill-edge of the heatsink (the side where the fan is) causing about ZERO air-flow and causing BSODs.

It has been a while since I reseated a CPU on a lappy, but did you make sure to lock the CPU locking screw all the way when putting it back in, if it has one, or was it just pressure-forced in/out?

[stilly]

There is a CD typically called MRI, it is apparently what GeekSquad is issued for troubleshooting, and includes a test of pretty much everything just by hitting enter. A torrent/ISO can be found if you look on the sea of information, and is bootable. I understand that this takes about an hour to run all tests (aside from HDD, and this is the major long test depending on drive size). This might be an option, as I do not know of anything opens source/free that digs that deep.

Does windows try to research the problem for you when it comes back up?

Are there clips on the HDD's SATA connectors holding them firmly in place?

I think this might be an ISO of something that is included on that MRI called the drive fitness test: https://www1.hgst.com/hdd/support/do...2_v416_b00.iso to test the drive...

I think we are all just throwing out ideas, but booting to and running diags from that MRI HAS been useful in some cases such as this... I hear.

I have MRI. I used it recently for someone's system that kept locking up. First I used speedfan though to determine that it was the graphics card that was overheating. Then I replaced the graphics card with a new one. Problem was solved for about 2 weeks, then it came back. I have not gone back there yet but he is monitoring the situation for me.

Okay, i just installed SPEEDFAN.

The temperatures are:
GPU: 41C
HD0: 40C
Temp1: 48C
Core0: 45C
Core1: 46C
Core2: 48C
Core3: 49C

This is while my computer is pretty much idle. Only Chrome running atm.

48 and 49 is kinda getting up there but nothing alarming. Since laptops tend to run hotter I would imagine that temps up to 57 would prolly be allowed.

Keep your eye on speedfan and see when you get a bsod if the temps go much over 55 degrees.

This might be either a driver or just defective hardware. And of course, since it is a laptop it is kinda hard to unplug all but the HD and run it in a burn in mode... :\

This thing might have a hardware issue that is just defective period. That is where I am leaning towards now.

Hey wait a second, what is the STOP code? forget about bugcheck, what is the STOP code that gives the bsod? Is it always the same thing?

What if you were to purchase a single 1GB or 2 GB piece of Kingston RAM and run with that instead of the g.skill?

[superbarnie]

I've already posted all the STOP codes above. They are shown in the Bugcheck Analysis. It's the string next to "Bugcheck".

I'll try this MRI.

[superbarnie]

I ran the MRI FACE thing and it didn't detect any problems.

I also disassembled the laptop and tried to remove as much dust as possible. But there wasn't much dust to begin with anyways.

There's hasn't been any crashes lately, but I also haven't been doing any resource intensive tasks lately either.

[cid`]

puzzling.. since its a laptop, take out the battery and leave just the power supply plugged in. see if that makes any difference.. everything you've said/done doesnt narrow it down to anything unfortunately, all your temps are way below TDP also.

Does it ever just restart or does it BSOD every time?

[Deadbolt]

its a combo of memory not being properly addressed due likely to the agent being overwhelmed and overheated.

new hardware time if you expect the performance from it you desire.

[stilly]

I've already posted all the STOP codes above. They are shown in the Bugcheck Analysis. It's the string next to "Bugcheck".

I'll try this MRI.

This is from windows 7 or vista?

Sorry, I am used to seeing the STOP codes, not bugcheck codes, I look at the last two digits/letters of the stop code for guidance normally but I do not see any that I recognize here.

Hmmm, what could it hurt to take out the battery and see if they continue like the other poster said.

I forget about that cause it is a laptop. but I agree with it, give it a try since we have nothing else left to lose here.

[superbarnie]

It's Windows 7 Home Premium x64.

I was reading this page. It says that the string next to "Bugcheck" is the STOP code.

[stilly]

Well then if that is the case then these look like random errors. The only thing I can guess is possible heat or memory. The next step is probably to open it up and see if there is any dirt or blockage anywhere inside or maybe even busted or close to busting capacitors. Something is not right.

Can you verify that on the BSOD, after it says STOP and that long number, the last few digits are indeed put into the bugcheck? Like here: STOP: 0x00000079 - This would mean that the bugcheck should say 79 then. Yeah I am more familiar with windows XP then Windows 7, but to make things worse this is a laptop also. And if you reloaded everything then it prolly means that it is hardware based. SOMETHING has changed and if it was not the software, it must be the hardware, and if you did not change anything, hmmm, put your old ram back in instead of the gskill.

Do you have your old ram? Maybe this is a case of incompatible ram and it finally took it that long to get here.

Is the RAM the only thing you replaced?