If someone could please read the dump file as I am having a hard time doing so. It started recently after a new mouse install but I have uninstalled that and it still is doing it. If you could read the dump and get back to me that would be greatly appreciated.

thanks,
Jay bob
jrimmel@wisc.edu

Attached Files

dumpfiles.zip (70.4 KB, 10 views)

Hi jaybob275,


The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
8. Upgrade BIOS and make sure that the motherboard has no leaking capacitor

If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.


Your debug report
Mini010106-01.dmp BugCheck 1000000A, {0, 1c, 1, 804e1bf8}
Owning Process 86344ae0 Image: lsass.exe
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+186 )

Hi Jay,

Do you have any update? Repost if you need further help.