Solved BSOD occurring at random in ntoskrnl.exe, error code: 0x0000003b

littleraskol · Dec 22, 2011

This is a custom-built desktop system. I built it at the end of September and it has been running fine with no problems up until this month. Since the beginning of the month, it has BSODed 4 times: Dec. 2nd, Dec. 6th, Dec. 19th, and today (Dec. 22nd). Each time, using "BlueScreenView" it shows that the driver causing it was "ntoskrnl.exe" and the error code was: 0x0000003b (For the BSOD that happened today, Windows did not capture a minidump for some reason, so I can only speculate that it was the same error...)

There is no real consistency in what causes it. The screen will just randomly "mess up" with kaleidoscopic distortion, any sound playing will stutter, and then the system crashes to a BSOD. I have installed no new hardware since I built the computer. The last two programs I installed before this began were Skyrim (Nov. 28th) and CDBurnerXP (Nov. 26th). It's hard for me to see how either of these could be the culprit, since it has never BSODed while they were running.

My only "guess" as to what might cause it is a partitioning issue. When I first installed Win7, it took up the whole disk (1 TB) with one partition. Later, I created separate OS and DATA partitions. However, the Windows disk management utility did not allow me to create the OS partition of the size I wanted, it limited me to something like 400 GB. I used GParted on an Unbuntu live USB to make the partitions I desired (250 GB OS and 750 GB DATA). I think this was a month before and BSODs showed up. If this is the problem, I will just have to re-intall Windows. I may do that anyway since I am going to install a separate hybrid drive for OS and applications. Unfortunately, I have no system restore points from before Dec. 6th.

Memtest86+ (about 6 passes), the Windows memory testing utility, and disk check have found no errors. I have not run Driver Verifier, but I will soon.

System Specs in quote:

System Manufacturer/Model Number: Custom Built
OS: Windows 7 Home Premium 64 bit (OEM disc)
CPU: AMD Phenom II X4 965 3.4 GHz
Motherboard: Asus M4A88T-V EVO
Memory: G.SKILL Ripjaws 8 GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333
Graphics Card(s): Asus ATI Radeon HD6870 1GB DDR5
Sound Card: Integrated
Monitor(s) Displays: Acer AL1912 19"
Screen Resolution: 1280x1024
Hard Drives: SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5"
PSU: CORSAIR Enthusiast Series TX750 V2 750W ATX12V v2.31

"dump.zip" contains the minidump folder, the system health report HTML, and the "Windows_NT6_BSOD_jcgriff2" report. The system health report is kind of messed up; it doesn't seem to know that I have antivirus installed (PC Tools AV Free), and also claims that the "PC Tools Data Store" is not installed properly. Not really sure what that even means. Will update later if Driver Verifier comes up with anything.

littleraskol · Dec 22, 2011

Driver Verifier returned something interesting. When I restarted, Windows initially failed to start, going to a BSOD I had never seen before: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION with an error code of 0x000000c1. When I next restarted, Windows ran startup recovery and asked me to restore to a restore point. After that, it started normally. For some reason, this BSOD also did not create a minidump.

littleraskol · Dec 29, 2011

This (edit: the issue described in the OP) happened again this morning while I was asleep. Does anyone have any insight into what might be causing this?

littleraskol · Dec 29, 2011

Possibly interesting detail: I went through the Action Center's "look for solutions for unsolved problems..." process, it could not find anything but had the following description of the problem:

Windows
Problem: Shut down unexpectedly
Files that help describe the problem:
122911-15459-01.dmp
sysdata.xml
WERInternalMetadata.xml
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

I'm not really sure if these files are helpful in any way. I can't find any of them besides the dump file, though.

writhziden · Dec 29, 2011

Taking a look... Should have some steps for you to take within a half hour.

Code:

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\Windows_NT6_BSOD_jcgriff2\120211-26208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e0b000 PsLoadedModuleList = 0xfffff800`03050670
Debug session time: Fri Dec  2 00:47:21.932 2011 (UTC - 7:00)
System Uptime: 18 days 6:03:13.480
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
...................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002e7fb65, fffff8800ae21b20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e7fb65, Address of the instruction which caused the bugcheck
Arg3: fffff8800ae21b20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e7fb65 498b08          mov     rcx,qword ptr [r8]
CONTEXT:  fffff8800ae21b20 -- (.cxr 0xfffff8800ae21b20)
rax=000000155e860003 rbx=0000000000000008 rcx=fffff880009ea060
rdx=0042034c61004201 rsi=0000000000000012 rdi=0000000000000008
rip=fffff80002e7fb65 rsp=fffff8800ae22500 rbp=fffff880009ea060
 r8=0042034c61004200  r9=fffff80002e0b000 r10=fffff880009ea060
r11=0000000000000000 r12=fffff80003012340 r13=0000000000000000
r14=0000000000000002 r15=000000006770534e
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02e7fb65 498b08          mov     rcx,qword ptr [r8] ds:002b:0042034c`61004200=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e7fb65
STACK_TEXT:  
fffff880`0ae22500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16

FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e7fb65 498b08          mov     rcx,qword ptr [r8]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
STACK_COMMAND:  .cxr 0xfffff8800ae21b20 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
Followup: MachineOwner
---------
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\Windows_NT6_BSOD_jcgriff2\120611-26613-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03091670
Debug session time: Tue Dec  6 19:08:26.024 2011 (UTC - 7:00)
System Uptime: 4 days 18:20:04.569
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ec0b65, fffff88003c9fb20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ec0b65, Address of the instruction which caused the bugcheck
Arg3: fffff88003c9fb20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ec0b65 498b08          mov     rcx,qword ptr [r8]
CONTEXT:  fffff88003c9fb20 -- (.cxr 0xfffff88003c9fb20)
rax=000000067b420002 rbx=0000000000000008 rcx=fffff88003165060
rdx=0046002057004601 rsi=0000000000000012 rdi=0000000000000008
rip=fffff80002ec0b65 rsp=fffff88003ca0500 rbp=fffff88003165060
 r8=0046002057004600  r9=fffff80002e4c000 r10=fffff88003165060
r11=0000000000000000 r12=fffff80003053340 r13=0000000000000000
r14=0000000000000002 r15=000000006770534e
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02ec0b65 498b08          mov     rcx,qword ptr [r8] ds:002b:00460020`57004600=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ec0b65
STACK_TEXT:  
fffff880`03ca0500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16

FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ec0b65 498b08          mov     rcx,qword ptr [r8]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
STACK_COMMAND:  .cxr 0xfffff88003c9fb20 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
Followup: MachineOwner
---------
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\Windows_NT6_BSOD_jcgriff2\121911-21200-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`0308e670
Debug session time: Mon Dec 19 04:29:53.773 2011 (UTC - 7:00)
System Uptime: 3 days 9:59:50.319
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ebdb65, fffff8800aab3b20, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ebdb65, Address of the instruction which caused the bugcheck
Arg3: fffff8800aab3b20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ebdb65 498b08          mov     rcx,qword ptr [r8]
CONTEXT:  fffff8800aab3b20 -- (.cxr 0xfffff8800aab3b20)
rax=00000003b97f0003 rbx=0000000000000008 rcx=fffff880009ea060
rdx=0046002057004601 rsi=0000000000000012 rdi=0000000000000008
rip=fffff80002ebdb65 rsp=fffff8800aab4500 rbp=fffff880009ea060
 r8=0046002057004600  r9=fffff80002e49000 r10=fffff880009ea060
r11=0000000000000000 r12=fffff80003050340 r13=0000000000000000
r14=0000000000000002 r15=000000006770534e
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02ebdb65 498b08          mov     rcx,qword ptr [r8] ds:002b:00460020`57004600=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WmiPrvSE.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ebdb65
STACK_TEXT:  
fffff880`0aab4500 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16

FOLLOWUP_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ebdb65 498b08          mov     rcx,qword ptr [r8]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
STACK_COMMAND:  .cxr 0xfffff8800aab3b20 ; kb
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0
Followup: MachineOwner
---------
 
[/list]

All three of your blue screens were basically the same. All pointed to system files, and are thus inconclusive. To rule out system file corruption, run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

littleraskol said:
Driver Verifier returned something interesting. When I restarted, Windows initially failed to start, going to a BSOD I had never seen before: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION with an error code of 0x000000c1. When I next restarted, Windows ran startup recovery and asked me to restore to a restore point. After that, it started normally. For some reason, this BSOD also did not create a minidump.

Can you also please post your most recent dmp files by running through http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html again? This will give us an update on anything that has changed with your system (any new application errors, hardware changes, etc.) since the last upload.

littleraskol · Dec 29, 2011

Thanks for the reply, I'll get on that and post back in a bit.

ETA: as info, I have not added any new hardware.

littleraskol · Dec 29, 2011

New BSOD report bundle attached.

I ran the SFC command in verify only mode, it seems to indicate no file system issues:

C:\Windows\system32>sfc /verifyonly

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

This is looking more an more dire. I am really hoping this was just a software issue that a format and reinstall can solve, but if there's no problems with the files... If this is hardware, the fact that it only started a month ago (and months after I built the machine) makes returning the parts a nightmare, because it's possible one of them got damaged instead of simply being flawed from the started. welp

writhziden · Dec 29, 2011

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\BSOD\Windows_NT6_BSOD_jcgriff2\122911-15459-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`03056670
Debug session time: Thu Dec 29 03:47:13.801 2011 (GMT-7)
System Uptime: 4 days 10:47:18.346
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e85b65, fffff88007dd7cd0, 0}

Probably caused by : hidusb.sys ( hidusb!HumGetStringDescriptor+10a )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e85b65, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007dd7cd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e85b65 498b08          mov     rcx,qword ptr [r8]

CONTEXT:  fffff88007dd7cd0 -- (.cxr 0xfffff88007dd7cd0)
rax=00000003583f0003 rbx=0000000000000001 rcx=fffff80003004d60
rdx=0042034c61004201 rsi=0000000000000012 rdi=0000000000000000
rip=fffff80002e85b65 rsp=fffff88007dd86b0 rbp=fffff80003004d60
 r8=0042034c61004200  r9=fffff80002e11000 r10=fffff80003004d60
r11=fffff88007dd8800 r12=fffff80003018340 r13=0000000000000000
r14=0000000000000002 r15=0000000055646948
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02e85b65 498b08          mov     rcx,qword ptr [r8] ds:002b:0042034c`61004200=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  mainserv.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fbc1de to fffff80002e85b65

STACK_TEXT:  
fffff880`07dd86b0 fffff800`02fbc1de : fffffa80`095e4558 fffff800`02e92f32 fffffa80`0ed6d8f0 fffff800`02e9f89c : nt!ExpInterlockedPopEntrySListFault16
fffff880`07dd86c0 fffff880`055b3b4e : 00000000`0000000a 00000000`00000001 fffffa80`08ecd0a0 fffff880`055abd2d : nt!ExAllocatePoolWithTag+0xfe
fffff880`07dd87b0 fffff880`055abf2f : fffffa80`00000106 fffffa80`0ed6dc48 fffffa80`0ed6dc00 fffffa80`0ad059b0 : hidusb!HumGetStringDescriptor+0x10a
fffff880`07dd8830 fffff880`055bc02f : fffffa80`0d791301 fffffa80`0ed6dc48 00000000`00000001 fffffa80`0ad05b20 : hidusb!HumInternalIoctl+0x10b
fffff880`07dd88a0 fffff880`055bbdd0 : fffffa80`0ed6dc48 fffff880`055c44a0 fffffa80`0c34ab30 00000000`000b01be : HIDCLASS!HidpGetDeviceString+0x8b
fffff880`07dd88e0 fffff880`055ba8d3 : fffff880`055c5301 fffffa80`0ed6d8f0 fffffa80`0c34ab30 00001f80`000b01be : HIDCLASS!HidpIrpMajorDeviceControl+0xb2c
fffff880`07dd8970 fffff880`0547f83f : 00000000`c00000bb 00000000`c00000bb fffff880`07dd8ca0 fffffa80`0ed6d8f0 : HIDCLASS!HidpMajorHandler+0x1c3
fffff880`07dd89e0 fffff800`031a8a97 : fffffa80`0bf2cf20 fffffa80`0bf2cf20 fffffa80`0ed6dc90 fffffa80`0ed6d8f0 : HidBatt!HidBattIoControl+0x87
fffff880`07dd8a10 fffff800`031a92f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`07dd8b40 fffff800`02e8ced3 : 00000000`73702450 00000000`0122f170 00000000`0122fd20 00000000`7efaa000 : nt!NtDeviceIoControlFile+0x56
fffff880`07dd8bb0 00000000`73702e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0122f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73702e09


FOLLOWUP_IP: 
hidusb!HumGetStringDescriptor+10a
fffff880`055b3b4e 4889842488000000 mov     qword ptr [rsp+88h],rax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  hidusb!HumGetStringDescriptor+10a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hidusb

IMAGE_NAME:  hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

STACK_COMMAND:  .cxr 0xfffff88007dd7cd0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

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

The blue screen error blames hidusb.sys, so go through the steps in http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html to help resolve the issue.

littleraskol · Dec 29, 2011

That's interesting, I'd have never guessed that. Is this the original 0x0000003b "SYSTEM_SERVICE_EXCEPTION" error or the 0x000000c1 "SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION" error that showed up once? Anyway, I will try that out and see how it goes. Thank you!

writhziden · Dec 29, 2011

littleraskol said:
That's interesting, I'd have never guessed that. Is this the original 0x0000003b "SYSTEM_SERVICE_EXCEPTION" error or the 0x000000c1 "SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION" error that showed up once? Anyway, I will try that out and see how it goes. Thank you!

This one was from today. I did not see any from Verifier running. More than likely, the blue screen during Verifier was not able to be saved. Often, one has to run Verifier one driver at a time to find the culprit or read it from the bottom of the blue screen while it is up on the screen while verifying multiple drivers.

littleraskol · Jan 4, 2012

Another BSOD, same error type and code, this morning at 3:35 AM. I had followed the steps for fixing USB issues when writhziden recommended it, but I guess that didn't work. It might be worth listing the USB peripherals I have attached:

Everything is connected to the computer by a Rosewill 7 port USB 2.0 hub. I think I may have plugged it into a USB 3.0 port if that matters.

WD 500 GB external hard drive, usually unplugged unless I need backup files
Netgear RangeMax Wireless-N USB 2.0 wireless adapter
Logitech mouse
APC Backup UPS ES550, USB connection allows UPS status info collection, which I don't think I actually use anymore
Brother HL-2040 printer, usually turned off
A simple USB to micro USB cable for my phone
One port left empty

Something of note is that yesterday I moved everything into a new case and attached a Seagate Momentus XT 500GB hybrid drive. This is going to be the destination for my Windows 7 OS and applications partitions, I plan to migrate it today using Backup and Restore, per these directions: How to move windows 7 to a new or larger hard drive using Backup and Restore

I've attached the most recent info. Eventually I may just have to re-install everything, but I'm hoping that can be a last resort...

writhziden · Jan 4, 2012

Code:

[list=1]
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\BSOD\Minidump\122911-15459-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e11000 PsLoadedModuleList = 0xfffff800`03056670
Debug session time: Thu Dec 29 03:47:13.801 2011 (GMT-7)
System Uptime: 4 days 10:47:18.346
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e85b65, fffff88007dd7cd0, 0}

Probably caused by : hidusb.sys ( hidusb!HumGetStringDescriptor+10a )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e85b65, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007dd7cd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e85b65 498b08          mov     rcx,qword ptr [r8]

CONTEXT:  fffff88007dd7cd0 -- (.cxr 0xfffff88007dd7cd0)
rax=00000003583f0003 rbx=0000000000000001 rcx=fffff80003004d60
rdx=0042034c61004201 rsi=0000000000000012 rdi=0000000000000000
rip=fffff80002e85b65 rsp=fffff88007dd86b0 rbp=fffff80003004d60
 r8=0042034c61004200  r9=fffff80002e11000 r10=fffff80003004d60
r11=fffff88007dd8800 r12=fffff80003018340 r13=0000000000000000
r14=0000000000000002 r15=0000000055646948
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02e85b65 498b08          mov     rcx,qword ptr [r8] ds:002b:0042034c`61004200=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  mainserv.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fbc1de to fffff80002e85b65

STACK_TEXT:  
fffff880`07dd86b0 fffff800`02fbc1de : fffffa80`095e4558 fffff800`02e92f32 fffffa80`0ed6d8f0 fffff800`02e9f89c : nt!ExpInterlockedPopEntrySListFault16
fffff880`07dd86c0 fffff880`055b3b4e : 00000000`0000000a 00000000`00000001 fffffa80`08ecd0a0 fffff880`055abd2d : nt!ExAllocatePoolWithTag+0xfe
fffff880`07dd87b0 fffff880`055abf2f : fffffa80`00000106 fffffa80`0ed6dc48 fffffa80`0ed6dc00 fffffa80`0ad059b0 : hidusb!HumGetStringDescriptor+0x10a
fffff880`07dd8830 fffff880`055bc02f : fffffa80`0d791301 fffffa80`0ed6dc48 00000000`00000001 fffffa80`0ad05b20 : hidusb!HumInternalIoctl+0x10b
fffff880`07dd88a0 fffff880`055bbdd0 : fffffa80`0ed6dc48 fffff880`055c44a0 fffffa80`0c34ab30 00000000`000b01be : HIDCLASS!HidpGetDeviceString+0x8b
fffff880`07dd88e0 fffff880`055ba8d3 : fffff880`055c5301 fffffa80`0ed6d8f0 fffffa80`0c34ab30 00001f80`000b01be : HIDCLASS!HidpIrpMajorDeviceControl+0xb2c
fffff880`07dd8970 fffff880`0547f83f : 00000000`c00000bb 00000000`c00000bb fffff880`07dd8ca0 fffffa80`0ed6d8f0 : HIDCLASS!HidpMajorHandler+0x1c3
fffff880`07dd89e0 fffff800`031a8a97 : fffffa80`0bf2cf20 fffffa80`0bf2cf20 fffffa80`0ed6dc90 fffffa80`0ed6d8f0 : HidBatt!HidBattIoControl+0x87
fffff880`07dd8a10 fffff800`031a92f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`07dd8b40 fffff800`02e8ced3 : 00000000`73702450 00000000`0122f170 00000000`0122fd20 00000000`7efaa000 : nt!NtDeviceIoControlFile+0x56
fffff880`07dd8bb0 00000000`73702e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0122f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73702e09


FOLLOWUP_IP: 
hidusb!HumGetStringDescriptor+10a
fffff880`055b3b4e 4889842488000000 mov     qword ptr [rsp+88h],rax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  hidusb!HumGetStringDescriptor+10a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hidusb

IMAGE_NAME:  hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

STACK_COMMAND:  .cxr 0xfffff88007dd7cd0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\BSOD\Minidump\010412-19141-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`0305c670
Debug session time: Wed Jan  4 01:19:39.034 2012 (GMT-7)
System Uptime: 0 days 8:10:04.189
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e8bb65, fffff88007d2bcd0, 0}

Probably caused by : hidusb.sys ( hidusb!HumGetStringDescriptor+10a )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e8bb65, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007d2bcd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02e8bb65 498b08          mov     rcx,qword ptr [r8]

CONTEXT:  fffff88007d2bcd0 -- (.cxr 0xfffff88007d2bcd0)
rax=00000000312e0003 rbx=0000000000000001 rcx=fffff88002f65060
rdx=0042032061004201 rsi=0000000000000012 rdi=0000000000000000
rip=fffff80002e8bb65 rsp=fffff88007d2c6b0 rbp=fffff88002f65060
 r8=0042032061004200  r9=fffff80002e17000 r10=fffff88002f65060
r11=fffff88007d2c800 r12=fffff8000301e340 r13=0000000000000000
r14=0000000000000002 r15=0000000055646948
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02e8bb65 498b08          mov     rcx,qword ptr [r8] ds:002b:00420320`61004200=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  mainserv.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fc21de to fffff80002e8bb65

STACK_TEXT:  
fffff880`07d2c6b0 fffff800`02fc21de : fffffa80`096c3c68 fffff800`02e98f32 fffffa80`0b8e6780 fffff800`02ea589c : nt!ExpInterlockedPopEntrySListFault16
fffff880`07d2c6c0 fffff880`03b8cb4e : 00000000`0000000a 00000000`00000001 fffffa80`0885b830 fffff880`03b84d2d : nt!ExAllocatePoolWithTag+0xfe
fffff880`07d2c7b0 fffff880`03b84f2f : fffffa80`00000106 fffffa80`0be60368 fffffa80`0be60320 fffffa80`08d7b330 : hidusb!HumGetStringDescriptor+0x10a
fffff880`07d2c830 fffff880`03b9502f : fffffa80`0ae3a301 fffffa80`0be60368 00000000`00000001 fffffa80`08d7b4a0 : hidusb!HumInternalIoctl+0x10b
fffff880`07d2c8a0 fffff880`03b94dd0 : fffffa80`0be60368 fffff880`03b9d4a0 fffffa80`08e14c80 00000000`000b01be : HIDCLASS!HidpGetDeviceString+0x8b
fffff880`07d2c8e0 fffff880`03b938d3 : fffff880`03b9e301 fffffa80`0be60010 fffffa80`08e14c80 fffff800`000b01be : HIDCLASS!HidpIrpMajorDeviceControl+0xb2c
fffff880`07d2c970 fffff880`03bc183f : 00000000`c00000bb 00000000`c00000bb fffff880`07d2cca0 fffffa80`0be60010 : HIDCLASS!HidpMajorHandler+0x1c3
fffff880`07d2c9e0 fffff800`031aea97 : fffffa80`099251c0 fffffa80`099251c0 fffffa80`0be603b0 fffffa80`0be60010 : HidBatt!HidBattIoControl+0x87
fffff880`07d2ca10 fffff800`031af2f6 : 00000000`010df100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`07d2cb40 fffff800`02e92ed3 : 00000000`73752450 00000000`010df170 00000000`010dfd20 00000000`7efaa000 : nt!NtDeviceIoControlFile+0x56
fffff880`07d2cbb0 00000000`73752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`010df0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73752e09


FOLLOWUP_IP: 
hidusb!HumGetStringDescriptor+10a
fffff880`03b8cb4e 4889842488000000 mov     qword ptr [rsp+88h],rax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  hidusb!HumGetStringDescriptor+10a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hidusb

IMAGE_NAME:  hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

STACK_COMMAND:  .cxr 0xfffff88007d2bcd0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

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


[/list]

The following drivers should be updated or the components removed if they are no longer supported. Please refer to Driver Reference and Drivers and Downloads

Code:

PCASp50a64	fffff880`081e8000	fffff880`081f4000	Tue Nov 28 19:45:19 2006 (456cf43f)	000172df		PCASp50a64.sys
jswpslwfx	fffff880`03f56000	fffff880`03f63000	Thu May 15 04:28:50 2008 (482c1062)	00011e66		jswpslwfx.sys

littleraskol · Jan 4, 2012

Thanks once again! I will get on that.

ETA: both of these seem to be related to my USB wireless adapter, hmm...

littleraskol · Jan 4, 2012

Something strange about the "jswpslwfx" driver... This is apparently a D-Link USB wireless adapter driver. But my wireless adapter is not made by D-Link... The D-Link driver download site lists a bunch of devices and I was not sure what on my computer could be using it. I searched my C: drive for "D-Link" and found that a file in my Netgear driver directory (C:\Program Files (x86)\NETGEAR\WN111v2\Driver) had a reference to it: arusb_win7x.inf. The following lines give some details:

Code:

[Strings]

...

DLINK                        = "D-Link Corporation"

...

DWA160.DeviceDesc            = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A)"
DWA160A2.DeviceDesc          = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A2)"

The ellipses are omitted text that is not relevant. Does this mean that my Netgear adapter is using some D-Link software? There is a listing on the D-Link driver page for "DWA-160," but I really don't understand what's going on here... If there's a better forum for this, I'll ask there.

writhziden · Jan 4, 2012

littleraskol said:
Something strange about the "jswpslwfx" driver... This is apparently a D-Link USB wireless adapter driver. But my wireless adapter is not made by D-Link... The D-Link driver download site lists a bunch of devices and I was not sure what on my computer could be using it. I searched my C: drive for "D-Link" and found that a file in my Netgear driver directory (C:\Program Files (x86)\NETGEAR\WN111v2\Driver) had a reference to it: arusb_win7x.inf. The following lines give some details:

Code:

[Strings] ... DLINK = "D-Link Corporation" ... DWA160.DeviceDesc = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A)" DWA160A2.DeviceDesc = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A2)"

The ellipses are omitted text that is not relevant. Does this mean that my Netgear adapter is using some D-Link software? There is a listing on the D-Link driver page for "DWA-160," but I really don't understand what's going on here... If there's a better forum for this, I'll ask there.

You could start a thread in the Drivers forum about it. I would have to do some research to find out more, but someone in there may already know the answer(s) to your question(s).

littleraskol · Jan 4, 2012

There's a similar odd issue with the "PCASp50a64" driver. This has something to do with a PCAUSA NDIS (Network Driver Interface Specification?) driver. Once again, a file in my Netgear directory has a reference: W32N55.INI in C:\Program Files (x86)\NETGEAR\WN111v2.

Code:

; Rawether for Windows OEM Customization File
; Copyright (c) 2003-2006 Printing Communications Assoc., Inc. (PCAUSA)
; All Rights Reserved.
; ------------------------------------------------------------------
;
[Manufacturer]
CompanyName="Printing Communications Assoc., Inc. (PCAUSA)"
LegalCopyright="Copyright (c) 1997-2006 Printing Communications Assoc., Inc. (PCAUSA)"

The PCAUSA site is a nightmare, I cannot figure out where, if anywhere, the driver downloads are (but I'll keep looking). Seems more and more like the easiest way to deal with this is to not use the USB adapter and get a real wireless card.

Side note, the D-Link driver has actual associated files in the Netgear driver directory: jswpslwfx.sys, jswpslwfx.cat, and jswpslwfx.inf. The PCAUSA driver is only refered to in the above file (W32N55.INI):

Code:

[SinglePacket.amd64]
NDIS50=PCASp50a64
NDIS60=PCASp50a64

So now I am doubly lost, because there doesn't even seem to be a PCASp50a64.sys or anything similar. I throw myself on the mercy of this forum for figuring out how to update these things, unless there's a better forum or I just buy a wireless card first.

littleraskol · Jan 4, 2012

writhziden said:
You could start a thread in the Drivers forum about it. I would have to do some research to find out more, but someone in there may already know the answer(s) to your question(s).

Alright, cool, I will repost this stuff there. Thanks!

littleraskol · Jan 4, 2012

A troubling development: I have gotten a new kind of BSOD error, which has appeared once when resuming from hibernate and then again when entering hibernate. Both have the code 0x000000d1 and the string DRIVER_IRQL_NOT_LESS_OR_EQUAL. Attached is the ZIP file. Interestingly, both of these happened when a USB flash drive was plugged into the front panel USB port while shutting down/starting up. One of the BSODs is traced back to "WN111v2w7x.sys" which I think is a wireless driver?

writhziden · Jan 4, 2012

littleraskol said:
A troubling development: I have gotten a new kind of BSOD error, which has appeared once when resuming from hibernate and then again when entering hibernate. Both have the code 0x000000d1 and the string DRIVER_IRQL_NOT_LESS_OR_EQUAL. Attached is the ZIP file. Interestingly, both of these happened when a USB flash drive was plugged into the front panel USB port while shutting down/starting up. One of the BSODs is traced back to "WN111v2w7x.sys" which I think is a wireless driver?

NETGEAR WN111v2 USB2.0 wifi driver to be exact. A very common problem during sleep and hibernation sequences. Basically, the system tells the device to turn off (go to sleep) when entering hibernation or sleep mode, then tells it turn on (wake up) when resuming from hibernation or sleep mode. The driver is supposed to turn the device off or on, and when it fails to do so (sometimes due to another driver interfering or because the driver itself has become corrupted), a blue screen results to protect your system.

Try uninstalling the device driver through device manager and re-installing the latest driver (start menu -> right click my computer/computer -> click manage -> click device manager [from the list on the left] -> expand network adapters -> right click the device -> click uninstall [do not hit ok in the dialog box that pops up after hitting uninstall] -> put a tick to delete driver software for the device and hit ok -> restart your computer and install the latest driver for the device when Windows starts up again).

littleraskol · Jan 4, 2012

Er, I think I might have caused this... I think I un-checked the "turn off on sleep" setting when I was messing around with the device properties. Still, wouldn't hurt to re-install the drivers anyway, all things considered. Thanks again.

Solved BSOD occurring at random in ntoskrnl.exe, error code: 0x0000003b

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer