Solved vwifibus.sys crash on shutdown?

todesign · Apr 1, 2013

Hi there I've basically had this crash since i built my windows 8 computer at the end of last year just never really got round to fixing it as it only happens several times a month and once it restarted it shutdowns nicely anyway. so its not been too much of problem finally trying to fix it.

the problem is my computer crash's sometimes 5-6 mins after the shutdown button has been hit. and restarts itself.

I've used the debugging tool via cmd to sort through my dump and mini-dump files. dump didn't really have anything in but the minidump seems to have found the problem regarding "driver power state failure" which is what the bsod is.

its seems to be a problem with a file called :

vwifibus.sys can someone please verify that i am correct?

i've attached my debugged log. hopefully I've done all the hard work for you :think:

usasma · Apr 2, 2013

Unfortunately, it's not quite as simple as that.
First off, the actual cause is rarely a Windows driver. In fact, well in excess of 90% of BSOD's are due to 3rd party drivers (ref: Windows Internals v5 and v6). After that the most common cause is hardware problems, and lastly are Windows drivers.

What often happens is that the offending driver writes to a section of memory that another driver owns. Then the offending driver exits - so there's no trace of it on the memory stack. Then the other driver goes to look at this memory location and panics because the info there is wrong - and it crashes. Yet there's no evidence left as to the original driver.

But, we can draw some conclusions from this. That is that this is a networking error, and may also be a wireless error.
This means that it's something that's using the networking - and maybe even the wireless connection drivers memory space.

If you have a wireless, USB network device - this may be a cause. Here's my canned speech on them:

I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

We use a program that will sort through the drivers, remove the Windows drivers, and will highlight known problem drivers. So that's why I ask you to:

Please provide this information so we can provide a complete analysis: http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html

I manually looked through the driver listing and found these potential problems:

sptd.sys
a04pwd2m.SYS
These drivers belong to Daemon Tools/Alcohol % software

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): ~~[DEL] DuplexSecure - FAQ [/DEL]~~ Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Click to expand...

A number of Creative Audio drivers dating from 2011 (there may be BSOD issues with these drivers in Win8)
AFAIK there aren't any updates for this - so the software should be uninstalled and the device removed from the system in order to test it.

athurx.sys wireless driver that dates from 2010 - should be updated to the latest, Win8 compatible version

todesign · Apr 2, 2013

cheers thanks for the info gives me plenty to go at

I'm pretty sure the creative drivers are up to date it was one of the first x-fi models so its getting on a bit now. i do use a tplink wireless receiver for internet to my computer so could quite easily be that. since I've only used it since i installed windows 8. I'm going to post the other dump files because I've wrote on a piece of paper the error and I've got another system file on it so it could be that as well. something called ntoskrnl.exe. so I'll see if i can find that dump again.

thanks again.

tom.

todesign · Apr 2, 2013

Right I've updated my tplink driver to the latest one, and updated my creative driver so I'll give it a bit now and see if anything changes

I'll post back in a week or so.

thanks again. i've installed SF_Diagnostic_Tool and on the driver list there's a few going back to 2006 which i gather will be latest drivers but I'll check them out as well.

todesign · Apr 4, 2013

Crashed the second day so much for a quick fix

Right I've uninstalled alcohol 120%, sptd.sys also disabled "kernal debug adapter" in network see if that makes a difference.

I was thinking if i pulled out my wireless adapter before u shutdown the computer every time, would it still produce this problem? might be a good way of ruling it out.

Also attached the other files you were after.

usasma · Apr 5, 2013

There are reports missing from the upload. Please:

1) Zip up the contents of the C:\Windows\Minidump directory and upload them with your next post. If there's nothing in there, please follow the instructions here: Set MiniDump

2) Please generate, zip up, and upload this report:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter (you can also press Win and R at the same time to open the Run dialog - then type in msinfo32.exe and press Enter)
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

todesign · Apr 5, 2013

I thought I'd included it all they were quite big files so I split them up must have forgot to send it will repost it when I get back from work.

todesign · Apr 5, 2013

revised rar file

usasma · Apr 6, 2013

You have a Qualcomm Atheros AR7015 Wireless USB Network Adapter:

I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

The WER section of MSINFO32 shows BSOD's involving the wifi in February and March. Prior to that there were some video issues that haven't popped back up.

Alcohol 120% (and Daemon Tools software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): ~~[DEL] DuplexSecure - FAQ [/DEL]~~ Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ctac32k.sys Wed Jul 2 04:38:22 2008 (486B3E7E)
Creative Audio Driver
http://www.carrona.org/drivers/driver.php?id=ctac32k.sys

npf.sys Tue Oct 20 14:00:19 2009 (4ADDFAB3)
NetGroup Packet Filter Driver, part of the WinPcap packet capture library
http://www.carrona.org/drivers/driver.php?id=npf.sys

athurx.sys Wed Jul 28 08:01:39 2010 (4C501C23)
Atheros AR9271 Wireless Network Adapter
http://www.carrona.org/drivers/driver.php?id=athurx.sys

emupia2k.sys Mon Aug 22 01:55:54 2011 (4E51EF6A)
Creative E-mu Plug-in Architecture Driver
http://www.carrona.org/drivers/driver.php?id=emupia2k.sys

ctsfm2k.sys Mon Aug 22 01:56:00 2011 (4E51EF70)
Creative SoundFont Management Device Driver
http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys

ctoss2k.sys Mon Aug 22 01:56:11 2011 (4E51EF7B)
Creative OS Services Driver
http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys

ha20x2k.sys Mon Aug 22 01:57:35 2011 (4E51EFCF)
Creative 20X HAL (WDM)
http://www.carrona.org/drivers/driver.php?id=ha20x2k.sys

ctaud2k.sys Mon Aug 22 01:58:28 2011 (4E51F004)
Creative Audio Driver (WDM)
http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys

ctprxy2k.sys Mon Aug 22 01:58:30 2011 (4E51F006)
Creative Audio Driver (WDM)
http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys

CTEXFIFX.SYS Mon Aug 22 01:59:38 2011 (4E51F04A)
Creative sound card driver
http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS

CT20XUT.SYS Mon Aug 22 01:59:44 2011 (4E51F050)
Creative sound card driver
http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS

CTHWIUT.SYS Mon Aug 22 01:59:47 2011 (4E51F053)
Creative sound card driver
http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Sun Mar 31 17:48:59.543 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\033113-41812-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 3:27:41.186[/B]
*** ERROR: Module load completed but symbols could not be loaded for vwifimp.sys
*** ERROR: Module load completed but symbols could not be loaded for vwifibus.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]vwifibus.sys[/B]
BugCheck [B]9F, {4, 12c, fffffa800e443580, fffff8800128e800}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000009F]DRIVER_POWER_STATE_FAILURE (9f)[/url]
Arguments: 
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: fffffa800e443580, The thread currently holding on to the Pnp lock.
Arg4: fffff8800128e800, nt!TRIAGE_9F_PNP on Win7
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x9F_4_vwifimp_IMAGE_vwifibus.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed:     3600
CurrentSpeed: [B]3602[/B]
  BIOS Version                  1009
  BIOS Release Date             03/27/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Sun Mar 31 17:48:59.543 2013 (UTC - 4:00)**************************
[COLOR=RED][B]ctac32k.sys                 Wed Jul  2 04:38:22 2008 (486B3E7E)[/B][/COLOR]
[COLOR=RED][B]npf.sys                     Tue Oct 20 14:00:19 2009 (4ADDFAB3)[/B][/COLOR]
[COLOR=RED][B]athurx.sys                  Wed Jul 28 08:01:39 2010 (4C501C23)[/B][/COLOR]
[COLOR=RED][B]emupia2k.sys                Mon Aug 22 01:55:54 2011 (4E51EF6A)[/B][/COLOR]
[COLOR=RED][B]ctsfm2k.sys                 Mon Aug 22 01:56:00 2011 (4E51EF70)[/B][/COLOR]
[COLOR=RED][B]ctoss2k.sys                 Mon Aug 22 01:56:11 2011 (4E51EF7B)[/B][/COLOR]
[COLOR=RED][B]ha20x2k.sys                 Mon Aug 22 01:57:35 2011 (4E51EFCF)[/B][/COLOR]
[COLOR=RED][B]ctaud2k.sys                 Mon Aug 22 01:58:28 2011 (4E51F004)[/B][/COLOR]
[COLOR=RED][B]ctprxy2k.sys                Mon Aug 22 01:58:30 2011 (4E51F006)[/B][/COLOR]
[COLOR=RED][B]CTEXFIFX.SYS                Mon Aug 22 01:59:38 2011 (4E51F04A)[/B][/COLOR]
[COLOR=RED][B]CT20XUT.SYS                 Mon Aug 22 01:59:44 2011 (4E51F050)[/B][/COLOR]
[COLOR=RED][B]CTHWIUT.SYS                 Mon Aug 22 01:59:47 2011 (4E51F053)[/B][/COLOR]
[COLOR=RED][B]a04pwd2m.SYS                Wed Dec 28 04:10:52 2011 (4EFADD1C)[/B][/COLOR]
PxHlpa64.sys                Tue Apr 24 13:26:29 2012 (4F96E245)
mv91cons.sys                Wed Jun  6 06:26:38 2012 (4FCF305E)
mvxxmm.sys                  Wed Jun  6 23:09:05 2012 (4FD01B51)
mvs91xx.sys                 Wed Jun  6 23:09:20 2012 (4FD01B60)
HECIx64.sys                 Thu Jul 12 22:18:26 2012 (4FFF8572)
dump_storahci.sys           Wed Jul 25 22:30:35 2012 (5010ABCB)
[COLOR=RED][B]sptd.sys                    Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
avgfwd6a.sys                Tue Sep  4 04:31:15 2012 (5045BC53)
avgrkx64.sys                Thu Sep 13 20:41:40 2012 (50527D44)
avgloga.sys                 Thu Sep 20 21:23:51 2012 (505BC1A7)
avgldx64.sys                Mon Oct  1 21:05:50 2012 (506A3DEE)
avgidsha.sys                Sun Oct 14 21:22:54 2012 (507B656E)
avgidsdrivera.sys           Mon Oct 22 06:47:11 2012 (5085242F)
intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
avgmfx64.sys                Thu Nov 15 17:03:50 2012 (50A566C6)
avgwfpa.sys                 Mon Nov 26 17:09:35 2012 (50B3E89F)
nvlddmkm.sys                Sat Feb  9 18:13:08 2013 (5116D804)
[/font]

todesign · Apr 6, 2013

I've tried uninstalling my creative card and reinstalling and every time I update it to the latest driver which is a 2013 one. I go back in device manager and it still reads as driver version : 6.0.1.1375 22/08/2011 and on there website it says driver version 2.18.0015 date : 25 Jan 13??? am I missing something or is there naming system just screwed up. It says 2.18.0015 on the file. i might try installing the beta one from last year see if it reads properly

usasma · Apr 7, 2013

In short, the version of the software package that has the driver in it is likely to be different than the version of the actual driver itself. In the memory dump info above, we only extract the date/time stamp as that info is used to determine if the driver is "older" Also, please note that there are about 9 Creative drivers in the above dump file.

I wouldn't worry about it too much if you've done the rest of the stuff that I suggested.
We'll just wait and see if there's any further BSOD's.
If not - you've fixed it.
If so - then we'll deal with the Creative issues. In this scenario the best way to test is to uninstall the software for the card and then to physically remove the card from your system.

todesign · Apr 7, 2013

Ok cool i'm looking into a pci network card aswell found a decent one for £35 dual band i reckons its that still.

todesign · Apr 14, 2013

Think we are getting somewhere!

Think we've got rid of the WiFi error with that driver update

i do get a different bsod now though

says "WIN8_DRIVER_FAULT" after debugging (the last 2 minidumps it created) I'll upload you the file says something about :-

"IMAGE_NAME: ntkrnlmp.exe" which people have said could need my motherboard drivers updating or something see what you think.

can upload you a full set of files again as well if you like?

usasma · Apr 15, 2013

ntkrnlmp.exe is the kernel (core) of the Windows Operating System. If there was a problem with it, you would have many more problems other than the occasional BSOD. Also, there are many mechanisms in place inside of Windows that ensure that this (and other) critical files don't get corrupted - making it even less likely that this is the problem. Finally, in most cases like this we find that it's a 3rd party driver that's corrupting the memory space that ntkrnlmp.exe is using - so that's why it blames it rather than the 3rd party driver.

The uploaded text file doesn't have much info in it, please zip up and upload the contents of the C:\Windows\Minidump folder so we can perform our own analysis of the memory dumps.

todesign · Apr 15, 2013

ahhhh right not good then

updated files attached

also includes previous mini dumps

usasma · Apr 17, 2013

Start by running Driver Verifier according to these instructions: Driver Verifier Settings

Also, as time permits, start running these free diagnostics (in case it's a hardware problem): Hardware Diagnostics

Analysis:
The following is for informational purposes only.

Code:

[FONT=lucida console]**************************Sat Apr 13 17:06:26.587 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041313-129171-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 6:15:24.470[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+6e )[/B]
BugCheck [B]9F, {4, 12c, fffffa8012a05040, fffff801e461d800}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000009F"]DRIVER_POWER_STATE_FAILURE (9f)[/URL]
Arguments: 
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: fffffa8012a05040, The thread currently holding on to the Pnp lock.
Arg4: fffff801e461d800, nt!TRIAGE_9F_PNP on Win7
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x9F_4_nt!PnpBugcheckPowerTimeout[/B]
CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed:     3600
CurrentSpeed: [B]3602[/B]
  BIOS Version                  1009
  BIOS Release Date             03/27/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Apr 10 16:12:38.283 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041013-32171-01.dmp]
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 4:17:23.924[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+6e )[/B]
BugCheck [B]9F, {4, 12c, fffffa800e42c040, fffff88002d74800}[/B]
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x0000009F"]DRIVER_POWER_STATE_FAILURE (9f)[/URL]
Arguments: 
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 000000000000012c, Timeout in seconds.
Arg3: fffffa800e42c040, The thread currently holding on to the Pnp lock.
Arg4: fffff88002d74800, nt!TRIAGE_9F_PNP on Win7
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x9F_4_nt!PnpBugcheckPowerTimeout[/B]
CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed:     3600
CurrentSpeed: [B]3602[/B]
  BIOS Version                  1009
  BIOS Release Date             03/27/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[FONT=lucida console]**************************Sat Apr 13 17:06:26.587 2013 (UTC - 4:00)**************************
PxHlpa64.sys        Tue Apr 24 13:26:29 2012 (4F96E245)
mv91cons.sys        Wed Jun  6 06:26:38 2012 (4FCF305E)
mvxxmm.sys          Wed Jun  6 23:09:05 2012 (4FD01B51)
mvs91xx.sys         Wed Jun  6 23:09:20 2012 (4FD01B60)
e1c63x64.sys        Thu Jul 12 17:46:10 2012 (4FFF45A2)
HECIx64.sys         Thu Jul 12 22:18:26 2012 (4FFF8572)
dump_storahci.sys   Wed Jul 25 22:30:35 2012 (5010ABCB)
avgfwd6a.sys        Tue Sep  4 04:31:15 2012 (5045BC53)
avgrkx64.sys        Thu Sep 13 20:41:40 2012 (50527D44)
avgloga.sys         Thu Sep 20 21:23:51 2012 (505BC1A7)
avgldx64.sys        Mon Oct  1 21:05:50 2012 (506A3DEE)
avgidsha.sys        Sun Oct 14 21:22:54 2012 (507B656E)
athuw8x.sys         Mon Oct 15 07:08:55 2012 (507BEEC7)
avgidsdrivera.sys   Mon Oct 22 06:47:11 2012 (5085242F)
intelppm.sys        Mon Nov  5 22:55:02 2012 (50988A16)
avgmfx64.sys        Thu Nov 15 17:03:50 2012 (50A566C6)
avgwfpa.sys         Mon Nov 26 17:09:35 2012 (50B3E89F)
nvlddmkm.sys        Sat Feb  9 18:13:08 2013 (5116D804)
[/FONT]

todesign · Apr 22, 2013

have reinstalled my graphics drivers again and AVG seems to have cured it

willl keep an eye on it. hopefully its fixed

thanks for your help.

Solved vwifibus.sys crash on shutdown?

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Member

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer