Debug A BSOD MiniDump?

Hi all,
I’ve been getting frequent BSODs listing MEMORY_MANAGEMENT & PFN_LIST_CORRUPT. I’ve been hunting for solutions on the internet and it seems to be a driver problem that Windows 7 doesn’t like.
I’ve ran a memtest and all hardware is working perfectly. No problem there.
So, I’ve resolved to using the Driver Verifier Manager to stress test my drivers and so far it gets to the Starting Windows screen and then blue screens.
If someone is good at debugging this latest mini dump that I’ve uploaded to highlight the problem, then that would brilliant. Hopefully I can get rid of this horrible problem.
http://db.tt/m1YSsEN9
Thanks if anyone can help.
Kez.
Answer #1
Anyone?
Answer #2
I've ran a memtest and all hardware is working perfectly.
memtest only test memory
the BSoD’s start right away after a boot or it take a while for them to happen
what are your temps
don’t see anything in the memory dump that helps
on the BSoD it’s self, just below the stop code, is there a file name listed ?
Answer #3
on the BSoD it's self, just below the stop code, is there a file name listed ?Filenames are generally useless for memory related errors as the file could vary every time. The stop code and error is essential though.
Use this tool to see the blue screen once again.
http://www.nirsoft.net/utils/blue_screen_view.html
I've ran a memtest and all hardware is working perfectly. No problem there. How are you so sure all the hardware is functioning correctly?
Answer #4
as the file could vary every time.
but if it’s the same file every time it just might ba a clue
and if it’s a bad driver then you get the same file name every time
been working on windows PC’s for almost 20 years and never had a “stop code and error” tell me what’s wrong
to me those codes are useless and the file name is the essential one
bluescreenview shows this, saying “ntoskrnl.exe” is the “caused by driver”
and here’s the error complete with codes
102911-27955-01.dmp   10/29/2011 11:51:46 PM   MEMORY_MANAGEMENT   0x0000001a   00000000`00000031   fffffa80`074db430   fffff880`0572c000   fffff8a0`1b54d3a2   ntoskrnl.exe   ntoskrnl.exe+7cc40               x64
for which I would have told the OP to test the memory, but that’s been done already
my guess is still heat till I see that the temps are good
running a disk check is also a good place to start
if temps are good the next thing would be to pull out and reseat any add-in cards (video or anyting in PCI slots)
Answer #5
been working on windows PC's for almost 20 years and never had a "stop code and error" tell me what's wrong
to me those codes are useless and the file name is the essential one Sometimes you can get hints with the stop code. 0x0000001a is related to unstable memory configuration. It’s not usually software related. Either the voltage or timing information is wrong or a problem with the motherboard itself.
Answer #6
unstable memory configuration.
if it’s memory related it could also indicate and overheating memory controller (northbridge chip of the chipset)
Answer #7
Exactly but remember newer CPUs have the IMC built in.
Answer #8
Thanks for the replies guys.
In regards to temps, the CPU is running at 40/idle 60-65/full load. The GPU is running at 35/idle 70/full load. I’ve disconnected all my components and re-connected them, My RAM doesn’t seem to be overheating at all. I’ve referred to the manufacturer (G-Skill RipJaws Memory) and voltage seems to be fine. PSU is a 700w OCZ setup and that isn’t overheating at max load.
The motherboard isn’t overheating either. Even at max load on all components. I even restored all defaults in the BIOS (which hadn’t been tampered with anyway) just to see if it solves my problem. I haven’t had a blue screen yet so we’ll see.
I am largely to believe it is a driver problem. Especially when Windows blue screened after I stress tested my “non-Microsoft” drivers.