Help bsod

H2SO4 said:

JNCable said:

I didnt know what some of the drivers were, and I googled them, and found nothing, so I tried windows 7 again, and still getting bsods, and the debuggers not working, so I don't even know whats causing the problems.

My "new" windows 7 bsods
Attachment 33789

Attachment 33790

Attachment 33791

If this is a legit version of Win7, in terms of licensing, then you've almost certainly got a hardware problem. One of the dumps shows the "system protection" driver - spsys.sys - causing a crash while attempting to deal with one of its periodic interrupts used for licensing verification purposes. Assuming it's not being interfered with by software which would have reason to interfere, it is a very hardware-ish crash.

As a suggestion, make sure the system is adequately cooled and nothing is overclocked.

It is legit, I checked the hashes I got it from a site that said it was legal, and if you don't believe them you check the hashes from the official site, or something like that and I did and they matched, but that site offered some illegial program called a loader that gave you a free registration key, but I didn't download or use that program, and it is't and it never was on my system, I just restart my system every thirty days.
And no overclocking and I haear the fans working fine

JNCable said:

H2SO4 said:

If this is a legit version of Win7, in terms of licensing, then you've almost certainly got a hardware problem. One of the dumps shows the "system protection" driver - spsys.sys - causing a crash while attempting to deal with one of its periodic interrupts used for licensing verification purposes. Assuming it's not being interfered with by software which would have reason to interfere, it is a very hardware-ish crash.

As a suggestion, make sure the system is adequately cooled and nothing is overclocked.

It is legit, I checked the hashes I got it from a site that said it was legal, and if you don't believe them you check the hashes from the official site, or something like that and I did and they matched, but that site offered some illegial program called a loader that gave you a free registration key, but I didn't download or use that program, and it is't and it never was on my system, I just restart my system every thirty days.
And no overclocking and I haear the fans working fine

I'm glad to hear that it's legit, but I would encourage you to get the actual image from Microsoft, as opposed to someplace else that has to go out of its way to tout its legitimacy.

Since you paid for a Windows license, Microsoft will presumably offer you a way to get the media or image directly from them or their affiliates. Otherwise, you run the risk of unknown nasties lurking underneath your OS, and in this case the licensing mechanism appears to be experiencing a spot of bother. If it's not caused by some sort of licensing trickery, then the nature of the crash would leave me surprised to find out that it wasn't a hardware problem.

So, you recommend just getting another copy of the iso, and if its not hardware that should fix it? Because my xp won't work either=/ So, if I'm not sure that will fix it, and if its hardware, any particualr part of this sytem in particular is most likely the part thats screwy?=/

If netbooks didn't have a max of 1g ram....I'd tottally buy one right now=/

Ok, I tried using a debugger on the bsod it won't let me upload and apparently what I gather from it, is it blames win32.sys and firefox (for the latest bsod at least)

Attachment 33819
Nvm just needed to zip the dump from before, here it is

can you edit which dump files are current and which ones are under XP?

JNCable said:

So, you recommend just getting another copy of the iso, and if its not hardware that should fix it?

To paraphrase the question, will a clean install of a "real" copy of Win7 run without constant BSODs on healthy hardware? Yes, absolutely.

JNCable said:

Because my xp won't work either=/ So, if I'm not sure that will fix it...

You had some ancient drivers under that XP installation, and it's entirely possible that they were at least partially responsible for the crashes. Some of the hardest problems to troubleshoot are the "compound" ones caused by multiple superimposed symptoms from different root causes - say a mix of hardware and driver crashes. For your sake, I hope the hardware is fine, the old drivers under XP were responsible for the XP crashes, and a new install of a Win7 image obtained directly from MS will work well.

As a suggestion, once you reinstall Win7 using an MS-sourced image, DON'T install anything else at all for a while... no updates, no apps, no games... literally nothing that's not on the Win7 disc. Only if that works flawlessly should you then consider adding other software, and do it slowly so that if the BSODs should return you've got a good idea of the likely cause.

JNCable said:

and if its hardware, any particualr part of this sytem in particular is most likely the part thats screwy?=/

Unfortunately, minidumps are a very poor way to discern just which hardware component may be responsible. They only provide a sparse summary of the software environment at the time of the crash, and with experience that can sometimes allow one to form a gut feeling as to whether the cause is likely to be hardware - but not necessarily which hardware component.

@Zigzag:Sure, here:
XP BSODs
Attachment 33820

Win 7 BSODs
Attachment 33821
Attachment 33822
Attachment 33823
Attachment 33824

Just found some fun things for y'all in my administrative event logs-.-

Service 'WMPNetworkSvc' did not start correctly because CoCreateInstance(CLSID_UPnPDeviceFinder) encountered error '0x80004005'. Verify that the UPnPHost service is running and that the UPnPHost component of Windows is installed properly.

Audit events have been dropped by the transport. 0

Warning 10/29/2009 6:47:59 PM WLAN-AutoConfig 4001 None

The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

The Computer Browser service depends on the Server service which failed to start because of the following error:
The dependency service or group failed to start.