Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

0xc0000185 and other errors at after "Welcome" Screen


  • Please log in to reply
12 replies to this topic

#1 Seraph06

Seraph06

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:09 PM

Posted 22 May 2012 - 07:44 AM

I need Help!
My Laptop recently loads too long at startup and gives alot of errors about startup applications failed to start.
When I leave my laptop to load, after about 10-20 minutes, it goes BSoD. It's very unresponsive while it's trying to load and explorer.exe crashes everytime I'm about to do something.
I'd like to notes though that when It survives the startup phase even with some errors but became responsive, it runs smoothly and I can accessed every files and folders on the Laptop.

Please help me determine and fix the problem Thank You!

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:09 AM

Posted 22 May 2012 - 07:58 AM

1) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

2) What happens when you boot to safe mode?

3) Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 Seraph06

Seraph06
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:09 PM

Posted 22 May 2012 - 09:37 AM

1. Nothing new, just one day it goes through a major slowdown in starting up.
2. "Help & Support" Comes up then hangs. As well as Explorer.exe seems to be slow and goes Unresponsive after a while of a little browsing. And After some time in safe mode, it will suddenly restart which I haven't seen the reason why yet.

I'm sorry but it seems I can't run the software you gave right now because I'm really having a hard time accessing my laptop even in safe mode.
But I'll attach latest dump files I got when it ran smoothly yesterday(after enduring the errors and restarts).

***Edit***
BTW, i'd like to add that I already experienced this before but my laptop is usable even after the errors of start-up applications but it disappeared when I repasted my GPU and CPU about less than a month ago.

Attached File  Dump Files.zip   70.13KB   1 downloads

Edited by Seraph06, 22 May 2012 - 09:48 AM.


#4 Seraph06

Seraph06
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:09 PM

Posted 22 May 2012 - 09:58 AM

Ok got it


==================================================
Dump File : 052212-29608-01.dmp
Crash Time : 5/22/2012 10:14:23 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`04c51620
Parameter 3 : fffffa80`04c51900
Parameter 4 : fffff800`02d9a510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052212-29608-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 271,816
==================================================

==================================================
Dump File : 052112-51589-01.dmp
Crash Time : 5/21/2012 11:50:36 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000006
Parameter 2 : fffff880`00cfa0e9
Parameter 3 : fffff880`06ff8778
Parameter 4 : fffff880`06ff7fd0
Caused By Driver : CI.dll
Caused By Address : CI.dll+110e9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : CI.dll+110e9
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052112-51589-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,720
==================================================

==================================================
Dump File : 052112-52665-01.dmp
Crash Time : 5/21/2012 5:08:55 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`05dc6b30
Parameter 3 : fffffa80`05dc6e10
Parameter 4 : fffff800`03999510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052112-52665-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,720
==================================================

==================================================
Dump File : 052112-28906-01.dmp
Crash Time : 5/21/2012 1:53:53 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`04c29b30
Parameter 3 : fffffa80`04c29e10
Parameter 4 : fffff800`02d9c510
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\052112-28906-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 271,816
==================================================

==================================================
Dump File : 042212-44819-01.dmp
Crash Time : 4/22/2012 2:19:24 AM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`4000c0c8
Parameter 2 : ffffffff`c0000185
Parameter 3 : 00000000`2c2cb860
Parameter 4 : fffff880`018195cc
Caused By Driver : fvevol.sys
Caused By Address : fvevol.sys+195cc
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042212-44819-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 288,440
==================================================

#5 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:09 AM

Posted 22 May 2012 - 11:01 AM

This could be any number of things. I suggest doing the following:

1) Boot to your Windows 7 DVD and run Startup Repair Options

2) Run a full scan with both your Anti Virus app AND with MalwareBytes

3) Look in Device Manager - are there any yellow or red symbols?

4) Have you recently updated any driver(s)? If so, roll back to the previous version.

5) Run a check on the hd ( To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.)

6) Check the ram ( download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.)

7) If you are using BitLocker, disable it (http://www.techtalkz.com/windows-7/515981-enable-disable-bitlocker-drive-encryption-windows-7-a.html)

Edited by Allan, 22 May 2012 - 11:03 AM.


#6 Seraph06

Seraph06
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:09 PM

Posted 22 May 2012 - 11:06 PM

ok I think the Check Disk fixed it. Currently trying to find the log of the Check Disk.
Gonna check it more after I recheck back start up applications I unchecked before and post the result here if it really is running fine now.
Btw, does that mean my HDD dying?

Thanks for the Help!

****EDIT*****
I forgot to note:
Done before Check Disk
1. Tried Startup Repair through Advanced Boot(don't have the installer CD atm), and found no errors.
2. Done Memtest and passed.
3. There is one yellow symbol on Device Manager, it's on USB Controller

Edited by Seraph06, 23 May 2012 - 01:11 AM.


#7 Seraph06

Seraph06
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:09 PM

Posted 22 May 2012 - 11:18 PM

Ok here's the log

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
392704 file records processed. File verification completed.
546 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
Read failure with status 0xc0000185 at offset 0x97c000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x96e000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x97c000 for 0x1000 bytes.
The USA check value, 0x73, at block 0x1 is incorrect.
The expected value is 0x2.
The multi-sector header signature for VCN 0xe of index $I30
in file 0xd78 is incorrect.
42 41 41 44 28 00 09 00 a6 de 4b 05 00 00 00 00 BAAD(.....K.....
0d 00 00 00 00 00 00 00 28 00 00 00 e8 07 00 00 ........(.......
Correcting error in index $I30 for file 3448.
The index bitmap $I30 in file 0xd78 is incorrect.
Correcting error in index $I30 for file 3448.
The down pointer of current index entry with length 0x78 is invalid.
9f 94 00 00 00 00 01 00 78 00 5e 00 01 00 00 00 ........x.^.....
78 0d 00 00 00 00 01 00 d6 16 7e f5 44 04 ca 01 x.........~.D...
00 39 da e5 27 04 ca 01 c1 30 e0 0f ba a4 cb 01 .9..'....0......
d6 16 7e f5 44 04 ca 01 00 20 00 00 00 00 00 00 ..~.D.... ......
00 16 00 00 00 00 00 00 20 00 00 00 00 00 00 00 ........ .......
0e 00 66 00 69 00 6e 00 67 00 65 00 72 00 2e 00 ..f.i.n.g.e.r...
65 00 78 00 65 00 2e 00 6d 00 75 00 69 00 01 00 e.x.e...m.u.i...
ff ff ff ff ff ff ff ff b1 94 00 00 00 00 01 00 ................
78 00 60 00 01 00 00 00 78 0d 00 00 00 00 01 00 x.`.....x.......
Sorting index $I30 in file 3448.
Read failure with status 0xc0000185 at offset 0x37f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x37f000 for 0x1000 bytes.
Read failure with status 0xc0000185 at offset 0x37f000 for 0x1000 bytes.
The index buffer at VCN 0x0 of index $I30 in file 0x1f851
cannot be read.
Correcting error in index $I30 for file 129105.
The index bitmap $I30 in file 0x1f851 is incorrect.
Correcting error in index $I30 for file 129105.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 c3 0b 19 d7 ab ca 01 ................
00 c3 0b 19 d7 ab ca 01 48 1c 63 f6 28 cd cb 01 ........H.c.(...
Sorting index $I30 in file 129105.
502020 index entries processed. Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file eventvwr.msc (23595) into directory file 3448.
Recovering orphaned file EventViewer_EventDetails.xsl (31585) into directory file 3448.
Recovering orphaned file eudcedit.exe.mui (38030) into directory file 3448.
Recovering orphaned file EventCreate.exe.mui (38031) into directory file 3448.
Recovering orphaned file eventvwr.exe.mui (38032) into directory file 3448.
Recovering orphaned file evr.dll.mui (38033) into directory file 3448.
Recovering orphaned file expand.exe.mui (38034) into directory file 3448.
Recovering orphaned file explorer.exe.mui (38036) into directory file 3448.
Recovering orphaned file explorerframe.dll.mui (38037) into directory file 3448.
Recovering orphaned file extrac32.exe.mui (38039) into directory file 3448.
Recovering orphaned file faultrep.dll.mui (38040) into directory file 3448.
Recovering orphaned file fc.exe.mui (38041) into directory file 3448.
Recovering orphaned file fde.dll.mui (38042) into directory file 3448.
Recovering orphaned file fdeploy.dll.mui (38043) into directory file 3448.
Recovering orphaned file filemgmt.dll.mui (38044) into directory file 3448.
Recovering orphaned file find.exe.mui (38045) into directory file 3448.
Recovering orphaned file findstr.exe.mui (38046) into directory file 3448.
Recovering orphaned file RESOUR~1 (129063) into directory file 129105.
Recovering orphaned file Resources (129063) into directory file 129105.
Recovering orphaned file VSShell (129106) into directory file 129105.
Recovering orphaned file SQLMAN~1.DLL (129169) into directory file 129105.
Recovering orphaned file SqlManager.dll (129169) into directory file 129105.
Recovering orphaned file schemas (129261) into directory file 129105.
Recovering orphaned file BATCHP~1.DLL (129306) into directory file 129105.
Recovering orphaned file batchparser.dll (129306) into directory file 129105.
Recovering orphaned file MICROS~1.DLL (129313) into directory file 129105.
Recovering orphaned file Microsoft.SqlServer.Management.PSProvider.dll (129313) into directory file 129105.
Recovering orphaned file MICROS~2.DLL (129314) into directory file 129105.
Recovering orphaned file Microsoft.SqlServer.Management.PSSnapins.dll (129314) into directory file 129105.
Recovering orphaned file SQLPRO~1.PS1 (129315) into directory file 129105.
Recovering orphaned file SQLProvider.Format.ps1xml (129315) into directory file 129105.
Recovering orphaned file SQLPRO~2.PS1 (129316) into directory file 129105.
Recovering orphaned file SQLProvider.Types.ps1xml (129316) into directory file 129105.
Recovering orphaned file SQLPS.exe (129317) into directory file 129105.
Recovering orphaned file SEMMAP.DLL (129319) into directory file 129105.
Recovering orphaned file sqlresld.dll (129324) into directory file 129105.
Recovering orphaned file SQLRES~1.DLL (129326) into directory file 129105.
Recovering orphaned file SqlResourceLoader.dll (129326) into directory file 129105.
Recovering orphaned file SQLSCM.DLL (129328) into directory file 129105.
Recovering orphaned file SQLSVC.DLL (129330) into directory file 129105.
Recovering orphaned file en (129669) into directory file 129105.
Recovering orphaned file MICROS~1.INS (129812) into directory file 129105.
Recovering orphaned file Microsoft.SqlServer.Management.PSProvider.InstallLog (129812) into directory file 129105.
Recovering orphaned file MICROS~2.INS (129815) into directory file 129105.
Recovering orphaned file Microsoft.SqlServer.Management.PSProvider.InstallState (129815) into directory file 129105.
Recovering orphaned file MICROS~3.INS (130022) into directory file 129105.
Recovering orphaned file Microsoft.SqlServer.Management.PSSnapins.InstallLog (130022) into directory file 129105.
37 unindexed files scanned. Recovering orphaned file MICROS~4.INS (130023) into directory file 129105.
Recovering orphaned file Microsoft.SqlServer.Management.PSSnapins.InstallState (130023) into directory file 129105.
0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
392704 file SDs/SIDs processed. CHKDSK is compacting the security descriptor stream
Cleaning up 2417 unused security descriptors.
54659 data files processed. CHKDSK is verifying Usn Journal...
36083280 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x5fb000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x60a000 for 0x1000 bytes.
Windows replaced bad clusters in file 39
of name \Windows\System32\winevt\Logs\MI01EB~1.EVT.
Read failure with status 0xc0000185 at offset 0x530000 for 0x3000 bytes.
Read failure with status 0xc0000185 at offset 0x531000 for 0x1000 bytes.
Windows replaced bad clusters in file 58509
of name \Users\Sky\AppData\Roaming\Dropbox\config.dbx.
Read failure with status 0xc0000185 at offset 0x109050000 for 0x9000 bytes.
Read failure with status 0xc0000185 at offset 0x109056000 for 0x1000 bytes.
Windows replaced bad clusters in file 97462
of name \PROGRA~2\COMMON~1\MICROS~1\THEMES14\AXIS\THMBNAIL.PNG.
392688 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
11783334 free clusters processed. Free space verification is complete.
Adding 5 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

204697599 KB total disk space.
156920920 KB in 276573 files.
141860 KB in 54662 indexes.
20 KB in bad sectors.
501459 KB in use by the system.
65536 KB occupied by the log file.
47133340 KB available on disk.

4096 bytes in each allocation unit.
51174399 total allocation units on disk.
11783335 allocation units available on disk.

Internal Info:
00 fe 05 00 eb 0d 05 00 83 e0 08 00 00 00 00 00 ................
54 0a 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 T...,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

#8 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:09 AM

Posted 23 May 2012 - 06:08 AM

3. There is one yellow symbol on Device Manager, it's on USB Controller


Go to the website of your laptop manufacturer and download and install the chipset driver.

#9 Seraph06

Seraph06
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:09 PM

Posted 25 May 2012 - 08:02 AM

The only Chipset I found is "Intel 5 Chipset" is that the one? And it's from 2 years ago. I don't think there's later than it.

Anyway is my HDD dying or it's normal for this to happen?

Thanks for All the help!! I think it's fixed for now.

#10 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:09 AM

Posted 25 May 2012 - 08:23 AM

If that's the only one then yes, you should install it. Then look in device manager to see if there's still an error. As for the hd, no way to tell. But EVERYONE should have recent backups of their data and in my opinion everyone should use disc imaging software on a regular basis - then you won't have to worry about the hd dying and losing everything.

#11 Seraph06

Seraph06
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:09 PM

Posted 26 May 2012 - 11:57 AM

Installed it, but the yellow symbol was still there. It's On Other Devices>USB Controller
Is this gonna affect something?

#12 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:09 AM

Posted 26 May 2012 - 02:07 PM

I guess not. If everything's working okay let's not worry about it.

#13 Allan

Allan

  • BC Advisor
  • 8,630 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:12:09 AM

Posted 26 May 2012 - 02:08 PM

I guess not. If everything's working okay let's not worry about it.

What you can do is right click on that item in device manager, uninstall it, and reboot.

Edited by Allan, 26 May 2012 - 02:08 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users