use winzip..dun use winrar...
ok?

whew.. finally manage to upload my minidump file. Thanks alot for your help francischuahcw. Really appreaciate it.
now i hope someone can help me define my problem because 5 minutes ago again i experience the blackout and the blue screen appear then autoreboot.
Pls help me
thanks

This post has been edited by HIM: Sep 10 2008, 01:39 AM

Attached File(s)
 1.zip ( 49.54k ) Number of downloads: 9

Guys my lappy is having this problem,when i try starting any games this error appears---->ati3duag.dll(PAGE_FAULT_IN_NONPAGED_AREA)....How do i solve this problem?anyway i try finding for the minidump file but i cant find it...

 Minidump.zip ( 99.38k ) Number of downloads: 9


tis is my minidump file....any pro pls help me check out izzit there got any problem???pm tell me pls......

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.

Yeah is not there something strange

---

Added on September 10, 2008, 5:15 pmAnyway im using Windows Vista not Windows XP....

This post has been edited by MohdFarid1994: Sep 10 2008, 05:15 PM

[quote=tthm,Sep 10 2008, 04:57 PM]
It is me or the file you have uploaded is encrypted with password?

I think i accidentally put in the password. Sorry for the trouble.
Here i reupload a new one. I change to ati ccc 8.8 one month ago. Before last saturday, all are working fine, so i dun think is GC driver problem. Really hope someone can help me solve this problem cause frequent blue screen scare will spoild my pc.
Thanks in advance

Attached File(s)
 1.zip ( 24.7k ) Number of downloads: 4

I meet BSOD at error code 0x0000001e. What does it mean? Below is the information I got le...



I also uploaded the dump files.

Thanks in advanced.

Attached File(s)
 Desktop.zip ( 39.44k ) Number of downloads: 1

Advice please

[quote=HIM,Sep 11 2008, 01:29 AM]
[quote=tthm,Sep 10 2008, 04:57 PM]
It is me or the file you have uploaded is encrypted with password?

I think i accidentally put in the password. Sorry for the trouble.
Here i reupload a new one. I change to ati ccc 8.8 one month ago. Before last saturday, all are working fine, so i dun think is GC driver problem. Really hope someone can help me solve this problem cause frequent blue screen scare will spoild my pc.
Thanks in advance

[/quote]
help me pls....

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

Here is all my minidump in 1 file.
The first one was a bsod while i was running acdsee10, and the second one was when i was using process explorer to terminate some application and while looking for the dll of the application..

I did tested my ram using memtest+ and got 0 errors after running for many hours (non-continuously). And the 2 bsods i got are after i got a stable test result from memtest (ram @ stock voltage) . Before this, i was giving 2.09v to the ram and this gets me 1 error in test #4 memtest. I did installed my os under the same ram condition as the one failing memtest test #4 ... <- possible cause?

Ram @ 1.85v = 100% stable
Ram @ 2.10v/2.00v = failed test #4 of memtest

Everything else is very stable though
 Minidump.zip ( 36.14k ) Number of downloads: 5


Thanks in advanced

This post has been edited by ivanchin99: Sep 14 2008, 12:56 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).

Not overclocking my ram now, running at stock voltage and stock timings..

Testing it now.. will get back to you:)

---

Added on September 14, 2008, 3:10 pmNope.. ran 3 passes and no error.
Ram running @ 640mhz 1.85v(auto)

This post has been edited by ivanchin99: Sep 14 2008, 03:10 PM

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.

Corsair 667 valueram 1gb x2

Well before this i set the timing of the rams to 2.1v and 4-4-4-12 and had some regular bsods.. Tested the ram individually and found that one of the ramstick wasnt able to withstand the 4-4-4-12 timing - plenty of errors in memtest while the other ram stick passes the test flawlessly

Of course, after setting back to auto voltage, i had no failing on memtest even when running at 4-4-4-12 except the acdsee bsod, hence i relax the timing to 5-5-5-15..

No overheating from cpu, prime95 running at 60+ and stays there..

well hopefully there wont be any bsod anymore

btw, would a os installed using rams that had 1 error in memtest caused my system to have bsod once in while like what im having?

Got a BSOD while playing war3, i think it has nothing to do with ram though, realtek thingie..

Here's the minidump
 Mini091408_01.zip ( 18.65k ) Number of downloads: 1



anyway, im pissed.. reformat in 10mins

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

It seems like the link u given is not working.
BTW, thanks alot for your help, but i think is not the GC or the driver problem.
This thing happent after i use my hostel LAN to on9. So i decided to do an experiment. I stop using LAN since last monday and the problem never appear again so far.
So will wait for another week, if nothing happen then i am sure that it is the LAN problem. At that time maybe will need your help to solve the LAN problem. hehe.
BTW, i will post my result up here so that can help the other
Thanks again for your help

This post has been edited by HIM: Sep 14 2008, 09:29 PM

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.

i already type %systemroot%\minidump at run..
but, it cant find the file..
then how can i post the zip file here..
help me..
=.=