BSODs, Occasional Freeses. Even after reinstall.

[HalfWin]

Hi, yes im new to the fourms and i would give a big introduction if i wasn't so low on time.

SPECS:

System Manufacturer/Model Number 		Cyberpower Custom 		 OS 		Windows 7 Home Premium 64 Bit 		 CPU 		AMD Phenom II X6 T55 		 Motherboard 		ASUS M4 		 Memory 		4GB DDR 3 - Corsair 1600mhz 		 Graphics Card(s) 		Geforce GT 220 		 Sound Card 		Some Random Cheap Thing. 		 Monitor(s) Displays 		2, 1920x1080 and 1024x768 		 Screen Resolution 		N/A 		 Hard Drives 		500GB Basic Brand 		 PSU 		580W also a random brand 		 Case 		--- 		 Cooling 		Just Fans. Supplied case fans

Ok guys this is going to be a long journey.
I had a virus about 2 or 3 weeks ago. Dunno where it came from, completly random as i did not download anything bad. Avg scanned it, reported nothing, so i deleted my account and it aparently fixed it. So everythings fine for a few more days, then i get random bsods. First a freese from playing portal 2 and after a reboot the keyboard wasn't happy with its current drivers and reinstalled them from windows. Then hell broke open and i was getting bsods everwhere. By the way it was a Cyborg Gaming Keyboard if that helps. So i reinstalled the drivers from the offical site wih a different keyboard and it fixed it for a day or 2. Now im still getting them, even after a Re-install which by the way, Windows PE itself bsods before installing. Then after a new desktop, everyting clean but still the bsods.

I am getting:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT

I have installed new memory and checked the old ones. They are both clean from faults. I have the dumps here. Which is all i can gather from a linux cd i used to get them. Which by the way dosn't get errors which means its windows based and to do with the hardware. One last thng is that i found some files missing from one of my games before i formatted so could it be bad sectors.


Phew, thanks VERY much for any help.

 

[FredeGail]

Hello HalfWin & Welcome to SevenForums!

:ar: BSOD Summary

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiStoreSetEvictPageFile+b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiStoreSetEvictPageFile+b

BUCKET_ID:  X64_0xA_nt!MiStoreSetEvictPageFile+b

Followup: MachineOwner

You experienced a memory corruption. Try removing one of the sticks and then see if a BSOD appears. If one appears suddenly, upload the latest .dmp. Put both of them back in and follow this guide (http://www.sevenforums.com/crash-lockup-debug-how/53854-check-your-ram.html) to test your sticks.

Best Regards,
FredeGail

 

[HalfWin]

May i ask, can the actual slots be broken, and if so can they be repaired. Becaouse im CERTAIN its not the memory.

 

[FredeGail]

May i ask, can the actual slots be broken, and if so can they be repaired. Becaouse im CERTAIN its not the memory.

The slots can be broken, yes. To test if your slots are broken, borrow some memory sticks that you're absolutely functional, and run Memtest86+ overnight or so.

Why are you so certain that it's not your sticks?

Best Regards,
FredeGail

 

[HalfWin]

thanks, well I had this error before with my old sticks and they were error free. These new ones havn't changed anything. But just incase its probably better to test them. When I put the new memory in there was quite a lot of dust. I cleaned out what I could but I might need to clean deeper.

EDIT: I used windows mem diagnostic to check the old pair.

 

[FredeGail]

thanks, well I had this error before with my old sticks and they were error free. These new ones havn't changed anything. But just incase its probably better to test them. When I put the new memory in there was quite a lot of dust. I cleaned out what I could but I might need to clean deeper.

EDIT: I used windows mem diagnostic to check the old pair.

I see. Post back your result.

The Windows Diagnose is certainly not recommended as it doesn't stress the RAM enough, and it doesn't test the slots either. MemTest86+ will cover all this.

Best Regards,
FredeGail

 

[HalfWin]

Well. I couldn't complete it beacouse it overheated. 47% finished. But there were over 600,000 Errors. So what would that mean?

EDIT: The ram was running at a lower speed than it was meant to as well. 1333 instead of 1600. Would this be a problem

 

[FredeGail]

Well. I couldn't complete it beacouse it overheated. 47% finished. But there were over 600,000 Errors. So what would that mean?

EDIT: The ram was running at a lower speed than it was meant to as well. 1333 instead of 1600. Would this be a problem

You had these errors with MemTest86+? Then there's surely something wrong with your sticks or slots. As mentioned, you can borrow some sticks that you know are functional, and then remake the test. If you get any errors by then, it might be your slots. Keep in mind to test in all slots.

I find it very unlikely in all those .dmp I analyse, that it's the slots that's broken. But it could be possible. If so, it's rocket science to change.

Best Regards,
FredeGail

 

[HalfWin]

Sorry to bump and old thread, but i figured its better than opening a new thread with simular issues. Ive had fewer crahses since and can last up to 3 days but when i do its a straight bsod with a memory management, Or a screen corruption followed by a bsod. The card i bought is a new ASUS EAH 5670 and new drivers wern't agreeing with it so i got really old ASUS website ones which are made in 2010 and are version 8.782. These now have become much fewer. So what i want to know is that can a MEMORY_MANAGEMENT encompass video memory and Page_Fault_In_Non-Paged_Area mean that the memorys at fault. It may be the card which i can send back or it could be another slot going again in which case i could easily go buy another motherboard with better support for newer memory. I would attach dumps but the system is hiding them from me.