[BSOD] Unexpected Kernel Mode Trap

D

deerrppp

New member
Joined
Aug 1, 2019
Posts
3
Hello everyone, new to this forum, saw this on google while searching for a fix on my problem.

I've been getting this BSOD after installing SSD.

First off, a little background, bought an SSD because I thought my main HDD is dying. This HDD has 3 partitions (C: Windows10, D: Windows7, E: Storage), sometimes I got blue screens after boot, worst is booting takes 30 minutes and then an hour waiting for the startup programs.

So then I installed Windows 10 on the SSD, without the HDD. Everything went fine, now I was thinking I can use my HDD as a storage device, so I plugged it in. Powered the PC and it detected the HDD as a boot device, it increased the bootup time for about 3 minutes (I'm booting on the SSD). Tried to access the HDD files and the disk usage spiked to 100%. I thought the problematic C: partition was the culprit on why the boot time increased even when I'm on SSD and why the HDD is always on 100%, so then I formatted the C: and the D: partition of my HDD, restarted the computer and the boot went great, I also got no high disk usage when browsing and opening files on partition E: of my HDD.
And then the problem starts maybe 3-4 days after, BSOD at random times, max that I got is 3 in a day. Tried to reformat the SSD again thinking maybe it's a software, same thing happened 2 days and BSOD is there again randomly. I also tried to run test on the RAM using memtest and there's no error.

Here's the GDrive link for the minidump generated. I don't know if it's the HDD, SSD, or even the PSU. Hope someone could help me on this one. TIA!
 
The UNEXPECTED_KERNEL_MODE_TRAP bug check has a value of 0x0000007F. This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

This trap could be a bound trap (a trap the kernel is not permitted to catch) or a double fault (a fault that occurred while processing an earlier fault, which always results in a system failure).

1st parameter = 0x8 - 0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:
  • A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
  • A hardware problem.
Code: 
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\080219-6359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*
Symbol search path is: SRV*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`28000000 PsLoadedModuleList = 0xfffff804`284432f0
Debug session time: Thu Aug  1 18:25:49.011 2019 (UTC + 2:00)
System Uptime: 0 days 10:56:03.720
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
0: kd> !analyze
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, fffff8042ac7ee50, fffff30bff925fe0, fffff804282d010b}

*** WARNING: Unable to verify timestamp for networktunnelx64.sys
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+2c5 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8042ac7ee50
Arg3: fffff30bff925fe0
Arg4: fffff804282d010b

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUS

SYSTEM_PRODUCT_NAME:  All Series

SYSTEM_SKU:  All

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2103

BIOS_DATE:  08/19/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  B85-PRO GAMER

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: 8

BUGCHECK_P2: fffff8042ac7ee50

BUGCHECK_P3: fffff30bff925fe0

BUGCHECK_P4: fffff804282d010b

BUGCHECK_STR:  0x7f_8

TRAP_FRAME:  fffff30bff9262b0 -- (.trap 0xfffff30bff9262b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000500 rbx=0000000000000000 rcx=0000000000000500
rdx=fffff30bff926478 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804281c5246 rsp=fffff30bff926448 rbp=fffff30bff9264a0
 r8=fffff30bff926440  r9=00000000000004d0 r10=fffff30bff925000
r11=fffff30bff925000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!_chkstk+0x36:
fffff804`281c5246 45841b          test    byte ptr [r11],r11b ds:fffff30b`ff925000=??
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: c79

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  conhost.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MICHAL

ANALYSIS_SESSION_TIME:  08-02-2019 13:05:05.0536

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

EXCEPTION_RECORD:  ffff808e973a9680 -- (.exr 0xffff808e973a9680)
ExceptionAddress: 0000000000000000
   ExceptionCode: 00000000
  ExceptionFlags: 00000000
NumberParameters: 0

LAST_CONTROL_TRANSFER:  from fffff804281ce6e9 to fffff804281bc900

STACK_OVERFLOW: Stack Limit: fffff30bff926000. Use (kF) and (!stackusage) to investigate stack usage.

STACK_TEXT: 
fffff804`2ac7ed08 fffff804`281ce6e9 : 00000000`0000007f 00000000`00000008 fffff804`2ac7ee50 fffff30b`ff925fe0 : nt!KeBugCheckEx
fffff804`2ac7ed10 fffff804`281c9545 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff804`2ac7ee50 fffff804`282d010b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x2c5
fffff30b`ff925fe0 fffff804`281dfeb0 : fffff30b`ff925000 fffff30b`ff9260a9 00000000`00000000 fffff30b`ff9261d0 : nt!MiGenerateAccessViolation+0x1f
fffff30b`ff926010 fffff804`2807aaef : 72745f52`472c706f 00000000`00000000 00000000`00000000 fffff30b`ff925000 : nt!MiSystemFault+0x1d2ec0
fffff30b`ff926110 fffff804`281ca920 : 69746341`0a0d3030 726f6c6f`435f6576 fffff30b`ff9278a0 72656c41`0a0d3631 : nt!MmAccessFault+0x34f
fffff30b`ff9262b0 fffff804`281c5246 : 00000000`00000000 00000000`0010000b fffff804`280cc81a fffff30b`ff927668 : nt!KiPageFault+0x360
fffff30b`ff926448 fffff804`280cc81a : fffff30b`ff927668 00000000`00000000 2d2d2d2d`00000003 2d2d2d2d`000004d0 : nt!_chkstk+0x36
fffff30b`ff926460 fffff804`2819922f : fffff804`283e5ccc fffff30b`00000001 fffff30b`ff9278a0 fffff30b`ff92c000 : nt!RtlUnwindEx+0xfa
fffff30b`ff926690 fffff804`281c5632 : fffff30b`ff9278a0 fffff30b`ff926c70 00000000`00000000 00000000`0010001f : nt!_C_specific_handler+0xef
fffff30b`ff926700 fffff804`280ca765 : fffff30b`ff927668 00000000`00000000 fffff30b`ff926c70 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
fffff30b`ff926730 fffff804`280cecfe : fffff30b`ff927668 fffff30b`ff9273b0 fffff30b`ff927668 00000000`00000000 : nt!RtlDispatchException+0x4a5
fffff30b`ff926e80 fffff804`281ce81d : ffff808e`973a9680 fffff804`2807caf6 ffffdc6e`371b8000 00007ff5`4f54d000 : nt!KiDispatchException+0x16e
fffff30b`ff927530 fffff804`281caa05 : ffff808e`973a95c0 00000000`000000ff 80000000`00000000 ffffb207`02039a60 : nt!KiExceptionDispatch+0x11d
fffff30b`ff927710 fffff804`28124b2b : ffffdc3f`faa7aa68 ffff808e`973a95c0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x445
fffff30b`ff9278a0 fffff804`280b19a5 : ffffdc3f`faa7aa68 ffffffff`00000018 00000000`00000000 ffffffff`00000420 : nt!MiMakeProtoLeafValid+0xaf
fffff30b`ff927930 fffff804`28654682 : 00007ff5`4f54d000 ffff808e`9a0c3ba0 ffffdd00`00000f00 00000000`00000000 : nt!MiSplitPrivatePage+0x365
fffff30b`ff927a10 fffff804`286542ec : ffff808e`9a0c3bc8 00007ff5`4f54cc00 00000000`00000440 00007ff5`4f54cc00 : nt!MiCopyToCfgBitMap+0x142
fffff30b`ff927ae0 fffff804`286536d8 : ffffdc3f`fca69978 00000000`00000000 00007ff9`4d341000 00000000`00000000 : nt!MiPopulateCfgBitMap+0xbc
fffff30b`ff927b90 fffff804`2861f710 : ffff808e`973a95c0 00000000`00000000 ffff808e`973a9680 fffff804`2802c450 : nt!MiMarkPrivateOpenCfgBits+0x30
fffff30b`ff927bd0 fffff804`2861f5e7 : ffff808e`92c05400 fffff804`2803944d 00000000`00000000 fffff804`28094e86 : nt!MiMarkProcessCfgBits+0x44
fffff30b`ff927c00 fffff804`285d9abf : 00000000`00000002 fffff30b`ff927d01 ffff808e`9a1d4b90 fffff30b`00000000 : nt!MiCommitVadCfgBits+0x16f
fffff30b`ff927c80 fffff804`28655146 : fffff30b`ff927f78 00000000`00000000 fffff30b`00000006 fffff804`00000001 : nt!MiReserveUserMemory+0x42f
fffff30b`ff927d60 fffff804`2864dc26 : 00007ff9`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiAllocateVirtualMemory+0x316
fffff30b`ff927ef0 fffff804`281ce118 : ffffffff`80002884 ffff808e`92c05080 00000000`00000000 fffff30b`ff9282b8 : nt!NtAllocateVirtualMemory+0x196
fffff30b`ff928090 fffff804`281c06c0 : fffff804`32967b76 0000025d`00000000 04c4b258`0462f09c 0c180e4b`ffffffff : nt!KiSystemServiceCopyEnd+0x28
fffff30b`ff928298 fffff804`32967b76 : 0000025d`00000000 04c4b258`0462f09c 0c180e4b`ffffffff 00000000`07070000 : nt!KiServiceLinkage
fffff30b`ff9282a0 0000025d`00000000 : 04c4b258`0462f09c 0c180e4b`ffffffff 00000000`07070000 00000000`00002000 : networktunnelx64+0x7b76
fffff30b`ff9282a8 04c4b258`0462f09c : 0c180e4b`ffffffff 00000000`07070000 00000000`00002000 00000000`00000040 : 0x0000025d`00000000
fffff30b`ff9282b0 0c180e4b`ffffffff : 00000000`07070000 00000000`00002000 00000000`00000040 00000000`00000000 : 0x04c4b258`0462f09c
fffff30b`ff9282b8 00000000`07070000 : 00000000`00002000 00000000`00000040 00000000`00000000 00007ff9`4d33f780 : 0x0c180e4b`ffffffff
fffff30b`ff9282c0 00000000`00002000 : 00000000`00000040 00000000`00000000 00007ff9`4d33f780 00007ff9`4d33f000 : 0x7070000
fffff30b`ff9282c8 00000000`00000040 : 00000000`00000000 00007ff9`4d33f780 00007ff9`4d33f000 00000000`00000000 : 0x2000
fffff30b`ff9282d0 00000000`00000000 : 00007ff9`4d33f780 00007ff9`4d33f000 00000000`00000000 00000000`00000000 : 0x40


THREAD_SHA1_HASH_MOD_FUNC:  b94c30df56f32ef34f1e0d03dfd482880c1c09c3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  83d60c3df1f749cbf47253d5ab6d50facc914569

THREAD_SHA1_HASH_MOD:  763730b0d2ffdf89572a59a73e1e28c3606473f6

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+2c5
fffff804`281c9545 90              nop

FAULT_INSTR_CODE:  6666c390

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+2c5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  3ed0f42

IMAGE_VERSION:  10.0.18362.239

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2c5

FAILURE_BUCKET_ID:  0x7f_8_nt!KiDoubleFaultAbort

BUCKET_ID:  0x7f_8_nt!KiDoubleFaultAbort

PRIMARY_PROBLEM_CLASS:  0x7f_8_nt!KiDoubleFaultAbort

TARGET_TIME:  2019-08-01T16:25:49.000Z

OSBUILD:  18362

OSSERVICEPACK:  239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  1972-02-02 09:33:06

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  690e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_nt!kidoublefaultabort

FAILURE_ID_HASH:  {d1f8395a-8c58-45da-6ebf-e8bb4aad2fc5}

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

0: kd> .load pde
=========================================================================================
 PDE v11.3 - Copyright 2017 Andrew Richards
=========================================================================================
0: kd> !dpx
Failed to read base and/or limit
0: kd> kF
 #   Memory  Child-SP          RetAddr           Call Site
00           fffff804`2ac7ed08 fffff804`281ce6e9 nt!KeBugCheckEx
01         8 fffff804`2ac7ed10 fffff804`281c9545 nt!KiBugCheckDispatch+0x69
02       140 fffff804`2ac7ee50 fffff804`282d010b nt!KiDoubleFaultAbort+0x2c5
03           fffff30b`ff925fe0 fffff804`281dfeb0 nt!MiGenerateAccessViolation+0x1f
04        30 fffff30b`ff926010 fffff804`2807aaef nt!MiSystemFault+0x1d2ec0
05       100 fffff30b`ff926110 fffff804`281ca920 nt!MmAccessFault+0x34f
06       1a0 fffff30b`ff9262b0 fffff804`281c5246 nt!KiPageFault+0x360
07       198 fffff30b`ff926448 fffff804`280cc81a nt!_chkstk+0x36
08        18 fffff30b`ff926460 fffff804`2819922f nt!RtlUnwindEx+0xfa
09       230 fffff30b`ff926690 fffff804`281c5632 nt!_C_specific_handler+0xef
0a        70 fffff30b`ff926700 fffff804`280ca765 nt!RtlpExecuteHandlerForException+0x12
0b        30 fffff30b`ff926730 fffff804`280cecfe nt!RtlDispatchException+0x4a5
0c       750 fffff30b`ff926e80 fffff804`281ce81d nt!KiDispatchException+0x16e
0d       6b0 fffff30b`ff927530 fffff804`281caa05 nt!KiExceptionDispatch+0x11d
0e       1e0 fffff30b`ff927710 fffff804`28124b2b nt!KiPageFault+0x445
0f       190 fffff30b`ff9278a0 fffff804`280b19a5 nt!MiMakeProtoLeafValid+0xaf
10        90 fffff30b`ff927930 fffff804`28654682 nt!MiSplitPrivatePage+0x365
11        e0 fffff30b`ff927a10 fffff804`286542ec nt!MiCopyToCfgBitMap+0x142
12        d0 fffff30b`ff927ae0 fffff804`286536d8 nt!MiPopulateCfgBitMap+0xbc
13        b0 fffff30b`ff927b90 fffff804`2861f710 nt!MiMarkPrivateOpenCfgBits+0x30
14        40 fffff30b`ff927bd0 fffff804`2861f5e7 nt!MiMarkProcessCfgBits+0x44
15        30 fffff30b`ff927c00 fffff804`285d9abf nt!MiCommitVadCfgBits+0x16f
16        80 fffff30b`ff927c80 fffff804`28655146 nt!MiReserveUserMemory+0x42f
17        e0 fffff30b`ff927d60 fffff804`2864dc26 nt!MiAllocateVirtualMemory+0x316
18       190 fffff30b`ff927ef0 fffff804`281ce118 nt!NtAllocateVirtualMemory+0x196
19       1a0 fffff30b`ff928090 fffff804`281c06c0 nt!KiSystemServiceCopyEnd+0x28
*** WARNING: Unable to verify timestamp for networktunnelx64.sys
1a       208 fffff30b`ff928298 fffff804`32967b76 nt!KiServiceLinkage
1b         8 fffff30b`ff9282a0 0000025d`00000000 networktunnelx64+0x7b76
1c         8 fffff30b`ff9282a8 04c4b258`0462f09c 0x0000025d`00000000
1d         8 fffff30b`ff9282b0 0c180e4b`ffffffff 0x04c4b258`0462f09c
1e         8 fffff30b`ff9282b8 00000000`07070000 0x0c180e4b`ffffffff
1f         8 fffff30b`ff9282c0 00000000`00002000 0x7070000
20         8 fffff30b`ff9282c8 00000000`00000040 0x2000
21         8 fffff30b`ff9282d0 00000000`00000000 0x40
0: kd> !stackusage
Stack Usage By Function
=================================================================================

      Size     Count  Module
0x00000750         1  nt!RtlDispatchException
0x000006B0         1  nt!KiDispatchException
0x00000230         1  nt!RtlUnwindEx
0x00000208         1  nt!KiSystemServiceCopyEnd
0x000001E0         1  nt!KiExceptionDispatch
0x000001A0         1  nt!MmAccessFault
0x000001A0         1  nt!NtAllocateVirtualMemory
0x00000198         1  nt!KiPageFault
0x00000190         1  nt!KiPageFault
0x00000190         1  nt!MiAllocateVirtualMemory
0x00000140         1  nt!KiBugCheckDispatch
0x00000100         1  nt!MiSystemFault
0x000000E0         1  nt!MiSplitPrivatePage
0x000000E0         1  nt!MiReserveUserMemory
0x000000D0         1  nt!MiCopyToCfgBitMap
0x000000B0         1  nt!MiPopulateCfgBitMap
0x00000090         1  nt!MiMakeProtoLeafValid
0x00000080         1  nt!MiCommitVadCfgBits
0x00000070         1  nt!_C_specific_handler
0x00000040         1  nt!MiMarkPrivateOpenCfgBits
0x00000030         1  nt!RtlpExecuteHandlerForException
0x00000030         1  nt!MiGenerateAccessViolation
0x00000030         1  nt!MiMarkProcessCfgBits
0x00000018         1  nt!_chkstk
0x00000008         2  nt!KeBugCheckEx
0x00000008         1  nt!KiServiceLinkage
0x00000008         1  networktunnelx64

Total Size: 0x00002410


Stack Usage By Module
=================================================================================

      Size     Count  Module
0x00002408        27  nt
0x00000008         1  networktunnelx64

Total Size: 0x00002410
0: kd> lmvm networktunnelx64
Browse full module list
start             end                 module name
fffff804`32960000 fffff804`32974000   networktunnelx64 T (no symbols)           
    Loaded symbol image file: networktunnelx64.sys
    Image path: \??\C:\Program Files (x86)\Pingzapper\Engine\networktunnelx64.sys
    Image name: networktunnelx64.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Jul 13 04:40:04 2017 (59675C14)
    CheckSum:         0001418A
    ImageSize:        00014000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
You are at fault with the networktunnelx64.sys driver. It is a driver used by various network programs, and you use it with the Pingzipper program. Looking at the fact that this program has not been updated for 2 years (Pingzapper — Download), one can presume that it has obtained EOL (End of Life) support status, which is why I suggest you uninstall the program and look around for an alternative
 
Thank goodness it was not a hardware fault.
But I've been using it since Windows 7 and Windows 10 build 1803, right now I'm on build 1903..
I'll test it out without using Pingzapper and see if it will have blue screen. Thank you very much!
 
Searched "pingzapper blue screen" and a bunch of users has had this problem too. One person pointed out that he/she had blue screen starting from build 1809. Thanks again for clearing things up :)
 
Also - go to the SSD manufacturer and check for a firmware upgrade.

Regards. . .

jcgriff2
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top