[aydyty]

here are the crash outputs from whocrashed:

On Sat 7/16/2011 12:19:18 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800024A3C7B, 0xFFFFFFFFFFFFFFFF, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED




On Thu 7/14/2011 10:30:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini071411-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A490)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000245401F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[Advertisements]

Yep I would suggest trying the memtest86 so that we can make sure if the memory is causing all this or not.

[rshaffer61]

Yep I would suggest trying the memtest86 so that we can make sure if the memory is causing all this or not.

[aydyty]

ran memtest - see post 39

[rshaffer61]

Have you tried to do a system restore back a ways to see if it will resolve the issue?

[aydyty]

I don't believe the restore points I found in the machine are old enough unfortunately.

[rshaffer61]

You will have to Perform a Repair Installation For Vista...guide is here...
This will allow you to repair your Vista installation and keep all of your personal user account files, settings, and programs

[wilder31]

May be Indexing Options? When it Hits a file or zip too large It goes haywire. sorry for the lack of specifics.

[rshaffer61]

Let me ask is this a SSD hard drive in this system?

[aydyty]

Don't belive so disk info from SIW

Attached Thumbnails

• 

[aydyty]

assuming I should still proceed with the Vista repair?

[aydyty]

Also, I don't belive I have a dvd that came with the machine- there is however a D: drive labeled as Factory Image?

[rshaffer61]

Nope not SSD and that would be the recovery partition. Using that will format the system and return it to factory new installation.

If you have a OEM Recovery Vista installation DVD that came preinstalled with your OEM brand computer instead, then it will most likely only be a clone of the hard drive with Vista allowing you to only do a clean install with it instead. These OEM computers often have a Recovery D:\ partition that does the same thing as the OEM Recovery Vista installation DVD.

In other words you will not be able to use that partition to do a repair installation.
This just got a little more complicated.

[aydyty]

any suggestions?

[rshaffer61]

On the side or bottom of your system there should be a sticker with the original OS version and your reg key. Can you tell me what the original OS version is?
You may have to borrow a OEM installation disk of the same version.

[aydyty]

Windows Vista Home Premium OEMact