BSODs, possible faulty hardware but not sure...

Hi Everyone,

My PC recently crashed, i.e. would not boot into Windows and I had to reinstall. I thought I may have fried the processor by overheating it (apparently I did not apply the thermal paste very effectively when I assembled this thing back in 2011...) but that does not seem to be the case, as I was able to reinstall Windows7 and get this machine back up and running. I'm still not sure why it crashed in the first place...

The first Windows7 reinstall I did last week had to be redone, because for some reason it would never successfully update Windows7 SP1 (it just kept throwing errors when it tried that update, although it would do other updates just fine).

My second attempt at the Windows7 reinstall seems to be working, as I was able to fully update this Windows7 installation and it is currently working just fine.

However, I am seeing a high number of BSODs since the reinstall, and I am wondering exactly what is going on here. I am leaning towards a hardware malfunction, but I'm not sure. I've run CHKDSK on my hdd and also run Memtest86+, and neither of those have found anything. I'm about all out of options/expertise.

Minidump logs are attached. Any help is much appreciated!

Another BSOD this morning. I was listening to Pandora and had just minimized my Chrome browser window, that's about all that I was doing at the time of the crash... so I'm not sure exactly what is causing it.

Updated dump log attached. Thanks in advance.

Hi - were you listening to Pandora using chrome?

From where were you streaming it..?

These streaming BSOD's are too common to be a case of deciding it is faulty hardware - unless streaming is somehow corrupting something or causing hardware to fail.

Dustin - your logs end similarly to mine, where your machine loses its name and a bunch of services stop and it keeps loading and revoking windows licenses..!

You also have this uniform 50% trial thing that some chrome users are having...

It has to be something to do with streaming and resultant corrupt data.
Some streams seem to leave areas of a disc with a bad record. VK mobile version seems to be especially dodgy (but have you seen the number of simple spy plug-ins available for that platform!?).
Windows appears to believe that the space is filled (and so can be overwritten), but it is actually empty space that is flagged as filled.

Whenever some network device tries to write to this "filled" empty space, it seems to start a lot of problems and it corrupts my network drivers.

When I am not streaming (even having windows media streaming service can cause it to break), I get "page fault in non-paged area", where the buffering is happening in the empty filled space.

I do not know if this is true, but it is my speculation based upon when I became an expert in this subject last night and this morning.

If I manage to get my machine working again - I am going to use only Incognito windows in Chrome and try to find a way to keep temp and buffering cache cleaner :/

The troubleshooting I've done myself, using the special_pool_header stuff, has led me to believe it is a network driver issue.
When I repaired my network drivers - the streaming worked ok.
On restart, the drivers are causing problems again.
I repair them, it works til restart, then BSOD like usual.

If I figure out if it is this journal index false filled space thing, page file or cache from network drivers and I figure out how to fix it - I will let you know

Thanks for the reply, tehsaccade.

Yes, I had Pandora open in Chrome, and that was my only window and only tab open at the time. I wasn't really doing anything else besides drinking my morning coffee when the BSOD occurred, although I had just minimized the browser window.

I am not sure that these BSODs are related to the streaming, but perhaps they are. The reason that I am leaning towards a hardware failure or malfunction is because of the initial Windows 'crash', or more specifically when my system would not boot into Windows last week and I had to reinstall (twice). Now I am getting persistent BSODs and all I can figure is hardware problem...

Either way, I'm out of ideas, so I was hoping my minidump logs would reveal something.

It's almost like the internet is so high voltage that the pressure of its delivery frys my computer and messes it up.

I'm for a conspiracy where they are running our HDD's down faster with streaming services, and causing them to fail, while driver corruption from disc failure compounds the problem - this is all to sell us stuff, somehow, if only new hard drives...

However - if you had an initial "crash" - it may have been this that corrupted your data/drivers. Make sense that a wound needs attention, right?

I'd start exploring looking for corrupt stuff that is getting worse unless you fix it.
Might not need a reinstall - you can do the repair install and not lose much stuff.

I hate to lose my adobe suite and documents.

I really want to know why suddenly our machines are renamed and suddenly network and search services fail.
Perhaps it is malware related. I stream from some dodgy places sometimes, and download some dodgy installers...

It might take a few hours, but have you run chkdsk to see if it's the HDD that has bad indexing or anything?
Mine has found some issues on the drives with pagefiles, and also on my system drive.

I will try to repair the network drivers and recreate the BSOD after it is completed with the disc checks.
After repairing the network drivers and restarting those services - I had no problems til the restart, as i said :/

Also - as part of symptoms - can you connect to skype or MSN?

I'm not sure what exactly is going on. Perhaps it is a grand conspiracy... lol.

I did perform a CHKDSK on my hard drive, and it found nothing wrong. I also did a memory diagnostic using MEMTEST86+, which found nothing wrong as well.

I've never had any need to use Skype or MSN, so I don't even have accounts with those services :|

Thanks for the input!

If your hardware is all ok, and your disc is all ok...

Next step is drivers, then, I reckon, starting with networking.
After that, I did BIOS.
After that, I'd start rolling back windows updates.

If I had to do a repair install, ok sure, then I can test out the updates 5-10 at a time each day, and find out which set causes the BSODs.

That happened with my last PC, and - to be honest - there was a mid-level / optional update lately before this BSOD spree for me.

I know it will end with me wiping everything and starting again, and then swearing off touching anything even remotely dodgy with my computer, which will last for about 2 days.

Sorry I can't help more, but I will keep investigating why our logfiles are similar.