locked
Command prompt always crashes in Win7 Pro 86x RRS feed

  • Question

  • Hey there, I'm on a Windows 7 Professional x86 machine and have become desparate about an annoying issue with my CMD. No matter how I try to start, it will always crash after 1 second. Error message is "Windows Command Prompt has stopped working"

    I did several things already, tried other cmd.exe files from other folders and Windows 7 machines, looked for viruses and rootkits, but nothing. It doesn't matter where, who, how often. It is particularly annoying when important software upgrades such as for .NET Framework fail because of the crashing CMD. Sometimes, when I'm starting a game for example, the CMD error appears once or twice, but when clicking the X the program may still start and run.

    I tried a regedit fix here on the forum (I stupidly can not post any links, the topic's title is "cmd.exe not working in Windows 7 x86 RTM"). I didn't try the "in-place upgrade" described there yet, because I'm not sure how smooth the system will work after that and I'm also not that eager to format my PC and re-install and re-configure everything.

    Can you come up with things I could/should try to fix it? Recommend any tools?

    Sunday, October 27, 2013 8:41 PM

Answers

  • boot from the Windows DVD, go to the repair options->command prompt and run this command:

    sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows
    
    

    Replace C: with the drive letter where you installed Windows. Is sfc able to restore the corrupted file?


    "A programmer is just a tool which converts caffeine into code"

    • Marked as answer by Cloud_TS Wednesday, November 6, 2013 3:47 PM
    Saturday, November 2, 2013 6:39 AM

All replies

  • Tilanus

    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.




    Wanikiya & Dyami--Team Zigzag

    Sunday, October 27, 2013 8:43 PM
  • How should I run this without a working command prompt?
    Sunday, October 27, 2013 8:46 PM
  • Tilanus'

    Sorry about that.  My bad.

    We could check event viewer to see why it is crashing.

    Please provide us with your Event Viewer administrative logs by following these steps:


    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file to skydrive or a file sharing service and put a link to it in your next post


    Wanikiya & Dyami--Team Zigzag


    • Edited by ZigZag3143x Sunday, October 27, 2013 8:52 PM
    Sunday, October 27, 2013 8:52 PM
  • https://skydrive.live.com/redir?resid=671F963E2AB1D525!1880&authkey=!ABeoF2TuIn8kfkY
    Sunday, October 27, 2013 10:59 PM
  • Hello?
    Monday, October 28, 2013 9:04 PM

  • please download this reg file from my SkyDrive:

    http://cid-128fc518635be2dc.office.live.com/self.aspx/.Public/MS%20Foren/Registry/LocalDumps.reg

    and make a double click on the file to import it.

    When an application (like cmd.exe) crashes, Windows Error Reporting Service [1] creates a dmp file under C:\Localdumps. Please upload the dump (zip it first) to your public Skydrive [2] folder and post the link here. I take a look at the dump with the Debugger, maybe I can see the cause.

    André

    [1] http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx
    [2] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code"


    Tuesday, October 29, 2013 6:11 AM
  • https://skydrive.live.com/redir?resid=671F963E2AB1D525!1881&authkey=!AMPxCFK1tlpf7yk
    Friday, November 1, 2013 3:10 PM
  • the cmd.exe is corrupted.

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !cmd
        4a162c00-4a162c14  21 bytes - cmd!TextCheck+166
    	[ 0f 85 0b f4 ff ff f6 06:00 00 00 00 00 00 00 00 ]
        4a162c16 - cmd!`string'+2 (+0x16)
    	[ 29:00 ]
        4a162c18 - cmd!`string'+4 (+0x02)
    	[ 7c:00 ]
        4a162c1a - cmd!`string'+6 (+0x02)
    	[ 26:00 ]
        4a162c1c - cmd!`string'+8 (+0x02)
    	[ 3d:00 ]
        4a162c1e - cmd!`string'+a (+0x02)
    	[ 2c:00 ]
        4a162c20 - cmd!`string'+c (+0x02)
    	[ 3b:00 ]
        4a162c22 - cmd!`string'+e (+0x02)
    	[ 22:00 ]
        4a162c26-4a162c35  16 bytes - cmd!_alloca_probe (+0x04)
    	[ 51 8d 4c 24 04 2b c8 1b:00 00 00 00 00 00 00 00 ]
        4a162c37-4a162c3e  8 bytes - cmd!_alloca_probe+11 (+0x11)
    	[ f0 ff ff 3b c8 73 09 2d:00 00 00 00 00 00 00 00 ]
        4a162c40 - cmd!_alloca_probe+24 (+0x09)
    	[ 10:00 ]
        4a162c43 - cmd!_alloca_probe+27 (+0x03)
    	[ 85:00 ]
        4a162c45-4a162c4b  7 bytes - cmd!_alloca_probe+29 (+0x02)
    	[ eb f3 8b c1 59 94 8b:00 00 00 00 00 00 00 ]
        4a162c4d-4a162c6b  31 bytes - cmd!_alloca_probe+1e (+0x08)
    	[ 89 04 24 c3 90 90 90 90:00 00 00 00 00 00 00 00 ]
        4a162c6d-4a162c74  8 bytes - cmd!GetDir+17 (+0x20)
    	[ 56 8b 75 08 0f 85 5a 92:00 00 00 00 00 00 00 00 ]
        4a162c77-4a162c90  26 bytes - cmd!GetDir+1d (+0x0a)
    	[ 56 ff 75 0c ff 15 bc 11:00 00 00 00 00 00 00 00 ]
        4a162c92-4a162c97  6 bytes - cmd!ResetConTitle+14 (+0x1b)
    	[ 80 3d 83 40 18 4a:00 00 00 00 46 ff ]
        4a162c99-4a162cad  21 bytes - cmd!ResetConTitle+1b (+0x07)
    	[ 0f 84 4b e9 ff ff ff 75:00 00 00 00 00 00 00 00 ]
        4a162caf-4a162cb4  6 bytes - cmd!ResetConTitle+2d (+0x16)
    	[ e9 36 e9 ff ff 25:00 00 00 00 00 00 ]
        4a162cb6 - cmd!`string'+2 (+0x07)
    	[ 73:00 ]
        4a162cba-4a162cbf  6 bytes - cmd!FindAndFix+e4 (+0x04)
    	[ a8 10 0f 84 d1 15:00 00 00 00 00 00 ]
        4a162cc2-4a162cc4  3 bytes - cmd!FindAndFix+ec (+0x08)
    	[ e9 96 28:00 00 00 ]
        4a162cc7-4a162ccc  6 bytes - cmd!ExpandAndApplyToFS+220 (+0x05)
    	[ ff 46 24 e9 4b 70:00 00 00 00 00 00 ]
        4a162ccf-4a162cd3  5 bytes - cmd!ChangeDirectory+19c (+0x08)
    	[ 8b c1 e9 6f 44:00 00 00 00 00 ]
        4a162cd6-4a162cdb  6 bytes - cmd!GetEnvVar+2f (+0x07)
    	[ 80 3d 81 40 18 4a:00 00 00 00 46 ff ]
        4a162cdd-4a162ce1  5 bytes - cmd!GetEnvVar+36 (+0x07)
    	[ 53 0f 84 48 01:00 00 00 00 00 ]
        4a162ce4-4a162cfb  24 bytes - cmd!GetEnvVar+3d (+0x07)
    	[ 8b 1d 14 10 16 4a 68 c0:00 00 00 00 46 ff 00 00 ]
        4a162cfe-4a162d0f  18 bytes - cmd!GetEnvVar+60 (+0x1a)
    	[ 68 f4 49 18 4a ff 75 08:00 00 00 46 ff 00 00 00 ]
        4a162d12-4a162d24  19 bytes - cmd!GetEnvVar+7b (+0x14)
    	[ 68 24 4a 18 4a ff 75 08:00 00 00 46 ff 00 00 00 ]
        4a162d26-4a162d38  19 bytes - cmd!GetEnvVar+92 (+0x14)
    	[ 68 80 2d 16 4a ff 75 08:00 00 00 46 ff 00 00 00 ]
        4a162d3a-4a162d4c  19 bytes - cmd!GetEnvVar+ad (+0x14)
    	[ 68 48 47 18 4a ff 75 08:00 00 00 46 ff 00 00 00 ]
        4a162d4e-4a162d5e  17 bytes - cmd!GetEnvVar+c9 (+0x14)
    	[ 68 34 48 18 4a ff 75 08:00 00 00 46 ff 00 00 00 ]
        4a162d62-4a162d69  8 bytes - cmd!GetEnvVar+d9 (+0x14)
    	[ 57 56 6a 01 50 e8 95 a9:00 00 00 00 00 00 00 00 ]
        4a162d6c-4a162d80  21 bytes - cmd!GetEnvVar+e3 (+0x0a)
    	[ 33 c9 66 89 0c 45 40 06:00 00 00 00 00 00 00 00 ]
        4a162d82 - cmd!`string'+2 (+0x16)
    	[ 4d:00 ]
        4a162d84 - cmd!`string'+4 (+0x02)
    	[ 44:00 ]
        4a162d86 - cmd!`string'+6 (+0x02)
    	[ 43:00 ]
        4a162d88 - cmd!`string'+8 (+0x02)
    	[ 4d:00 ]
        4a162d8a - cmd!`string'+a (+0x02)
    	[ 44:00 ]
        4a162d8c - cmd!`string'+c (+0x02)
    	[ 4c:00 ]
        4a162d8e - cmd!`string'+e (+0x02)
    	[ 49:00 ]
        4a162d90 - cmd!`string'+10 (+0x02)
    	[ 4e:00 ]
        4a162d92 - cmd!`string'+12 (+0x02)
    	[ 45:00 ]
        4a162d96-4a162dc1  44 bytes - cmd!`string'+16 (+0x04)
    	[ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
        4a162dc3-4a162dcd  11 bytes - cmd!FillBuf+384 (+0x2d)
    	[ ff 35 9c 41 18 4a 33 c0:00 00 00 00 46 ff 00 00 ]
        4a162dd0-4a162dff  48 bytes - cmd!FillBuf+391 (+0x0d)
    	[ 57 66 a3 42 06 1a 4a e8:00 00 00 00 00 46 ff 00 ]
        4a163202-4a163214  19 bytes - cmd!SearchForExecutable+755 (+0x432)
    	[ 33 c0 40 5b 8b 4d fc 5f:00 00 00 00 00 00 00 00 ]
        4a163216-4a16322e  25 bytes - cmd!SearchForExecutable+70e (+0x14)
    	[ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
        4a163230-4a16323d  14 bytes - cmd!MyGetEnvVarPtr+18 (+0x1a)
    	[ 56 8b 35 c4 41 18 4a 3b:00 00 00 00 00 46 ff 00 ]
        4a16323f-4a16325f  33 bytes - cmd!MyGetEnvVarPtr+2a (+0x0f)
    	[ 57 ff 75 08 e8 c5 f8 ff:00 00 00 00 00 00 00 00 ]
    WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
    8192 errors : !cmd (4a162c00-4a1652ab)
    

    this causes a memory corruption:

    BUCKET_ID:  APPLICATION_FAULT_MEMORY_CORRUPTION_INVALID_POINTER_WRITE_LARGE_memory_corruption!cmd
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_ID_HASH_STRING:  um:memory_corruption_large_c0000005_memory_corruption!cmd
    

    Use sfc.exe /scannow to detect and repair corrupted files:

    Use the System File Checker tool to repair missing or corrupted system files in Windows 8.1, Windows 8, Windows 7 or Windows Vista

    http://support.microsoft.com/kb/929833

    create a shortcut with the commandline and make a rightlcick and select "run as admin"


    "A programmer is just a tool which converts caffeine into code"

    Friday, November 1, 2013 6:34 PM
  • Use sfc.exe /scannow to detect and repair corrupted files:

    Use the System File Checker tool to repair missing or corrupted system files in Windows 8.1, Windows 8, Windows 7 or Windows Vista

    http://support.microsoft.com/kb/929833

    create a shortcut with the commandline and make a rightlcick and select "run as admin"

    Okay, thanks for looking through it. Sfc.exe doesn't work either though, no matter as what (admin or not) or where I start it (there's just one, don't worry). A console just shows up shortly and disappears quickly right after. No error message, nothing. It's even that short that the Task Manager doesn't list the process.

    What should I do?

    Friday, November 1, 2013 7:38 PM
  • boot from the Windows DVD, go to the repair options->command prompt and run this command:

    sfc /SCANNOW /OFFBOOTDIR=c:\ /OFFWINDIR=c:\windows
    
    

    Replace C: with the drive letter where you installed Windows. Is sfc able to restore the corrupted file?


    "A programmer is just a tool which converts caffeine into code"

    • Marked as answer by Cloud_TS Wednesday, November 6, 2013 3:47 PM
    Saturday, November 2, 2013 6:39 AM