| View previous topic :: View next topic |
| Author |
Message |
Choycolate Master Cheater
Reputation: -1
Joined: 18 Oct 2008 Posts: 284
|
Posted: Fri Aug 21, 2009 4:18 pm Post subject: [HELP] my computer start up wont work |
|
|
when i open it it opens in CMD then never opens
it saids too big to fit memory
_________________
|
|
| Back to top |
|
 |
SF I'm a spammer
Reputation: 119
Joined: 19 Mar 2007 Posts: 6028
|
Posted: Fri Aug 21, 2009 6:39 pm Post subject: |
|
|
Honestly, I have no clue what the hell you mean. Try describing it better or something..
_________________
|
|
| Back to top |
|
 |
Polynomial Grandmaster Cheater
Reputation: 5
Joined: 17 Feb 2008 Posts: 524 Location: Inside the Intel CET shadow stack
|
Posted: Fri Aug 21, 2009 6:44 pm Post subject: |
|
|
It's a corrupted PE header.
The PE header of an executable contains a few pointers and such to describe the file. If these are corrupted then it might try to load a huge amount of data into memory.
If this occurs when you click "My Computer", then you need to either System Restore to before this issue started occuring, repair your Windows installation with the Windows CD, or reformat.
_________________
It's not fun unless every exploit mitigation is enabled.
Please do not reply to my posts with LLM-generated slop; I consider it to be an insult to my time. |
|
| Back to top |
|
 |
Karakawe I post too much
Reputation: 3
Joined: 17 Apr 2007 Posts: 3899
|
Posted: Fri Aug 21, 2009 7:01 pm Post subject: |
|
|
| The repair install should work here.
|
|
| Back to top |
|
 |
Choycolate Master Cheater
Reputation: -1
Joined: 18 Oct 2008 Posts: 284
|
Posted: Fri Aug 21, 2009 8:23 pm Post subject: |
|
|
actually it says the same thing for every file except my computer and when i try to use the properties in my computer
FIREFOX works too
_________________
|
|
| Back to top |
|
 |
hcavolsdsadgadsg I'm a spammer
Reputation: 26
Joined: 11 Jun 2007 Posts: 5801
|
Posted: Fri Aug 21, 2009 11:36 pm Post subject: |
|
|
| Burningmace wrote: | It's a corrupted PE header.
The PE header of an executable contains a few pointers and such to describe the file. If these are corrupted then it might try to load a huge amount of data into memory.
If this occurs when you click "My Computer", then you need to either System Restore to before this issue started occuring, repair your Windows installation with the Windows CD, or reformat. |
afaik, windows will not load a PE that isn't valid.
in the PE header is a checksum, if you modify something else without editing the checksum, you will end up with a non functioning program.
|
|
| Back to top |
|
 |
Polynomial Grandmaster Cheater
Reputation: 5
Joined: 17 Feb 2008 Posts: 524 Location: Inside the Intel CET shadow stack
|
Posted: Sat Aug 22, 2009 8:00 am Post subject: |
|
|
| slovach wrote: | | Burningmace wrote: | It's a corrupted PE header.
The PE header of an executable contains a few pointers and such to describe the file. If these are corrupted then it might try to load a huge amount of data into memory.
If this occurs when you click "My Computer", then you need to either System Restore to before this issue started occuring, repair your Windows installation with the Windows CD, or reformat. |
afaik, windows will not load a PE that isn't valid.
in the PE header is a checksum, if you modify something else without editing the checksum, you will end up with a non functioning program. |
It depends where you screw it up. The DOS stub ("This application cannot be executed in MS-DOS mode.") is usually the section that causes the "too large for memory" error - hence why it is loaded in a CMD window. Normally when you screw up the code itself (asm) so that it represents invalid code, you get an NTVDM error stating that the command was invalid. However, if you just mess up the DOS stub, you get strange results.
_________________
It's not fun unless every exploit mitigation is enabled.
Please do not reply to my posts with LLM-generated slop; I consider it to be an insult to my time. |
|
| Back to top |
|
 |
|