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

BSOD but not in safe mode


  • Please log in to reply
4 replies to this topic

#1 jitu_jariwala

jitu_jariwala

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:04:18 AM

Posted 07 October 2013 - 04:21 AM

My Dell XPS (win 7 Home premium SP1, 64-bit) is showing blue screen from this morning, but Safe mode working fine. 

When I run Diagnostics, it shows following errors 

Error code 0F00 07FD
Msg. DISK Self- test Read Error

Error code 0F00 065D
Msg. DISK Self- test Read Error

Error code 0F00 0232
Msg. DISK Block 29515392: Interrupt Request(IRQ) did no set in time


after that I have tried 
BlueScreenview
 

Here are reports from it
 

==================================================
Dump File         : 100713-54225-01.dmp
Crash Time        : 07-10-2013 10:42:30: AM
Bug Check String  : CRITICAL_OBJECT_TERMINATION
Bug Check Code    : 0x000000f4
Parameter 1       : 00000000`00000003
Parameter 2       : fffffa80`0cd3d930
Parameter 3       : fffffa80`0cd3dc10
Parameter 4       : fffff800`0498a350
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor         : x64
Crash Address     : ntoskrnl.exe+75c00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\100713-54225-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 07-10-2013 10:47:02: AM
==================================================

==================================================
Dump File         : 090813-153785-01.dmp
Crash Time        : 08-09-2013 10:06:54: AM
Bug Check String  : DRIVER_POWER_STATE_FAILURE
Bug Check Code    : 0x0000009f
Parameter 1       : 00000000`00000003
Parameter 2       : fffffa80`07771a00
Parameter 3       : fffff800`00b9c3d8
Parameter 4       : fffffa80`18d70bd0
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18113 (win7sp1_gdr.130318-1533)
Processor         : x64
Crash Address     : ntoskrnl.exe+75c00
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\090813-153785-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 837,664
Dump File Time    : 08-09-2013 10:34:07: AM
==================================================

 

 



BC AdBot (Login to Remove)

 


#2 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:04:18 AM

Posted 07 October 2013 - 04:38 AM

:welcome: to the Bleeping Computer forum mate.

 

What you are experiencing is Bug check F4  CRITICAL_OBJECT_TERMINATION which is mainly caused by a failing hard drive. Your Dell diagnostic report also confirm a failing hard drive ( is it Windows version ? ). Please backup all the data to an external medium immediately and run Dell boot time diagnostics.

 

1. Press F12 during power on to bring startup menu.

 

2. Select Diagnostic and let it to check the hardware.

 

 



#3 jitu_jariwala

jitu_jariwala
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:04:18 AM

Posted 07 October 2013 - 04:48 AM

Thanks for warm welcome 

I have already done Diagnostic, so I am already taking back up in external drive.

Is there any chance to fix BSOD ?  ( As I have mention earlier I have windows 7 Home premium SP1, 64-bit )



#4 jitu_jariwala

jitu_jariwala
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:04:18 AM

Posted 07 October 2013 - 06:27 AM

After doing bit of research I did run chkdsk /r

now I am writing this from normal mode, it seems my windows is at least working. NO BSOD for 20 minutes 
Here I am posting partial result, of chkdsk 
 

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
 
A disk check has been scheduled.
Windows will now check the disk.    


Cleaning up 86 unused index entries from index $SII of file 9.
Cleaning up 86 unused index entries from index $SDH of file 9.
Cleaning up 86 unused security descriptors.
Security descriptor verification completed.
  35809 data files processed.                                           
 
CHKDSK is verifying Usn Journal...
The USN Journal entry at offset 0x1732de000 and length 0x26fb680 crosses
the page boundary.
The USN Journal entry at offset 0x1732df000 and length 0x26fb6a0 crosses
the page boundary.
The USN Journal entry at offset 0x1732e0000 and length 0x259a108 crosses
the page boundary.
The USN Journal entry at offset 0x1732e1000 and length 0x26fb7a0 crosses
the page boundary.
The USN Journal entry at offset 0x1732e2000 and length 0x26fb680 crosses
the page boundary.
Repairing Usn Journal file record segment.
  33972408 USN bytes processed.                                            
 
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc00000b5 at offset 0xec688000 for 0x3000 bytes.
Read failure with status 0xc00000b5 at offset 0xec68a000 for 0x1000 bytes.
Windows replaced bad clusters in file 28825
of name \Windows\Prefetch\CONHOS~1.PF.
Read failure with status 0xc00000b5 at offset 0x323c9000 for 0xe000 bytes.
Read failure with status 0xc00000b5 at offset 0x323ce000 for 0x1000 bytes.
Windows replaced bad clusters in file 61651
of name \Windows\Prefetch\FACEBO~1.PF.
  261872 files processed.                                                
 
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  5084997 free clusters processed.                                        
 
Free space verification is complete.
Adding 3 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.
 
                    


 


#5 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:04:18 AM

Posted 07 October 2013 - 07:06 AM

 

Read failure with status 0xc00000b5 at offset 0x323c9000 for 0xe000 bytes.

Read failure with status 0xc00000b5 at offset 0x323ce000 for 0x1000 bytes.

 

There is bad sectors in your hard drive surface and it is failing slowly. Running check disk only fixes file system corruption caused by the bad sectors. Actual bad sectors will be there and slowly begin to infect neighbor sectors. Continue to use this hard drive will make the system unstable. Only permanent way to fix your issue is to replace the drive.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users