Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Blue Screen issue - NT Kernel


31 Jan 2012   #1

windows 7 64bit
 
 
Blue Screen issue - NT Kernel

Hey guys...I think my computer is on the way out. Getting constant blue screens and could really do with sorting it. I've done all the conventional things, even did a wipe back to factory settings.

Anyway, I've attached the DMP info...hopefully one of you geniuses will be able to assist me.

My System SpecsSystem Spec
.

31 Jan 2012   #2

Windows 7 Home Premium 64 Bit
 
 

No attachment in your post. Please follow the http://www.sevenforums.com/crashes-d...tructions.html and upload the .zip file using the methods outlined in the Screenshots and Files - Upload and Post in Seven Forums tutorial.
My System SpecsSystem Spec
31 Jan 2012   #3

windows 7 64bit
 
 

Sorry...it was a different upload procedure than I was used to..forgot to press upload!

should be there now.

thanks writhziden.
My System SpecsSystem Spec
.


31 Jan 2012   #4

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [F:\BSODDmpFiles\supes\dmp\013112-24390-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02816000 PsLoadedModuleList = 0xfffff800`02a5b670 Debug session time: Tue Jan 31 05:57:52.002 2012 (GMT-7) System Uptime: 0 days 0:04:31.737 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {3, 5, 1, fffff880049c47b0} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : hardware ( nvlddmkm+12e7b0 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000003, memory referenced Arg2: 0000000000000005, IRQL Arg3: 0000000000000001, value 0 = read operation, 1 = write operation Arg4: fffff880049c47b0, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac5100 0000000000000003 CURRENT_IRQL: 5 FAULTING_IP: nvlddmkm+12e7b0 fffff880`049c47b0 c07402ffc6 sal byte ptr [rdx+rax-1],0C6h CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80000b9c690 -- (.trap 0xfffff80000b9c690) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8002d5b430 rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000 rip=fffff880049c47b0 rsp=fffff80000b9c820 rbp=0000000000000003 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc nvlddmkm+0x12e7b0: fffff880`049c47b0 c07402ffc6 sal byte ptr [rdx+rax-1],0C6h ds:0140:00000000`00000003=?? Resetting default scope MISALIGNED_IP: nvlddmkm+12e7b0 fffff880`049c47b0 c07402ffc6 sal byte ptr [rdx+rax-1],0C6h LAST_CONTROL_TRANSFER: from fffff800028921e9 to fffff80002892c40 STACK_TEXT: fffff800`00b9c548 fffff800`028921e9 : 00000000`0000000a 00000000`00000003 00000000`00000005 00000000`00000001 : nt!KeBugCheckEx fffff800`00b9c550 fffff800`02890e60 : 00000000`ff1fe040 00000000`00000304 fffffa80`00000000 fffffa80`02d5b430 : nt!KiBugCheckDispatch+0x69 fffff800`00b9c690 fffff880`049c47b0 : 00000000`00000001 fffff800`02a08e80 fffffa80`03d42038 fffff880`049c05b0 : nt!KiPageFault+0x260 fffff800`00b9c820 00000000`00000001 : fffff800`02a08e80 fffffa80`03d42038 fffff880`049c05b0 fffffa80`02b6a550 : nvlddmkm+0x12e7b0 fffff800`00b9c828 fffff800`02a08e80 : fffffa80`03d42038 fffff880`049c05b0 fffffa80`02b6a550 fffffa80`018642a0 : 0x1 fffff800`00b9c830 fffffa80`03d42038 : fffff880`049c05b0 fffffa80`02b6a550 fffffa80`018642a0 fffffa80`018642a0 : nt!KiInitialPCR+0x180 fffff800`00b9c838 fffff880`049c05b0 : fffffa80`02b6a550 fffffa80`018642a0 fffffa80`018642a0 fffff880`049d4c69 : 0xfffffa80`03d42038 fffff800`00b9c840 fffffa80`02b6a550 : fffffa80`018642a0 fffffa80`018642a0 fffff880`049d4c69 00000000`00000005 : nvlddmkm+0x12a5b0 fffff800`00b9c848 fffffa80`018642a0 : fffffa80`018642a0 fffff880`049d4c69 00000000`00000005 fffffa80`018642a0 : 0xfffffa80`02b6a550 fffff800`00b9c850 fffffa80`018642a0 : fffff880`049d4c69 00000000`00000005 fffffa80`018642a0 00000000`00000002 : 0xfffffa80`018642a0 fffff800`00b9c858 fffff880`049d4c69 : 00000000`00000005 fffffa80`018642a0 00000000`00000002 fffff880`049dfa77 : 0xfffffa80`018642a0 fffff800`00b9c860 00000000`00000005 : fffffa80`018642a0 00000000`00000002 fffff880`049dfa77 fffffa80`018642a0 : nvlddmkm+0x13ec69 fffff800`00b9c868 fffffa80`018642a0 : 00000000`00000002 fffff880`049dfa77 fffffa80`018642a0 fffff880`04a116e5 : 0x5 fffff800`00b9c870 00000000`00000002 : fffff880`049dfa77 fffffa80`018642a0 fffff880`04a116e5 fffffa80`018642a0 : 0xfffffa80`018642a0 fffff800`00b9c878 fffff880`049dfa77 : fffffa80`018642a0 fffff880`04a116e5 fffffa80`018642a0 00000000`00000000 : 0x2 fffff800`00b9c880 fffffa80`018642a0 : fffff880`04a116e5 fffffa80`018642a0 00000000`00000000 00000000`00000000 : nvlddmkm+0x149a77 fffff800`00b9c888 fffff880`04a116e5 : fffffa80`018642a0 00000000`00000000 00000000`00000000 fffffa80`02b6a550 : 0xfffffa80`018642a0 fffff800`00b9c890 fffffa80`018642a0 : 00000000`00000000 00000000`00000000 fffffa80`02b6a550 00000000`00000000 : nvlddmkm+0x17b6e5 fffff800`00b9c898 00000000`00000000 : 00000000`00000000 fffffa80`02b6a550 00000000`00000000 fffff880`049cc75e : 0xfffffa80`018642a0 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+12e7b0 fffff880`049c47b0 c07402ffc6 sal byte ptr [rdx+rax-1],0C6h SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nvlddmkm+12e7b0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys Followup: MachineOwner ---------
  2. Loading Dump File [F:\BSODDmpFiles\supes\dmp\013112-36906-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02814000 PsLoadedModuleList = 0xfffff800`02a59670 Debug session time: Tue Jan 31 05:52:13.306 2012 (GMT-7) System Uptime: 0 days 0:18:15.041 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff80003c4ce50, 0, 0, fffff88004a7994d} Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff80003c4ce50 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff88004a7994d Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3D PROCESS_NAME: System CURRENT_IRQL: 5 EXCEPTION_RECORD: fffff80003c4d5f8 -- (.exr 0xfffff80003c4d5f8) Cannot read Exception record @ fffff80003c4d5f8 TRAP_FRAME: fffff80003c4d6a0 -- (.trap 0xfffff80003c4d6a0) Unable to read trap frame at fffff800`03c4d6a0 LAST_CONTROL_TRANSFER: from fffff800028901e9 to fffff80002890c40 STACK_TEXT: fffff800`03c4c598 fffff800`028901e9 : 00000000`0000003d fffff800`03c4ce50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff800`03c4c5a0 fffff800`0288c529 : fffffa80`0202cd80 00000000`00000000 fffff800`03c4ce50 fffff800`028bc830 : nt!KiBugCheckDispatch+0x69 fffff800`03c4c6e0 fffff800`028bc4fd : fffff880`053a1890 fffff880`04fde00c fffff880`048f7000 fffff800`03c4d5f8 : nt!KiInterruptHandler+0x29 fffff800`03c4c710 fffff800`028bb2d5 : fffff800`029daf04 fffff800`03c4c788 fffff800`03c4d5f8 fffff800`02814000 : nt!RtlpExecuteHandlerForException+0xd fffff800`03c4c740 fffff800`028cc361 : fffff800`03c4d5f8 fffff800`03c4ce50 fffff800`00000000 00000000`00000004 : nt!RtlDispatchException+0x415 fffff800`03c4ce20 fffff800`028902c2 : fffff800`03c4d5f8 fffffa80`018422a0 fffff800`03c4d6a0 00000000`00000000 : nt!KiDispatchException+0x135 fffff800`03c4d4c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiInterruptHandler+29 fffff800`0288c529 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiInterruptHandler+29 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x3D_nt!KiInterruptHandler+29 BUCKET_ID: X64_0x3D_nt!KiInterruptHandler+29 Followup: MachineOwner ---------
  3. Loading Dump File [F:\BSODDmpFiles\supes\dmp\013012-22265-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`02813000 PsLoadedModuleList = 0xfffff800`02a58670 Debug session time: Mon Jan 30 09:28:34.329 2012 (GMT-7) System Uptime: 0 days 7:33:00.063 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff88006dd994d, 5, 8, fffff88006dd994d} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+12a5b0 ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff88006dd994d, memory referenced Arg2: 0000000000000005, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: fffff88006dd994d, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ac2100 fffff88006dd994d CURRENT_IRQL: 5 FAULTING_IP: +5e55952f02b1dd20 fffff880`06dd994d ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: fffff80003c566a0 -- (.trap 0xfffff80003c566a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000009 rbx=0000000000000000 rcx=fffffa80018702a0 rdx=000000000000000c rsi=0000000000000000 rdi=0000000000000000 rip=fffff88006dd994d rsp=fffff80003c56830 rbp=fffffa80018702a0 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffffa80037ed950 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc fffff880`06dd994d ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000288f1e9 to fffff8000288fc40 FAILED_INSTRUCTION_ADDRESS: +5e55952f02b1dd20 fffff880`06dd994d ?? ??? STACK_TEXT: fffff800`03c56558 fffff800`0288f1e9 : 00000000`0000000a fffff880`06dd994d 00000000`00000005 00000000`00000008 : nt!KeBugCheckEx fffff800`03c56560 fffff800`0288de60 : fffffa80`018702a0 fffff880`049715b0 00000000`00000002 fffffa80`018702a0 : nt!KiBugCheckDispatch+0x69 fffff800`03c566a0 fffff880`06dd994d : fffffa80`018702a0 fffff880`049715b0 fffffa80`02c8e410 fffffa80`02cd9000 : nt!KiPageFault+0x260 fffff800`03c56830 fffffa80`018702a0 : fffff880`049715b0 fffffa80`02c8e410 fffffa80`02cd9000 00000000`ffffffff : 0xfffff880`06dd994d fffff800`03c56838 fffff880`049715b0 : fffffa80`02c8e410 fffffa80`02cd9000 00000000`ffffffff 00000000`00000000 : 0xfffffa80`018702a0 fffff800`03c56840 fffffa80`02c8e410 : fffffa80`02cd9000 00000000`ffffffff 00000000`00000000 fffffa80`018702a0 : nvlddmkm+0x12a5b0 fffff800`03c56848 fffffa80`02cd9000 : 00000000`ffffffff 00000000`00000000 fffffa80`018702a0 00000000`00000001 : 0xfffffa80`02c8e410 fffff800`03c56850 00000000`ffffffff : 00000000`00000000 fffffa80`018702a0 00000000`00000001 00000000`00000000 : 0xfffffa80`02cd9000 fffff800`03c56858 00000000`00000000 : fffffa80`018702a0 00000000`00000001 00000000`00000000 fffff880`04973de6 : 0xffffffff STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+12a5b0 fffff880`049715b0 ?? ??? SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: nvlddmkm+12a5b0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c8387 FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+12a5b0 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+12a5b0 Followup: MachineOwner ---------
  1. Possible cause Drivers... Appears to be your nVidia driver causing the problem with this crash.
  2. Possible cause Drivers... Does not indicate which driver.
  3. Possible cause Drivers... Appears to be your nVidia driver causing the problem with this crash.
Start by either installing the latest driver for your graphics card or re-installing the latest driver. It is possible the driver you have on your system is corrupt and replacing it will resolve the crashes.

If you are overclocking any hardware, please stop.

Do the following steps to replace your display card driver.
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
    • Right click the adapter
    • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts

Alternatively:
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
    • Right click the adapter
    • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
My System SpecsSystem Spec
31 Jan 2012   #5

Windows 7 Home Premium 64 Bit
 
 

I also note
Code:
TuneUpUtilitiesDriver64	fffff880`0469a000	fffff880`046a2000	Thu Sep 17 05:54:52 2009 (4ab2238c)	000052de		TuneUpUtilitiesDriver64.sys
on your system. We do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step as automated registry cleaning causes more harm to the registry than it actually repairs.

In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.
My System SpecsSystem Spec
31 Jan 2012   #6

windows 7 64bit
 
 

Ok..thank you very much.

Let me update the driver and I'll report back.

thanks again
My System SpecsSystem Spec
31 Jan 2012   #7

windows 7 64bit
 
 

Hi there,

I uninstalled the driver and downloaded a new one, thought all was going well until I got another blue screen as I was typing something in Word.

The attached image shows the latest crashes and the reasons for them. (I know you could see these from the previous file I uploaded)

What should i do now?
My System SpecsSystem Spec
31 Jan 2012   #8

Windows 7 Home Premium 64 Bit
 
 

Try to narrow down whether it is the graphics card as it appears, or an underlying driver. An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
My System SpecsSystem Spec
31 Jan 2012   #9

windows 7 64bit
 
 

I ran Driver Verifier, but...and excuse my ignorance here, I'm not sure what's supposed to happen from there? In a perfect world I'd get a pop up message telling me what Driver was causing hassle...

I've attached an updated dmp folder (although I'm aware that's probably the exact same as before)
My System SpecsSystem Spec
31 Jan 2012   #10

Windows 7 Home Premium 64 Bit
 
 

Just run until you get a few crashes and can upload more dump files caused by Verifier. Try to cause the crashes using the same methods that usually cause it.
My System SpecsSystem Spec
Reply

 Blue Screen issue - NT Kernel




Thread Tools



Similar help and support threads for2: Blue Screen issue - NT Kernel
Thread Forum
Blue Screen of Death - Event ID 41 Kernel-Power BSOD Help and Support
blue screen bsod kernel power event id 41 BSOD Help and Support
How can I solve this Blue Screen Kernel problem BSOD Help and Support
Blue Screen,kernel-power ID 41 help :( BSOD Help and Support
Blue Screen Crash, Event ID 41, kernel-power BSOD Help and Support
i7 crash/blue screen/kernel dump/windows7 or xp BSOD Help and Support
Blue Screen - kernel power event id 41 BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:09 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33