problem event name startup repair offline - slightly different problem

[perkroyale]

Hi,
Hoping somebody can help with this problem which despite trawling through these very helpful forums & tutorials, I have been unable to resolve. I have tried to include all the information possible although I am relatively new to this field so my terminology is probably not completely accurate. If any further information would be useful I would be glad to post it.

My unmodified msi u130 netbook is about 18 months old and has been working perfectly.
Yesterday when performing a standard operation online (uploading an image to a facebook event) the screen went black and the laptop instantly powered down. This is the first time the system has spontaneously powered itself down.
I restarted the system, which loaded as normal, I managed to get back online (although with less programs running) and next time I tried to upload the same image again on the same website this time the screen went white and the same instant power down occurred. I also experienced an unusual (hot or burning) smell coming from the netbook. Having replaced my screen a few weeks earlier I opened up the case to have a look to see if anything inside appeared burnt out but was unable to see any visible difference, nor any obvious hardware issue.

Since reassembling, which I am confident I did correctly (as I am about the previous screen installation) upon turning the computer on I get the usual pre-boot manufacturers screen (black with msi logo, with options to run setup, boot menu, recovery menu). Windows then appears to start to load as normal for about 1 second then I get a blue screen for a fraction of a second and the computer turns off instantly again.

Upon restart I get the black screen advising me to choose startup repair or start windows normally. when I choose start windows normally it loops back to the same condition described above.

I followed the startup repair process detailed in the thread:

Problem Event Name: StartupRepairOffline - Microsoft Answers

Startup repair seems to work as it should (blue windows environment, moveable mouse cursor but always results in the window with the message "Startup repair cannot repair this computer automatically"

the problem details showed:

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21201003
Problem Signature 05: AutoFailover
Problem Signature 06: 2
Problem Signature 07: NoBootCause
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

which is subtley different to the problem log detailed in the above thread ie. problem signature 04 is 21201003. I have also noticed that the number after the ":" in the line 'Problem Signature 06:' has been increasing as i have repeatedly attempted to rerun startup repair. The full problem details now state

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21201003
Problem Signature 05: AutoFailover
Problem Signature 06: 11
Problem Signature 07: NoBootCause
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

since reaching this apparent stalemate I have followed fix tutorials for the startup repair infinite loop recovery thread

http://www.sevenforums.com/tutorials/139576-startup-repair-infinite-loop-recovery.html
to no avail

I have run through all the options in system recovery. I have already described above the results from running startup repair.
system restore and system image recovery won't work as I never created a restore point or system iso.
The windows memory diagnostic ran through its two test passes detecting no problems the two times i have run it, each time resulting in an eventual restart and return to the startup repair screen.
seemingly out of options I have tried the reinstall windows option wich looked like it was working then informed me that I didn't have enough disk space (which seems correct as I have been close to a full hard drive for ages)


I have read up as much as I can on other possible solutions to this but have been unable to find a fix. . .

So, is this as i suspect, a hardware problem? if so what could have broken that would mean that the screen, mouse and hard drive still work?(using command prompt i can find files I know should be there using the 'dir' command) is it worth replacing? Is there a software fix or anything i can try? Is there a way to recover my files safely (gigabytes of music - I am a DJ by profession) without recourse to buying a new computer and a USB caddy for the HDD, eg: can I copy to memory stick using commands in command prompt (my attempts have been unsuccessful, inserting the memory stick freezes the system and i have to restart)?Is there any way of salvaging a working system from this at expense of lost data?


Hope somebody can help!
Thanks

 

[MvdB]

Hi Perkroyale, welcome to SF. It seems nobody has seen this post yet. Is it still valid? Please post back if so and I'll see what I can do to help.

 

[radryan]

I am having same issue but I have a samsung r580 jbb2 us i3 core(1st gen), a Seagate momentus ct hybrid had(new), 4 gig ddr ram. Windows gets to starting windows and bout half of logo then bod's with this stop code- stop: 0x0000007b (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000) - And as other guy said startup repair says exactly as he explained. I WOULD LOVE SOME HELP. ASAP IF YOU CAN.

 

[radryan]

Sorry its a Seagate momentus XT not ct

 

[saffy49]

Hi,
Hoping somebody can help with this problem which despite trawling through these very helpful forums & tutorials, I have been unable to resolve. I have tried to include all the information possible although I am relatively new to this field so my terminology is probably not completely accurate. If any further information would be useful I would be glad to post it.

My unmodified msi u130 netbook is about 18 months old and has been working perfectly.
Yesterday when performing a standard operation online (uploading an image to a facebook event) the screen went black and the laptop instantly powered down. This is the first time the system has spontaneously powered itself down.
I restarted the system, which loaded as normal, I managed to get back online (although with less programs running) and next time I tried to upload the same image again on the same website this time the screen went white and the same instant power down occurred. I also experienced an unusual (hot or burning) smell coming from the netbook. Having replaced my screen a few weeks earlier I opened up the case to have a look to see if anything inside appeared burnt out but was unable to see any visible difference, nor any obvious hardware issue.

Since reassembling, which I am confident I did correctly (as I am about the previous screen installation) upon turning the computer on I get the usual pre-boot manufacturers screen (black with msi logo, with options to run setup, boot menu, recovery menu). Windows then appears to start to load as normal for about 1 second then I get a blue screen for a fraction of a second and the computer turns off instantly again.

Upon restart I get the black screen advising me to choose startup repair or start windows normally. when I choose start windows normally it loops back to the same condition described above.

I followed the startup repair process detailed in the thread:

Problem Event Name: StartupRepairOffline - Microsoft Answers

Startup repair seems to work as it should (blue windows environment, moveable mouse cursor but always results in the window with the message "Startup repair cannot repair this computer automatically"

the problem details showed:

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21201003
Problem Signature 05: AutoFailover
Problem Signature 06: 2
Problem Signature 07: NoBootCause
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

which is subtley different to the problem log detailed in the above thread ie. problem signature 04 is 21201003. I have also noticed that the number after the ":" in the line 'Problem Signature 06:' has been increasing as i have repeatedly attempted to rerun startup repair. The full problem details now state

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 21201003
Problem Signature 05: AutoFailover
Problem Signature 06: 11
Problem Signature 07: NoBootCause
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

since reaching this apparent stalemate I have followed fix tutorials for the startup repair infinite loop recovery thread

http://www.sevenforums.com/tutorials/139576-startup-repair-infinite-loop-recovery.html
to no avail

I have run through all the options in system recovery. I have already described above the results from running startup repair.
system restore and system image recovery won't work as I never created a restore point or system iso.
The windows memory diagnostic ran through its two test passes detecting no problems the two times i have run it, each time resulting in an eventual restart and return to the startup repair screen.
seemingly out of options I have tried the reinstall windows option wich looked like it was working then informed me that I didn't have enough disk space (which seems correct as I have been close to a full hard drive for ages)


I have read up as much as I can on other possible solutions to this but have been unable to find a fix. . .

So, is this as i suspect, a hardware problem? if so what could have broken that would mean that the screen, mouse and hard drive still work?(using command prompt i can find files I know should be there using the 'dir' command) is it worth replacing? Is there a software fix or anything i can try? Is there a way to recover my files safely (gigabytes of music - I am a DJ by profession) without recourse to buying a new computer and a USB caddy for the HDD, eg: can I copy to memory stick using commands in command prompt (my attempts have been unsuccessful, inserting the memory stick freezes the system and i have to restart)?Is there any way of salvaging a working system from this at expense of lost data?


Hope somebody can help!
Thanks

and myself have exactly the same problem on my daughters lap top please help!!