asked on
BSOD on Windows 7. BAD_POOL_HEADER, PFN_CORRUPTED, PAGE_FAULT_ON_UNPAGE
Hello,
I'm having continuous BSOD on my recently installed Windows 7, with a NVIDIA card. It worked well for the first 2 days but then I started to have BSOD. I've restored the system to before my installation of Windows Live and it seemed to work fine. However now, without any extra install besides the the normal updates, the Blue screens are back. I have had all of the Stop messages on the top on the BSOD output.
I run the memory diagnostics tool and somewhere close to the beggining it says "Hardware problems detected. Contact your computer manufacturer for a solution". Which I think is really a crummy message since it could at least tell me which memory has a problem: video, RAM, processor cache. So it's pretty useless unless I start gutting the system component per component.
I would really appreciate some help on this.
R.
I'm having continuous BSOD on my recently installed Windows 7, with a NVIDIA card. It worked well for the first 2 days but then I started to have BSOD. I've restored the system to before my installation of Windows Live and it seemed to work fine. However now, without any extra install besides the the normal updates, the Blue screens are back. I have had all of the Stop messages on the top on the BSOD output.
I run the memory diagnostics tool and somewhere close to the beggining it says "Hardware problems detected. Contact your computer manufacturer for a solution". Which I think is really a crummy message since it could at least tell me which memory has a problem: video, RAM, processor cache. So it's pretty useless unless I start gutting the system component per component.
I would really appreciate some help on this.
R.
Windows 7
Last Comment
nobus
can you post the minidump for more info? see windows\minidumps
ASKER
This is the latest minidump I got.
110910-31512-01.dmp
110910-31512-01.dmp
ASKER
110810-25256-01.dmp is a Dump I got that I didn´t even noticed. The computer did not crash afterwards for over one day.
110610-33399-01.dmp is the first I got when the computer started to crash 40 seconds after login. I see my Desktop and it crashes very little after. I can only send this because I´m running on Safe mode and it takes longer to cra
110610-33399-01.dmp
110810-25256-01.dmp
110610-33399-01.dmp is the first I got when the computer started to crash 40 seconds after login. I see my Desktop and it crashes very little after. I can only send this because I´m running on Safe mode and it takes longer to cra
110610-33399-01.dmp
110810-25256-01.dmp
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
@nobus. Thanks for the info. I'll try it this evening (it's 10 AM here).
post results !
ASKER
While attempting to put the memtest iso in the system I realized that my DVD drive was not properly connected. The SATA cable somehow got loose. after reconnecting the cable I've let the memtest86 run one round, nearly 30 minutes, and no errors were detected. This evening I'll let it run all night to be sure.
ok - how much ram you have? 1 or 2 Gb takes more than 30 minutes for 1 pass
since you have the ubcd - run also a disk diag - then at least , you're sur about the basics
since you have the ubcd - run also a disk diag - then at least , you're sur about the basics
ASKER
Ok, I've run it again and no errors were detected. For now I'll consider the problem solved.
ASKER
Oops, I hadn't seen nobus' last comment. I'll try it today.
if no ram problems are detected - do test the disk
if it is ok, run a disk scan for errors on it; and if that is ok - defragment it !
if it is ok, run a disk scan for errors on it; and if that is ok - defragment it !
ASKER
Went through a full system analysis and all checked out ok. Later on I re-installed a device that caused the problem to come back. It turns out that the driver is corrupted. A system restore fixed that. I would like to thank nobus for providing me with the tools to perform a thorough diagnostic.
>> Later on I re-installed a device that caused the problem to come back << thanks for the feedback - what device was that ?
ASKER
It's a USB device using a proprietary driver. it was still a Beta version (from my work) and there were still some glitches on the version I was installing. Should have thought about that earlier.
tx for feedback!