thanks a lot. got some work to do now..
meanwhile I'm adding here another late BSOD, this one was CACHE_MANAGER at 0x00000034, file's attached.
just another thing to be sure, when u said
with which software you would reccomende using for that ?"You might want to run full memory diagnostics, if you haven't done so already."
No problem :)
That one looks distinctly more hardware-ish than the others. Minidumps are not a good way to pinpoint the exact component which is defective - if any - but in this case the crash suggests memory unreliability.
The in-built memtest/mdsched (same thing done in a different way) has a subtle advantage over the (very popular) memtest86 that's not easy to explain succinctly. It doesn't really matter which one you choose right now though - both will perform the same task.
As a word of caution, not finding anything wrong on the first few passes doesn't by itself prove much. It can take hours or days for some types of memory abnormalities to manifest themselves during normal operation, so there's no guarantee that a memory tester will expose and isolate a problem straight away.
ok, so meanwhile I've updated the NIC driver and also the O/B sound card driver..
got another BSOD on the way - another SYSTEM_SERVICE_EXCEPTION on 0x0000003b, file's attached..
I'm gonna do the VERIFIER /FLAGS 1 /ALL cmd now.
I did the verifier cmd, I attached a screen shot of what it said,
at restart I got another BSOD - BAD_POOL_HEADER at 0x00000019.
I'm going to run the memtest now.
did the memtest - no errors.
in your point of view at the moment, would you reckon its a software or hardware problem ?
I'm relatively confident it's hardware.
I see (from the latest dumps) that you've updated the NIC driver. There's comparatively little in terms of 3rd-party drivers on your machine, and despite the "special pool" setting the latest crash fingers the kernel as being a pool corruptor. That usually means hardware.
A few minutes of memtesting is frequently not enough. Try running the diagnostics overnight.
I did another memtest, this time I used the memtest86 and took the long check. didn't find any errors.
since the last BSOD - BAD_POOL_HEADER , I didn't recive any other BSOD.
I hope that it'll remain stable.
I havent did the reviever /reset cmd - is it importent ? maybe it has something to do with the BSODs stop appearing ?
I really appreciate ur work on this forum - thanks a lot guys !
Don't do the /reset command until you're finished generating BSOD's.
The purpose of the /FLAGS 1 /ALL command is to make the system crash - hopefully naming the faulty driver when it does.
When you run the /reset command, the system will no longer stress the drivers - making a BSOD much less likely. Normally you'll see a small bit of a performance increase when doing this (depending on the settings and your system's specifications).
hey guys,
after a few days of quiet those damn BSODS came back!
I got quiet a few SYSTEM_SERVICE_EXCEPTION , CACHE_MANAGER and MEMORY_MANAGEMENT. I attached the minidumps here.
theres one dump that I know that I got over, had to do with a beta NVIDIA driver so I changed back to the latest. (I did learn something from you guys!:))
also , when u reviewed my system you suggested that my power(450W) unit was too anaemic for a present computer, should I change it ?
Quote