Frequent BSoD and PC does not memorize time HELP

[P4or]

Hi there, i am new to this forum and i would like to receive help with my problem.
I apologize for bad grammar first.
Second, this is my system:

Processor: AMD Athlon II x2 240 processor 2812 dual core
Graphics: ATI Radeon 4600 HD
Ram: 3 gb of ram not sure how to identify them i will provide more information tomorrow when i open up PC.
Motherboard:As rock also not sure which model.
HD:1.Maxtor 6L160P0
2.Seagate barracuda st380815as

Not sure if i typed all the stuff correctly but i think this will help a bit.
Now, i have blue screen for past few weeks almost every 2 days, and it occurs at random time. Also, sometimes when i restart or turn off pc it happens to ''forget time'' and reverse it when pc was last time booted.
Now i was suspicious of old HD maxtor, i detached it for 2 days and i still had BSoD. Now i think something is wrong with either memory or motherboard.

Thanks.

 

[Orgie]

I would say look up your motherboard model and see if there is a BIOS update for it. don't know if that will fix the bluescreening but it may fix the time changing.

For your Bluescreen windows creates a folder with dump files. ( C drive - Windows - minidumps)
Upload those files onto http://www.osronline.com/page.cfm?name=analyze and that should give you an idea of what can be happening. feel free to post the report.

 

[P4or]

I would say look up your motherboard model and see if there is a BIOS update for it. don't know if that will fix the bluescreening but it may fix the time changing.

For your Bluescreen windows creates a folder with dump files. ( C drive - Windows - minidumps)
Upload those files onto http://www.osronline.com/page.cfm?name=analyze and that should give you an idea of what can be happening. feel free to post the report.

I will try to install new bios and also replace battery on MB because friend told me that could be the case, since my PC forgets time sometimes when i shut it down, but that is not logical at all...
And i installed bsod viewer but i accidentally deleted dump files with CCleaner (dumb me)
Anyway i will do some test and try to post results here as fast as possible.

EDIT:Motherboard is ASRock N68-S

 

[Orgie]

I would agree with the battery, just didn't say as if it was the battery normally it will do every time and it would go back way in the past if it was the battery.

yeah once you get a dump files look into it.

 

[P4or]

I would agree with the battery, just didn't say as if it was the battery normally it will do every time and it would go back way in the past if it was the battery.

yeah once you get a dump files look into it.

I had no BSoD today, i am still waiting, however, windows explorer freezed and crashed once and i had to restart manually, i could still enter games move mouse but nothing was on screen. This morning i had clock once again changed, but now after i came home and turned on pc (i had it unplugged from elecriticity completely) he memorized clock. Still waiting for BSoD to occur, posting results asap!
And i didn't change battery btw.

 

[P4or]

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 001904fb
Arg2: 9ec67864
Arg3: 9ec67440
Arg4: 8ae70f38

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_RECORD: 9ec67864 -- (.exr 0xffffffff9ec67864)
ExceptionAddress: 8ae70f38 (Ntfs!NtfsModifySecurity+0x00000207)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 1bff7b0e
Attempt to write to address 1bff7b0e

CONTEXT: 9ec67440 -- (.cxr 0xffffffff9ec67440)
eax=0009ec67 ebx=9ec67a9c ecx=9ec67b0c edx=00000000 esi=97ffe2f0 edi=00000000
eip=8ae70f38 esp=9ec6792c ebp=9ec679bc iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
Ntfs!NtfsModifySecurity+0x207:
8ae70f38 ddb10200397d fnsave [ecx+7D390002h] ds:0023:1bff7b0e=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 1bff7b0e

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82ba184c
Unable to read MiSystemVaType memory at 82b80f00
1bff7b0e

FOLLOWUP_IP:
Ntfs!NtfsModifySecurity+207
8ae70f38 ddb10200397d fnsave [ecx+7D390002h]

FAULTING_IP:
Ntfs!NtfsModifySecurity+207
8ae70f38 ddb10200397d fnsave [ecx+7D390002h]

BUGCHECK_STR: 0x24

MISALIGNED_IP:
Ntfs!NtfsModifySecurity+207
8ae70f38 ddb10200397d fnsave [ecx+7D390002h]

LAST_CONTROL_TRANSFER: from 8ae70f1e to 8ae70f38

STACK_TEXT:
9ec6792c 8ae70f1e 14259245 9be8bdb0 97ffe2f0 Ntfs!NtfsModifySecurity+0x207
9ec679bc 8ae712c4 9ec67a9c 9be8bdb0 97ffe2f0 Ntfs!NtfsModifySecurity+0x1f5
9ec67a24 8aea57ee 9ec67a9c 853faa08 14259171 Ntfs!NtfsCommonSetSecurityInfo+0x290
9ec67a88 8aea587b 9ec67a9c 853faa08 00000001 Ntfs!NtfsFsdDispatchSwitch+0x205
9ec67bbc 82a6ec1e 85fdf020 853faa08 853faa08 Ntfs!NtfsFsdDispatchWait+0x1c
9ec67bd4 8adcf20c 8605bb68 853faa08 00000000 nt!IofCallDriver+0x63
9ec67bf8 8adcf3cb 9ec67c18 8605bb68 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
9ec67c30 82a6ec1e 8605bb68 853faa08 85508580 fltmgr!FltpDispatch+0xc5
9ec67c48 82c9c784 b896e7a8 00000000 00000000 nt!IofCallDriver+0x63
9ec67ca4 82ca0e23 8605bb68 00000000 9ec67cdc nt!IopGetSetSecurityObject+0x257
9ec67cd0 82c3a959 85508501 20000004 9f2c7f20 nt!ObSetSecurityObjectByPointer+0x40
9ec67d20 82a758c6 00001450 20000004 08d1d698 nt!NtSetSecurityObject+0x150
9ec67d20 778f70f4 00001450 20000004 08d1d698 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0616ece8 00000000 00000000 00000000 00000000 0x778f70f4


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Ntfs!NtfsModifySecurity+207

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xffffffff9ec67440 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED_Ntfs.sys

BUCKET_ID: IP_MISALIGNED_Ntfs.sys

Followup: MachineOwner

This is what i got from OSR site, any clue? I can't understand a bit

 

[Orgie]

Hey sorry went on vacation just getting back, looks like the process that could of crashed it is chrome.exe

i would say unistall chrome and see if you experience the bluescreen. if you don't try installing it again and see if you get different results.

 

[Orgie]

Also if you have more dump files post them just want to see if they all are the same or different.

 

[Paul NZ]

That means a corrupt hdd / files. And you may have to replace the hdd to fix it

 

[P4or]

Also if you have more dump files post them just want to see if they all are the same or different.

I will post more results soon enough...i will also try to uninstall chrome and see if that could help..

That means a corrupt hdd / files. And you may have to replace the hdd to fix it

are you pretty sure about that?

 

[P4or]

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000002, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000002, address which referenced memory

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

READ_ADDRESS: GetPointerFromAddress: unable to read from 82bbb84c
Unable to read MiSystemVaType memory at 82b9af00
00000002

CURRENT_IRQL: 2

FAULTING_IP:
+0
00000002 ?? ???

PROCESS_NAME: System

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

TRAP_FRAME: 94007558 -- (.trap 0xffffffff94007558)
ErrCode = 00000010
eax=00000001 ebx=8b2a841d ecx=a2000101 edx=854ef1b0 esi=94007614 edi=00000000
eip=00000002 esp=940075cc ebp=854ef1b0 iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
00000002 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 00000002 to 82a92b7f

FAILED_INSTRUCTION_ADDRESS:
+0
00000002 ?? ???

STACK_TEXT:
94007558 00000002 badb0d00 854ef1b0 00000000 nt!KiTrap0E+0x1b3
WARNING: Frame IP not in any known module. Following frames may be wrong.
940075c8 85f2b000 940075ec 82adcc4b 00000000 0x2
940075d0 82adcc4b 00000000 00000000 8b312c80 0x85f2b000
940075ec 8b296b86 86440001 0000000b 85f23b50 nt!ExReleaseRundownProtectionCacheAwareEx+0x15
940075fc 85f2b000 00000000 94007604 00000000 tcpip!FlpReturnNetBufferListChain+0xa8
94007614 8b28ba38 85f23b50 8538f508 00007688 0x85f2b000
9400767c 8b28c26a 85f0b9d8 85f2b000 00000000 tcpip!TcpMatchReceive+0x237
940076cc 8b28c2ab 85f23b50 85f2b000 0000bb01 tcpip!TcpPreValidatedReceive+0x293
940076e8 8b2865cf 85f23b50 85f2b000 94007724 tcpip!TcpReceive+0x2d
940076f8 8b28e814 9400770c c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
94007724 8b28e156 8b307f90 94007778 c000023e tcpip!IppDeliverListToProtocol+0x49
94007744 8b28c518 8b307da0 00000006 94007778 tcpip!IppProcessDeliverList+0x2a
9400779c 8b28dfff 8b307da0 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1fb
94007830 8b29c515 86391120 00000000 94007801 tcpip!IpFlcReceivePackets+0xbe5
940078ac 8b296a9d 86448cf8 858687e8 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x746
940078e0 82adaac3 858687e8 bcd11256 85f26b30 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x11e
94007948 8b296c0b 8b29697f 94007970 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132
94007984 8b0dc18d 86448c02 85868700 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
940079bc 8b0ca5be 86448580 858687e8 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x188
940079e4 8b0ca4b2 00000000 858687e8 8624e0e0 ndis!ndisIndicateSortedNetBufferLists+0x4a
94007b60 8b075c2d 8624e0e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
94007b7c 8b0ca553 8624e0e0 858687e8 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2d
94007ba4 8b075c88 8624e0e0 858687e8 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
94007bcc 90b67616 8624e0e0 858687e8 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
94007bf0 90b8433c 8634f000 90b9bd30 00000004 nvm62x32+0x4616
94007c24 90b84619 00020000 00000001 8634f000 nvm62x32+0x2133c
94007c48 90b785a2 00000000 94007c70 90b68af1 nvm62x32+0x21619
94007c54 90b68af1 90b9d4c4 90b9bd30 00000000 nvm62x32+0x155a2
94007c70 8b0ca89a 8634f000 00000000 94007c9c nvm62x32+0x5af1
94007cac 8b0ac1bd 866e1ee4 006e1ed0 00000000 ndis!ndisMiniportDpc+0xe2
94007d0c 8b07b8e0 866e1fd0 00000000 860e95c8 ndis!ndisQueuedMiniportDpcWorkItem+0xd0
94007d50 82c5b141 00000001 bcd1168e 00000000 ndis!ndisReceiveWorkerThread+0x161
94007d90 82b02559 8b07b77f 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_IP:
tcpip!FlpReturnNetBufferListChain+a8
8b296b86 c9 leave

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: tcpip!FlpReturnNetBufferListChain+a8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 533f5805

FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_tcpip!FlpReturnNetBufferListChain+a8

BUCKET_ID: 0xD1_CODE_AV_BAD_IP_tcpip!FlpReturnNetBufferListChain+a8

Followup: MachineOwner

This one happened 4 days ago

 

[P4or]

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: a533c000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 82a4f505, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82b7f84c
Unable to read MiSystemVaType memory at 82b5ef00
a533c000

FAULTING_IP:
nt!memset+45
82a4f505 f3ab rep stos dword ptr es:[edi]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: vprot.exe

CURRENT_IRQL: 0

TRAP_FRAME: a533b754 -- (.trap 0xffffffffa533b754)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=0bf552f2 edx=00000003 esi=8582d2f0 edi=a533c000
eip=82a4f505 esp=a533b7c8 ebp=a533b8dc iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010213
nt!memset+0x45:
82a4f505 f3ab rep stos dword ptr es:[edi]
Resetting default scope

LAST_CONTROL_TRANSFER: from 82a56aa8 to 82aa3879

STACK_TEXT:
a533b73c 82a56aa8 00000001 a533c000 00000000 nt!MmAccessFault+0x104
a533b73c 82a4f505 00000001 a533c000 00000000 nt!KiTrap0E+0xdc
a533b7c8 8aed1f53 a533b7e8 00000000 2fd553e3 nt!memset+0x45
a533b8dc 00000000 00000000 00000000 00000000 Ntfs!NtfsAccessCheck+0x224


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
82a56aa8 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f

FAILURE_BUCKET_ID: 0x50_nt!KiTrap0E+dc

BUCKET_ID: 0x50_nt!KiTrap0E+dc

Followup: MachineOwner
---------
this one happened 2 days ago

 

[P4or]

System Uptime: 0 days 0:45:36.156
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82c74ed1, The address that the exception occurred at
Arg3: 8c36bc60, Trap Frame
Arg4: 00000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nt!NtAlpcQueryInformationMessage+c2
82c74ed1 0000 add byte ptr [eax],al

TRAP_FRAME: 8c36bc60 -- (.trap 0xffffffff8c36bc60)
ErrCode = 00000002
eax=00000000 ebx=00000000 ecx=a1dfec00 edx=8be578b8 esi=0000045c edi=879d0dd8
eip=82c74ed1 esp=8c36bcd4 ebp=8c36bd14 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!NtAlpcQueryInformationMessage+0xc2:
82c74ed1 0000 add byte ptr [eax],al ds:0023:00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!NtAlpcQueryInformationMessage+c2
82c74ed1 0000 add byte ptr [eax],al

LAST_CONTROL_TRANSFER: from 82a518c6 to 82c74ed1

STACK_TEXT:
8c36bd14 82a518c6 00000290 003f80c8 00000001 nt!NtAlpcQueryInformationMessage+0xc2
8c36bd14 771870f4 00000290 003f80c8 00000001 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
0048f8ac 00000000 00000000 00000000 00000000 0x771870f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!NtAlpcQueryInformationMessage+c2
82c74ed1 0000 add byte ptr [eax],al

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!NtAlpcQueryInformationMessage+c2

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner

this one happened today

 

[P4or]

Also this is image of BSoD that happened i think 22. i had cellphone in my hand so i managed to capture a shot, but i read few hours ago i can turn off auto restart

 

[Orgie]

All of these bluescreens are different i would say it could be you RAM causing the issues. i would recomend doing a memory dance. Remove all but one and test the system and keep switching it until you see which on is causing it.

long process but thats more likely where you issue is

 

[Orgie]

This is not a HDD issue, you already swapped known good HDD. this is more likely a memory issue.

 

[Paul NZ]

Upload the dmp files somewhere then post the link . Is Mcafee installed? This can cause that 0xd1 stop error. Or what firewall is installed. Wouldnt be surprised, if AVG is causing this. Its crap

The 0x50 stop error tells you the cause vprot.exe. . Uninstall AVG security toolbar

 

[P4or]

Upload the dmp files somewhere then post the link . Is Mcafee installed? This can cause that 0xd1 stop error. Or what firewall is installed. Wouldnt be surprised, if AVG is causing this. Its crap

The 0x50 stop error tells you the cause vprot.exe. . Uninstall AVG security toolbar

well i had no avg installed for some time still i had bsod, mcafee is not installed however...i will upload all dump files on some site and link it here just a sec...

 

[P4or]

All of these bluescreens are different i would say it could be you RAM causing the issues. i would recomend doing a memory dance. Remove all but one and test the system and keep switching it until you see which on is causing it.

long process but thats more likely where you issue is

I will do memory dance and post results in range of 4 or 2 days.

 

[Paul NZ]

Uninstall AVG toolbar then. Then upload the dmp files

 

[P4or]

http://www.filedropper.com/112614-39656-01
http://www.filedropper.com/112414-44171-01
http://www.filedropper.com/112414-32953-01
http://www.filedropper.com/112214-44531-01
http://www.filedropper.com/111914-27203-01
http://www.filedropper.com/111814-32187-01

Here are all dumps i have saved so far..

 

[Paul NZ]

2 are ntfs.sys with a 0x24 stop error. So if the hdd has been replaced, try another SATA cable or another port.

This has something to do with the hdd

Files for AVG are still installed. So if you've uninstalled it use their removal tool to remove the rest of it

This file is old nvm62x32.sys from 2008. See if there are any updates for your Nvidia Ethernet drivers

Your Nvidia SATA drivers are also old / from 2010. See if there are updates. This maybe the cause of this 0x24 stop error

This file L6GX.sys is old / from 2010 see if there are updates for it. I think it belongs to Guitarport or something

The 0x1e stop error maybe caused by AVG

 

[P4or]

2 are ntfs.sys with a 0x24 stop error. So if the hdd has been replaced, try another SATA cable or another port.

This has something to do with the hdd

Files for AVG are still installed. So if you've uninstalled it use their removal tool to remove the rest of it

This file is old nvm62x32.sys from 2008. See if there are any updates for your Nvidia Ethernet drivers

Your Nvidia SATA drivers are also old / from 2010. See if there are updates. This maybe the cause of this 0x24 stop error

This file L6GX.sys is old / from 2010 see if there are updates for it. I think it belongs to Guitarport or something

The 0x1e stop error maybe caused by AVG

I have 2 sata 2 and sata 1 ports/cables i will switch them now..
I uninstalled AVG completely. Also removed all the files.
I also installed complete all in one driver pack for this motherboard, should work..
And i am pretty sure that i downloaded latest driver for this usb guitar amp..

 

[Paul NZ]

Did you use the AVG removal tool?

Well old drivers can crash windows. And that maybe why tcpip.sys and that 0x24 stop error come up

 

[P4or]

Did you use the AVG removal tool?

Well old drivers can crash windows. And that maybe why tcpip.sys and that 0x24 stop error come up

I removed avg completely with removal tool, and tcpip.sys probably has to do with lag reducing registry fix i installed yesterday, that is not causing problems i had that on old pc and it was working fine.