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

BSOD Crazy


  • Please log in to reply
20 replies to this topic

#1 BBrown1999

BBrown1999

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 09 September 2014 - 03:36 PM

my apologies in advance for the length of this post. In July of 2013, I purchased a Dell M4700 Workstation for video editing purposes...and have had problems since. Even though it is still under the warranty(3 years), Dell has yet to really fix the machine. Here are some specs:

-3rd Gen Intel Core i7 374OQM
-Ultra Sharp FHD 1920x1080 15.6”
-Nvidia Quadro K2000M 2GB(in addition to a more standard graphics card)
-Windows 7
-No Raid
-750GB 7200rpm HDD
-Dell Wireless 1540 802
-16GB DDR3-1600 SDRAM 2 DIMM

The issues have mostly been BSODs and occasional random shut offs. I have yet to determine a cause for the errors. Sometimes they occur during a light workload, and others happen during a heavy edit sessions. I've had 3-4 in a few hours, but usually just 2-4 BSODs a month at random. Many repeat. 

0xBE
0xD1
0x4E
0x01
0x7E
0x50
0x0A
0x1E
0x3B
0xC2

Through the advisement of Dell... I re-installed Windows 7 and drivers, which did not seem to help. After having multiple online techs re-install my Nvida drivers, they opted to have a Tech visit my home and replace the motherboard, graphics card and all 16GBs of memory...still problems. Another online tech re-installed my BIOS and Nvida drivers...somewhat worked..but now my computer has massive start-up delays. Dell thinks it is the hard drive going bad and will send my a new one shortly. If the hard drive is indeed dying, I think it's due to the random shut-off caused by all the BSODs.

I ran a few different diagnostics (before and after the new hardware installs), which never indicate a hardware issue. There has never been an indication that I need to install drivers from my Device Manager, although some driver re-installs seem to delay the next BSOD. My Event Viewer is chalked full of errors. Virus scans show nothing is wrong. 

Dell has a third party System Checkup diagnostic on their site. It was the only scan to indicate I may have problems...3787 registry irregularities and corruption in the hard drive. It's a pay to fix system, so I wasn't sure if it's trustworthy.  

My gut tells me it's a simple fix, but frustration is mounting. I would bet on Drivers, the OS and corruption...but I can't say I'm that knowledgeable in computers. I do run some heavy software like After Effects and Premiere with 3rd party plug-ins, but I have yet to have an error ID a program. 

The biggest concern is losing the video files I work on. Although I keep my projects stored on external devices, I'm a bit leery that too many random shut offs could damage my work. It's a more of a question of when, not if there will be another BSOD or additional error. 

Thank you kindly for the help.



BC AdBot (Login to Remove)

 


m

#2 Allan

Allan

  • BC Advisor
  • 8,465 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:59 PM

Posted 09 September 2014 - 04:09 PM

Download BlueScreenView:

http://www.nirsoft.net/utils/blue_screen_view.html

unzip downloaded file and double click on BlueScreenView.exe to run the program.

when scanning is done, go to EDIT - Select All

Go to FILE - SAVE Selected Items, and save the report as BSOD.txt

Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply



#3 BBrown1999

BBrown1999
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 09 September 2014 - 04:14 PM

.


Edited by BBrown1999, 09 September 2014 - 04:45 PM.


#4 Allan

Allan

  • BC Advisor
  • 8,465 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:59 PM

Posted 09 September 2014 - 04:40 PM

That is not the correct information. Please re-read the instructions and post again. This time, please just post the 10 most recent errors - this thread is already much too long. Thanks.



#5 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:02:59 AM

Posted 09 September 2014 - 04:46 PM

Can you upload the dump files to a file sharing site in onedrive so I can analyse them.

They're located in C:\Windows\minidump copy them to the desktop, compress them in a .zip folder then upload that folder.

 

Can you also include a Kernel memory dump if possible as that should help a lot.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

#6 BBrown1999

BBrown1999
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 09 September 2014 - 05:47 PM

Ok, thank you, will do. Will google drive work for you? I will also attach a folder that includes a WinDebug translation of each file. Hopefully I followed your instructions correctly on the Kernal dump. 

 

Just give me a few hours, I work second shift,..I'll have them up tonight.

 

Allan, will theses files suffice or do you still prefer the information through BlueScreenView?



#7 BBrown1999

BBrown1999
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 10 September 2014 - 02:51 AM

Okay, here are the links:

 

https://drive.google.com/file/d/0B7-_Le3rDDQzRi1jbW9jR2VlcUU/edit?usp=sharing

 

https://drive.google.com/file/d/0B7-_Le3rDDQzZkVUcVpGd3QydUE/edit?usp=sharing

 

 

Allan...hopefully this is what you were looking for, still crazy long. If not, well I'll edit it down again..

 

==================================================
Dump File         : 090914-38922-01.dmp
Crash Time        : 9/9/2014 4:53:43 AM
Bug Check String  : BAD_POOL_CALLER
Bug Check Code    : 0x000000c2
Parameter 1       : 00000000`00000007
Parameter 2       : 00000000`0000109b
Parameter 3       : 00000000`11050203
Parameter 4       : fffff8a0`1ef1a5d0
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+16df
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\090914-38922-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 295,776
Dump File Time    : 9/9/2014 4:55:20 AM
==================================================
 
==================================================
Dump File         : 073114-20779-01.dmp
Crash Time        : 7/31/2014 1:28:34 PM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff680`00008aa0
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`03390167
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\073114-20779-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 295,720
Dump File Time    : 7/31/2014 3:14:01 PM
==================================================
 
==================================================
Dump File         : 070114-21060-01.dmp
Crash Time        : 7/1/2014 1:08:12 AM
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x0000000a
Parameter 1       : fffff680`00006ac0
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : fffff800`02c7d55b
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\070114-21060-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 295,656
Dump File Time    : 7/1/2014 1:50:22 PM
==================================================
 
==================================================
Dump File         : 062914-16177-01.dmp
Crash Time        : 6/27/2014 11:57:13 PM
Bug Check String  : PFN_LIST_CORRUPT
Bug Check Code    : 0x0000004e
Parameter 1       : 00000000`00000099
Parameter 2       : 00000000`002124b2
Parameter 3       : 00000000`00000002
Parameter 4       : 00000000`00211ff2
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\062914-16177-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 295,648
Dump File Time    : 6/29/2014 7:55:22 PM
==================================================
 
==================================================
Dump File         : 062514-15537-01.dmp
Crash Time        : 6/25/2014 10:33:12 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041284
Parameter 2       : 00000000`7be89001
Parameter 3       : 00000000`0011451d
Parameter 4       : fffff700`01080000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\062514-15537-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 295,648
Dump File Time    : 6/25/2014 10:36:13 PM
==================================================
 
==================================================
Dump File         : 020314-20732-01.dmp
Crash Time        : 2/3/2014 8:54:10 PM
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffff8a0`4bf71a9e
Parameter 2       : 00000000`00000000
Parameter 3       : fffff880`015ce961
Parameter 4       : 00000000`00000005
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\020314-20732-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 300,280
Dump File Time    : 2/3/2014 8:56:29 PM
==================================================
 
==================================================
Dump File         : 011614-26520-01.dmp
Crash Time        : 1/16/2014 11:48:01 PM
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffffa80`c4a587b8
Parameter 2       : 00000000`00000001
Parameter 3       : fffff800`02c96cc4
Parameter 4       : 00000000`00000005
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+abc45
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011614-26520-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 300,376
Dump File Time    : 1/16/2014 11:50:56 PM
==================================================
 
==================================================
Dump File         : 011314-34741-01.dmp
Crash Time        : 1/10/2014 7:48:28 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041284
Parameter 2       : 00000000`06e03001
Parameter 3       : 00000000`0000005a
Parameter 4       : fffff700`01080000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011314-34741-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 299,952
Dump File Time    : 1/13/2014 8:23:11 PM
==================================================
 
==================================================
Dump File         : 121213-20264-01.dmp
Crash Time        : 12/12/2013 9:23:53 PM
Bug Check String  : APC_INDEX_MISMATCH
Bug Check Code    : 0x00000001
Parameter 1       : 00000000`76f6685a
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`ffff0000
Parameter 4       : fffff880`0ce9fb60
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75bc0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\121213-20264-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 299,944
Dump File Time    : 12/12/2013 9:25:11 PM
==================================================
 
==================================================
Dump File         : 121013-28314-01.dmp
Crash Time        : 12/10/2013 2:22:44 AM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`02d1a06c
Parameter 3       : fffff880`039f3058
Parameter 4       : fffff880`039f28b0
Caused By Driver  : fltmgr.sys
Caused By Address : fltmgr.sys+13a00
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+b606c
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\121013-28314-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 299,912
Dump File Time    : 12/10/2013 2:25:14 AM
==================================================


#8 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:02:59 AM

Posted 10 September 2014 - 06:25 AM

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000011050203, Memory contents of the pool block
Arg4: fffff8a01ef1a5d0, Address of the block of pool being deallocated

So we have a 0xC2 bugcheck, this shows us that a driver tried to free a pool which was already freed.

7: kd> !pool fffff8a01ef1a5d0
Pool page fffff8a01ef1a5d0 region is Paged pool
 fffff8a01ef1a000 size:  4d0 previous size:    0  (Free )  Ntff
 fffff8a01ef1a4d0 size:   10 previous size:  4d0  (Free)       MmSm
 fffff8a01ef1a4e0 size:   30 previous size:   10  (Allocated)  PfFK
 fffff8a01ef1a510 size:   80 previous size:   30  (Allocated)  VdPN
 fffff8a01ef1a590 size:   30 previous size:   80  (Allocated)  Ntf0
*fffff8a01ef1a5c0 size:   50 previous size:   30  (Free ) *IoNm
		Pooltag IoNm : Io parsing names, Binary : nt!io
 fffff8a01ef1a610 size:  1d0 previous size:   50  (Allocated)  FMfn
 fffff8a01ef1a7e0 size:   30 previous size:  1d0  (Allocated)  PfFK
 fffff8a01ef1a810 size:  580 previous size:   30  (Allocated)  NtfF
 fffff8a01ef1ad90 size:   90 previous size:  580  (Allocated)  VdPN
 fffff8a01ef1ae20 size:   90 previous size:   90  (Allocated)  FSim
 fffff8a01ef1aeb0 size:  150 previous size:   90  (Allocated)  NtFS

I then noticed this.

7: kd> dc fffff8a01ef1a5c0
fffff8a0`1ef1a5c0  11050203 6d4e6f49 15d22150 fffffa80  ....IoNmP!......
fffff8a0`1ef1a5d0  1057005c 006e0069 006f0064 00730077  \.W.i.n.d.o.w.s.
fffff8a0`1ef1a5e0  8046005c 006e006f 00730074 0061005c  \.F.o.n.t.s.\.a.
fffff8a0`1ef1a5f0  08690072 006c0061 002e0069 00740074  r.i.a.l.i...t.t.
fffff8a0`1ef1a600  00000066 36303945 10014142 fffffa80  f...E906BA......
fffff8a0`1ef1a610  031d0205 6e664d46 1ee02450 fffff8a0  ....FMfnP$......
fffff8a0`1ef1a620  01bcf204 00000000 00000000 00000000  ................
fffff8a0`1ef1a630  026f0e0a 00000000 1ef1a638 fffff8a0  ..o.....8.......

Notice the \Windows\Fonts\ariali.ttf file?

That's related to your Windows fonts, you should clear the font cache.

 

Go to this location C:\Windows:\ServiceProfiles:\LocalService:\Appdata:\Local then delete the fntcache.dat file.

 

Make sure to create a restore point before hand just in case.



#9 Allan

Allan

  • BC Advisor
  • 8,465 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:59 PM

Posted 10 September 2014 - 06:37 AM

 
 

For the time being please disregard the post above this one.

 

Okay, your bsod's are all over the place. This is generally caused by one of two things: malwlare or a major hardware malfunction (including the motherboard). Please do the following:

 

1) Run full system scans with BOTH your installed anti virus app and with MalwareBytes.

 

2) If both scans come up clean, check the ram. To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility for several hours (even overnight).

 

3) If the above test shows the ram is good, my next guess would be your motherboard. I would certainly return it to Dell under warranty.



#10 Jared44

Jared44

  • BSOD Kernel Dump Expert
  • 205 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Dronfield
  • Local time:02:59 AM

Posted 10 September 2014 - 06:40 AM

I was in a bit of a rush actually, I'll need to go through it properly later on.
The dump files themselves don't seem to be caused by malware or hardware.
It seems a driver is using bad instruction pointers and referencing invalid memory.

It may well be bad RAM as Allan suggested though, it can cause a lot of unexpected problems.

Some bugchecks are most of the time software issues such as 0x7Es and 0x1s which you have experienced.

Edited by Jared44, 10 September 2014 - 06:51 AM.


#11 BBrown1999

BBrown1999
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 10 September 2014 - 07:24 PM

Man, it's disheartening to hear the motherboard could be the culprit. Dell just replaced it 7 months ago...along with all the memory and video card. I would return the entire machine if I could.

 

RAM was Dell's first guess, especially with those early BSOD error codes...then they shifted to Nvidia. Besides the first few, I have written down all the error codes experienced...0xC2 is the newest and not one I recall.

 

Scan Results:

Microsoft Security Essentials: nothing

 

MalwareBytes: 3 results

https://drive.google.com/folderview?id=0B7-_Le3rDDQzQUxUYW43M1llbkE&usp=sharing 

 

I will run memtest86 asap and share the results asap. 



#12 BBrown1999

BBrown1999
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 11 September 2014 - 05:07 AM

Okay, ran memtest86+ for 8hrs or so.....no problems found. 



#13 Allan

Allan

  • BC Advisor
  • 8,465 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:59 PM

Posted 11 September 2014 - 08:08 AM

Yeah, I'm sorry but my guess would be the mobo. I've had this happen on several systems where I'd see every blue screen error possible and in each case it was the motherboard. I'd get it back to Dell.



#14 BBrown1999

BBrown1999
  • Topic Starter

  • Members
  • 30 posts
  • OFFLINE
  •  
  • Local time:09:59 PM

Posted 11 September 2014 - 10:24 AM

Bummer.

Did the malwarebyes scan bring anything to your attention? I did notice an adobe premiere file in the results....maybe corruption also plays a part?

Also, in your experience Allan, do you find windows 7 or 8 more stable? There were plenty of BSODs before the new hardware install...maybe it's time for a different OS?

#15 Allan

Allan

  • BC Advisor
  • 8,465 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:59 PM

Posted 11 September 2014 - 10:44 AM

The items MB found are classified as "potentially unwanted programs". MB has a very aggressive posture when it comes to identifying PUP's but as a rule they are nothing to be concerned with.

 

As for stability, I don't have a problem with ANY OS (and I use them all). Your problem is almost certainly hardware related and has nothing to do with the OS.

 

One other thing you can do is look in device manager - are there any yellow or red symbols?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users