BSOD for 2 Months

[emohamad]

Hi,

I'm fighting a BSOD for about 50 days now, It's happening randomly in different situations for a minimum of two times daily.

I'm suspecting that my memory is the problem (2x2GB Chaintech APOGEE) as it appears in a weird way in Gigabyte easytune (some times appear as one memory module, other times with different frequency and properties for each module).

I ran Memtest86 with one module at a time and there were no errors.

I also ran the Windows 7 Memory test on both modules with no errors.

CPU: Intel i7-930

Mainboard: Gigabyte X58A-UD3R

Display: Geforce GTS 250 1GB

HDD: Seagate 1TB SATA

Windows Version: Windows 7 Ultimate 64

Windows Type: Full Retail

Hardware Age: 2 Months

Windows Age: Around 50 Days (Repaired Two Days ago)

Running Kaspersky Internet Security 2011 11.0.0.232

I appreciate any help, This BSOD causes a serious pain & I lost work many times because of it.

Thanks in advance.

 

[madtownidiot]

One error is caused by Kaspersky.. will check further.. and others will be here to take a look. I would recommend removing it and replacing with MSE or another antivirus
View attachment 113115

 

[usasma]

Your system only has 15 hotfixes installed, there are at least (at a minimum) 55 available for Win7. Please visit Windows Update and download all the updates for your system.

Please update your Western Digital External drive program/drivers as the Western Digital SCSI Arcitecture Model (SAM) WDM driver is from 2008. (wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C))

Please remove your Gigabyte EasyTune6 driver as it has known issues w/Win7 (GVTDrv64.sys Tue Sep 05 03:10:02 2006 (44FD22CA))

If that doesn't fix things, please post back and we'll try some other stuff.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 11 08:11:13.351 2010 (UTC - 5:00)
System Uptime: 0 days 2:55:33.349
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`0365df10 fefffa80`0365df10 fffffa80`0365df10
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 10 23:18:20.024 2010 (UTC - 5:00)
System Uptime: 0 days 4:34:18.133
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`031fc90d fffff880`08f96e48 fffff880`08f966a0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 10 18:42:55.904 2010 (UTC - 5:00)
System Uptime: 1 days 2:34:02.012
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+80 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchProtocol
Bugcheck code 0000003B
Arguments 00000000`c0000096 fffff800`03086266 fffff880`0a4aa5f0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[emohamad]

Thanks for all the feedback.

@madtownidiot
I removed kaspersky internet security & installed MSE.

I'm totally surprised, Now I'm enjoying my first day without a single BSOD.
I didn't use my PC for heavy work the last 24Hrs. but, I always had BSODs even when I left it idle.

@usasma
I had all windows 7 updates before repairing windows & had BSODs all the time, I'll update again.
I'll update WD Drivers & remove EasyTune.

I'll be posting again tomorrow.

Many thanks for the advice, I really appreciate your help.

 

[emohamad]

Hi,

I updated my WD Driver,removed easytune6 last night & things were alright.
But, while updating windows today I had 2 BSODs (One of them didn't save a dmp file successfully)

After installing around 60 important updates, I had another couple of BSODs while working (3ds max 9 32bit).

Please, review the attachment & give me your ideas.
the performance report still complains about something related to kaspersky internet security even after uninstalling it!!!!!

I hope this nightmare will end soon. Thanks for your time.

 

[usasma]

Sometimes fixing one problem reveals another problem, etc, etc, etc. So we just keep working until we solve it.

The perfmon report is complaining that a Kaspersky component isn't there (since you uninstalled it that's a logical response).
But, since you uninstalled Kaspersky, perfmon shouldn't be complaining about a missing component (since there's nothing there for the missing component to work with).
Use this free tool to remove any remnants of Kaspersky that the uninstaller didn't get: Removal tool for Kaspersky Lab products

Western Digital driver is still outdated: wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
Don't worry about it for now, but we'll keep an eye on it.

9 memory dumps from 11 to 13 November 2010 (3 days)
6 different BSOD error codes
5 different causes blamed
This is most likely a hardware problem - but can still be a number of different issues.

Let's use Driver Verifier to try and force the issue. Please use these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Then, while waiting for us to post back, try these free hardware diagnostics:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov 13 16:22:22.347 2010 (UTC - 5:00)
System Uptime: 0 days 2:25:37.455
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+463ba )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  wlsetup-web.ex
Bugcheck code 00000018
Arguments fffffa80`03725200 fffffa80`0426aaf0 00000000`00000001 02000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 13 01:25:53.489 2010 (UTC - 5:00)
System Uptime: 0 days 0:16:02.597
Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
Bugcheck code 00000050
Arguments fffffb80`058ba920 00000000`00000000 fffff800`031c778c 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Nov 13 01:08:04.632 2010 (UTC - 5:00)
System Uptime: 0 days 3:10:03.740
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`0337a67c fffff880`08061ec0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 11 13:57:24.644 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:22.753
Probably caused by : tcpip.sys ( tcpip!TcpRestructureHashTable+24 )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 11 13:53:34.280 2010 (UTC - 5:00)
System Uptime: 0 days 1:41:37.388
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+433 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`030cf933 00000000`00000000 ffffffff`ffffffff
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 11 12:06:03.371 2010 (UTC - 5:00)
System Uptime: 0 days 3:48:30.368
Probably caused by : ntkrnlmp.exe ( nt!KiSignalThread+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`03086d8f fffff880`08a070f0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Nov 11 08:11:13.351 2010 (UTC - 5:00)
System Uptime: 0 days 2:55:33.349
Probably caused by : Pool_Corruption ( nt!ExFreePool+536 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffffa80`0365df10 fefffa80`0365df10 fffffa80`0365df10
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 10 23:18:20.024 2010 (UTC - 5:00)
System Uptime: 0 days 4:34:18.133
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetInfo+11f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`031fc90d fffff880`08f96e48 fffff880`08f966a0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Nov 10 18:42:55.904 2010 (UTC - 5:00)
System Uptime: 1 days 2:34:02.012
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXRstor+80 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchProtocol
Bugcheck code 0000003B
Arguments 00000000`c0000096 fffff800`03086266 fffff880`0a4aa5f0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[emohamad]

I ran Memtest86+ for 6 passes with no errors.

I ran Prime95 (Small FFTs), The first error was after 1Hr 19Mins (NO OVERCLOCKING INVOLVED)
I don't know much about this tool, can anyone help me explain these results.

I'm wondering if there's a more self explanatory tool for testing CPU & MoBo.

Thanks.

 

[usasma]

Please run Prime95 with the Blend test and the Large FFT's test and let us know the approximate time to failure (if it fails). Small FFT testing focuses more on the CPU, but it's not only the CPU.

This will help us to decide what direction to take the testing in.

There are no reliable, complete motherboard testing utilities. We use PCCheck at work ($300 US) and it's not always correct, nor does it test all components. I've recommended SiSoft Sandra Lite as a freeware mobo tester - but take a look at it to see if it'll meet your needs: SiSoftware Zone (list of available modules here: BenchmarkHQ )

Some CPU tests that I've seen (but haven't used):
CPU Stress test - Overclock.net - Overclocking.net
Fossil Free Online CPU Load or Stress Test.

A nice discussion of the details about Prime95: Torture test your CPU with Prime95

 

[emohamad]

Thanks for the feedback

I did the blend test, Here's the result (a failure after only 6 Mins of work)

Large FFTs (a failure after 22 Mins of work)

Another Blend test (a failure after 2 Mins of work)

You'll find an error summary attached, Can these results give us any clue???!!

Thanks again for your time.

 

[usasma]

Looks like memory/mobo channels to me (but memory can be CPU/RAM/Video/maybe even mobo).
I'll have to read a bit more about Prime95 - but in short we're talking one of 4 things:
- CPU
- mobo
- RAM (not likely as it passed MemTest)
- Video

I'll post back as soon as I figure out a bit more.

Meanwhile, try the first 2 links from this Google search for CPU tests: http://www.google.com/search?q=cpu+...s=org.mozilla:en-US:official&client=firefox-a

And try these 2 video stress tests:

FurMark download site: http://www.ozone3d.net/benchmarks/fur/
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - http://nvworld.ru/utilities/vmt/
Artifact Locator - http://nvworld.ru/utilities/alocator/
Sorry, but I don't read the language that this website is made in.

 

[usasma]

Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64)
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

You have fast crashes in Blend - and not so fast in In-place large FFT's. The difference here is the amount of memory tested. I'd suggest running MemTest overnight just to be sure.
If it's not RAM, then the other forms of memory will be tested by the stress tests that I mentioned above.

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64)
- CPU

So, it's most likely that you have some sort of memory issue, with the CPU/Memory interface (mobo) being next most likely, and the CPU being the least likely.

Run the stress tests and let's see what you've got.

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.

 

[emohamad]

Tried Hot CPU Tester Pro 4.41
The first trial, I had dozens of errors and the program crash after around 5hrs (No Log Saved)
The second trial, a BSOD after around 5hrs (Log & Mini-dumps are attached).

Also tried
Intel® Processor Diagnostic Tool(32bit) & It didn't return any errors.

I'll try BurnIn64 (another stress test) & post again.

I'm going to concentrate on testing only the CPU & If it's OK then the problem may be in my RAM (Am I getting it right here??)

Thanks

 

[usasma]

In another thread today the person had run 17 passes of MemTest without any problems. And they found that the system would have problems with one of the RAM sticks in Prime95 ( http://www.sevenforums.com/crashes-debugging/124155-blue-screens-again-2.html#post1076674 ). So, I'd suggest the following tests:

Here's a DRAFT Prime95 testing sequence that I'm working on (I've included your links to CPU tests).

DRAFT Prime95 testing procedure
This is in case you are getting errors in Prime95 and want to nail down the cause

Run HDD diag and MemTest prior to Prime95

Run Blend test
Run Inplace Large FFT's test
Run Small FFT's test

Run CPU Stress Tests
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld - PCWorld
- CPU Stress test - Overclock.net - Overclocking.net

Run Video Stress Tests
- FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
- МИРNVIDIA / Утилиты / VMT
- МИРNVIDIA / Утилиты / Artifact Locator

Swap RAM sticks around per Steps 7 through 10 of this link and run Prime95 (in Blend mode) on each stick/slot: Memory Diagnostics
This is because of issues found in this topic: http://www.sevenforums.com/crashes-debugging/124155-blue-screens-again-2.html#post1076674
************************
DISCUSSION:
Small FFT's test CPU cache and very little memory.
Large FFT's access' a lot of memory - but in-place option keeps it limited
Blend is not run in-place, so it cycles the tests through a lot of RAM

All tests stress the CPU
In-place large FFT's and Blend also test CPU/RAM interface (mobo in all but Athlon64)
In-place large FFT's stress CPU more than Blend
MemTest is better at testing RAM

Prime 95 tests 3 things:
- Memory
- CPU/RAM interface (mobo in all but Athlon64)
- CPU

FWIW - the distinction between RAM and different types of memory in the system is one that I've made. The documentation that I've read speaks of RAM issues and CPU cache - and doesn't mention the other aspects. BUT, this is just speculation on my part, so we'll have to see how it works for us.

FWIW - I can't make anything of the log file - and the crashes seem to be user level memory dumps of the crash of the system while using Hot CPU Tester (and it's what's cited as the cause of the crash).

Because of the other topic I mentioned, I'd have to wonder if there's an issue with the RAM that MemTest didn't catch. I'd suggest testing the RAM by running Prime 95 (in Blend mode) on each stick individually in each slot.

 

[emohamad]

Hi,

Earlier today I replaced my 2x2GB Chaintech APOGEE RAM,
with 2 x Kingston KVR1333D3N9/2G

I'm running the first Prime95 test (Blend Test) with 15mins duration up till now, I'll post the results at morning.

I hope my problem is now solved.

 

[emohamad]

Prime95 blend test has been running for the past 7Hrs with no errors.

I'll try Hot CPU Tester & post again.

 

[usasma]

Update to the "DRAFT"(thanks to Reventon), the Intel Core i-series of processors seem to have the memory controller onboard (similar to the Athlon64)