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

Computer Freezes when I try to Defrag or use ChkDsk


  • Please log in to reply

#1
lucid_

lucid_

    New Member

  • Member
  • Pip
  • 7 posts
I have been trying over and over trying to use ChkDsk and to defrag my computer and each time it freezes. When I run chkdsk in the command prompt, i have to restart the computer and then it works fine. but when i right click in my computer on the C: drive and go to check for errors, it freezes up. Same for when I try to defrag this disk. I even tried using the program "Smart Defrag" and that freezes the computer too. Any help?
  • 0

Advertisements


#2
isimaster

isimaster

    Member

  • Member
  • PipPipPip
  • 225 posts
Boot into safe mode. Try the chkdsk or defrag.
let me know if you have the same problem.
  • 0

#3
lucid_

lucid_

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
I have tried the defrag in safemode and it froze, but i never tried the chkdsk in safemode. But i was able to run the chkdsk as the computer started up but it said it only had 3 parts, while the chkdsk when you right click on the c: drive has for parts, and btw it freezes when its about %80 with the 4th and final part
  • 0

#4
isimaster

isimaster

    Member

  • Member
  • PipPipPip
  • 225 posts
During stage 4, Chkdsk verifies all clusters in use; during stage 5, Chkdsk verifies unused clusters.

The percent complete that Chkdsk displays during stage 4 is based on the percent of used clusters that are checked. The percent complete that Chkdsk displays during stage 5 is the percent of unused clusters that are checked. Used clusters typically take longer to check than unused clusters, so stage 4 lasts longer than stage 5 on a volume with equal amounts of used and unused clusters. For a volume with mostly unused clusters, stage 5 takes longer than stage 4.

How long have you let this run?
I would back up your system ASAP!!
  • 0

#5
lucid_

lucid_

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Generally its about 10 to 15 minutes in before it freezes. The way i know its frozen is the clock in the bottom right corner is stuck.

I just tried backing up. Great. I set it up to back up and took a nap. When I woke up, the computer was at the login screen. I dont get why that happens. My computer always crashes with a blue screen. But unfortunantly the blue screen is only up for about 2 seconds, then it reboots the computer. I saved the error log. it is:

BCCode : 77 BCP1 : 00000001 BCP2 : 00000000 BCP3 : 00000000
BCP4 : BA4F7D24 OSVer : 5_1_2600 SP : 3_0 Product : 256_1
C:\DOCUME~1\Jimmy\LOCALS~1\Temp\WER4b31.dir00\Mini031909-02.dmp
C:\DOCUME~1\Jimmy\LOCALS~1\Temp\WER4b31.dir00\sysdata.xml


I have also saved another one that I never got around too looking up. Here it is:

BCCode : 1000007f BCP1 : 0000000D BCP2 : 00000000 BCP3 : 00000000
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1

C:\DOCUME~1\Jimmy\LOCALS~1\Temp\WER4ddc.dir00\Mini030409-02.dmp
C:\DOCUME~1\Jimmy\LOCALS~1\Temp\WER4ddc.dir00\sysdata.xml


I will try to back it up again. Any ideas why these problems are happening?
  • 0

#6
lucid_

lucid_

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Well Great. I had the back up going for literally 10 minutes and windows crashed again. Heres the error report:

BCCode : 77 BCP1 : 00000001 BCP2 : 00000000 BCP3 : 00000000
BCP4 : 9EDD4C34 OSVer : 5_1_2600 SP : 3_0 Product : 256_1


C:\DOCUME~1\Jimmy\LOCALS~1\Temp\WERa283.dir00\Mini031909-03.dmp
C:\DOCUME~1\Jimmy\LOCALS~1\Temp\WERa283.dir00\sysdata.xml
  • 0

#7
lucid_

lucid_

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Ok, I was able to packup my harddrive when I put it into safe mode. Still, I don't know why it wouldn't let me in normal mode.
  • 0

#8
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
Download WhoCrashed from my list below. Open the program, click Analyze and post the results with your next post.
  • 0

#9
lucid_

lucid_

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Here you go. thanks for helping out.


Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Thu 3/19/2009 4:11:54 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0x9EDD4C34)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 3/19/2009 1:56:03 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0xBA4F7D24)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 3/19/2009 4:22:58 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xFFFFFFE9, 0x1, 0x805266AA, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 3/5/2009 4:13:37 AM your computer crashed
This was likely caused by the following module: d347bus.sys
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\WINDOWS\system32\drivers\d347bus.sys
product:
company:
description: PnP BIOS Extension



On Wed 3/4/2009 5:16:41 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000BE (0x380097, 0xA296E025, 0xBA4D3DE4, 0xA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 2/26/2009 11:30:39 PM your computer crashed
This was likely caused by the following module: lbd.sys
Bugcheck code: 0x10000050 (0xEA2E4000, 0x0, 0x80582627, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\lbd.sys
product: Ad-Aware
company: Lavasoft AB
description: Boot Driver



On Tue 2/24/2009 11:37:45 PM your computer crashed
This was likely caused by the following module: lbd.sys
Bugcheck code: 0x10000050 (0xE5E3E000, 0x0, 0x80582627, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\lbd.sys
product: Ad-Aware
company: Lavasoft AB
description: Boot Driver



On Tue 2/24/2009 5:32:11 PM your computer crashed
This was likely caused by the following module: lbd.sys
Bugcheck code: 0x10000050 (0xEBCD8000, 0x0, 0x80582627, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\lbd.sys
product: Ad-Aware
company: Lavasoft AB
description: Boot Driver



On Fri 2/20/2009 7:36:18 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBBE6E9AA, 0x980C1AD4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 2/16/2009 2:13:05 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFE00080, 0xFF, 0x1, 0x805287B0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 2/9/2009 7:20:33 PM your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x89D9DDA0, 0x89D9DF14, 0x805D297C)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 1/25/2009 7:31:44 PM your computer crashed
This was likely caused by the following module: atswpwdf.sys
Bugcheck code: 0x100000D1 (0xC48401FF, 0x2, 0x1, 0xA082F3ED)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\atswpwdf.sys
product: Swipe Fingerprint Sensor WDF USB Driver Prototype
company: AuthenTec, Inc.
description: AuthenTec Swipe Sensor WDF USB Driver Prototype



On Sat 12/6/2008 9:14:20 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x77 (0x1, 0x0, 0x0, 0x9201DC20)
Error: KERNEL_STACK_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 11/24/2008 7:37:52 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xFFFFFFEA, 0x1, 0x805266AA, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 11/16/2008 3:05:57 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x100000D0 (0xC0120FBC, 0x2, 0x0, 0x8054821D)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Tue 11/4/2008 6:30:31 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBBE6E910, 0x94FF4AD4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/30/2008 6:29:18 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x10000050 (0x8E2CC000, 0x1, 0xB9D7215E, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 10/30/2008 12:25:42 AM your computer crashed
This was likely caused by the following module: igxpmp32.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xAFE50EE9, 0xBA4FEE2C, 0xBA4FEB28)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\igxpmp32.sys
product: Intel Graphics Accelerator Drivers for Windows NT®
company: Intel Corporation
description: Intel Graphics Miniport Driver



On Sat 10/25/2008 8:13:21 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xFFFFFFE9, 0x1, 0x805266AA, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
  • 0

#10
The Skeptic

The Skeptic

    Trusted Tech

  • Technician
  • 4,075 posts
There are multiple problems with your computer. Most related to the operating system. Some are related to Adaware by Lavasoft and to the fingerprint recognition module.

My opinion is that your best option is to reformat and clean install your system. There are other options like "windows repair" but I doubt if you are going to get a stable system.

Your computer is so unstable that even a backup is a problem at the present state of affairs. I suggest that you follow these instructions to backup your data before formatting:

Download Puppy Linux from my list of links below. Download "puppy 2.16.1 seamonkey fulldrivers.ISO". Burn the ISO file to create a bootable CD. For this purpose you can download BurnCDCC from the links below. It's a very simple tool, used exclusively to burn ISO files.

Insert the disk into the CD/DVD drive and boot the computer. Use the default setting except for choosing screen resolution of 600x800 when given the option to do so. After the program is loaded click the icon that looks like flash disk. This will open the file system and will enable browsing your folders. Find the folders that you want to backup, copy and paste them to another storage device.

If the computer doesn't boot, please set boot order in the BIOS so that the CD drive is first priority boot device.
  • 0

#11
lucid_

lucid_

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Ok, I was able to backup my computer when I put it into safemode. I will try to reinstall windows when I am done with classes since all my classes require a computer. As long as its not a hardware problem its fine, thats all im trying to make sure. Thanks for the help.
  • 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