Another BSOD interesting situation. Community help needed!

[Dolke]

Hi there.

BSODs is happening randomly on an older PC running Windows 7 ultimate x86 (32-bit). OS installation is 2 months old. It is full retail version.
Sometimes system remains stable for like 3 days and then, for no particular reason, it crashes few times a day. Help needed! TY in advance.

PC config:

Motherboard: Gigabyte 8L848P-G
CPU: Prescott, Pentium 4 HT, 3GHZ, 1mb L2 cashe
RAM: 2x512MB, both DDR1-400, PC3200, Kingmax and Kingston
GPU: GeForce MX440, nVidia NV17, 64mb
HDD: SATA Seagate, 160 gb and SATA2 Samsung 7200, 1tb

Zips:

 

[raceb4us]

Hi Dolke, I looked at a few of your DMP files and noticed this a few times.

BugCheck 1000008E, {c000001d, 91d3280f, 80d9995c, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
You may have a DRAM module with an issue. Please try runnng memtest86 on your system. Can be found here.

 

[Dolke]

Already done that m8.

Several passes with no errors. Also tested separate and together.
Also, I changed my AV software. Removed Avast free av, and installed Avira free AV. That helped a little, as BSODs are not that often as before.

Ty for the suggestion though.

 

[raceb4us]

Your welcome. Would it be possible to run your DRAM modules at 333MHz and see if it doesn't help with your issue?

 

[Dolke]

You mean to manually adjust DRAM frequency in the BIOS?
I'll give it a shoot. Just to say that this same config runs windows XP without this issue, as I have dual boot.

 

[raceb4us]

The vast majority of your systems BSODs point to memory corruption. Windows 7 is less of a burden on hardware than Vista is but it does tax your system more than Windows XP.
Do you know if the chipset on your board is Intel or Nvidia, if so which model?

 

[Dolke]

@raceb4us

I found specifications of the mobo on the Gigabyte site. LINK

According to that specification page, mobo it is based on the Intel chipset.
North Bridge : Intel® 848P MCH
South Bridge : Intel® ICH5

P.S. I'll try to manually slow down the speed of the DRAM in BIOS later on today as Im not in the office right now.

 

[Dolke]

@raceb4us

I investigated through my BIOS searching the way to slow down memory frequency and this is what I found:

1st, I already have latest stable BIOS version for the mobo (F5 v.).
There are 2 options in advance frequency/voltage tab:

1. Memory Frequency by DRAM SPD data > I can make changes
2. Memory Frequency (Mhz) > I cannot change this setting and currently it shows 400 Mhz.

This first option that I can change I can set to one of the following values: 1.33 , 1.66 , 2.0 , AUTO.
Right now it is set to AUTO.

Also there is warning msg next to this option: "Wrong freq. may make system cant boot. Clear CMOS to overcome wrong freq. issue."

Hope this helps you to help me
Regards.

 

[raceb4us]

Hi Dolke, I hope you had an enjoyable weekend.

You mentioned earlier that you had run Memtest on single modules, but have you tried running Windows with only one memory module? If it crashes with one module, than try the other one.

Some of your drivers are from 2005/2006, but considering the age of your components it is expected. I don't think you can much about that.

 

[Dolke]

Hi raceb4us, it really was. Hope u had the same.

I didn't run windows with only one module. Will 7 work with only 512mb of ram?
I'll give it a shoot, but even if it works that way I don't think it will be usable...

U said that mostly all issues pinpoint to memory corruption. Is it possible that modules are to hot at some point? Can overheating be the problem, and if can is there some tool to view memory temperature?

ty

 

[raceb4us]

Here is a fun thread for running Windows 7 on an older computer.

It should work with 512MB of RAM. Normally I wouldn't recommend running an un-matched pair of modules though I guess people do it all the time. In your case it worked fine with Xp and the memory controller should set the memory timing to the slowest module. If both modules work when running separately it may be an issue of running them together.

I wouldn't think temperature would be an issue if it runs XP and passed Memtest.

 

[Dolke]

Ty for another good suggestion friend.

Although, I think it would take me lots of time to preform this test, as I need to run the PC with single module for at least 5 days. I'll think about it, but I'll also think about buying another Kingmax or Kingston module on online auctions. I'll look for completely the same module. They are used but good and tested, and cost just as 10$ so its not such an investment.

Ty for the link also. Its quite funny.
Well when we want to put makeup on old dinosaurs, sometimes they refuse

EDIT: Found one Kingston PC3200-DDR400, 512 mb around 9 bucks so I'll go for it...

EDIT2: Today i had 4-5 BSODs I bought that module but until it arrives (3-4 days) I need to work somehow. I run now with only one module. Really hope that unmatched pairs are the cause for crashing. Thumbs up!

 

[raceb4us]

Please let me know how it works out with one module.

 

[Dolke]

Update:

3rd day as PC runs with only one DRAM module. No crashes so far so I guess that unmatched pair of memory sticks really is the main cause for the crashes. I'll get back to you once again when the memory that I bought arrives.

Regards

 

[zigzag3143]

Yep RAM is very finicky when it comes to mismatching. even the same model, and speed purchased at different times can be flaky. After all it does have to do billions of transfers per second

 

[raceb4us]

Dolke, it is great knowing your system has been more stable.

 

[Dolke]

Yes... entered 4th day with no crashes. It must be unmatched pair issue.
Ty mate for all the suggestions. Memory is ordered, it will probably arrive in Tuesday.

until then...

EDIT:
Memory has arrived. So far so good. 2 matched Kingston modules tested OK.
Ill keep you posted.

 

[Dolke]

Yep it seems that problem is fixed!
ty raceb4us for helping troubleshoot the issue.

I think mods can lablel this thread as SOLVED as I dont experience BSODs anymore.
All the best
Dolke