Windows 7: BSODs appearing after each 24 hour cycle

hello, i purchased this system in March 2009 and i assembled it myself. when i was using Windows Vista x64, i had no problems. it was only after a few months installing Windows 7 x64, i found that BSODs kept appearing. no new hardware added since last year's assembly.

key problem: after leaving my PC on for more than 24-36 hours, with no CPU/memory/graphics applications running constantly, it will crash.

common BSOD errors: either "page fault in non-paged area" or "memory" messages

when crashes: always after about 24-36 hours running, with perhaps only torrents left on idle, no other CPU/memor/graphics applications running

PC use: only very light gaming, heavy web-browsing, chats, rare Photoshopping, word-processing



temperatures: when gaming, CPU no more than 50C & graphics card no more than 65C, hard drives no more than 45C, memory unsure

how BSOD avoided: i notice if i shud down my PC about after 24hrs running, and leave it OFF for a few hours, BSODs will not appear. but anything more than 24-36hrs running, it will crash

memory testing: used memtest 386. when after BSODs, it will show PLENTY of errors with the test unable to end ie. persistent errors appearing. if i leave the PC OFF for 24hrs or more, and then retest, NO errors. which is odd.

tried: swapping memory slots, no difference. tried cleaning dust (even thought little dust), no difference.

graphics card stress test: when tested within 24hours usage of PC, no errors.

heat?: unsure, bcoz if i turn on the Air-Conditioning in the room, CPU/hard drive/graphics card temps will drop even under load bcoz of cooler ambient temperature. it still will crash even though if the PC has been running more than 24-36 hours.


soo..... i'm suspecting it's either faulty memory or motherboard. i dunno what is the cause bcoz my system will crash after 24-36hr period. EVEN if i think the temps are normal. and when the PC is idle.

what i will say is, i can tell when exactly it will go into BSOD:
1. if i'm gaming, the game will crash & report hardware failure. even if i'm constantly monitoring the graphics card temp, no more than 60C.
2. MSN will crash all of a sudden.
3. Windows Aero will report & error & turn off into basic theme.
4. of the 3 web-browsers to show pre-BSOD signs, it is Firefox. FF will crash suddenly. IE or Google Chrome has never shown pre-BSOD crashes.

if any one of those 4 signs appear b4 an actual BSOD, my attempt to shut down properly will lead lead to BSOD immediately or system unable to shut down correctly. sometimes, when my PC is idle & not running anything, if after the 24-36 hour period, BSOD will also appear.

i would very much appreciate if i could get help on which piece of hardware you think is at fault. so i can go & replace.

my hardware details are in my signature, and i've attached the dump files.

thank you in advance.

kind regards,
Alex

A lot of these are memory-related, but they're not specifically RAM. Also, the Aero thing and the fact that it seems to happen on a fairly regular pattern leads me to believe that enabling driver verifier might be a good idea to see if another dump with it enabled points us to the culprit (if it isn't hardware).

Alex hi and welcome

Thanks for doing all the prelim work

Ok you have the usual memory, and video drivers listed as probably causing the crashes, but one thing I noticed is a file called fastfat.sys. This is an XP file that vista sometimes used but isnt (as far as I know) in win 7 did you do an upgrade or clean install?

These are the usual causes of the most frequent bug check
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Let us know

Ken

thanks for the reply. i'm away from my pc for the next few days, but i'll give it a go when i get back, and let you know how it fairs with another dump file.

hey Ken

sorry for the late reply, i'm out of town at the moment.

i did a clean installation. in fact, several clean installations, however, the problem persists.

when u say defective memory but not just RAM, what other defective memory do you mean?

so how does one go about solving this? replace the RAM/mobo?