Online free porn at mobile phone

Nukem! · 26th March 2017, 04:42

Two folders of celebrity pron (Cameron Diaz + Charlize Theron) cause Windoze10 to flake/ restart. 100%.

When I open the sick folders, the system cycles and ponders, and then all Windows vanish, and the task bar comes back in a bit.

Does anyone have a clue why?

Virus scans on the folder are clean, which presumes Kasp + AVG can SEE it. I've tried accessing it from admin & blah-user accounts with the same effect. I haven't tried safe mode yet

xiandaniel · 26th March 2017, 05:18

Too long path?

Nukem! · 26th March 2017, 06:40

Long path... No. I've worked with LOONG names, and this aint it.
File Explorer is just… dying when I open either of these two folders. Otherwise things are OK.

The std max path length for WinXP and Win7 is 260 chars (less unprintables is 256). Most commonly encountered when a deep collection of folders is copied into another deep collection. Is it a problem only for networks, where the server has its own file mgmt logic? You can hack your registry for longer MAXFILELENGTH, but it mostly just moves the problem around.

In Win7, a long-name file will just sit there (no crash); you can't directly access them. My work-around was shortening some of the parent folders' names, and then fixing the big boy.

digitalsierra · 26th March 2017, 07:24

corrupted sector of your hard drive?

Obivanwa · 26th March 2017, 08:28

I've had the same thing happen. It doesn't matter if this folder is on an external or my computer. Every time I open the folder my computer, which is quite new, freaks out.

The folder contains video and audio files.

Pad · 26th March 2017, 14:38

Why don't you try accessing the folder using Command Prompt. If you can access it with Command Prompt and your machine doesn't go bananas, you could try copying all of the files in the bad folder to a newly created folder with Command Prompt. Then try to access the new folder in Windows Explorer and see if that is stable. If it is stable you can just delete the bad folder.

Have a look at item 2 in this article for information on copying all files in a folder using Command Prompt.

Nukem! · 26th March 2017, 19:38

THANKS, Pad. The command prompt mostly worked.
CMD could access the folders / files. (CMD is also useful for making >> DIRectory lists)
There were 3 bad files, all MPG extns of various sizes, all all had their mod dates reset to FEB1999. (found by trial and error)
There are co-located JPGs with reset dates, too. But they can be accessed & processed.

Are there any guesses why MPGs should have such a fatal effect?

Pad · 26th March 2017, 21:55

Quote:

Originally Posted by Nukem!

THANKS, Pad. The command prompt mostly worked.
CMD could access the folders / files. (CMD is also useful for making >> DIRectory lists)
There were 3 bad files, all MPG extns of various sizes, all all had their mod dates reset to FEB1999. (found by trial and error)
There are co-located JPGs with reset dates, too. But they can be accessed & processed.

Excellent - glad the suggestion worked.

Quote:

Originally Posted by Nukem!

Are there any guesses why MPGs should have such a fatal effect?

As all of the bad files had their mod dates reset it probably has something to do with that. Are the created dates on those files later than the mod date? If so - maybe that's just confusing the hell out of Explorer and it melts down trying to figure it out.

Or maybe it could be that it has something to do with creating thumbnails in Explorer. I know that earlier iterations of Windows had problems creating thumbnails with some types of video files. Having said that - you'd think MS would have sorted that by now.

Just thinking aloud with both of those suggestions.

digitalsierra · 26th March 2017, 23:28

I had something similar happen to me just now. I couldn't access one of my newly created folders (windows explorer would just close on me). My first thought was - how did I catch a virus from reading Nukem's post !???

It wasn't a virus. In Windows 10, I kept getting a message 'You have files awaiting to be burned'. Except I didn't want to burn anything. I opened up windows explorer and pasted in "Shell:CD burning". Then I deleted all the files/folders awaiting burning. After that, I could go into my original folder again.

26th March 2017, 04:42	#1
Nukem! Junior Member Addicted Join Date: Apr 2014 Posts: 100 Thanks: 1,022 Thanked 285 Times in 81 Posts	certain folders will KILL Win10. Why? Two folders of celebrity pron (Cameron Diaz + Charlize Theron) cause Windoze10 to flake/ restart. 100%. When I open the sick folders, the system cycles and ponders, and then all Windows vanish, and the task bar comes back in a bit. Does anyone have a clue why? Virus scans on the folder are clean, which presumes Kasp + AVG can SEE it. I've tried accessing it from admin & blah-user accounts with the same effect. I haven't tried safe mode yet

26th March 2017, 08:28	#5
Obivanwa Registered User Addicted Join Date: Jun 2013 Posts: 424 Thanks: 887 Thanked 946 Times in 342 Posts	I've had the same thing happen. It doesn't matter if this folder is on an external or my computer. Every time I open the folder my computer, which is quite new, freaks out. The folder contains video and audio files. Last edited by Obivanwa; 26th March 2017 at 08:28.

26th March 2017, 14:38	#6
Pad Fan of Cairy Hunt Postaholic Join Date: Mar 2007 Location: Alice's Restaurant Posts: 5,154 Thanks: 19,788 Thanked 22,962 Times in 4,188 Posts	Why don't you try accessing the folder using Command Prompt. If you can access it with Command Prompt and your machine doesn't go bananas, you could try copying all of the files in the bad folder to a newly created folder with Command Prompt. Then try to access the new folder in Windows Explorer and see if that is stable. If it is stable you can just delete the bad folder. Have a look at item 2 in this article for information on copying all files in a folder using Command Prompt. Last edited by Pad; 26th March 2017 at 14:40.

26th March 2017, 05:18	#2
xiandaniel They taught me to give my life for motherland... not my ass! Clinically Insane Join Date: Oct 2010 Location: Italia Posts: 4,871 Thanks: 83,164 Thanked 42,514 Times in 4,951 Posts	Too long path?

26th March 2017, 06:40	#3
Nukem! Junior Member Addicted Join Date: Apr 2014 Posts: 100 Thanks: 1,022 Thanked 285 Times in 81 Posts	Long path... No. I've worked with LOONG names, and this aint it. File Explorer is just… dying when I open either of these two folders. Otherwise things are OK. The std max path length for WinXP and Win7 is 260 chars (less unprintables is 256). Most commonly encountered when a deep collection of folders is copied into another deep collection. Is it a problem only for networks, where the server has its own file mgmt logic? You can hack your registry for longer MAXFILELENGTH, but it mostly just moves the problem around. In Win7, a long-name file will just sit there (no crash); you can't directly access them. My work-around was shortening some of the parent folders' names, and then fixing the big boy.

26th March 2017, 07:24	#4
digitalsierra Registered User Addicted Join Date: Mar 2012 Location: Canada! Posts: 267 Thanks: 1,949 Thanked 1,879 Times in 227 Posts	corrupted sector of your hard drive?

26th March 2017, 19:38	#7
Nukem! Junior Member Addicted Join Date: Apr 2014 Posts: 100 Thanks: 1,022 Thanked 285 Times in 81 Posts	THANKS, Pad. The command prompt mostly worked. CMD could access the folders / files. (CMD is also useful for making >> DIRectory lists) There were 3 bad files, all MPG extns of various sizes, all all had their mod dates reset to FEB1999. (found by trial and error) There are co-located JPGs with reset dates, too. But they can be accessed & processed. Are there any guesses why MPGs should have such a fatal effect?

26th March 2017, 23:28	#9
digitalsierra Registered User Addicted Join Date: Mar 2012 Location: Canada! Posts: 267 Thanks: 1,949 Thanked 1,879 Times in 227 Posts	I had something similar happen to me just now. I couldn't access one of my newly created folders (windows explorer would just close on me). My first thought was - how did I catch a virus from reading Nukem's post !??? It wasn't a virus. In Windows 10, I kept getting a message 'You have files awaiting to be burned'. Except I didn't want to burn anything. I opened up windows explorer and pasted in "Shell:CD burning". Then I deleted all the files/folders awaiting burning. After that, I could go into my original folder again.