Blue Screen after dedicating video memory

[kogues]

BSOD after dedicating video memory: dmp file added

New system, ZT systems, amd phenom quad core, 8g memory, onboard video ati 3100, when I go into the bios and turn the video settings from auto to 1g, opening screen comes up perfectly, enter password, flash as it goes to desktop and blue screen. If I change the video setting to anything below 1g it works perfect, but system performance is below average. ZT tech support says its because I'm taking an entire gig of memory out of the dual channel memory....doesn't sound right to me...any input will be appreciated.

 

[zigzag3143]

New system, ZT systems, amd phenom quad core, 8g memory, onboard video ati 3100, when I go into the bios and turn the video settings from auto to 1g, opening screen comes up perfectly, enter password, flash as it goes to desktop and blue screen. If I change the video setting to anything below 1g it works perfect, but system performance is below average. ZT tech support says its because I'm taking an entire gig of memory out of the dual channel memory....doesn't sound right to me...any input will be appreciated.

Actaul DMP file would help. use these to find and upload them.http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

thanks


Ken

 

[kogues]

Will do as soon as I get home, I'll post them.

 

[kogues]

ok here's the latest minidump report. please let me know if i didn't do the attachment correctly.

 

[kogues]

I'm really hoping someone can help me figure this out, I don't think the ZT tech support answer is correct...

 

[kogues]

can anyone tell me what the minidump file says? I can't seem to get into it. Thanks

 

[Tews]

Your dmp file shows your error as PFN_LIST_CORRUPT (Page Frame Number)

This bugcheck usually occurs for one of two reasons, the first reason being memory corruption. If there is a buggy driver in the system that is writing on memory that it does not own, it could easily corrupt one of the PFN lists or entries. In order to rule this out, you should run Driver Verifier with Special Pool enabled for suspect drivers in the system. This will hopefully allow you to catch the misbehaving driver in the act of scribbling memory, instead of receiving a crash sometime later when the O/S discovers the damage.

Download memtest86 and allow it to run overnight... let us know how it comes out...