Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: MS Word 2007 runs in W7 Safe Mode Only?


01 Jan 2014   #1

Western Australia
 
 
MS Word 2007 runs in W7 Safe Mode Only?

Hi All - First post - so greetings.

About 2 weeks ago when booting up my Windows 7 OS Desktop CHKDISK ran and eventually reached the desktop - but following that (or maybe causing that not sure) - each time I tried to open MS Word 2007 it just hung my computer. Same if I started MS Word 2007 in safe mode. Same applies to a third party Website Designer app.



I tried an uninstall and reinstal of MS Office - but that didn't fix the problem.

The curious thing is that I CAN start MS Word 2007 if Windows is in safe mode.

I've tried deleting and recreating the word template file - no good.

The other strange thing is that all my recovery points have disappeared - didn't change anything - I've recovered previously when copping a glitch after an update - so goodness knows how they dissapeared.

I guess as a last resort I could back everything up and reinstal Windows 7 and MS Office 2007

I've looked across the net - can find lots of starting MS Office in safe mode - but not remedying the starting of MS Word and my third party ap so they start when Windows 7 is booted up normally.

Suggestions?
BTW - what would cause my recovery points to dissapear?

My System SpecsSystem Spec
.

02 Jan 2014   #2

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64
 
 

Please do the following:

1. Click Start
2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type sfc /scannow and hit enter.

Report the output from the command window once it finishes.

More detail: SFC /SCANNOW Command - System File Checker
My System SpecsSystem Spec
02 Jan 2014   #3

Western Australia
 
 

Cheers Golden ... running now....
My System SpecsSystem Spec
.


02 Jan 2014   #4

Western Australia
 
 

OK - that's run in the DOS window output was "Windows Resource Protection did not find any integrity violations" ?
My System SpecsSystem Spec
02 Jan 2014   #5

Western Australia
 
 

So where to from here Golden please?
My System SpecsSystem Spec
02 Jan 2014   #6

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64
 
 

What was the report after that initial chkdsk that ran? Any errors reported?
My System SpecsSystem Spec
02 Jan 2014   #7

Western Australia
 
 

Quote   Quote: Originally Posted by Golden View Post
What was the report after that initial chkdsk that ran? Any errors reported?
A couple of sector errors and orphan files - said it fixed those - from memory - I went into event viewer and did a find on Chkdsk - didn't find any
My System SpecsSystem Spec
02 Jan 2014   #8

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64
 
 

Try a ckdsk again please.

1. Click Start
2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type chkdsk /R and hit enter.

You will be prompted whether you wish to schedule a chkdsk scan at next startup, type 'Y' and hit enter. Now restart your computer and chkdsk will automatically run.

More detail: Disk Check
My System SpecsSystem Spec
03 Jan 2014   #9

Western Australia
 
 
Chkdsk Done

OK - few - just finished the chkdsk - only things of note (noted on lap top as Desk Top process ran) was one bad cluster name \windows\system32\spool\drivers\x64\CNMUIA2.DLL and one bad bitmap file.

I did manage to find the chkdsk log files this time by invoking eventvwr.msc

Here's a dump of the Chkdsk:



Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
401152 file records processed. File verification completed.
1203 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
495364 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
401152 file SDs/SIDs processed. Cleaning up 20 unused index entries from index $SII of file 0x9.
Cleaning up 20 unused index entries from index $SDH of file 0x9.
Cleaning up 20 unused security descriptors.
Security descriptor verification completed.
47107 data files processed. CHKDSK is verifying Usn Journal...
33576192 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x31830000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x31830000 for 0x1000 bytes.
Windows replaced bad clusters in file 16442
of name \Windows\System32\spool\drivers\x64\3\CNMUIA2.DLL.
401136 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
104559540 free clusters processed. Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
557697124 KB in 345142 files.
189076 KB in 47108 indexes.
4 KB in bad sectors.
533043 KB in use by the system.
65536 KB occupied by the log file.
418238160 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
104559540 allocation units available on disk.

Internal Info:
00 1f 06 00 46 fc 05 00 bb c8 0a 00 00 00 00 00 ....F...........
7f 25 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 .%..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.


here's another from 02/01 - can provide more if you like....



Checking file system on C:
The type of the file system is NTFS.
Volume label is Local Disk.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
Attribute record of type 0x80 and instance tag 0x3 is cross linked
starting at 0x9fa89f for possibly 0x29 clusters.
Some clusters occupied by attribute of type 0x80 and instance tag 0x3
in file 0x57ca1 is already in use.
Deleting corrupt attribute record (128, "")
from file record segment 359585.
401152 file records processed. File verification completed.
1197 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
The file reference 0x3f6000000010e59 of index entry 005658.ldb of index $I30
with parent 0xb8b is not the same as 0x3f7000000010e59.
Deleting index entry 005658.ldb in index $I30 of file 2955.
The file reference 0x2ab000000010ef2 of index entry 005659.log of index $I30
with parent 0xb8b is not the same as 0x2b3000000010ef2.
Deleting index entry 005659.log in index $I30 of file 2955.
Unable to locate the file name attribute of index entry CURRENT
of index $I30 with parent 0xb8b in file 0x113f2.
Deleting index entry CURRENT in index $I30 of file 2955.
Unable to locate the file name attribute of index entry MANIFEST-005657
of index $I30 with parent 0xb8b in file 0x10f05.
Deleting index entry MANIFEST-005657 in index $I30 of file 2955.
Unable to locate the file name attribute of index entry MANIFE~2
of index $I30 with parent 0xb8b in file 0x10f05.
Deleting index entry MANIFE~2 in index $I30 of file 2955.
The file reference 0x1c9000000010e0c of index entry CURRENT of index $I30
with parent 0x333f is not the same as 0x1cb000000010e0c.
Deleting index entry CURRENT in index $I30 of file 13119.
The file reference 0x174000000010e05 of index entry MANIFEST-002123 of index $I30
with parent 0x333f is not the same as 0x179000000010e05.
Deleting index entry MANIFEST-002123 in index $I30 of file 13119.
The file reference 0x174000000010e05 of index entry MANIFE~2 of index $I30
with parent 0x333f is not the same as 0x179000000010e05.
Deleting index entry MANIFE~2 in index $I30 of file 13119.
Unable to locate the file name attribute of index entry 002971.ldb
of index $I30 with parent 0x40f8 in file 0x10e90.
Deleting index entry 002971.ldb in index $I30 of file 16632.
The file reference 0x2c0000000010e9d of index entry 002972.log of index $I30
with parent 0x40f8 is not the same as 0x2c1000000010e9d.
Deleting index entry 002972.log in index $I30 of file 16632.
The file reference 0x2c000000010f16 of index entry CURRENT of index $I30
with parent 0x40f8 is not the same as 0x2d000000010f16.
Deleting index entry CURRENT in index $I30 of file 16632.
The file reference 0x256000000010ea4 of index entry MANIFEST-002970 of index $I30
with parent 0x40f8 is not the same as 0x257000000010ea4.
Deleting index entry MANIFEST-002970 in index $I30 of file 16632.
The file reference 0x256000000010ea4 of index entry MANIFE~2 of index $I30
with parent 0x40f8 is not the same as 0x257000000010ea4.
Deleting index entry MANIFE~2 in index $I30 of file 16632.
The file reference 0x528000000010de7 of index entry lockfile of index $I30
with parent 0x8dfa is not the same as 0x536000000010de7.
Deleting index entry lockfile in index $I30 of file 36346.
Unable to locate the file name attribute of index entry SPLWOW64.EXE-297C4568.pf
of index $I30 with parent 0x293a4 in file 0xfcdc.
Deleting index entry SPLWOW64.EXE-297C4568.pf in index $I30 of file 168868.
Unable to locate the file name attribute of index entry SPLWOW~1.PF
of index $I30 with parent 0x293a4 in file 0xfcdc.
Deleting index entry SPLWOW~1.PF in index $I30 of file 168868.
The file reference 0x32e000000010e3e of index entry CURRENT of index $I30
with parent 0x55296 is not the same as 0x332000000010e3e.
Deleting index entry CURRENT in index $I30 of file 348822.
The file reference 0x2d6000000010e2c of index entry MANIFEST-006769 of index $I30
with parent 0x55296 is not the same as 0x2d8000000010e2c.
Deleting index entry MANIFEST-006769 in index $I30 of file 348822.
The file reference 0x2d6000000010e2c of index entry MANIFE~1 of index $I30
with parent 0x55296 is not the same as 0x2d8000000010e2c.
Deleting index entry MANIFE~1 in index $I30 of file 348822.
Unable to locate the file name attribute of index entry CURRENT
of index $I30 with parent 0x57c94 in file 0x10ebc.
Deleting index entry CURRENT in index $I30 of file 359572.
492662 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
401152 file SDs/SIDs processed. Cleaning up 9 unused index entries from index $SII of file 0x9.
Cleaning up 9 unused index entries from index $SDH of file 0x9.
Cleaning up 9 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 359585.
45757 data files processed. CHKDSK is verifying Usn Journal...
The remaining of an USN page at offset 0x41ffab000 in file 0xe032
should be filled with zeros.
Repairing Usn Journal file record segment.
37333016 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

976657407 KB total disk space.
556475492 KB in 346605 files.
188680 KB in 45757 indexes.
0 KB in bad sectors.
536367 KB in use by the system.
65536 KB occupied by the log file.
419456868 KB available on disk.

4096 bytes in each allocation unit.
244164351 total allocation units on disk.
104864217 allocation units available on disk.

Internal Info:
00 1f 06 00 b7 fc 05 00 1b c9 0a 00 00 00 00 00 ................
7a 25 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 z%..,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

EDIT UPDATE 15:10 HOURS WST:

Just tried to open MS Word 2007 - and it opened ! as did my third party ap - HOWEVER, both came up with an error dialogue - print driver host for 32 bit application has stopped working - would I be correct in suspecting that DLL file error has something to do with this as it is a printer issue?
My System SpecsSystem Spec
03 Jan 2014   #10

Microsoft Community Contributor Award Recipient

Windows 7 Ult. x64 Windows 8.1 x64
 
 

Jeez what a mess. The only thing I can think of now is to reinstall Word now thar you used a /R on the chkdsk. If that doesn't work, then a reinstall of Windows and Office would be the way to go (painful I know).

If you do decide to do a reinstall, we should do a proper clean up that drive first. Let us know.
My System SpecsSystem Spec
Reply

 MS Word 2007 runs in W7 Safe Mode Only?




Thread Tools



Similar help and support threads for2: MS Word 2007 runs in W7 Safe Mode Only?
Thread Forum
BSOD Computer only runs in Safe Mode BSOD Help and Support
Solved BSOD in normal mode (various errors), Runs fine in Safe Mode BSOD Help and Support
Computer runs really slow in normal mode, but runs fine in safe mode BSOD Help and Support
Win 7 32&64 pro freeze on load but runs in safe mode. BSOD Help and Support
Systems runs in safe mode - Normal mode locks up BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:33 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33