I'm at my wit's end...

don't know what sort of optical drive you have installed in your rig,
but it seems to me that you are stressing that PSU close to the max..

try fitting a more powerful one - say 500/600watts
that ought to improve your system stability..

you can pick them up relatively cheaply, these days..
and, as you probably already know, they are really easy to fit..

you can verify your PSU requirements here..
http://educations.newegg.com/tool/psucalc/index.html

zigzag3143 said:

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.

I haven't done the memtest yet, but I did the sfc scan... it told me of of files that it couldn't repair... however, when I tried to pull out the "[SR]" tags using the command, the txt file was empty... so, I copied the entire cbs.log file into the sfcdetails.txt file and am attaching that here... I do notice the SR string a lot, so I'm frustrated that the SR string command didn't work...

Thanks,
mikewhen

mikewhen said:

zigzag3143 said:

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.

I haven't done the memtest yet, but I did the sfc scan... it told me of of files that it couldn't repair... however, when I tried to pull out the "[SR]" tags using the command, the txt file was empty... so, I copied the entire cbs.log file into the sfcdetails.txt file and am attaching that here... I do notice the SR string a lot, so I'm frustrated that the SR string command didn't work...

Thanks,
mikewhen

I've run the memtest on my two sticks...

the first stick passed all 5 passes in either of the two memory slots that I've been using...
the second stick failed in 3 of the 5 passes that I did in the first slot; I didn't think I needed to go on... I've attached a txt file of the 3 errors; all happening on the same test... currently, I'm running on the one good stick...

So, as of right now, I'm planning on buying another stick (or maybe a two-stick set to replace both), plus upgrading my PSU...

Thanks,
mikewhen

mikewhen said:

I've run the memtest on my two sticks...

the first stick passed all 5 passes in either of the two memory slots that I've been using...
the second stick failed in 3 of the 5 passes that I did in the first slot; I didn't think I needed to go on... I've attached a txt file of the 3 errors; all happening on the same test... currently, I'm running on the one good stick...

So, as of right now, I'm planning on buying another stick (or maybe a two-stick set to replace both), plus upgrading my PSU...

Thanks,
mikewhen

OK, I purchased a set of G-Skill Ripjaws 2GBx2 DDR3-1600's, and a new 500 watt PSU, installed it all yesterday, and so far, so good - no crashes; my MSE has been updating definitions without failing; have had no applications stop working suddenly....

the only issue I have now is that the Service Pack 1 will still not load for me... but, that's another post...

one other question : my assumption is that since my new memory sticks are DDR3-1600, and the one good one from my original set is a DDR3-1333, I really can't use the original one as a third stick in my machine... am I right about that ???

I thank all of you for helping me with this; you do good work...

mikewhen