This is causing 90% of my Win7 64bit BSOD's...

[UNDCTIATC]

WTF is this?

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff9e0084e02c0, 0x0000000000000000, 0xfffff88003c7b293, 0x0000000000000005

any suggestions thnx a bunch!

 

[HalfAHertz]

you should upload the whole minidump file

 

[oily_17]

0x00000050 is a PAGE_FAULT_IN_NONPAGED_AREA stop code.You can read more on stop codes here -

http://aumha.org/a/stop.htm

First off I would run Memtest on your memory to check for errors -

http://www.memtest.org/

 

[sttubs]

0x00000050 is a PAGE_FAULT_IN_NONPAGED_AREA stop code.You can read more on stop codes here -

http://aumha.org/a/stop.htm

First off I would run Memtest on your memory to check for errors -

http://www.memtest.org/

Test one stick at a time.

 

[Kreij]

If the sticks all test okay, test each slot individually (if you can). It could be a bad slot.

 

[UNDCTIATC]

- System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2010-04-18T13:44:16.000000000Z

EventRecordID 75672

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer FATTYMCGHEE-PC

Security


- EventData

param1 0x000000d1 (0xfffff8800bf8ded8, 0x0000000000000002, 0x0000000000000000, 0xfffff880018656b5)
param2 C:\Windows\MEMORY.DMP
param3 041810-13384-01

 

[UNDCTIATC]

it won't let me add the memory.dmp file because its 312mb. is there another way to do it? even zipped its 55mb.

Reading other things ive heard this: To bump up the voltage in MCP,FSB and Ram. I have an ASUS P7P55D-E Pro. If anyone knows the proper way to bump up that voltage without frying everything plz let me know.

 

[Kreij]

Go into System Properties->Advanced and set the "Write debugging information" to small memory dump.

 

[sneekypeet]

I had issues with my ripjaws on a similar Asus. Make sure the voltage is set to 1.65V for the ram, then you will need quite a bit of QPI/VTT (IMC Voltage) to get those sticks running right. 1.35-1.4V is my guestimate. No need to push the "NB" as that and the PLL do little to make the ram stable.

 

[UNDCTIATC]

I had issues with my ripjaws on a similar Asus. Make sure the voltage is set to 1.65V for the ram, then you will need quite a bit of QPI/VTT (IMC Voltage) to get those sticks running right. 1.35-1.4V is my guestimate. No need to push the "NB" as that and the PLL do little to make the ram stable.

Ok thnx. I just ran Memtest86x and it ran 10x all pass 100%. I bumped up all voltages across the board but i will bump up the ram to 1.65 and IMC to 1.35 or higher. The CPU and others are already high because i have this puppy oc'd to 4.3. I have gotten it to 4.9 but i backed it down Lol

 

[UNDCTIATC]

I had issues with my ripjaws on a similar Asus. Make sure the voltage is set to 1.65V for the ram, then you will need quite a bit of QPI/VTT (IMC Voltage) to get those sticks running right. 1.35-1.4V is my guestimate. No need to push the "NB" as that and the PLL do little to make the ram stable.

Since I hate reformatting with a passion, i tweaked the voltages. Computer has been stable for over 24 hours which was unheard of for the past week. Below are the listed voltages for the ASUS P7P55D-e Pro:

Ram(1.65v): G.Skill Ripjaw 1568mhz 9-9-9-24-4-74-10-5-20 2N
CPU(1.325v): i5 (3.3Ghz) Running 4.32 Ghz at 30-50c
IMC: 1.35v
Dram: 1.65v
CPU PLL: 1.8125v
PCH: 1.0625v

The last two the pll and pch i bumped up one notch and the ram from 1.6 to 1.65. Any higher and the risk of dmg to the cpu is high. So far these settings have produced a stable system and the memory writing is no longer an issue. Thanks for all the help and suggestions: PROBLEM SOLVED