The ONLY clue I have is that a program crashed much earlier in the day, literally about 4 hours before this happened. Could there have been some residual bit in the memory that caused it?
Intermittant BSOD
Started by
Chazz K
, Jan 30 2009 10:56 PM
#1
Posted 30 January 2009 - 10:56 PM
The ONLY clue I have is that a program crashed much earlier in the day, literally about 4 hours before this happened. Could there have been some residual bit in the memory that caused it?
#2
Posted 31 January 2009 - 12:31 AM
Your dump file refers to PAGE_FAULT_IN_NONPAGED_AREA error at win32k.sys
It looks to me like RAM problem.
Run memtest
Click this for a guide to using Memtest
Click this to download Memtest
Run it overnight if possible.
It looks to me like RAM problem.
Run memtest
Click this for a guide to using Memtest
Click this to download Memtest
Run it overnight if possible.
#3
Posted 31 January 2009 - 12:37 PM
Ran it overnight, using all tests, 9 passes on all four gigs of memory. No failures, no problems at all.
It couldn't POSSIBLY be that I have 4 gigs of memory, but Windows XP is only seeing as 3.5, could it?
It couldn't POSSIBLY be that I have 4 gigs of memory, but Windows XP is only seeing as 3.5, could it?
#4
Posted 31 January 2009 - 02:08 PM
It's normal for 32-bit system. It won't see whole 4GB.
You have to remember, that no software RAM test (like memtest) is 100% reliable, so...
Since you have a looooot of RAM (XP really needs no more than 1GB), leave just one RAM stick (do you have 4x1GB, or 2x2GB?), remove the others, and run the computer like that for a while. If it checks out, add another stick, and so on.
You have to remember, that no software RAM test (like memtest) is 100% reliable, so...
Since you have a looooot of RAM (XP really needs no more than 1GB), leave just one RAM stick (do you have 4x1GB, or 2x2GB?), remove the others, and run the computer like that for a while. If it checks out, add another stick, and so on.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users