Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Blue screen and system freeze


  • Please log in to reply

#46
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
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.
  • 0

Advertisements


#47
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Yep I would suggest trying the memtest86 so that we can make sure if the memory is causing all this or not.
  • 0

#48
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
ran memtest - see post 39
  • 0

#49
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Have you tried to do a system restore back a ways to see if it will resolve the issue?
  • 0

#50
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
I don't believe the restore points I found in the machine are old enough unfortunately.
  • 0

#51
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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
  • 0

#52
wilder31

wilder31

    New Member

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

#53
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Let me ask is this a SSD hard drive in this system?
  • 0

#54
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
Don't belive so disk info from SIW

Attached Thumbnails

  • drive info.jpg

  • 0

#55
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
assuming I should still proceed with the Vista repair?
  • 0

Advertisements


#56
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
Also, I don't belive I have a dvd that came with the machine- there is however a D: drive labeled as Factory Image?
  • 0

#57
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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.
  • 0

#58
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
any suggestions?
  • 0

#59
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
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.
  • 0

#60
aydyty

aydyty

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 116 posts
Windows Vista Home Premium OEMact
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP