BSOD crash help Please

[Irish88]

hello,

My first home-build has been crashing at what seems like random times. The blue screen of death pops up saying memory dump then the computer restarts before I can see much more of the screen. (stays up for a couple seconds)

I am using (if the components matter to you)
AMD Phenom II x4 955 BE
Gigabyte GA-MA785GMT-UD2H with onboard graphics (

ATI Radeon HD 4200)​

4 GB OCZ RAM

Thanks for any help/suggestions

(The minidump file is attached)
Thanks again

 

[ttran]

Hi and Welcome to SF

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL http://www.carrona.org/bsodindx.html#top

Usual causes: Device driver

Different stop codes, different things were blamed, this can be hardware issue...we don't know for sure yet
One stop code is 24, which is usually related to hard drive, also ntfs.sys is the hard drive controller driver, therefore I would suggest you to run these:
http://www.sevenforums.com/tutorials/433-disk-check.html
HD Diagnostic

Run system files check: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Scan whole computer for malware: Malwarebytes

As you can see the stop code I listed above, memory corruption is one of the potential cause. Memory corruption is also mentioned in those dmp.
Please download third party called memtest86, burn it to CD using ISO Recorder v3 , and let it run for at least 7 passes

Let us know if you need help

Tuan

 

[Irish88]

Well first, Thanks Tuan for getting me a quick reply with some stuff to try.

I ran the disk check and Malware scan with no problems.

The File check did returned following:
"Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log windir\Logs\CBS\CBS.log
For example C:Windows\system32>"

I found the folder and opened one file but I don't really know what to do with it or what to look for. I can attach it on here but I'm running the memtest86 right now. I tried to open the other file but it would not let me (said I didn't have permission, I think).

I started the memtest86 and got TONS of errors right from the start and then I saw that some people said to run the test with just one stick at a time, so I tried that. The first stick did the same thing so I stopped it and am trying the other one which is good so far (only 20 minutes into the test though. How long do you usually let it run? However long it takes for the "7 passes" you mentioned? Do you have a rough idea of how long that takes?)

So it appears that at least one of my sticks of RAM is bad -> next step to fill out a RMA request to OCZ I guess...

any other thought/suggestons?

Thanks again and Happy 4th of July!
God Bless 'MERICA

 

[ttran]

Hi buddy
I think the time to run 7 passes is depended on different machines. For me, I take quite long coz my machine is suck...
yes, try to test individual ram stick to find a good one, then test it on different slots...it is possible that your motherboard slots are bad (possible).
If you are overclocking anything, set it to normal.....................
It appear that your system file are corrupt, you might need to do system repair...we will get to that later when u done Ram check

Happy 4th of July!!!!!!!!!!!!!!!!!!

 

[Irish88]

All the slots appear to be working okay. (I don't do any overclocking.) I let memtest86 run long enough to pass at least 1 test with the good RAM in each slot, so it looks like it was just the stick of RAM. I'm guessing that would long enough to just test the RAM slot

On to system repair then?

 

[CarlTR6]

You need to make several passes with the RAM in each slot. Five should do since you are using a known good RAM stick.

I also find a couple of older drivers on your system:

gdrv.sys Thu Mar 12 23:22:29 2009 (49B9D175) - which appears to be a driver for Gigabyte's Dynamic Energy Saver Advanced program or a Gigabyte EasyTune6 driver GIGABYTE - Support&Download - Motherboard - Utility

netr28ux.sys Tue Apr 28 06:23:32 2009 (49F6D924) - Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer)Ralink corp.

While certainly bad RAM will cause BSOD's, obsolete drivers can also. I suggest that after you get your RAM problem solved, you update these two drivers from the manufacturers' sites. Download the updated drivers and install them.

I found that gdrv.sys has caused problems on other systems. It is a Gigabyte utility driver. You may opt to uninstall the utility.

In one of the dumps, I saw a hint that possibly your network adapter was involved. This might be due to he obsolete netr28ux.sys. Update this driver or get a new wireless adapter.

 

[Irish88]

okay, I will run the memtest for a while more. What about the system repair?

Thanks

 

[CarlTR6]

At this point, I would not do a system repair. You need to thoroughly check your RAM. System repair does not fix RAM. Follow what I suggested in the post above and update your drivers. Then you can do a system repair if needed.