I like eveyone else in here have been experiencing the BSOD.The last one was today.
0X0000007E (0X0000005, 0XB5BE0202, 0XBA3DBBA8, 0XBA3DB8A4)
KMIXER.SYS ADDRESS B5BE0202 BASE AT B5BD1000.

I have been reading that a lot of BSOD can come from faulty memory, so I ran memtest for 9hours straight and it came up no errors.
I have attached 5 minidumps.

My pc is overclocked but not by much and it only really seems to reboot if I well
umm umm umm lets say I help people leave the yahoo chat rooms sometimes. boot boot boot.

Asus probe tells me that my +12v are between 12.5v - 12.8v mbm5 tells me i'm at 11.92v - 12.20v everest says i'm at 12.74v.It is a generic 450w I got in my case.(No money for a new psu).

P.S when I run everest it doesn't show anything in my AGP slot but my msi 6600gt is in there.Lol I can see it.

Hi,

Your windows install an unstable version of ZoneAlarm. De-install or Upgrade ZA. If it still crashes, 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. Run chkdsk /r at command prompt
9. Run 3D Mark to stress test your video ram

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
Mini111405-01.dmp BugCheck 1000007E, {c0000005, b540a1a9, b97d0bb4, b97d08b0}
Probably caused by : kmixer.sys ( kmixer!MmxSrc_Filtered+109 )

Mini111505-01.dmp BugCheck 1000007E, {c0000005, b5dea202, b9affba8, b9aff8a4}
Mini111505-01.dmp DEFAULT_BUCKET_ID: DRIVER_FAULT
Probably caused by : kmixer.sys ( kmixer!MmxSrc_Filtered+162 )

Mini112505-01.dmp BugCheck 100000D1, {0, 9, 0, 0}
Probably caused by : nv4_mini.sys ( nv4_mini+4ba89 )

Mini112605-01.dmp BugCheck 1000000A, {760c7f3b, 2, 0, 804eb3eb}
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+184 )

Mini112805-01.dmp BugCheck 1000007E, {c0000005, b5be0202, ba3dbba8, ba3db8a4}
Probably caused by : kmixer.sys ( kmixer!MmxSrc_Filtered+162 )

Thank you cpc.
my cpu fan is ok
idle temps 29-30c under load 40-42c
my pc is dust free
like I said my psu is generic 450w
I have run 3d mark and all is good
I ran sisoft sandra and did a stress test for cpu and mem it passed.
I think the memory crash was when i was messing around with the ram timings.
I uninstalled zone alarm and the only BSOD i'm getting is the kmixer.sys again.
I can play games all day and its fine.
Just this kmixer BSOD i want to kill off I guess.

Hi,

Kmixer is a stable program, it crashes only if it is hardware error (ie faulty ram, m.b or PSU). Do you reseat the memory to another memory slot?

I resat the ram in a different slot altogether.I ran the program that always causes the BSOD and it crashed with kmixer.sys again.My ram is kingston hyper x khx3200a/256 x2.I went to the kingston web site and they say they don't make hyper x for my mobo(asus a7n8x)but if that were the problem it would either not work at all or crash all of the time.I can run a bittorrent client and adobe photoshop all day long and be running on 4% of free memory and it's fine(just slow), but 30 seconds of the bad prog and BOOM( I ran memtest/doc memory and goldmemory and they all report no errors) so I am going to delete the prog causing the trouble and see what happens from there.Thank you for your help and i will keepp you posted if anything else happens but I am leaning to my psu ( don't have a spare do ya?) it's an MGE 450w psu with 17a on the 12v rails.

CASE: MGE SIDEWINDER + MGE 450W PSU +12V@17A
MOBO: ASUS A7N8X
CPU: AMD ATHLON 2600+ 1.92GHZ@2.3GHZ + STOCK HSF IDLE 32c LOAD 42c
MEMORY: KINGSTON HYPER X PC3200 400MHZ 2X256 RUNNING DUAL CHANNEL
HDD: 60GB WD 30GB WD BOTH 5200RPM
GFX: MSI 6600GT AGP 128MB
FANS: 5x 80MM LED CASE FANS
DRIVES 1x FLOPPY 1x CDRW
PCI: 10/100 NIC

run memtest86 overnight to find bad ram.

my last memtest was 9 hours it did like 35 passes and no bad ram found.

Does your motherboard accept that brand and type of RAM? ASUS is very picky about RAM. RTFM to see what types it will take. If you're overclocking - don't. I never recommend overclocking.

Kingston

KVR400X64
C25/256

2.5

256MB

Single

Winbond

W942508BH-5

This is the ram on the asus qvl chart.Mine is khx3200a/256 x2.

then you probably don't have bad ram. The problem is elsewhere. Are you overclocking?

Set everything to the stock setting on each piece of hardware and run prime95 again. Try to test the RAM in another computer if you can or try another stick in your computer to see if you still get the BSOD.

I have overclocked.I have attached a pic of the results from crystalcpuid.Remember this is an athlon xp 2600+.
I have deleted the program that was causing the crashes so I cant set it to stock speeds to try it with that and I am going to see if it crashes without that prog.

Highest i have had this was 2497mhz @ fsb 217.2mhz (on stock hsf 49c). I ran it for like 5 mins and then set it back to 2305mhz and I haven't been able to clock it at that again( crap psu I think).My video card is only mildly overclocked from 900mhz memory to 1ghz but I have read most 6600gts are clocked at 1ghz anyways.

Ok werty i ran prime 95 for 9 hours @ stock speed mem + cpu @166mhz and no errors.
I reverted back to my overclocked 200mhz and it stops within 10 minutes.I am going to adjust the vcore a little and retest as advised in the stress test text file in prime 95.

you're risking frying your memory and cpu.
adjusting the vcore is dangerous.

The vcore has been raised from 1.65v to 1.72v and my pc is stable.Prime 95 says that my pc is at more risk by being unstable than upping vcore.