It seems like memory related problem more than motherboard problem. Anyhow, have you tried to use single/double channel RAM configuration and changing your RAM timing from 1T to 2T?

Refer to your motherboard manual for RAM configuration.

Memtest sometimes failed to detect error proper especially related to power fluctuation under normal use.

Oh ya, your Windows need to be updated to the latest service packs and patches.

Hopes it'll help...

Few questions,

1. How many devices you have connected to your USB port as it seems snppro.sys caused your system USB device driver to crash?

2. Your system crashes only when you're using the webcam?

3. Can list out your system spec?

Hopes it'll help...

From just one minidump file, it could be mostly hardware related problem. It's best to attach around 5 or 6 of your latest minidump files for better analysis.

Is it possible to list out your system spec as I saw some pretty old driver still running in your system.

Hopes it'll help...

This post has been edited by tthm: Dec 14 2006, 09:11 AM

Try to unplug unnecessary devices from your USB especially your webcam as your system crash was caused by the webcam driver.

Then you'll need to monitor the situation for some time.

You could try to use single or double channel RAM configuration to test.

Overvoltage or undervoltage are able to cause such error as well. Try to play around your RAM timing, it might help.

Hopes it'll help...

Are you using NForce motherboard?

You could try to uninstall your NForce Nvidia Firewall software (NAM) and see if it'll help.

Open this link below and proceed to read Small memory dump and Configure the dump type,

Overview of memory dump file options for Windows Server 2003, Windows XP, and Windows 2000

You could also read the 1st page of this thread for more info. If you need further assistance, please upload your memory dump files here.

Hi serenayap,

Do you encounter any random restart with your computer with blue screen?

Else I have to split your problem to a new thread as this thread is for Blue Screen error issues only.

Regards,
Mod

Please upload a few of your latest minidump files. The one uploaded was corrupted.

From your minidump,


You could try to check if any of your connected hardware or software driver are compatible to your Vista. I can see you're running some old hardware/software from your notebook.

Other things you can do is to upload all the 4 minidumps for a more accurate understanding of your crashes.

Hope it'll helps...

You could try this steps below to open the minidump folder,

1. Click Start/[ button and click on [b]Run option.
2. Type %SystemRoot%\minidump and click OK.
3. Zip or RAR those files (e.g. mini090508.dmp, etc) you can see and upload to this thread.

From there on, we'll try to analyze your system crash file and try to find the culprit causing your system crash.

---

Added on September 7, 2008, 1:06 amEither your system memory having problem (less likely) or you could try to remove / uninstall / disable cFosSpeed software. All your minidump files seems to be pointing to that software cfosspeed.sys and running in idle mode.

This post has been edited by tthm: Sep 7 2008, 01:06 AM

Your system error seems to be point to bad driver memory management. Try installing the correct driver for your motherboard.

You could upload the minidump files here for more detail analysis.

It is me or the file you have uploaded is encrypted with password?

Your problem seems to be on the graphics driver side. Try installing newer or older (sometimes older version give more stable performance) version of your graphic card driver. Other things you might want to check including your Windows version and the service packs version. Is it the latest version for your graphic driver requirement?

Uploading the minidump files do provide a much better view of the cause. You can try looking into your C:\Windows\Minidump or just type %SystemRoot%\Minidump into the run command on your Start Menu.

All your 4 minidumps points to your Kaspersky (kl1.sys) as the cause. Suggest to uninstall Kaspersky and monitor if BSOD appear again.

Open System Properties, select Advanced system settings tab and then Startup and Recovery Settings. Under Write debugging information make sure Small memory dump (64KB) is selected. You can see the default Small dump directory: path as %SystemRoot%\Minidump. Restart your computer as instructed and continue using your computer like normal.

Then you can just wait till BSOD happen and check for minidump files.

Your minidump file seems to be pointing to your graphic card hanging (most probabily the driver causing this error only). Recommend to drop back to older version of your graphic card driver to test out your hardware.

You may refer to Known Issues Under the Windows Vista Operating System in the link below for any issues,

Release Notes

Let me know the result of your test.

From your minidump, kl1.sys (Kaspersky) seems to be the cause (see below link for another user reported similar error to yours). Try to upload more minidump for better analysis or you could try to uninstall Kaspersky like what was done by the user in the link mentioned.

BSOD Klif.sys Vista 64 bit SP 1

You might need to check for overheating of your graphical. Suggest to lock back your graphic card overclock component or you could try to get the latest or previous supported driver for your graphic card.


Most probably your memory is the cause. Try testing your system memory using Memtest or others memory testing software.

Recommended to upload all or the latest 4 or 5 minidumps for a more detail analysis.

And your problem is?

This post has been edited by tthm: Sep 14 2008, 12:42 AM

Both the minidump indicate memory related error (Bugcheck 8E and Bugcheck 50). How long have you be overclocking your RAM?

You might want to try testing using Windows Memory Diagnostic tools found under my signature. Use Extended Test (T) to test running condition under stimulated Windows usage for at least 2 cycle or more.

Other test include running normal Windows with minimum RAM piece one by one to check and check hardware temperature (especially your RAM and CPU).

Can I know how many RAM piece your system running with as well as the type of RAM?

Have you tested running with bare minimum RAM pieces?

Any overheating from your CPU?

Let me know if your system crashes again. Need more minidump files for better analysis.

Yes to your question. Actually depends on your system if it suddenly try to access (read / write) to a particularly unstable area of the memory, causing system to crash.

From your minidump,

BugCheck 1000008E, {c0000005, ac66000b, 9f2cb6cc, 0}
Probably caused by : RtkHDAud.sys ( RtkHDAud+7000b )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

9f2cb744 ac61d5ee 00000000 fb907728 fbadce38 RtkHDAud+0x7000b
9f2cb990 acaaa97d 882c3008 9f2cb9bc acaaa872 RtkHDAud+0x2d5ee
9f2cb9bc acaaa9cf 882c3008 fb907728 e19c6644 portcls!PcDispatchProperty+0x130
9f2cb9e4 b912ff5c 00000004 fbc7de28 fbc7de20 portcls!PropertyItemPropertyHandler+0x2b
9f2cba48 b912fed9 882c3008 0000000c e19c6644 ks!KspPropertyHandler+0x616
9f2cba6c acaa86a9 882c3008 0000000c e19c65b8 ks!KsPropertyHandler+0x19
9f2cba80 acab570f 882c3008 0000000c e19c65b8 portcls!PcHandlePropertyWithTable+0x1b
9f2cbab8 acaa874d fb9076a8 89ff2498 882c3008 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e5
9f2cbad4 b912ff1f 89ff2498 882c3008 9f2cbafc portcls!DispatchDeviceIoControl+0x49
9f2cbae4 acaa88c0 89ff2498 882c3008 89ff2550 ks!KsDispatchIrp+0x126
9f2cbafc acaa8881 89ff2498 882c3008 9f2cbb30 portcls!KsoDispatchIrp+0x43
9f2cbb0c ac9eb08e 89ff2498 882c3008 00000000 portcls!PcDispatchIrp+0x5f
9f2cbb30 804ef18f 89ff2498 00000004 882c3008 RtkHDAud+0x3fb08e
9f2cbb40 ba2f8774 e167b850 00000000 882c3008 nt!IopfCallDriver+0x31
9f2cbb90 ba2fb2a2 882c3008 fbc7de28 e34b5428 sysaudio!ForwardIrpNode+0x1b2
9f2cbbe8 b912ff95 897899c8 882c3008 9f2cbc1c sysaudio!CPinInstance::PinDispatchIoControl+0x153
9f2cbbf8 804ef18f 897899c8 882c3008 806e6410 ks!DispatchDeviceIoControl+0x28
9f2cbc08 8057f982 882c3150 f7be2470 882c3008 nt!IopfCallDriver+0x31
9f2cbc1c 805807f7 897899c8 882c3008 f7be2470 nt!IopSynchronousServiceTail+0x70
9f2cbcb8 80579274 000026c4 00002374 00000000 nt!IopXxxControlFile+0x5c5
9f2cbcec ac5785d8 000026c4 00002374 00000000 nt!NtDeviceIoControlFile+0x2a
9f2cbd34 8054161c 000026c4 00002374 00000000 klif+0x105d8
9f2cbd34 7c90e4f4 000026c4 00002374 00000000 nt!KiFastCallEntry+0xfc
0013f0fc 00000000 00000000 00000000 00000000 0x7c90e4f4

SYMBOL_NAME: RtkHDAud+7000b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RtkHDAud
IMAGE_NAME: RtkHDAud.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47ea2755
FAILURE_BUCKET_ID: 0x8E_RtkHDAud+7000b
BUCKET_ID: 0x8E_RtkHDAud+7000b

From the looks of it, your system crashed during access to your sound card.

Anyway, try to update here if your system crashes again. Might not be just the memory causing the error, suspecting other possible cause. Will need more minidump files to get more info.

Hmmm....
Just for reference purpose only for your uploaded minidump,

BugCheck 116, {fffffa80050774e0, fffffa6002629390, 0, d}
Probably caused by : atikmdag.sys ( atikmdag+29390 )
VIDEO_TDR_FAILURE (116)
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
STACK_TEXT:
fffffa60`04296a08 fffffa60`02cba398 : 00000000`00000116 fffffa80`050774e0 fffffa60`02629390 00000000`00000000 : nt!KeBugCheckEx
fffffa60`04296a10 fffffa60`02cba24a : fffffa60`02629390 fffffa80`050774e0 fffffa80`066fd540 fffffa80`050774e0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffffa60`04296a50 fffffa60`02c74d8a : 00000000`00001a5c 00000000`00000000 fffffa80`066fd540 00000000`00005f74 : dxgkrnl!TdrIsRecoveryRequired+0x1ee
fffffa60`04296a90 fffffa60`02d3526b : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000002 : dxgkrnl!VidSchiReportHwHang+0x312
fffffa60`04296b40 fffffa60`02d33e6d : fffffa80`066fd540 00000000`00000000 00000000`00005f74 fffffa80`066fd540 : dxgkrnl!VidSchiCheckHwProgress+0x7b
fffffa60`04296b70 fffffa60`02c790f8 : ffffffff`ff676980 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VidSchiWaitForSchedulerEvents+0x199
fffffa60`04296bf0 fffffa60`02d33c8d : 00000000`00000000 fffffa80`066fd2d0 00000000`00000080 fffffa80`066fd540 : dxgkrnl!VidSchiScheduleCommandToRun+0x398
fffffa60`04296d10 fffff800`0228df73 : fffffa80`066ff3c0 fffff800`02064697 fffffa60`019fc380 00000000`00000001 : dxgkrnl!VidSchiWorkerThread+0x95
fffffa60`04296d50 fffff800`020a4526 : fffffa60`005ec180 fffffa80`066ff3c0 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`04296d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_NAME: atikmdag+29390

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 489298df

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmdag.sys

Anyway, just monitor your system and post up your test result for record keeping.

Try using just 1 piece of ram one at a time and run memory test to confirm memory failure (starting with the failed ram stick). Need you to confirm if the same error appear again or not. Otherwise suspecting unstable motherboard or overheating component (motherboard or ram chip).

Good to hear that.

No more warranty left for your motherboard? Some motherboard like Intel comes with 3 years warranty.

You may read through topics posted here.

After deciding to go for your chosen AV security suites, download it and try it out for 30 days free trial (most will give 30 days trial).

Hi horcruxes,

Your minidump shows most (if not all) of your system crash was caused by hardware error (random memory and CPU error) and mostly during your Warcraft session.

Would like you to check your system and CPU temperature. You can view your temperature after any crash from your BIOS or your system monitoring software that came with your motherboard.

Also physically check to see if your motherboard have any leaking / bulging capacitor. See the link below to identify how leaking / bulging looks like,

Bad Capacitors Information and symptoms

Dear najibian,

Stop spamming here in Technical Support with your pointless post!

Regards,
Mod

Your dump files seems to be pointing to memory failure (possible overheating) after a really pro-long usage and it crashes randomly from firefox to windows explorer to your windows system application.

Suggest to monitor your system and RAM temperature right after any crash.

Sorry for the late reply.

Did you monitor your system temperature (e.g. CPU, north-bridge chipset and also graphic card)?

You may want to do a full memory test on your system for a few cycle to see if your system RAM fail over long running time. For the software, you may want to Windows Memory Diagnostic.