Windows 7: I'm at my wit's end...

I built this computer back in November and it has given me nothing but trouble ever since... I've re-loaded the OS at least twice; the last time in December...

I'm running Windows 7 Home Premium 64-bit; it's an OEM version...



I get many, many BSOD's doing all sorts of stuff... watching videos; upgrading with Windows Update; using Office, looking at mail with Windows Live Mail, etc...

also, programs stop working for no apparent reason; I have to re-boot to be able to use them again...

I have to update numerous times before an update loads without failing (this is especially prevalent in updating definitions in Microsoft Security Essentials)...

I'm attaching the zip file (hopefully I'm doing this right)...

I thank you for the help !!!

mikewhen

Mike Hi and welcome

There are at least 8 different causes wich is usually indicative of a hardware problem. Since a majority of these point to memory management, and cache management I would start by test the ram.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.


Also just to verify the OS I would run a system file check

SFC /SCANNOW Command - System File Checker

Let us know the results on both


Ken J

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool
memory is completely depleted, this error can stop the system.

However, during the indexing process, if the amount of available nonpaged pool memory is very low,
another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

You have some processes that are somewhat uncommon in my experience. Might I suggest turning off or uninstalling what you don't need until you have system stability again? You'll want to at least make sure your iTunes, Google and Amazon apps are not making it harder to resolve the issue.

Ouch, just tried opening your DMP files with my new Visual Studio 2010, which reported "debugging older style crash dumps is not supported".

I did find a tool that you might look at, |MG| BlueScreenView 1.31 Download but I do not have any experience with it.

Here is a Microsoft article on crash dump debugging. You would need to perform it to examine your particular system image... http://support.microsoft.com/kb/315263

You might consider turning off indexing since WSEARCH is aborting. At least until things get in order again.

Your health report today shows your anti-virus is not installed. You might re-install MSE. Personally, I keep a download handy instead of having to re-download.

One oddity. You have really nice system performance numbers in everything except your gaming graphics. This seems really odd considering how awesome the rest of your machine is and this number is a clunker. Could you check that you have the latest graphic drivers installed for your hardware?

Interesting... MSE is loaded and running... I do have the exe downloaded... I'll try that after running the memtests...

Thanks,
mikewhen

I went to the device manager and checked for updates... the system looked online and said I have the latest driver...

Thanks,
mikewhen

Mike Hi and welcome

There are at least 8 different causes wich is usually indicative of a hardware problem. Since a majority of these point to memory management, and cache management I would start by test the ram.

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.


Also just to verify the OS I would run a system file check

SFC /SCANNOW Command - System File Checker

Let us know the results on both


Ken J

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool
memory is completely depleted, this error can stop the system.

However, during the indexing process, if the amount of available nonpaged pool memory is very low,
another kernel-mode driver requiring nonpaged pool memory can also trigger this error.[/QUOTE]

I started the memtest, but then noticed your note about doing individual sticks, which I didn't do... I'll re-submit..

also, I ran the scannow; it told me there were some errors that it couldn't fix... I'll re-run using the "scan and read" (Option 3)...

Thanks,
mikewhen