BSOD,with 3 minidumps file

[martin10522]

Got 3 bsod today,please check them =(

 

[stoneys-nutz]

Hello martin10522,
Can you fill out your system specs, bottom left hand corner, thanks.

 

[martin10522]

Hello martin10522,
Can you fill out your system specs, bottom left hand corner, thanks.

Ok there you go.

Anyway,can you tell me whats wrong?
I filled in.
Btw i was using vista and i downgraded to xp and i thought it would solve BSOD...but nah =/

Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
2.67 GHz Performance Rated at: 5.874 GHz
3.2 GB
Microsoft Windows XP Home Edition (Build Service Pack 32600)
You Have: GeForce 9600 GT
Features:
Video RAM 256 MB 512.0 MB

3D Yes Yes

Hardware T&L Yes Yes

Pixel Shader version 3.0 3.0

Vertex Shader version 3.0 3.0
Realtek High Definition Audio
465.1 GB (actually i have 1TB but its on C:\)

 

[martin10522]

Anyway,
What is
ntoskrnl.exe?
As i saw it on my bsod

 

[stoneys-nutz]

It is showing as memory corruption, i would remove all the memory and try one stick at a time, in all the slots, this will tell you which stick/ram slot is bad, (if any) can you confirm that nothing is overclocked.
Check to see that the ram voltage, and speed, is set at the manufacturers recommended settings.
If all the ram passes, then up the voltage on the NB, just a bit.

 

[martin10522]

It is showing as memory corruption, i would remove all the memory and try one stick at a time, in all the slots, this will tell you which stick/ram slot is bad, (if any) can you confirm that nothing is overclocked.
Check to see that the ram voltage, and speed, is set at the manufacturers recommended settings.
If all the ram passes, then up the voltage on the NB, just a bit.

Err..u know im not a computer pro..
And i only have two sticks.Should i try the 2nd one first?

I dont know if im overclocked,i bought it from a computer store.
Even if it is overclocked idk if they did set the bios,and idk how aswell.

Also..

"
Check to see that the ram voltage, and speed, is set at the manufacturers recommended settings.
If all the ram passes, then up the voltage on the NB, just a bit."

I dont understand
Firstly,where is manufacturers recommended settings?
Secondly,WHat is NB?and how do i "up the voltage"?
Sorry for the annoying,And tyvm for helping me all the time,idk how to "reward" you,but tyvm!

 

[stoneys-nutz]

OK, no problems, remove one stick and try, give it a good long run, do all the things that would normally give a BSOD.
If all goes well, remove that stick and replace with the other one.
Try this first.
What make and model is your ram ?. Look on the side of the ram sticks, it may give you the voltage and timings on there, some do.
Remember to give the one stick of ram a long run, hours not minutes.

 

[martin10522]

OK, no problems, remove one stick and try, give it a good long run, do all the things that would normally give a BSOD.
If all goes well, remove that stick and replace with the other one.
Try this first.
What make and model is your ram ?. Look on the side of the ram sticks, it may give you the voltage and timings on there, some do.
Remember to give the one stick of ram a long run, hours not minutes.

Ok im reading it now,i bought this computer from a store,like i told them what cpu,gpu and ram i want and they get them and make a computer for me.
My ram is..
kingston
2GB PC3 - 10600 CL9 240 - Pin DIMM

And the product is

KVR1333D3N9/2G

im not sure if this is the thing u wanted,i got that number/code from the ram ...box?or something,because they gave me CPU,Ram,gpu's box/pack to prove that they bought it.

If this is not the number u wanted,ill tell u when i remove 1 ram.

 

[stoneys-nutz]

The recommended voltage is 1.5V.
Leave the timings on auto for now.

 

[martin10522]

The recommended voltage is 1.5V.
Leave the timings on auto for now.

Yep,i took out 1 ram and it says
1.5V

"Leave the timings on auto for now. "
what do u mean?u know im stupid :P

Oh and btw,3 of the minidump files were also caused by memory corruption?

 

[stoneys-nutz]

For now, don't touch anything in the Bios, just try it with one stick.

 

[martin10522]

For now, don't touch anything in the Bios, just try it with one stick.

*sigh*
i've done it with the first one and i got BSOD,here is the minidump files,can u check if it is internet corruption?so i know it is the problem of this RAM

Also,could it be something with my RAM slot?
because it is put in 1 and 3 but there is 4 lol,should i put it on 1,2 or just keep it 1 3?

 

[stoneys-nutz]

Try it with the second one and see what happens.

 

[zigzag3143]

For now, don't touch anything in the Bios, just try it with one stick.

*sigh*
i've done it with the first one and i got BSOD,here is the minidump files,can u check if it is internet corruption?so i know it is the problem of this RAM

Hi and welcome

Any reason you didnt say you were running XP? SP3?

Your dump was caused by many things.
First old drivers
You have drivers that date from 1996-2006. These will always cause problems XP is newer than some of these drivers (see the list)
Then Your Avast was central to the crash



giveio.sys 0xf7a50000 0xf7a50680 0x00000680 0x316334f5 4/3/1996 9:33:25 PM
RDPCDD.sys 0xf79bd000 0xf79be080 0x00001080 0x3b7d82c0 8/17/2001 3:46:56 PM
Beep.SYS 0xf79b9000 0xf79ba080 0x00001080 0x3b7d82e5 8/17/2001 3:47:33 PM
Null.SYS 0xf7a91000 0xf7a91b80 0x00000b80 0x3b7d82eb 8/17/2001 3:47:39 PM
mouhid.sys 0xb4df3000 0xb4df5f80 0x00002f80 0x3b7d82fd 8/17/2001 3:47:57 PM
BOOTVID.dll 0xf7897000 0xf789a000 0x00003000 0x3b7d8345 8/17/2001 3:49:09 PM
kdcom.dll 0xf7987000 0xf7988b80 0x00001b80 0x3b7d8346 8/17/2001 3:49:10 PM
Fs_Rec.SYS 0xf79b7000 0xf79b8f00 0x00001f00 0x3b7d8361 8/17/2001 3:49:37 PM
ParVdm.SYS 0xf79a9000 0xf79aaa80 0x00001a80 0x3b7d836d 8/17/2001 3:49:49 PM
ptilink.sys 0xf77df000 0xf77e3580 0x00004580 0x3b7d8371 8/17/2001 3:49:53 PM
pciide.sys 0xf7a4f000 0xf7a4fd00 0x00000d00 0x3b7d83e5 8/17/2001 3:51:49 PM
ftdisk.sys 0xf74d8000 0xf74f6880 0x0001e880 0x3b7d8419 8/17/2001 3:52:41 PM
dxgthk.sys 0xb4e1d000 0xb4e1dd00 0x00000d00 0x3b7d8438 8/17/2001 3:53:12 PM
Dxapi.sys 0xb4798000 0xb479a900 0x00002900 0x3b7d843f 8/17/2001 3:53:19 PM
raspti.sys 0xf77e7000 0xf77eb080 0x00004080 0x3b7d84c4 8/17/2001 3:55:32 PM
rasacd.sys 0xb6f53000 0xb6f55280 0x00002280 0x3b7d84cb 8/17/2001 3:55:39 PM
fsvga.sys 0xb87ea000 0xb87ecf80 0x00002f80 0x3b7d8531 8/17/2001 3:57:21 PM
mnmdd.SYS 0xf79bb000 0xf79bc080 0x00001080 0x3b7d8538 8/17/2001 3:57:28 PM
audstub.sys 0xf7a76000 0xf7a76c00 0x00000c00 0x3b7d85bc 8/17/2001 3:59:40 PM
USBD.SYS 0xf799f000 0xf79a0280 0x00001280 0x3b7d8682 8/17/2001 4:02:58 PM
WMILIB.SYS 0xf7989000 0xf798a100 0x00001100 0x3b7d878b 8/17/2001 4:07:23 PM
dump_WMILIB.SYS 0xf79cd000 0xf79ce100 0x00001100 0x3b7d878b 8/17/2001 4:07:23 PM
admjoy.sys 0xb87e6000 0xb87e8a80 0x00002a80 0x3c992dce 3/20/2002 7:48:14 PM
HDAudBus.sys 0xb72c2000 0xb72ea000 0x00028000 0x4295ef55 5/26/2005 10:46:29 AM
speedfan.sys 0xf798b000 0xf798c480 0x00001480 0x4516880f 9/24/2006 8:28:47 AM




Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Mini111609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x805644c0
Debug session time: Mon Nov 16 09:41:50.875 2009 (GMT-5)
System Uptime: 0 days 0:15:44.472
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {a880, 2, 1, 80702a79}

*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+68ac )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000a880, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80702a79, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 0000a880

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireQueuedSpinLock+2d
80702a79 8711 xchg edx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: GTAIV.exe

LAST_CONTROL_TRANSFER: from 80702a41 to 80702a79

STACK_TEXT:
a07ac818 80702a41 804e3099 88aee813 88aee680 hal!KeAcquireQueuedSpinLock+0x2d
a07ac81c 804e3099 88aee813 88aee680 00000000 hal!KeAcquireQueuedSpinLockRaiseToSynch+0x5
a07ac830 f74a331a 89110bf0 00000000 00000000 nt!KeSetEvent+0x10
a07ac844 804e28ff 89911960 88aee680 89110be0 fltmgr!FltpGeneralCompletion+0x16
a07ac874 f7b526bb a07ac8a4 00000000 a07ac964 nt!IopfCompleteRequest+0xa2
a07ac884 f7b78028 88b799b8 88aee680 00000000 Ntfs!NtfsCompleteRequest+0xac
a07ac964 804e23d9 89ae4020 88aee680 887a8520 Ntfs!NtfsFsdCreate+0x4a0
a07ac974 f7493876 00000000 89af6630 89110be0 nt!IopfCallDriver+0x31
a07ac9c0 804e23d9 89b98ac0 00000001 88aee680 sr!SrCreate+0x150
a07ac9d0 f74a3e9b 00000000 88aee680 88aee834 nt!IopfCallDriver+0x31
a07ac9f4 f74b0754 a07aca14 89911960 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
a07aca30 804e23d9 89911960 88aee680 88aee87c fltmgr!FltpCreate+0x26a
a07aca40 a09a38ac 88aee690 89b6ba00 887a8520 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
a07aca64 a099d83c 891829c0 00aee680 804e23d9 aswMon2+0x68ac
a07acb60 8056e03b 89b8a9e0 00000000 88730008 aswMon2+0x83c
a07acbd8 80571358 00000000 a07acc18 00000040 nt!ObpLookupObjectName+0x53c
a07acc2c 8057d246 00000000 00000000 00000001 nt!ObOpenObjectByName+0xea
a07acca8 8057d315 0012e01c 00100020 0012dfd4 nt!IopCreateFile+0x407
a07acd04 8057d4c3 0012e01c 00100020 0012dfd4 nt!IoCreateFile+0x8e
a07acd44 804de99f 0012e01c 00100020 0012dfd4 nt!NtOpenFile+0x27
a07acd44 7c92e514 0012e01c 00100020 0012dfd4 nt!KiFastCallEntry+0xfc
0012e268 00000000 00000000 00000000 00000000 0x7c92e514


STACK_COMMAND: kb

FOLLOWUP_IP:
aswMon2+68ac
a09a38ac ?? ???

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: aswMon2+68ac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswMon2

IMAGE_NAME: aswMon2.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4aaf72cc

FAILURE_BUCKET_ID: 0xA_aswMon2+68ac

BUCKET_ID: 0xA_aswMon2+68ac

Followup: MachineOwner
---------

 

[martin10522]

For now, don't touch anything in the Bios, just try it with one stick.

*sigh*
i've done it with the first one and i got BSOD,here is the minidump files,can u check if it is internet corruption?so i know it is the problem of this RAM

Hi and welcome

Any reason you didnt say you were running XP? SP3?

Your dump was caused by many things.
First old drivers
You have drivers that date from 1996-2006. These will always cause problems XP is newer than some of these drivers (see the list)
Then Your Avast was central to the crash



giveio.sys 0xf7a50000 0xf7a50680 0x00000680 0x316334f5 4/3/1996 9:33:25 PM
RDPCDD.sys 0xf79bd000 0xf79be080 0x00001080 0x3b7d82c0 8/17/2001 3:46:56 PM
Beep.SYS 0xf79b9000 0xf79ba080 0x00001080 0x3b7d82e5 8/17/2001 3:47:33 PM
Null.SYS 0xf7a91000 0xf7a91b80 0x00000b80 0x3b7d82eb 8/17/2001 3:47:39 PM
mouhid.sys 0xb4df3000 0xb4df5f80 0x00002f80 0x3b7d82fd 8/17/2001 3:47:57 PM
BOOTVID.dll 0xf7897000 0xf789a000 0x00003000 0x3b7d8345 8/17/2001 3:49:09 PM
kdcom.dll 0xf7987000 0xf7988b80 0x00001b80 0x3b7d8346 8/17/2001 3:49:10 PM
Fs_Rec.SYS 0xf79b7000 0xf79b8f00 0x00001f00 0x3b7d8361 8/17/2001 3:49:37 PM
ParVdm.SYS 0xf79a9000 0xf79aaa80 0x00001a80 0x3b7d836d 8/17/2001 3:49:49 PM
ptilink.sys 0xf77df000 0xf77e3580 0x00004580 0x3b7d8371 8/17/2001 3:49:53 PM
pciide.sys 0xf7a4f000 0xf7a4fd00 0x00000d00 0x3b7d83e5 8/17/2001 3:51:49 PM
ftdisk.sys 0xf74d8000 0xf74f6880 0x0001e880 0x3b7d8419 8/17/2001 3:52:41 PM
dxgthk.sys 0xb4e1d000 0xb4e1dd00 0x00000d00 0x3b7d8438 8/17/2001 3:53:12 PM
Dxapi.sys 0xb4798000 0xb479a900 0x00002900 0x3b7d843f 8/17/2001 3:53:19 PM
raspti.sys 0xf77e7000 0xf77eb080 0x00004080 0x3b7d84c4 8/17/2001 3:55:32 PM
rasacd.sys 0xb6f53000 0xb6f55280 0x00002280 0x3b7d84cb 8/17/2001 3:55:39 PM
fsvga.sys 0xb87ea000 0xb87ecf80 0x00002f80 0x3b7d8531 8/17/2001 3:57:21 PM
mnmdd.SYS 0xf79bb000 0xf79bc080 0x00001080 0x3b7d8538 8/17/2001 3:57:28 PM
audstub.sys 0xf7a76000 0xf7a76c00 0x00000c00 0x3b7d85bc 8/17/2001 3:59:40 PM
USBD.SYS 0xf799f000 0xf79a0280 0x00001280 0x3b7d8682 8/17/2001 4:02:58 PM
WMILIB.SYS 0xf7989000 0xf798a100 0x00001100 0x3b7d878b 8/17/2001 4:07:23 PM
dump_WMILIB.SYS 0xf79cd000 0xf79ce100 0x00001100 0x3b7d878b 8/17/2001 4:07:23 PM
admjoy.sys 0xb87e6000 0xb87e8a80 0x00002a80 0x3c992dce 3/20/2002 7:48:14 PM
HDAudBus.sys 0xb72c2000 0xb72ea000 0x00028000 0x4295ef55 5/26/2005 10:46:29 AM
speedfan.sys 0xf798b000 0xf798c480 0x00001480 0x4516880f 9/24/2006 8:28:47 AM




Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Mini111609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x805644c0
Debug session time: Mon Nov 16 09:41:50.875 2009 (GMT-5)
System Uptime: 0 days 0:15:44.472
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {a880, 2, 1, 80702a79}

*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+68ac )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000a880, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80702a79, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 0000a880

CURRENT_IRQL: 2

FAULTING_IP:
hal!KeAcquireQueuedSpinLock+2d
80702a79 8711 xchg edx,dword ptr [ecx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: GTAIV.exe

LAST_CONTROL_TRANSFER: from 80702a41 to 80702a79

STACK_TEXT:
a07ac818 80702a41 804e3099 88aee813 88aee680 hal!KeAcquireQueuedSpinLock+0x2d
a07ac81c 804e3099 88aee813 88aee680 00000000 hal!KeAcquireQueuedSpinLockRaiseToSynch+0x5
a07ac830 f74a331a 89110bf0 00000000 00000000 nt!KeSetEvent+0x10
a07ac844 804e28ff 89911960 88aee680 89110be0 fltmgr!FltpGeneralCompletion+0x16
a07ac874 f7b526bb a07ac8a4 00000000 a07ac964 nt!IopfCompleteRequest+0xa2
a07ac884 f7b78028 88b799b8 88aee680 00000000 Ntfs!NtfsCompleteRequest+0xac
a07ac964 804e23d9 89ae4020 88aee680 887a8520 Ntfs!NtfsFsdCreate+0x4a0
a07ac974 f7493876 00000000 89af6630 89110be0 nt!IopfCallDriver+0x31
a07ac9c0 804e23d9 89b98ac0 00000001 88aee680 sr!SrCreate+0x150
a07ac9d0 f74a3e9b 00000000 88aee680 88aee834 nt!IopfCallDriver+0x31
a07ac9f4 f74b0754 a07aca14 89911960 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
a07aca30 804e23d9 89911960 88aee680 88aee87c fltmgr!FltpCreate+0x26a
a07aca40 a09a38ac 88aee690 89b6ba00 887a8520 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
a07aca64 a099d83c 891829c0 00aee680 804e23d9 aswMon2+0x68ac
a07acb60 8056e03b 89b8a9e0 00000000 88730008 aswMon2+0x83c
a07acbd8 80571358 00000000 a07acc18 00000040 nt!ObpLookupObjectName+0x53c
a07acc2c 8057d246 00000000 00000000 00000001 nt!ObOpenObjectByName+0xea
a07acca8 8057d315 0012e01c 00100020 0012dfd4 nt!IopCreateFile+0x407
a07acd04 8057d4c3 0012e01c 00100020 0012dfd4 nt!IoCreateFile+0x8e
a07acd44 804de99f 0012e01c 00100020 0012dfd4 nt!NtOpenFile+0x27
a07acd44 7c92e514 0012e01c 00100020 0012dfd4 nt!KiFastCallEntry+0xfc
0012e268 00000000 00000000 00000000 00000000 0x7c92e514


STACK_COMMAND: kb

FOLLOWUP_IP:
aswMon2+68ac
a09a38ac ?? ???

SYMBOL_STACK_INDEX: d

SYMBOL_NAME: aswMon2+68ac

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswMon2

IMAGE_NAME: aswMon2.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4aaf72cc

FAILURE_BUCKET_ID: 0xA_aswMon2+68ac

BUCKET_ID: 0xA_aswMon2+68ac

Followup: MachineOwner
---------

I did say i am running xp SP3,look at my system specs.
Also,
can you tell me what driver are those?i think it is motherboard's right?
Because its the only 1 that i installed with disk
I updated video card driver to the lastest one.
So is my cpu.
And my audio card,
i also tried to find updates drivers for my motherboard,i updated 2 of them,and i cant find another...

Also i downloaded Avast from this forum's link,and it was the lastest i guess...
How come i cause crash??=/

And so should i test the ram still?
Is it memory corrupted for this minidump?

 

[martin10522]

Ah,also,there is a programme for checking your drivers and update it for you right?can you tell me the name?because i forgot where i found it while i was using vista =/

 

[martin10522]

Sorry for the triple post,
I have a bad news,i got BSod with another ram aswell,so i guess its not the RAM's problem,perhaps it is really driver's problem.
But i got to know which drivers are outdate,and i will try to find those driver
Also why avast cause bsod?
Anyway heres the minidump file

 

[martin10522]

Please help =(!

 

[martin10522]

ok heres another minidump file