hey all

i've just build a new computer about 2 months ago and since then i unfortunately encouner a lot of blue screens.

here are some logs of the last 7 blue screens (there were more):



BugCheck 4E, {99, 23c475, 7, 0}



Probably caused by : memory_corruption ( nt!MiDeletePte+447 )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0023c475, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0

Debugging Details:
------------------




BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: RelicCOH.exe

LAST_CONTROL_TRANSFER: from 80523b8f to 804f9f05

STACK_TEXT:
b0dbfb84 80523b8f 0000004e 00000099 0023c475 nt!KeBugCheckEx+0x1b
b0dbfbc8 80523d5e c00c6490 18c92000 00000000 nt!MiDeletePte+0x447
b0dbfc90 8051a434 00001590 18de1fff 00000000 nt!MiDeleteVirtualAddresses+0x164
b0dbfcac 805b21b0 189e0000 18de1fff b0dbfd64 nt!MiDeleteFreeVm+0x20
b0dbfd4c 8054137c ffffffff 00ffeefc 00ffef14 nt!NtFreeVirtualMemory+0x42e
b0dbfd4c 7c90eb94 ffffffff 00ffeefc 00ffef14 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00ffee5c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeletePte+447
80523b8f 8b5008 mov edx,dword ptr [eax+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeletePte+447

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 469f3fa8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

Followup: MachineOwner
---------

------------------------------------------------------------------------------------------------------

BugCheck 4E, {99, 2283d3, 7, 0}



Probably caused by : memory_corruption ( nt!MiDeletePte+447 )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 002283d3, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0

Debugging Details:
------------------




BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: RelicCOH.exe

LAST_CONTROL_TRANSFER: from 80523b8f to 804f9f05

STACK_TEXT:
b2174808 80523b8f 0000004e 00000099 002283d3 nt!KeBugCheckEx+0x1b
b217484c 8051a57b c0177490 2ee92000 00000000 nt!MiDeletePte+0x447
b2174ca4 805b230a 2ee92000 c0177490 879a7a30 nt!MiDecommitPages+0x131
b2174d4c 8054137c ffffffff 00fffb84 00fffb88 nt!NtFreeVirtualMemory+0x588
b2174d4c 7c90eb94 ffffffff 00fffb84 00fffb88 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00fffb30 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeletePte+447
80523b8f 8b5008 mov edx,dword ptr [eax+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeletePte+447

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 469f3fa8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

Followup: MachineOwner
---------



-------------------------------------------------------------------------------------------------------



BugCheck 1000000A, {8f01840c, 2, 0, 80511827}



Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+133 )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 8f01840c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80511827, address which referenced memory

Debugging Details:
------------------




READ_ADDRESS: 8f01840c

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiDeleteValidAddress+133
80511827 8b580c mov ebx,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from 805af057 to 80511827

STACK_TEXT:
b1445c14 805af057 06892201 84f4c020 007ffff8 nt!MiDeleteValidAddress+0x133
b1445c34 8051330d 84f4c020 84f4c158 84f4c020 nt!MiDeleteAddressesInWorkingSet+0x65
b1445c68 805d1391 00f4c020 8792df38 40010004 nt!MmCleanProcessAddressSpace+0x193
b1445cf0 805d1475 40010004 b1445d4c 804ff90f nt!PspExitThread+0x621
b1445cfc 804ff90f 8792df38 b1445d48 b1445d3c nt!PsExitSpecialApc+0x23
b1445d4c 805413e7 00000001 00000000 b1445d64 nt!KiDeliverApc+0x1af
b1445d4c 7c90eb94 00000001 00000000 b1445d64 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
0469fd38 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeleteValidAddress+133
80511827 8b580c mov ebx,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiDeleteValidAddress+133

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 469f3fa8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiDeleteValidAddress+133

BUCKET_ID: 0xA_nt!MiDeleteValidAddress+133

Followup: MachineOwner
---------



-------------------------------------------------------------------------------------------------------


BugCheck 1000000A, {9cfffff0, 2, 0, 80511827}



Probably caused by : memory_corruption ( nt!MiDeleteValidAddress+133 )

Followup: MachineOwner
---------

1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 9cfffff0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80511827, address which referenced memory

Debugging Details:
------------------




READ_ADDRESS: 9cfffff0

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiDeleteValidAddress+133
80511827 8b580c mov ebx,dword ptr [eax+0Ch]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: msmsgs.exe

LAST_CONTROL_TRANSFER: from 805af057 to 80511827

STACK_TEXT:
b1c02c2c 805af057 00092201 869cd620 007ffff8 nt!MiDeleteValidAddress+0x133
b1c02c4c 8051330d 869cd620 869cd758 869cd620 nt!MiDeleteAddressesInWorkingSet+0x65
b1c02c80 805d1391 009cd620 869b33d8 869b3620 nt!MmCleanProcessAddressSpace+0x193
b1c02d08 805d1554 c0000005 869b33d8 00000000 nt!PspExitThread+0x621
b1c02d28 805d172f 869b33d8 c0000005 b1c02d64 nt!PspTerminateThreadByPointer+0x52
b1c02d54 8054137c 00000000 c0000005 0006fee4 nt!NtTerminateProcess+0x105
b1c02d54 7c90eb94 00000000 c0000005 0006fee4 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006fee4 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeleteValidAddress+133
80511827 8b580c mov ebx,dword ptr [eax+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiDeleteValidAddress+133

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 469f3fa8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiDeleteValidAddress+133

BUCKET_ID: 0xA_nt!MiDeleteValidAddress+133

Followup: MachineOwner
---------



-------------------------------------------------------------------------------------------------------


BugCheck 4E, {99, 20bec5, 7, 0}



Probably caused by : memory_corruption ( nt!MiDeletePte+447 )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0020bec5, page frame number
Arg3: 00000007, current page state
Arg4: 00000000, 0

Debugging Details:
------------------




BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from 80523b8f to 804f9f05

STACK_TEXT:
b1226b84 80523b8f 0000004e 00000099 0020bec5 nt!KeBugCheckEx+0x1b
b1226bc8 80523d5e c009e490 13c92000 00000000 nt!MiDeletePte+0x447
b1226c90 8051a434 00000490 13d71fff 00000000 nt!MiDeleteVirtualAddresses+0x164
b1226cac 805b21b0 13c00000 13d71fff b1226d64 nt!MiDeleteFreeVm+0x20
b1226d4c 8054137c ffffffff 11c4e36c 11c4e370 nt!NtFreeVirtualMemory+0x42e
b1226d4c 7c90eb94 ffffffff 11c4e36c 11c4e370 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
11c4e360 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDeletePte+447
80523b8f 8b5008 mov edx,dword ptr [eax+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeletePte+447

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 469f3fa8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

BUCKET_ID: 0x4E_99_nt!MiDeletePte+447

Followup: MachineOwner
---------


-------------------------------------------------------------------------------------------------------


BugCheck 10000050, {af78e49c, 0, bf802d46, 0}


Could not read faulting driver name


Probably caused by : win32k.sys ( win32k+2d46 )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: af78e49c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf802d46, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name



READ_ADDRESS: af78e49c

FAULTING_IP:
win32k+2d46
bf802d46 8b4814 mov ecx,dword ptr [eax+14h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from bf80e9aa to bf802d46

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b0d2dd14 bf80e9aa bc811d70 00000003 00000000 win32k+0x2d46
b0d2dd2c bf80ea2a bc811d70 00000003 00000000 win32k!EngFreeUserMem+0x4ea6
b0d2dd40 bf80ea5b bc811d70 00000003 10ecf83c win32k!EngFreeUserMem+0x4f26
b0d2dd54 8054137c 00090252 00000003 10ecf858 win32k!EngFreeUserMem+0x4f57
b0d2dd54 7c90eb94 00090252 00000003 10ecf858 nt!KiFastCallEntry+0xfc
10ecf828 7e418c3e 7744ddb8 00090252 00000003 0x7c90eb94
10ecf858 7744e317 07c5fe68 00000001 00000433 0x7e418c3e
10ecf870 77450d8a 07c5fe68 0aa00eb0 10ecfa08 0x7744e317
10ecf9a0 7e418724 00090252 00000433 00000000 0x77450d8a
10ecf9cc 7e418806 77450340 00090252 00000433 0x7e418724
10ecfa34 7e41b88b 00210fa8 77450340 00090252 0x7e418806
10ecfa70 7e41b8f3 00641d70 005fbeb8 00000000 0x7e41b88b
10ecfa90 436c07d5 00090252 00000433 00000000 0x7e41b8f3
10ecfab4 4374fed4 0a8049c8 00010712 00010712 0x436c07d5
10ecfb00 436c07ba 0a8049c8 00010712 00010712 0x4374fed4
10ecfb88 4374f2df 10ecfc54 000001cb 000001b5 0x436c07ba
10ecfbac 4374ec71 056ab668 0a899d08 10ecfc54 0x4374f2df
10ecfcf8 4374eb10 00000020 00000000 00000001 0x4374ec71
10ecfe1c 4368e1af 00000000 00000020 00000712 0x4374eb10
10ecfe48 7e418724 00010712 00000020 00000712 0x4368e1af
10ecfe74 7e418806 4368e163 00010712 00000020 0x7e418724
10ecfedc 7e4189bd 00000000 4368e163 00010712 0x7e418806
10ecff3c 7e418a00 10ecff64 00000000 10ecffb4 0x7e4189bd
10ecff4c 42f8e693 10ecff64 079a4d78 00140000 0x7e418a00
10ecffb4 7c80b6a3 09ee5618 079a4d78 00140000 0x42f8e693
10ecffec 00000000 42f8e45c 07a30538 00000000 0x7c80b6a3


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k+2d46
bf802d46 8b4814 mov ecx,dword ptr [eax+14h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k+2d46

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46d2c6a4

FAILURE_BUCKET_ID: 0x50_win32k+2d46

BUCKET_ID: 0x50_win32k+2d46

Followup: MachineOwner
---------



-------------------------------------------------------------------------------------------------------



BugCheck 1000000A, {28, 2, 0, 8052369b}



Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+3d )

Followup: MachineOwner
---------

1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000028, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 8052369b, address which referenced memory

Debugging Details:
------------------




READ_ADDRESS: 00000028

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReleasePageFileSpace+3d
8052369b 8b7828 mov edi,dword ptr [eax+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: mscorsvw.exe

LAST_CONTROL_TRANSFER: from 8051178a to 8052369b

STACK_TEXT:
b0e4ec00 8051178a 88c40308 0c080001 c08871a4 nt!MiReleasePageFileSpace+0x3d
b0e4ec2c 805af057 01492201 86e56020 007ffff8 nt!MiDeleteValidAddress+0x96
b0e4ec4c 8051330d 86e56020 86e56158 86e56020 nt!MiDeleteAddressesInWorkingSet+0x65
b0e4ec80 805d1391 00e56020 86e23ba0 86e23de8 nt!MmCleanProcessAddressSpace+0x193
b0e4ed08 805d1554 00000000 86e23ba0 00000000 nt!PspExitThread+0x621
b0e4ed28 805d172f 86e23ba0 00000000 b0e4ed64 nt!PspTerminateThreadByPointer+0x52
b0e4ed54 8054137c 00000000 00000000 0012fbf8 nt!NtTerminateProcess+0x105
b0e4ed54 7c90eb94 00000000 00000000 0012fbf8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fbf8 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiReleasePageFileSpace+3d
8052369b 8b7828 mov edi,dword ptr [eax+28h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiReleasePageFileSpace+3d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 469f3fa8

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+3d

BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+3d

Followup: MachineOwner
---------


--------------------------------------------------------------------------------------------------------


thanks for the help

Welcome to D-A-L.

Anticipating that the memory is correct/compatable for your motherboard,,,,,

Based upon your listed reports, you probably have a memory problem, or possibly an incorrect/corrupted driver.

As a first measure, ensure your memory modules are correctly/fully inserted into the memory bank slots. Then I recommend testing your memory. Here are a couple of testers which can be put on a bootable floppy or bootable CD;

Download and run MemTest86+.
http://www.memtest.org/

Use the appropriate downloaded file to create either a floppy bootdisk or a bootable CD. For a floppy, unzip the files to an empty directory and (with a floppy in your drive) run the install.bat file. When complete, you won't see any files on the floppy, but they are there. Just boot the machine with this floppy and run it as long as you can afford to.

If there are errors, run it on one memory module at a time to narrow down the possibilities. (ie; Remove all but one module.)

You may have to set your bios boot device sequence to boot from the floppy (or CDROM) drive first.


[MICROSOFT MEMORY TESTER]
http://oca.microsoft.com/en/windiag.asp

Also ensure you have installed the latest motherboard/chipset drivers for your machine.

i've already tested my system with memtest86 for 7 hours and it didn't show any problem...
i'll try the MICROSOFT MEMORY TESTER now...

by the way, i have ASUS M2N-E mb with bios revision 1001 (which automatically came with it and it's not the latest one)
should i upgrade my bios to the newest one? i'm afraid the blue screen will show up in the middle of the installation and the my computer will become unusable...

Bios Version 0304 contains a memory patch update;
http://support.asus.com/download/dow...Language=en-us

The other updates are for newer CPU's. If your current bios is below this version I think it would be a good idea to update the bios to this (or a higher version). Note some are BETA. This choice is yours.

I would make a bootable floppy or CD and run the Awdflash.exe program for updating from there, outside of the windows environment.

Did you run memtest86 ( http://www.memtest86.com/ ) or memtest86+?

I personally would run all three. I've seen the MS tester list errors that memtest86 didn't list on the same machine.

the microsoft memory tester just ran now without any problems...

any more ideas?

Just to add my perspective:

I'd also suggest the latest stable BIOS be installed.

Also do not overclock in case you are.

You also might want to verify your RAM is running at the prescribed voltage.

Several of your BSODs show 'virtual' memory faults.

This could be your hard drive and or your Page File.

If Check Disk has not been running after these crashes then force it to run:

CHKDSK
--------------------------------------------------
Try running Check Disk:

Go to start Run... and type: cmd

Then type: chkdsk /f

You will be told the volume is in use do you want to run chkdsk on next boot? Type: Y and reboot.

You can also run the manufacturers diagnostic on your hard drive.

If you have had these errors ever since the build there must be a hardware issue.

Are you sure the RAM is compatible?

Does your graphics card have the proper power connections?

Do you have an adequate PSU?

Also what is the operating system?

If Vista is all of your hardware 'Vista ready'?

Did you load all the latest motherboard drivers and the latest drivers for your graphics card etc.?

1) i'm not overclocking
2) how do i check the memory voltage? through BIOS? on what voltage should i put it? i think it's on 1.8V now
3) what's page file?
4) i've already run western digital diagnostic and no problems
5) yes the ram is compatible. these are my computer components:
Asus M2N-E
XFX 8600GTS XXX
SoundBlaster X-Fi Xtremegamer
Western Digital 1600AAJS
G. Skill memory sticks (http://www.newegg.com/Product/Produc...82E16820231098)
Heck 450TD-TF
6) i'll look at the power cable connected to the graphic card....although there's only one way to do it...
7)windows xp pro sp2
8)which drivers should i download for my motherboard? i'll try to install the latest chipset driver now


thanks alot again

All the drivers and BIOS are here:

http://support.asus.com/download/dow...us&model=M2N-E

Did you update the BIOS?

Did you run Check Disk?

This explains Page File:

http://www.aumha.org/win5/a/xpvm.php

Are you sure the WD part number is correct?
http://www.westerndigital.com/wdsear...S&sl=en-US&sc=

If you can get a stable windows "session", here's the WD hard disk analysis tools (Data Lifeguard);
http://support.wdc.com/download/downloadxml.asp

(If you'd rather avoid the windows environment for disk testing (advisable), DOS tools (floppy or CD) are available here as well.)