some BSODs just for you

[The Apathetic]

Hello there,

Here are all the BSODs I've had since I installed this windows a few days ago..

Some of them say Memory-Corruption so that mean the ram is bad, but what about the other ones?

Btw, it's windows 7 Ultimate x86 build 7600..

 

[Jonathan_King]

I had trouble loading the files in my debugger, but if you have bad memory, it can manifest itself in other ways. If the debugger points to system files and the like, it could be caused by bad RAM.

Try downloading Memtest86 and burning the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

Also, open an elevated command prompt and run sfc /scannow.

 

[The Apathetic]

I already know that the ram I have is faulty, I posted here to determine if there are any other problems other than the ram..

And I ran the scannow twice over the past few days, it didn't find any corrupt files.

 

[zigzag3143]

Hello there,

Here are all the BSODs I've had since I installed this windows a few days ago..

Some of them say Memory-Corruption so that mean the ram is bad, but what about the other ones?

Btw, it's windows 7 Ultimate x86 build 7600..

All of these report memory and we cant diagnose other problems till that is fixed. when you tested the memory were all of them bad?

Ken

021610-18330-01.dmp    2/16/2010 4:12:54 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x887ac885    0x98553a14    0x00000000    fltmgr.sys    fltmgr.sys+a885    32-bit    
021610-14227-01.dmp    2/16/2010 4:15:46 PM    BAD_POOL_HEADER    0x00000019    0x00000020    0x9f595950    0x9f595958    0x0a016000    hal.dll    hal.dll+5ba9    32-bit    
021410-32885-01.dmp    2/14/2010 1:12:01 PM    MEMORY_MANAGEMENT    0x0000001a    0x00041790    0xc080208a    0x0000ffff    0x00000000    ntoskrnl.exe    ntoskrnl.exe+b9c1d    32-bit    
021410-13790-01.dmp    2/14/2010 9:11:06 PM    MEMORY_MANAGEMENT    0x0000001a    0x00005003    0xc0802000    0x000003de    0x73f18005    ntoskrnl.exe    ntoskrnl.exe+dce10    32-bit    
020910-24975-01.dmp    2/9/2010 4:10:58 AM    MEMORY_MANAGEMENT    0x0000001a    0x00041284    0x02754001    0x00000000    0xc0802000    ntoskrnl.exe    ntoskrnl.exe+dcd10    32-bit

 

[The Apathetic]

I had two memory chips, 1 was destroyed after powering the rig with a 600w OCZ PSU and the remaining 1 became faulty about 2 weeks ago.

I already purchased a new 2gig chip (haven't installed it yet), but I just wanted to make sure that there are no other problems other than my faulty ram, cause I just don't understand why it went faulty so fast, I got it only few months ago. The new chip I just bought drained every single penny I have, but at least this time it has a warranty, I'm just afraid that there might be something in my rig that is making the memory chips go faulty or something..

 

[Jonathan_King]

I had two memory chips, 1 was destroyed after powering the rig with a 600w OCZ PSU and the remaining 1 became faulty about 2 weeks ago.

I already purchased a new 2gig chip (haven't installed it yet), but I just wanted to make sure that there are no other problems other than my faulty ram, cause I just don't understand why it went faulty so fast, I got it only few months ago. The new chip I just bought drained every single penny I have, but at least this time it has a warranty, I'm just afraid that there might be something in my rig that is making the memory chips go faulty or something..

If there was, unfortunately, we could not tell from the dmps.

 

[The Apathetic]

Well, at least we tried, thank you all very much for your help .