Jump to content
AIDA64 Discussion Forum
Memories4Life

Getting bad AGAIN!

Recommended Posts

Aidia64 is getting really bad for me. Harddrives going missing from OSD (have to restart adia), sensor update freq take between 2-6sec even though i have sensors set to 1,000ms (1sec).  Change settings in preferences and program hangs for several secs the list goes on.  For the past year or so i havnt seen a version of adia64 that works with both my systems.  I stopped using Adia but keep looking out for updates hoping things will get better (beta most of the time) but the problems get worse.  Honestly guys this is my final attempt with adia if these problem persist then i have to quit using the software for good as it isnt worth paying yearly for something that gets broken or doesnt work most the time (for me anyways).

 

System 1

X99-E WS USB 3.0, 5960x, nVidia titan x, 64gb ram, 1 x OCZ revo350 (480gb), 1xSamsung 950 pro (512gb), 2 x Samsung 840 (500GB), 2x Samsung 850 (500gb), 2x Samsung 850 (1TB), 2x Seagate (2TB), Win10

 

System 2

X99-M WS 3.1, 5820x, nvidia 980ti, 32GB ram, 1x Samsung 950 pro (256), 4x samsung 850 500gb, 2x WD (3TB) Green. Win10

 

I will try work with you guys but if i dont see an improvement then ill just have to call it a day. And for the record the ONLY software i am having problems with is aida all other monitoring softwares i have used works fine for me just most have limited functionality.

 

Thanks.

Share this post


Link to post
Share on other sites
9 hours ago, Memories4Life said:

And for the record the ONLY software i am having problems with is aida all other monitoring softwares i have used works fine for me just most have limited functionality.

That's exactly why such issues could happen ;)  AIDA64 simply can monitor more hardware components than most other software out there. But sometimes, digging deep and interrogating several sensor devices could cause inadvertent headaches.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

Before creating that dump, it would be best if you could disable OSD Panel and restart AIDA64.


Thanks,
Fiery

Share this post


Link to post
Share on other sites

Hi Fiery,

 

Thank you for responding.  First i must appologise for the post which you deleted.  Having a valid AIDA64 license i didnt know that those with invalid valid AIDA64 license would see adds. I have never seen the adds and i thought that was down to me using my HOST file to prevent the web from dumb rubbish/junk onto my systems.  So please forgive me for that error in judgement.  Should i be posting up this dump file for both my systems?

Share this post


Link to post
Share on other sites

System 1.

I am aware that having Corsair Link running can cause Adia problems. I never have CLink running just use it to send command line instructions to switch profiles which i use a custom .bat file to achive so i dont need Clink running just installed.  I have also removed Clink and still have the sam problem.

 

------[ AIDA64 Extreme v5.80.4068 Beta ]------

------[ Microsoft Windows 10 Pro 10.0.14393.693 (64-bit) ]------

------[ Motherboard Info ]------

Motherboard ID      : <DMI>
Motherboard Model   : Asus X99-E WS
Motherboard Chipset : Intel Wellsburg X99, Intel Haswell-E

DMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product      : X99-E WS
DMI MB Version      : Rev 1.xx
DMI MB Serial       : System Serial Number
DMI SYS Manufacturer: ASUS
DMI SYS Product     : All Series
DMI SYS Version     : System Version
DMI SYS Serial      : System Serial Number
DMI BIOS Version    : 3402

------[ Video Adapters ]------

EVGA e-GeForce GTX Titan X [10DE-17C2 / 3842-2999]

------[ Video Driver ]------

nvapi.dll: 21.21.13.7849
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um

------[ Sensor Profiling (Init) ]------

SensorInfo        : 1650.395 ms
GPUSensorInfo     :   16.839 ms
GPU01 / NV Diode  :    0.004 ms
GPU01 / NV Fan PWM:    0.000 ms
HDD               :    0.190 ms
SPD               :    1.274 ms
AMB               :    0.001 ms
DIMMTS            :    1.206 ms
Asus EPU2         :    0.000 ms
Asus EPU1         :    0.000 ms
nVIDIA SPP        :    0.000 ms
nVIDIA MCP        :    0.001 ms
Intel GMCH        :    0.001 ms
Intel PCH         :    0.014 ms
Intel SNB         :    0.064 ms
Zambezi           :    0.000 ms
Kaveri            :    0.000 ms
AMD SVI2          :    0.000 ms
MTC0303           :    0.000 ms
Smart Battery     :    0.000 ms
HID UPS           :    0.000 ms
Kraken X52        :    0.000 ms
LM78              :   43.287 ms
TT DPS            :    0.000 ms
Digifanless       :    0.000 ms
Corsair RMi       :  657.365 ms
Corsair AXi       :    0.000 ms
Odin              :    0.000 ms
Aquaero           :  874.011 ms

------[ Sensor Profiling (Last) ]------

SensorInfo        :  995.168 ms
GPUSensorInfo     :   19.836 ms
GPU01 / NV Diode  :    0.005 ms
GPU01 / NV Fan PWM:    0.000 ms
HDD               :    0.354 ms
SPD               :    2.541 ms
AMB               :    0.003 ms
DIMMTS            :    1.265 ms
Asus EPU2         :    0.001 ms
Asus EPU1         :    0.000 ms
nVIDIA SPP        :    0.000 ms
nVIDIA MCP        :    0.001 ms
Intel GMCH        :    0.001 ms
Intel PCH         :    0.015 ms
Intel SNB         :    0.052 ms
Zambezi           :    0.000 ms
Kaveri            :    0.000 ms
AMD SVI2          :    0.000 ms
MTC0303           :    0.000 ms
Smart Battery     :    0.000 ms
HID UPS           :    0.001 ms
Kraken X52        :    0.000 ms
LM78              :   43.917 ms
TT DPS            :    0.000 ms
Digifanless       :    0.000 ms
Corsair RMi       :  666.815 ms
Corsair AXi       :    0.000 ms
Odin              :    0.000 ms
Aquaero           :  202.965 ms

 

Share this post


Link to post
Share on other sites

System 2.

 

On this system i dont have C-link installed.

 

------[ AIDA64 Extreme v5.80.4068 Beta ]------

------[ Microsoft Windows 10 Pro 10.0.14393.693 (64-bit) ]------

------[ Motherboard Info ]------

Motherboard ID      : <DMI>
Motherboard Model   : Asus X99-M WS
Motherboard Chipset : Intel Wellsburg X99, Intel Haswell-E

DMI MB Manufacturer : ASUSTeK COMPUTER INC.
DMI MB Product      : X99-M WS
DMI MB Version      : Rev 1.xx
DMI MB Serial       :
DMI SYS Manufacturer: ASUS
DMI SYS Product     : All Series
DMI SYS Version     : System Version
DMI SYS Serial      : System Serial Number
DMI BIOS Version    : 3101

------[ Video Adapters ]------

EVGA e-GeForce GTX 980 Ti [10DE-17C8 / 3842-1996]

------[ Video Driver ]------

nvapi.dll: 21.21.13.7849
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dumx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2umx|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvd3dum|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um|||C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_02838dee03d82b94\nvwgf2um

------[ Sensor Profiling (Init) ]------

SensorInfo        :  169.006 ms
GPUSensorInfo     :   48.370 ms
GPU01 / NV Diode  :    0.002 ms
GPU01 / NV Fan PWM:    2.047 ms
HDD               :    0.091 ms
SPD               :    0.763 ms
AMB               :    0.001 ms
DIMMTS            :    0.001 ms
Asus EPU2         :    0.001 ms
Asus EPU1         :    0.000 ms
nVIDIA SPP        :    0.000 ms
nVIDIA MCP        :    0.000 ms
Intel GMCH        :    0.001 ms
Intel PCH         :    0.007 ms
Intel SNB         :    0.058 ms
Zambezi           :    0.000 ms
Kaveri            :    0.000 ms
AMD SVI2          :    0.000 ms
MTC0303           :    0.000 ms
Smart Battery     :    0.000 ms
LM78              :   44.654 ms
TT DPS            :    0.000 ms
Digifanless       :    0.000 ms
Corsair RMi       :    0.001 ms
Corsair AXi       :    0.000 ms
Odin              :    0.000 ms
Aquaero           :    0.000 ms

------[ Sensor Profiling (Last) ]------

SensorInfo        :  147.305 ms
GPUSensorInfo     :   46.613 ms
GPU01 / NV Diode  :    0.003 ms
GPU01 / NV Fan PWM:    3.301 ms
HDD               :    0.092 ms
SPD               :    0.758 ms
AMB               :    0.002 ms
DIMMTS            :    0.002 ms
Asus EPU2         :    0.000 ms
Asus EPU1         :    0.000 ms
nVIDIA SPP        :    0.000 ms
nVIDIA MCP        :    0.001 ms
Intel GMCH        :    0.000 ms
Intel PCH         :    0.002 ms
Intel SNB         :    0.018 ms
Zambezi           :    0.000 ms
Kaveri            :    0.000 ms
AMD SVI2          :    0.000 ms
MTC0303           :    0.000 ms
Smart Battery     :    0.000 ms
LM78              :   44.548 ms
TT DPS            :    0.000 ms
Digifanless       :    0.000 ms
Corsair RMi       :    0.000 ms
Corsair AXi       :    0.000 ms
Odin              :    0.000 ms
Aquaero           :    0.000 ms

 

Share this post


Link to post
Share on other sites

Thank you, and no worries about the mentioned post ;)

Thanks for the dumps! What I can see there is that the Corsair RMi and Aquaero monitoring methods take quite a bit of time to complete. It's not 2 to 6 seconds, but more like 1 second per update.  So that alone wouldn't explain the 2 to 6 seconds update rate you've mentioned in your opening post. However, it would still be interesting and helpful to try and disable the individual hardware monitoring modules, to see which one solves the slowness. You can disable the Aquaero and RMi modules if you right-click on the bottom status bar of AIDA64 main window --> HWMon Modules, and click on Aquaero or Corsair AXi / HXi / RMi.  You don't need to restart AIDA64 to enable/disable those modules. Let me know how the behavior of AIDA64 changes when you enable/disable those individual modules.

As for the matter of CL, as long as you have the latest version of Corsair Link software installed, you should have no issues running it and AIDA64 simultaneously.

Share this post


Link to post
Share on other sites

Hi Fiery,

You suggestion has improved but there is still a 2sec delay on the X99-E and on the X99-M there is a sec delay but its random... ie sensors tick ever second as they should but every 5-8 seconds they will be a delay of 2 secs.... hope you understand what i mean here.

 

 

P.S Sorry for delay.  Demanding clients. :rolleyes:

Share this post


Link to post
Share on other sites
2 hours ago, Memories4Life said:

Hi Fiery,

You suggestion has improved but there is still a 2sec delay on the X99-E and on the X99-M there is a sec delay but its random... ie sensors tick ever second as they should but every 5-8 seconds they will be a delay of 2 secs.... hope you understand what i mean here.

P.S Sorry for delay.  Demanding clients. :rolleyes:

Such 2-second steps are absolutely normal. The way it works is that for example when you have a 1 second update frequency set, the sensor values are updated in a 1 second step. But, that 1 second delay starts when the previous sensor polling is done. So when the polling itself takes more than zero seconds, the actual update rate will be longer than 1 second.  When the polling of all sensor values take e.g. 600 milliseconds, the effective update rate will be 1600 milliseconds or 1.6 sec.

The solution to that pecularity is to lower the update frequency to e.g. 500 miliseconds.

Share this post


Link to post
Share on other sites

Hi Fiery,

This comes with a problem.  If you set to 500ms and have a clock displaying the seconds go alittle crazy.  Is there any chance of removing the clock from responding to this change?

 

ie... it takes 30secs (there abouts) to cycle a full minute once set to 500ms

 

ALso Corsair have released CL V4.5.x.x and this have improved the compatibility with aida64.

Share this post


Link to post
Share on other sites
5 hours ago, Memories4Life said:

Hi Fiery,

This comes with a problem.  If you set to 500ms and have a clock displaying the seconds go alittle crazy.  Is there any chance of removing the clock from responding to this change?

 

ie... it takes 30secs (there abouts) to cycle a full minute once set to 500ms

 

ALso Corsair have released CL V4.5.x.x and this have improved the compatibility with aida64.

Even if you have a 500 millisec or 100 millisec update rate, the clock will not go crazy. It will however not skip a second, so it will look smoother than with a 1 sec update rate.

CL: Great to hear, thank you!

Share this post


Link to post
Share on other sites
Quote

 

Hi Fiery,

This lag isnt working for me its become very annoying to be honest.  I never had this problem in the past using the same system config x2. The X99-E is alot worst than the X99-M, the first system is more important to me when it comes to monitoring.  At present im getting better reults using the Aquaero 6XT plus the sensors match my motherboard readings where Aida is always a few degrees out. When Aida launches im always missing drives (See screenshot) and i have to quit Aida and restart to show my drives (X99-E Board).  I find myself consistantly trying to find out why Aida is dong this.  Like i mentioned i never used to have this problem and every update i try seems to be worst than the previous (possible some confliction with the X99-E V1 & V2 boards.  Thanks for helping me Fiery but im going to quit using Aida becuase it isnt giving me Value for money.  Thank you and good luck with the Aida Project.

Missing Drives.JPG

Share this post


Link to post
Share on other sites

The missing drives could be because of Aquasuite. The latest version of that software seems to open drives exclusively, and monitors them in a way that makes other software unable to access the drives :(

Share this post


Link to post
Share on other sites

See i was thinking that at the start but then i removed the Auqasuite and disconnected the controller from the internal USB port and ran for 24hrs with the same problem.  The Screenshot above is the X99-E without the Aquasuite installed.

Share this post


Link to post
Share on other sites
3 minutes ago, Memories4Life said:

See i was thinking that at the start but then i removed the Auqasuite and disconnected the controller from the internal USB port and ran for 24hrs with the same problem.  The Screenshot above is the X99-E without the Aquasuite installed.

Meanwhile we've found a solution to fix the collision between AIDA64 and aquasuite 2017.  It will be implemented in the next AIDA64 beta update.  I'm not sure if it helps about the slow updates too, but it's worth a try ;)

Share this post


Link to post
Share on other sites
On 2017. 02. 17. at 3:12 PM, Memories4Life said:

See i was thinking that at the start but then i removed the Auqasuite and disconnected the controller from the internal USB port and ran for 24hrs with the same problem.  The Screenshot above is the X99-E without the Aquasuite installed.

The mentioned new AIDA64 beta build is available for download at:

https://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know if it helps.

Share this post


Link to post
Share on other sites

i Still got the same problem with my drives not apparing even though i told you this had nothing to do with the Aquasuite because i had removed the Aquasuite and disconnected from the usb port.  Still get heavy lagging.  basically the software isnt usable for me.  I have switched to using Aquasuite and dont have any of these problems, allbeit im missing a number of monitoring sensors but its a small price to pay.  Thanks for the suppport but ill be quiting the use of Aida64 from here on as i dont see the need to pay for a service (subscription) that doesnt work for me.  

 

Wish you guys well with the future development of Aida.

 

Good Luck!

Share this post


Link to post
Share on other sites
6 hours ago, Memories4Life said:

Wish you guys well with the future development of Aida.

Good Luck!

Thank you B)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...