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.

Latest News:    Xbash Malware Deletes Databases on Linux, Mines for Coins on Windows

Featured Deal: Get 98% off the 2018 CompTIA Certification Training Bundle: Lifetime Access Deal

Photo

Dump while Hyper-V workout

Started by Suncatcher , Mar 13 2018 11:05 AM

  • Please log in to reply
5 replies to this topic

#1 Suncatcher

Suncatcher

  • Members
  • 48 posts
  • OFFLINE
    •  
  • Local time:03:25 AM

Posted 13 March 2018 - 11:05 AM

HI,

 

  · System Manufacturer: Dell
  · Inspiron 7559
  · Windows 10 Pro 16299.248
  · x64 (64-bit)?
  · Win 10 Home
  · OEM upgraded to Pro
  · 3 years
  · Age of OS installation 1 month
 
  · Laptop 
   · CPU Core i5 i6300HQ
   · Video Card Intel HD 530 & Geforce GTX 960M
 
Here is what WinDbg says about memory dump file
 

Microsoft ® Windows Debugger Version 10.0.16299.91 AMD64

Copyright © Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\aws\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
 
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff802`e2683000 PsLoadedModuleList = 0xfffff802`e29ea110
Debug session time: Tue Mar 13 16:29:09.539 2018 (UTC + 2:00)
System Uptime: 0 days 6:36:33.812
Loading Kernel Symbols
...............................................................
.........Page 120ac4 not present in the dump file. Type ".hh dbgerr004" for details
.......................................................
................................................................
..............................
Loading User Symbols
 
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 133, {1, 1e00, fffff802e2a80370, 0}
 
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+f2583 )
 
Followup:     MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff802e2a80370, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
 
Debugging Details:
------------------
 
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 401
 
BUILD_VERSION_STRING:  16299.15.amd64fre.rs3_release.170928-1534
 
SYSTEM_MANUFACTURER:  Dell Inc.
 
SYSTEM_PRODUCT_NAME:  Inspiron 7559
 
SYSTEM_SKU:  0706
 
SYSTEM_VERSION:  1.2.5
 
BIOS_VENDOR:  Dell Inc.
 
BIOS_VERSION:  1.2.5
 
BIOS_DATE:  09/26/2017
 
BASEBOARD_MANUFACTURER:  Dell Inc.
 
BASEBOARD_PRODUCT:  0H87XC
 
BASEBOARD_VERSION:  A00
 
DUMP_TYPE:  1
 
BUGCHECK_P1: 1
 
BUGCHECK_P2: 1e00
 
BUGCHECK_P3: fffff802e2a80370
 
BUGCHECK_P4: 0
 
DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
 
CPU_COUNT: 4
 
CPU_MHZ: 900
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 5e
 
CPU_STEPPING: 3
 
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: BA'00000000 (cache) BA'00000000 (init)
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  0x133
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  d
 
ANALYSIS_SESSION_HOST:  XXXXXXX
 
ANALYSIS_SESSION_TIME:  03-13-2018 17:46:03.0748
 
ANALYSIS_VERSION: 10.0.16299.91 amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff802e283eab3 to fffff802e27f8430
 
STACK_TEXT:  
fffff802`e32839b8 fffff802`e283eab3 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`e2a80370 : nt!KeBugCheckEx
fffff802`e32839c0 fffff802`e274a1b8 : 000031e6`96d52564 fffff802`e0f59180 00000000`00173c74 00000000`00000000 : nt!KeAccumulateTicks+0xf2583
fffff802`e3283a20 fffff802`e26074c6 : 000031e6`96d4c880 00000000`00000000 fffff802`e3283df0 00000000`00000001 : nt!KeClockInterruptNotify+0x5f8
fffff802`e3283d30 fffff802`e27178c5 : fffff802`e265a550 fffff802`e2737232 ffffc08d`30384040 fffff802`e27371f5 : hal!HalpTimerClockInterrupt+0x56
fffff802`e3283d60 fffff802`e27f9d1a : fffff802`e3283e70 fffff802`e265a550 00000000`00000000 ffffc08d`2c574c00 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`e3283da0 fffff802`e27fa227 : ffffc08d`3168600e 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff802`e3283df0 fffff802`e27f98a9 : ffffd181`611aea00 ffffd181`611aea00 ffffc08d`352e4030 ffffc08d`2c574c00 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`e3283f80 fffff802`e27f95b7 : ffffc08d`352e4030 00000000`00000000 00000001`ffffffff fffffff6`00000002 : nt!KiScanInterruptObjectList+0xc9
ffffbf8c`01e966b0 fffff80d`419b535e : 00000000`00000000 00000000`00000000 ffffc08d`2fc40700 00000000`00000000 : nt!KiChainedDispatch+0x37
ffffbf8c`01e96840 fffff80d`419c1ae3 : 00000000`00000000 ffffc08d`2c98dc60 ffffc08d`00000000 00000000`0000000a : ndis!ndisMIndicateNetBufferListsToOpen+0x104ee
ffffbf8c`01e96910 fffff80d`419a5583 : ffffc08d`2c4301a0 ffffbf8c`01e96b01 fffff80d`419a4a50 ffffbf8c`01e96b60 : ndis!ndisMTopReceiveNetBufferLists+0x1d093
ffffbf8c`01e96a10 fffff80d`419a498e : 00000000`00002381 ffffc08d`2c4301a0 ffffc08d`2fc404a0 00000000`00000000 : ndis!ndisCallReceiveHandler+0x43
ffffbf8c`01e96a60 fffff80d`43fb1a3e : 00000000`00000000 00000000`00000000 ffffbf8c`01e96c60 00006894`9c7bc310 : ndis!NdisMIndicateReceiveNetBufferLists+0x5ae
ffffbf8c`01e96bd0 fffff80d`43fb160b : ffffc08d`2d7fb000 ffffc08d`2fc404a0 00000000`00000000 00000000`cf639600 : vmswitch!VmsExtMpIndicatePackets+0x16e
ffffbf8c`01e96ca0 fffff80d`419a6468 : 00000000`00000000 00000000`00000000 ffffc08d`2c658f02 00000000`00000000 : vmswitch!VmsExtMpSendNetBufferLists+0x2fb
ffffbf8c`01e96e80 fffff80d`419a310b : ffffc08d`2c430100 ffffc08d`2fc404a0 00000000`00000000 ffffbf8c`01e96ff9 : ndis!ndisMSendNBLToMiniportInternal+0x108
ffffbf8c`01e96f40 fffff80d`43fa6e30 : ffffc08d`2c574c00 ffffc08d`2fc404a0 ffffc08d`00000000 ffffc08d`00000021 : ndis!NdisSendNetBufferLists+0x33b
ffffbf8c`01e970a0 fffff80d`43fa4878 : ffffc08d`2d7fb000 ffffc08d`2c9a0001 ffffc08d`2c7f7900 00000000`0000000a : vmswitch!VmsExtPtRouteNetBufferLists+0x460
ffffbf8c`01e97170 fffff80d`419a4fae : 00000000`00000001 00000000`00000001 00000000`00000001 ffffbf8c`01e97510 : vmswitch!VmsPtNicReceiveNetBufferLists+0x18a8
ffffbf8c`01e973a0 fffff80d`419a4c12 : ffffc08d`2c9a6001 00000000`00000000 00000000`00000000 00000000`0000000a : ndis!ndisMIndicateNetBufferListsToOpen+0x13e
ffffbf8c`01e97470 fffff80d`419a5583 : ffffc08d`2c7b41a0 ffff0000`00009401 fffff80d`419a4a50 fffffff6`00000002 : ndis!ndisMTopReceiveNetBufferLists+0x1c2
ffffbf8c`01e97570 fffff80d`419a498e : 00000000`00000000 fffff802`e26066fd fffff7ae`40001ec8 00000000`0000002f : ndis!ndisCallReceiveHandler+0x43
ffffbf8c`01e975c0 fffff80d`48a93c8c : ffffc08d`2c97e000 00000000`00000000 00000000`00000200 ffffc08d`2f4e4030 : ndis!NdisMIndicateReceiveNetBufferLists+0x5ae
ffffbf8c`01e97730 fffff80d`48a819f6 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : rt640x64!MpHandleRecvIntPriVLanJumbo+0xb24
ffffbf8c`01e97920 fffff80d`419c384c : 815f067f`0000000a 00000000`00000000 ba0d1556`0865015d dc050045`00082c20 : rt640x64!MPHandleInterrupt+0x366
ffffbf8c`01e97990 fffff80d`419b2534 : ffffc08d`2b084900 00000000`00000000 ffffc08d`2d795848 00000000`00000000 : ndis!ndisQueuedMiniportDpcWorkItem+0x1ae0c
ffffbf8c`01e97ac0 fffff802`e2799b87 : ffffc08d`2bee4040 ffffc08d`2bee4040 fffff80d`419b23d0 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x164
ffffbf8c`01e97b90 fffff802`e27ffbe6 : fffff802`e0f59180 ffffc08d`2bee4040 fffff802`e2799b40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffbf8c`01e97be0 00000000`00000000 : ffffbf8c`01e98000 ffffbf8c`01e91000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
THREAD_SHA1_HASH_MOD_FUNC:  17963406c2e4a27d6b0bf0ea37b18f7ebce25cde
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  85046a51deaf129158f50fb493aa68c7aa312448
 
THREAD_SHA1_HASH_MOD:  2b40ad853785a6d9d4878ba4ec8e79420cf57766
 
FOLLOWUP_IP: 
nt!KeAccumulateTicks+f2583
fffff802`e283eab3 cc              int     3
 
FAULT_INSTR_CODE:  ab3944cc
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt!KeAccumulateTicks+f2583
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  5a7e7659
 
STACK_COMMAND:  .thread ; .cxr ; kb
 
BUCKET_ID_FUNC_OFFSET:  f2583
 
FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks
 
BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks
 
PRIMARY_PROBLEM_CLASS:  0x133_ISR_nt!KeAccumulateTicks
 
TARGET_TIME:  2018-03-13T14:29:09.000Z
 
OSBUILD:  16299
 
OSSERVICEPACK:  0
 
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:  2018-02-10 06:34:33
 
BUILDDATESTAMP_STR:  170928-1534
 
BUILDLAB_STR:  rs3_release
 
BUILDOSVER_STR:  10.0.16299.15.amd64fre.rs3_release.170928-1534
 
ANALYSIS_SESSION_ELAPSED_TIME:  17fd
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x133_isr_nt!keaccumulateticks
 
FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
 
Followup:     MachineOwner
---------

 

I was running Clonezilla in guest Hyper-V machine, and was constructing saved Clonezilla image located in LAN samba share (to remote img file).

 

Also, together with dump I had such error

 

MlzBgLT.png

Attached Files


Edited by Suncatcher, 13 March 2018 - 11:09 AM.

BC AdBot (Login to Remove)

 

#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
    •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:08:25 PM

Posted 13 March 2018 - 10:13 PM 

0: kd> !analyze -show 133 1 1e00 fffff802e2a80370 0
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff802e2a80370
Arg4: 0000000000000000
0: kd> k
 # Child-SP          RetAddr           Call Site
00 fffff802`e32839b8 fffff802`e283eab3 nt!KeBugCheckEx
01 fffff802`e32839c0 fffff802`e274a1b8 nt!KeAccumulateTicks+0xf2583
02 fffff802`e3283a20 fffff802`e26074c6 nt!KeClockInterruptNotify+0x5f8
03 fffff802`e3283d30 fffff802`e27178c5 hal!HalpTimerClockInterrupt+0x56
04 fffff802`e3283d60 fffff802`e27f9d1a nt!KiCallInterruptServiceRoutine+0xa5
05 fffff802`e3283da0 fffff802`e27fa227 nt!KiInterruptSubDispatchNoLockNoEtw+0xea
06 fffff802`e3283df0 fffff802`e27f98a9 nt!KiInterruptDispatchNoLockNoEtw+0x37
07 fffff802`e3283f80 fffff802`e27f95b7 nt!KiScanInterruptObjectList+0xc9
08 ffffbf8c`01e966b0 fffff80d`419b535e nt!KiChainedDispatch+0x37
09 ffffbf8c`01e96840 fffff80d`419c1ae3 ndis!ndisMIndicateNetBufferListsToOpen+0x104ee
0a ffffbf8c`01e96910 fffff80d`419a5583 ndis!ndisMTopReceiveNetBufferLists+0x1d093
0b ffffbf8c`01e96a10 fffff80d`419a498e ndis!ndisCallReceiveHandler+0x43
0c ffffbf8c`01e96a60 fffff80d`43fb1a3e ndis!NdisMIndicateReceiveNetBufferLists+0x5ae
0d ffffbf8c`01e96bd0 fffff80d`43fb160b vmswitch!VmsExtMpIndicatePackets+0x16e
0e ffffbf8c`01e96ca0 fffff80d`419a6468 vmswitch!VmsExtMpSendNetBufferLists+0x2fb
0f ffffbf8c`01e96e80 fffff80d`419a310b ndis!ndisMSendNBLToMiniportInternal+0x108
10 ffffbf8c`01e96f40 fffff80d`43fa6e30 ndis!NdisSendNetBufferLists+0x33b
11 ffffbf8c`01e970a0 fffff80d`43fa4878 vmswitch!VmsExtPtRouteNetBufferLists+0x460
12 ffffbf8c`01e97170 fffff80d`419a4fae vmswitch!VmsPtNicReceiveNetBufferLists+0x18a8
13 ffffbf8c`01e973a0 fffff80d`419a4c12 ndis!ndisMIndicateNetBufferListsToOpen+0x13e
14 ffffbf8c`01e97470 fffff80d`419a5583 ndis!ndisMTopReceiveNetBufferLists+0x1c2
15 ffffbf8c`01e97570 fffff80d`419a498e ndis!ndisCallReceiveHandler+0x43
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
16 ffffbf8c`01e975c0 fffff80d`48a93c8c ndis!NdisMIndicateReceiveNetBufferLists+0x5ae
17 ffffbf8c`01e97730 ffffc08d`2c97e000 rt640x64+0x13c8c
18 ffffbf8c`01e97738 00000000`00000000 0xffffc08d`2c97e000
0: kd> lm k vm rt640x64
Browse full module list
start             end                 module name
fffff80d`48a80000 fffff80d`48b18000   rt640x64 T (no symbols)           
    Loaded symbol image file: rt640x64.sys
    Image path: \SystemRoot\System32\drivers\rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Oct 05 09:32:55 2016 (57F50107)
    CheckSum:         00096635
    ImageSize:        00098000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Try the obvious and reinstall your Realtek PCIe GBE Family Controller driver. Do remember that I am working with only one dump; I prefer a handful for more informed suggestions.

Can you send me the Live Kernel Event dump file? I'm curious if there's any info to peruse. Instructions:

• Press and hold the Windows Key + R on your keyboard at the same time.
• Type in %WinDir%\LiveKernelReports and hit Enter on your keyboard.
• If prompted to take permissions of that folder, please do so.
• Copy/paste the entire contents of that folder to your Desktop.
• Zip up (use .ZIP!!!) those files and attach them in your next reply.

 

The crashes only occur during your "Hyper-V workout?"
 


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)

#3 Suncatcher

Suncatcher
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
    •  
  • Local time:03:25 AM

Posted 08 April 2018 - 11:21 AM

The crashes only occur during your "Hyper-V workout?"

 

Yes. Here is the ZIP of LiveKernelReports folder (caution! 2Gb in size!)

Could you please also elaborate another, more recent, LiveKernelEvent error?

 

Attached File  Sketch3.png   267.23KB   0 downloads

 

It has another code, 164, but probably is related to previous one. I put both into the archive and uploaded to cloud.


Edited by Suncatcher, 08 April 2018 - 11:32 AM.

#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
    •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:08:25 PM

Posted 09 April 2018 - 06:04 PM

Have the BSODs stopped? I can't get the dump files to download; Google is very slow.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)

#5 Suncatcher

Suncatcher
  • Topic Starter

  • Members
  • 48 posts
  • OFFLINE
    •  
  • Local time:03:25 AM

Posted 10 April 2018 - 12:59 AM

Have the BSODs stopped? I can't get the dump files to download; Google is very slow.

 

Since 6.04 there haven't been any. Will observe later.

I updated the Ethernet driver according to your your first recommendation.


#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,027 posts
  • OFFLINE
    •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:08:25 PM

Posted 10 April 2018 - 12:25 PM

Great, let us know how everything goes!


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)

Back to Windows Crashes and Blue Screen of Death (BSOD) Help and Support


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users


  1. BleepingComputer.com
  2. → Microsoft Windows Support
  3. → Windows Crashes and Blue Screen of Death (BSOD) Help and Support
  4. Privacy Policy
  5. Rules ·