[Burjo]

Hi,
I brought my new Desktop PC only 2 Weeks ago and i am ready to throw it through the shop window.

Everyday i my system crashes for no reason.
a blue screen comes up and it happens so quickly i can't get any of the info.
when it comes up it says deleating memory cache or something.

It has even happened when the system is ideling with no applications open.

my PC info is:

Windows Vista Home Premium
Intel(R) Core(TM)2 Quad CPU Q6600 A 2.40GHz
3.24GB RAM (there is actually 4 GB)
NVIDIA GeForce 8500 GT

I hope you can Help.

Thanks Burjo.

[sporg]

Hi there,

If it is a new pc and under garante I would recoment taking it back.

Regards

Gary Sparg
www.tekrevolution.com

[Rich-M]

Did you build this unit or have it built for you? Did you add ram to it?
Have you checked for heat issues? You can download and install speedfan to check those as well as fan speeds:
http://www.almico.com/sfdownload.php

[Burjo]

The PC was a package deal, but i added an extra 2 GB Ram.
I am unsure how to check for heat issues, but i will check in after i have looked at Speedfan.

[Rich-M]

Originally Posted by Burjo

The PC was a package deal, but i added an extra 2 GB Ram.
I am unsure how to check for heat issues, but i will check in after i have looked at Speedfan.

Speedfan will check temps and fan speeds for you. Added ram? Unless you used a configurator at a ram maker site, the ram is incompatible, and that is one of the most common mistakes made. I have seen even the same maker same model but different batch not working but you just cannot buy any old speed and "toss" it in.
I only buy ram approved for my boards at the following sites:
www.crucial.com
www.corsair.com
www.kingston.com

[Burjo]

Rich-M
I downloaded speedfan and my temps are running around 33 to 37 for all Cores.
I know the Ram I installed is Kingston DDR2 but thats it.
How can i see what motherboard and type of ram my PC has so i can check if i have purchased the correct ram.
BurJo

[Rich-M]

Download and run this:
http://www.gtopala.com/siw-download.html

[Rollin' Rog]

You can get the typical BSOD stop message by running sysdm.cpl and in Advanced > Startup and Recovery, UNcheck automatically restart.

"Small minidump" should also be selected under "write debugging information".

I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to %systemroot%\minidump and copy the last few minidump files to that folder.%systemroot% is normally c:\windows. They are numbered by date. You can paste that address in address bar to get there.
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder.
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

This might point us to a non-system driver causing the error, if one exists for it.

>>> Vista has it's own memory tester which you should run: mdsched.exe.

Read the additional info and run the extended tests.

Further information might be gleaned by a visit to the Control Panel > Performance Information and Tools > Advanced.

Here there is a "reliabiity monitor" and a health diagnostic. The reiliability monitor can be useful in associating problems with installs or system changes.

[Burjo]

Rich-M thanks, that program shows i have the following Hardware.
RAM Slot 1 and 3 come with the PC and i added Slot 2 and 4

Motherboard.....
Manufacturer Intel Corporation
Model DG33TL
Version AAD89517-803

RAM.....

Device Locator Slot 1
Capacity 1024 MBytes
Memory Type DDR2 SDRAM
Speed DDR2-666 (333 MHz)
Data Width 64 bits
Voltage SSTL 1.8V
Error Correction None
Refresh Reduced (.5x)...7.8 µs
Module Height 30.0 mm
EPP SPD Support No


Device Locator Slot 2
Manufacturer Kingston
Part Number 9905316-005.A04LF
Serial Number C532BEF0
Capacity 1024 MBytes
Memory Type DDR2 SDRAM
Speed DDR2-666 (333 MHz)
Data Width 64 bits
Voltage SSTL 1.8V
Error Correction None
Refresh Reduced (.5x)...7.8 µs
Manufacturing Date 2007, Week 19
Module Height 30.0 mm
EPP SPD Support No


Device Locator Slot 3
Capacity 1024 MBytes
Memory Type DDR2 SDRAM
Speed DDR2-666 (333 MHz)
Data Width 64 bits
Voltage SSTL 1.8V
Error Correction None
Refresh Reduced (.5x)...7.8 µs
Module Height 30.0 mm
EPP SPD Support No


Device Locator Slot 4
Manufacturer Kingston
Part Number 9905316-005.A04LF
Serial Number C632B6F0
Capacity 1024 MBytes
Memory Type DDR2 SDRAM
Speed DDR2-666 (333 MHz)
Data Width 64 bits
Voltage SSTL 1.8V
Error Correction None
Refresh Reduced (.5x)...7.8 µs
Manufacturing Date 2007, Week 19
Module Height 30.0 mm
EPP SPD Support No

Thanks.

[Burjo]

Rollin' Rog.
I have unchecked the auto restart and changed the write debugging info to small minidump.
i have attached the last 6 dumps for you to look at. 2 are from before i made the write debugging change and 4 are from after i made the change.

Also run a windows mem test and it told me i had an error and should see my computer manuf.

also looked at the reliability monitor.
from the 18/1/08 untill the 31/1/08

i have had windows failures everyday but 1.
i have had app failuers everyday but 4.
i have had hardware failure only once.


ALSO
this is the second time i'm typing the above in as i had another 2 BSOD's.
I was able to read it this time and get the info. ***The first one Reads***
**********************************************
A problem has been detected by you computer Blah. Blah. Blah.

fltmgr.sys

An attempt was made to write to read-only memory.

If this is the first time your'vfe seen this stop error message Blah. Blah. restart your PC.
If this screen appears again follow these steps:

make sure your hardware and software is prperly installed.

If problem continues, disable remove new hardware and software. disable BIOS memory options such as Caching or Shadowing.

Blah. Blah. Instructions on how to F8 Safe Boot

Technical Infomation.

*** STOP: 0x000000BE (0x91DEF6AC, 0xA3D08101, 0x9E9F7A9C, 0x0000000B)

*** fltmgr.sys - ADDRESS 8077ACD2 BASE AT 8075F000, DATASTAMP 4549acc2

Collecting data for crash dump...
Initializing disk for crash dump...
Physical memory dump complete...

*******************************************************

the second BSOD happened right after i reboot my system from the first BSOD.

it reads...***********
*******************************************************

A problem has been detected by you computer Blah. Blah. Blah.

If this is the first time your'vfe seen this stop error message Blah. Blah. restart your PC.
If this screen appears again follow these steps:

Disable or uninstall any anti-virus, disk defrag. or backup utilities. check your hard drive config. and check for hard drive corruption and resart your computer.

Technical Infomation

*** STOP: 0x00000024 (01001904AB, 0x8378BBac, 0x8378B8A8, 0x8295F2CD)

*** ftfs.sys - ADDRESS 8295F1CD BASE AT 828BF000 DATESTAMP 47214597

Collecting data for crash dump...
Initializing disk for crash dump...
Physical memory dump complete...
****************************************************

Thanks BurJo

[Gulo Luseus]

If you have an error in memory, as shown by win mem checker, it seems likely that you have the problem. Have you tried removing the new mem and running without it? and if that works, try removing the original mem and running with just that. Ifneither makes a diff, try using just one stick at a time, do a mem check, and see if one is faulty. From the sound of it, theres the problem

[Rich-M]

It's all to obvious the ram is not compatible and you can only use one or the other. if I were you I would buy more of the exact same Kingston after testing it runs OK on only that and ditch the generic it came loaded with as you won't know what it really is or be able to match it and it may not have been totally compatible to begin with.

[Rollin' Rog]

I would have to agree that the most likely cause of the problem is the additional ram, as many of the STOPs show "memory corruption" as the cause -- or other faults which are associated with memory corruption.

One outside possibility is that a corrupt Trend Micro install could be corrupting memory -- as a few stops are in file system drivers or filters that a scanner might be mucking up. And Trend is the faulting module in one of the STOPs

[Burjo]

I have run the mem scan on all my Ram.
It turns out that one of the generic sticks are faulty, so it is removed.

Hopefully i shuldn't have any mem probs anymore.

[Rollin' Rog]

Great, when you are indeed convinced that all is well, feel free to mark the thread "Solved" using the Thread Tools menu here.