Chkdsk: endless boot loop

beginner99

New member
Local time
9:18 AM
Messages
14
When I start the PC i see the windows logo like normal. then chkdsk is activated and runs through. However at the end it goes too fast that I can't read the result if it was successful or not. The screen turns black and then the computer reboots and the process repeat. No blue screen.

Boot disk is recognized properly incl size (checked in BIOS). I tried safe mode but there it just gets stuck while loading and the boot disk (intel g2 80 gb ssd) makes some noise, coil whine.

What are my options to be able to actually read the result from chkdsk?
 

My Computer My Computer

At a glance

Windows Home Premium 64bit
OS
Windows Home Premium 64bit
Boot feorm recovery environment, or advanced boot options->repair computer->"command prompt".
Perform a chkdsk/f command there
 

My Computer My Computer

At a glance

Microsoft Windows 7 Home Premium 64-bits 7601...Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz4,00 GBATI Mobility Radeon HD 5400 Series
Computer type
Laptop
Computer Manufacturer/Model Number
ACER ASPIRE 5742G
OS
Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
CPU
Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz
Motherboard
Acer Aspire 5742G
Memory
4,00 GB
Graphics Card(s)
ATI Mobility Radeon HD 5400 Series
Sound Card
(1) AMD High Definition Audio Device (2) Realtek High Defi
Screen Resolution
1366 x 768 x 32 bits (4294967296 colors) @ 60 Hz
Hard Drives
WDC WD5000BEVT-22ZAT0
Boot feorm recovery environment, or advanced boot options->repair computer->"command prompt".
Perform a chkdsk/f command there

I get following error (translated so english wording might be different):

Indexentry .nbattrs in index $130 of the file 274341 will be deleted

Then just on the next line:

Unknown error <696e647863686b2e e0b>.
The protocoled messages could not be transferred to the event protocol. Status: 50

EDIT:

starting safe mode allows block when \Windows\system32\DRIVERS\CLASSPNP.sys was loaded
 

My Computer My Computer

At a glance

Windows Home Premium 64bit
OS
Windows Home Premium 64bit
FYI: Was not able to solve this. It clearly was an issue with a broken Windows install and not defective hardware. My OS ran on an Intel G2 SSD and it is somewhat known that unexpected power loss can lead to drive corruption. Combing this with the fact that at there currently are renewing "utilites" (natural gas, power,...) to on the whole street this seem the most believable interpretation of what happened. I re-imaged to an old backup from last November. Note that this is only the OS, so that is not that much of an issue expect for having to install some updates.
 

My Computer My Computer

At a glance

Windows Home Premium 64bit
OS
Windows Home Premium 64bit
Back
Top