Member Avatar for normanallen

I am using Windows 7 Ultimate 32-bit.
After a reinstall, I have installed XP Mode.
However, with Windows Explorer (and other utilities that access files), I can see all the files in any folder, but as soon as I try to do anything with any file, the system crashes and reboots.
It says an error code of 100007e.
I AM running as an administrator.
Any help appreciated.

  • 3 Contributors
  • 3 Replies
  • 310 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by normanallen

Dani AI

Generated

A focused troubleshooting plan will find whether the 100007e crash is a kernel/driver fault or an interaction between Windows Virtual PC’s integration and the host. Two parallel tracks save time: (A) collect crash evidence (minidump + Event Viewer BugCheck) so the offending driver or component can be identified, and (B) isolate the VM integration layer from the guest so file-access can be tested without host-side filters. This follows ’s hardware-check instinct and ’s point about limiting XP Mode surface area.

Useful, concrete steps and quick checks:

  • Disable automatic restart so the full stop text remains visible (System → Advanced system settings → Startup and Recovery → uncheck Automatic restart).
  • Configure small memory dumps and reproduce the crash. Locate dumps at C:\Windows\Minidump and the BugCheck entry in Event Viewer (Windows Logs → System).
  • Run basic host checks and repairs:
    sfc /scannow
chkdsk C: /f
mdsched.exe
eventvwr.msc
  • Open a minidump with BlueScreenView/WhoCrashed or WinDbg and run !analyze -v to see the likely driver name and stack.

Isolation and targeted fixes

  • Test whether crashes occur when working only on the VM’s virtual disk (not on shared/host drives). If file ops on shared folders trigger the crash, suspect host-side file-system filter drivers (antivirus, backup, encryption) or the Virtual PC integration driver.
  • Temporarily disable integration features (shared folders/drive mapping/clipboard), perform a clean boot (msconfig → hide Microsoft services → disable others), then retest. If the minidump names a third-party driver, update or remove that driver. Reinstall/repair Windows Virtual PC integration components or try an alternative VM product if integration can’t be made stable.

When driver-level analysis is needed, include the latest minidump filename, the Event Viewer BugCheck text (code and parameters) and any driver name shown by !analyze -v; those items make it possible to target the exact faulty component.

Recommended Answers

All 3 Replies

Member Avatar for Rik_

What was your reason for re-installing windows 7? Have you checked the condition of your hard drive and your ram?

Member Avatar for rubberman

What Rik said. Also, why XP mode (other than because you are more comfortable with it)?

Member Avatar for normanallen

I had a problem that was gradually making the system unusable. After discussion with others I finally decided that a reinstall would clear the problem. It did.
Before the reinstall I used a Linux CD to test the memory - no apparent problems. I also used a disk checker (name doesn't spring to mind) but it said the disk was fine.
I also installed VirtualBox and then XP, and explorer worked just fine!
I have a 16-bit application that was written using Borland Turbo C and I haven't converted all the functionality yet. Need to see the answers so I can check the new version (in Visual C++).
I also have a third party application that just will not run on windows 7, despite everything I try. It works just fine in XP mode. So at the moment I need XP Mode.
Everything else I do works just fine in W7. If I could get those two apps working (or converted) I wouldn't need it ay more.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.