Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Screens and Windows crashes when using Anti-Virus , Spyware programs. NEED HELP.


  • Please log in to reply
1 reply to this topic

#1 Gthomas18

Gthomas18

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:24 AM

Posted 16 December 2012 - 04:31 PM

I need help from u guys please, I am running Windows XP in a Dell XPS410 Desktop and my problem started when using my Norton Anti-Virus,Anti-Malware and Superantispyware programs. When i run these programs in 15 to 20 min blue screen pops up saying about some problems it detected. I've tried to restore the system to a past date but it didn't resolve the problem. Now I followed all the steps in this post found the dump files and download the debugger . But before all these thing happened, 2 months ago i installed GeForce GT 430 graphics card in my computer system. And a week later a blue screen poped up saying cannot find the awaymode. Any suggestion is welcome.
Thanks


im really looking for some help which im sure members here are more capable of... I did the dump analysis and thought of posting it here hoping someone might want to have a look at it and come up with an advise...


Date 12/15/12


Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini121512-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120821-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Dec 15 10:38:35.875 2012 (GMT-6)
System Uptime: 1 days 23:17:27.613
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 0, 0, b143cc34}

Probably caused by : memory_corruption ( nt!MmInPageKernelStack+176 )

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

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

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 00000000, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: b143cc34, address of signature on kernel stack

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


ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

BUGCHECK_STR: 0x77_1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80512e9c to 804f9f9f

STACK_TEXT:
b8573d58 80512e9c 00000077 00000001 00000000 nt!KeBugCheckEx+0x1b
b8573d8c 8053fe2e 00441020 00000000 8aae93a0 nt!MmInPageKernelStack+0x176
b8573da4 805402fe 89441080 805cffbe 00000000 nt!KiInSwapKernelStacks+0x16
b8573dac 805cffbe 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
b8573ddc 805461ae 80540282 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmInPageKernelStack+176
80512e9c 8a550b mov dl,byte ptr [ebp+0Bh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmInPageKernelStack+176

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 503385d0

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+176

BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+176

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








DATE 12/13/12

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini121312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120821-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Dec 13 02:12:53.281 2012 (GMT-6)
System Uptime: 0 days 16:37:00.023
Loading Kernel Symbols
...............................................................
....................................................
Loading User Symbols
Loading unloaded module list
....................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 0, 0, b8513d24}

Probably caused by : memory_corruption ( nt!MmInPageKernelStack+176 )

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

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

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 00000000, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: b8513d24, address of signature on kernel stack

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


ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1

BUGCHECK_STR: 0x77_1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80512e9c to 804f9f9f

STACK_TEXT:
b8573d58 80512e9c 00000077 00000001 00000000 nt!KeBugCheckEx+0x1b
b8573d8c 8053fe2e 00af38a0 00000000 8aae93a0 nt!MmInPageKernelStack+0x176
b8573da4 805402fe 8aaf3900 805cffbe 00000000 nt!KiInSwapKernelStacks+0x16
b8573dac 805cffbe 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
b8573ddc 805461ae 80540282 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmInPageKernelStack+176
80512e9c 8a550b mov dl,byte ptr [ebp+0Bh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmInPageKernelStack+176

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 503385d0

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+176

BUCKET_ID: 0x77_1_nt!MmInPageKernelStack+176

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





DATE 12/09/12 01


Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini120912-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120821-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Dec 9 13:01:59.812 2012 (GMT-6)
System Uptime: 0 days 0:14:02.558
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {e1ca4938, c00000b5, bf91eac1, 4ff54860}

Probably caused by : win32k.sys ( win32k!IdleTimerProc+a1 )

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

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: e1ca4938, lock type that was held (value 1,2,3, or PTE address)
Arg2: c00000b5, error status (normally i/o status code)
Arg3: bf91eac1, current process (virtual address for lock type 3, or PTE)
Arg4: 4ff54860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc00000b5 - {Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.

BUGCHECK_STR: 0x7a_c00000b5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: csrss.exe

TRAP_FRAME: b186ea0c -- (.trap 0xffffffffb186ea0c)
ErrCode = 00000010
eax=00000001 ebx=00000032 ecx=b9e6d398 edx=00000bcd esi=e1b684c8 edi=00000112
eip=bf91eac1 esp=b186ea80 ebp=b186eaa4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!StartScreenSaver:
bf91eac1 8bff mov edi,edi
Resetting default scope

LAST_CONTROL_TRANSFER: from 80515bf6 to 804f9f9f

STACK_TEXT:
b186e8d8 80515bf6 0000007a e1ca4938 c00000b5 nt!KeBugCheckEx+0x1b
b186e908 80516763 81f04d30 e1ca4938 bf91eac1 nt!MiWaitForInPageComplete+0x1ca
b186e988 805202bd e1ca4938 bf91eac1 c05fc8f0 nt!MiDispatchFault+0x2c1
b186e9f4 80544640 00000008 bf91eac1 00000000 nt!MmAccessFault+0x877
b186e9f4 bf91eac1 00000008 bf91eac1 00000000 nt!KiTrap0E+0xd0
b186ea7c bf80151e 00000000 0000001f bf801309 win32k!StartScreenSaver
b186ea88 bf801309 0000001f 00000001 00000000 win32k!IdleTimerProc+0xa1
b186eaa4 bf80128c 00000000 00000118 00007ffd win32k!xxxHungAppDemon+0xe
b186ead4 bf882d8d 00000022 006efff4 bf8010aa win32k!TimersProc+0xad
b186ed30 bf8b8afc b187e490 00000002 b186ed54 win32k!RawInputThread+0x634
b186ed40 bf8010cd b187e490 b186ed64 006efff4 win32k!xxxCreateSystemThreads+0x60
b186ed54 805416cc 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
b186ed54 7c90e514 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!IdleTimerProc+a1
bf80151e e926ffffff jmp win32k!IdleTimerProc+0xa1 (bf801449)

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: win32k!IdleTimerProc+a1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 508505c1

FAILURE_BUCKET_ID: 0x7a_c00000b5_win32k!IdleTimerProc+a1

BUCKET_ID: 0x7a_c00000b5_win32k!IdleTimerProc+a1

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





DATE 12/09/12 -02



Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini120912-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120821-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Dec 9 21:19:56.359 2012 (GMT-6)
System Uptime: 0 days 5:51:22.120
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {c00000b5, c00000b5, 0, 6b53000}

Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+4f5 )

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

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

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: c00000b5, status code
Arg2: c00000b5, i/o status code
Arg3: 00000000, page file number
Arg4: 06b53000, offset into page file

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


ERROR_CODE: (NTSTATUS) 0xc00000b5 - {Device Timeout} The specified I/O operation on %hs was not completed before the time-out period expired.

BUGCHECK_STR: 0x77_c00000b5

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 80511ffd to 804f9f9f

STACK_TEXT:
b8573cdc 80511ffd 00000077 c00000b5 c00000b5 nt!KeBugCheckEx+0x1b
b8573d50 80512e6f c056d638 000734fa 00000001 nt!MiMakeOutswappedPageResident+0x4f5
b8573d8c 8053fe2e 00df3bd8 00000000 8aae9300 nt!MmInPageKernelStack+0x149
b8573da4 805402fe 89df3c38 805cffbe 00000000 nt!KiInSwapKernelStacks+0x16
b8573dac 805cffbe 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
b8573ddc 805461ae 80540282 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiMakeOutswappedPageResident+4f5
80511ffd cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiMakeOutswappedPageResident+4f5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 503385d0

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x77_c00000b5_nt!MiMakeOutswappedPageResident+4f5

BUCKET_ID: 0x77_c00000b5_nt!MiMakeOutswappedPageResident+4f5

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







DATE 12/02/12


Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini120212-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.120821-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Dec 2 03:44:04.125 2012 (GMT-6)
System Uptime: 1 days 7:35:40.140
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf9569a9, 9a30dc00, 0}

Probably caused by : win32k.sys ( win32k!GreGetGlyphIndicesW+af )

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

1: kd> !analyze -v
*******************************************************************************
* *
* 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: bf9569a9, The address that the exception occurred at
Arg3: 9a30dc00, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP:
win32k!GreGetGlyphIndicesW+af
bf9569a9 8b4004 mov eax,dword ptr [eax+4]

TRAP_FRAME: 9a30dc00 -- (.trap 0xffffffff9a30dc00)
ErrCode = 00000000
eax=00000000 ebx=00000100 ecx=00000000 edx=00000000 esi=e21e5000 edi=e80cf008
eip=bf9569a9 esp=9a30dc74 ebp=9a30dc8c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!GreGetGlyphIndicesW+0xaf:
bf9569a9 8b4004 mov eax,dword ptr [eax+4] ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: chrome.exe

LAST_CONTROL_TRANSFER: from bf94e036 to bf9569a9

STACK_TEXT:
9a30dc8c bf94e036 e38aa7c0 e21e5200 e798a558 win32k!GreGetGlyphIndicesW+0xaf
9a30dd28 bf94e0b2 e5010c17 0012df30 00000100 win32k!NtGdiGetGlyphIndicesWInternal+0xf2
9a30dd48 805416cc e5010c17 0012df30 00000100 win32k!NtGdiGetGlyphIndicesW+0x1b
9a30dd48 7c90e514 e5010c17 0012df30 00000100 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012dea0 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!GreGetGlyphIndicesW+af
bf9569a9 8b4004 mov eax,dword ptr [eax+4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!GreGetGlyphIndicesW+af

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 508505c1

FAILURE_BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af

BUCKET_ID: 0x8E_win32k!GreGetGlyphIndicesW+af

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


*Moderator Edit: Moved topic from Applications and Guides> Microsoft Windows Mini-Guides
to the more appropriate forum. ~ Queen-Evie*

Edited by Queen-Evie, 17 December 2012 - 04:33 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,565 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:10:24 AM

Posted 17 December 2012 - 07:59 PM

Please download MiniToolBox , save it to your desktop and run it.

Checkmark the following checkboxes:
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size.

Click Go and paste the content into your next post.

Also...please Publish a Snapshot using Speccy - http://www.bleepingcomputer.com/forums/topic323892.html/page__p__1797792#entry1797792 .

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users