Sign in with
Sign up | Sign in
Your question

BSOD 0x00000024

Last response: in Windows 7
November 9, 2012 3:15:59 AM

I'm having a problem I cannot seem to fix at all. I'll provide the backstory and what steps I've tried to take to resolve the problem, but I'm literally at a place where I don't know what to do. My ultimate end goal is to just recover personal files from my old hard drive and that's it. I don't care how I access that drive, I just need to access it. The problem is I can't no matter how hard I try.

So a week ago I was having problems with my computer. Lots of blue screen errors (unfortunately I don't have those numbers anymore) and even after try to do chkdsk, running repair programs, defragging, etc., nothing seemed to help. I had a 1TB HDD partitioned into two sections. I backed up my personal files to the second partition (the one without Windows) and then tried to do a repair of the Windows installation. That didn't help, so I just wiped that first partition and did a fresh install of Windows. Everything seemed to be working great, no errors, no BSOD, nothing. So I moved back my personal files to the partition with windows on it (my second partition is where I hold all my games) and called it a night after I had gotten everything back to normal.

The next day my computer is on and it suddenly just turns itself off. When I restarted it I got a blue screen error that flashed on my screen and immediately rebooted the computer. When it tried the second time I got another BSOD, this one giving me the error of 0x00000024. I tried booting last known good config, safe mode, disk repair... seems no options can get me back into Windows.

I figured I'd boot up using the Windows 7 CD that I have, but after it loads the files and then shows the windows icon as it's booting the cd, I get the exact same BSOD. I can't understand it... how can I not even load the CD?? Just for kicks I unplugged the SATA connection to my HDD and restarted the computer... the Windows CD loaded just fine. Plugged the HDD back in, BSOD whether trying to boot the disk or the CD.

I thought there was maybe something corrupted with the Windows installation on the disk, and I was due for a computer upgrade anyways, so I ended up replacing my motherboard, new CPU, new RAM, new CD drive, two new SSDs... basically everything in my computer changed except for the case and my graphics card.

After I hook up all the hardware, I purposefully leave the old HDD unplugged. I install Windows on my new system no problem. Everything is working great on it (typing from it now). However, if I shut off the computer and plug in my old HDD (with the intent to pull the personal files/data from it) I get the EXACT same BSOD, whether I try to boot to my new Windows installation on my SSD or from the Windows 7 CD. I triple checked and my system is NOT trying to start from the old Windows installation on the HDD. But if it is plugged in I cannot get my system to start at all. I unplug the drive and everything works beautifully.

I honestly don't know what to do and I'm freaking out that I've lost years of pictures, various files, graphic design projects, etc... I know it's my own fault for not having a proper backup, but I really need some help. I tried booting up the computer and then just plugging in the old HDD while the comp is running, but nothing happens and I can't get it to show. However, the drive IS visible in BIOS, so I know the system knows it's there. Please someone tell me I have a way of pulling the data from this disk... I'm desperate.

More about : bsod 0x00000024

a b $ Windows 7
November 9, 2012 4:41:36 AM

You can recover your files from the old hard drive but you have to be able to connect it to the computer in some fashion and you say that when you do you get the BSOD. There is obvioudly something wrong with the old hard drive that makes your computer instantly BSOD
By any chance did you ever use different cables to connect the hard drive ?
This may be a long shot and maybe not work but at the moment it's all I can come up with. If you get an external enclosure that connects to your computer by usb it wouldd change the connecton type and maybe give you a chance to get some files off and after you could get another hard drive and use the external enclosure as a backup drive.
November 9, 2012 4:49:14 AM

Ha! Your solution was actually something I was JUST thinking of. Unfortunately it's late here and all the stores are closed. I'll have to run to a store tomorrow to grab an adapter.

The problem I have right now is I can't start up Windows with the drive plugged in, and I can't get it to be recognized by Windows if I plug it in after Windows is already running. So my thought was turning it into an external drive by getting a SATA to USB adapter w/ an adapter to plug power into an external source and seeing if the computer will recognize it that way.

I could care less about the drive... I just want some way to recognize it while Windows is running so I can extract the data I want from it.
Related resources
a b $ Windows 7
November 9, 2012 4:52:30 AM

I understand and that's what I was trying to think of for a way to get the drive connected.Hope it works for you , if not post back and we'll see if there is another way.
November 9, 2012 4:54:56 AM

I'll post asap tomorrow once I am able to try this out. Thank you for the advice!
a b $ Windows 7
November 9, 2012 5:13:55 AM

If you set the DVD drive as the primary boot device, then and insert a bootable DVD, connect the bad HDD, and start, does the system boot from the DVD?
November 9, 2012 12:28:33 PM

Alexoiu, the system won't start that way. I'll set my DVD drive as primary boot, insert the Windows CD and then try and boot up the system (with that bad HDD plugged in). It will go through the process of loading the windows files, but the second it brings me to the part where it show the windows logo "forming" that is when I get the BSOD.

It goes to BSOD on that exact moment whether I'm trying to boot up normally or trying to boot up from the windows cd.

November 9, 2012 11:44:53 PM

I bought the adapter and it did show up in the list of Hard Drives in My Computer. Unfortunately when I click on it it says I have to format in order to access (which I won't do obviously). I'm burning a Knoppix Linux Live CD to try and boot from it and pull the files that way now that I know I can access the drive externally. I will update my progress after I try this (and the CD just finished burning so time to boot!)
November 10, 2012 12:26:57 AM

So I can't boot the CD... well, it boots but my screen goes all haywire after it loads linux. I can hear linux working but the screen shows a jumbled white/black screen. The only other time I've ever seen that is when something has gone wrong with my graphics card. But my graphics card is fine and it only does it trying to boot that linux cd...
November 10, 2012 12:27:52 AM

This is AFTER linux has completed it's loading process. Almost like the display options are getting messed up when trying to use Linux.
November 10, 2012 1:18:39 AM

I setup a PartedMagic Linux CD since Knoppix was giving me so much trouble. Booted up in the PartedMagic CD no problem. Finally I thought I was making some progress...

Accessing the File Manager I could view all my other drives, but when I clicked on the bad HDD it gave me an error and wouldn't let me access the drive. I ran the disk health program and it reported back NO errors on that drive... it said everything was running great. So here I am posting this trying to figure out what I'm doing wrong.

First, yes it booted successfully and it was done via CD.

Here's the device info from Disk Health:

  1. smartctl 6.0 2012-10-10 r3643 [i686-linux-3.5.6-pmagic] (local build)
  2. Copyright (C) 2002-12, Bruce Allen, Christian Franke,
  5. Model Family: Western Digital AV-GP (AF)
  6. Device Model: WDC WD10EURS-630AB1
  7. Serial Number: WD-WCAV5R502016
  8. LU WWN Device Id: 5 0014ee 205b15a2d
  9. Firmware Version: 80.00A80
  10. User Capacity: 1,000,204,886,016 bytes [1.00 TB]
  11. Sector Sizes: 512 bytes logical, 4096 bytes physical
  12. Device is: In smartctl database [for details use: -P show]
  13. ATA Version is: ATA8-ACS (minor revision not indicated)
  14. SATA Version is: SATA 2.6, 3.0 Gb/s
  15. Local Time is: Fri Nov 9 19:05:32 2012 UTC
  16. SMART support is: Available - device has SMART capability.
  17. SMART support is: Enabled
  20. SMART overall-health self-assessment test result: PASSED
  22. General SMART Values:
  23. Offline data collection status: (0x80) Offline data collection activity
  24. was never started.
  25. Auto Offline Data Collection: Enabled.
  26. Self-test execution status: ( 0) The previous self-test routine completed
  27. without error or no self-test has ever
  28. been run.
  29. Total time to complete Offline
  30. data collection: (19800) seconds.
  31. Offline data collection
  32. capabilities: (0x7b) SMART execute Offline immediate.
  33. Auto Offline data collection on/off support.
  34. Suspend Offline collection upon new
  35. command.
  36. Offline surface scan supported.
  37. Self-test supported.
  38. Conveyance Self-test supported.
  39. Selective Self-test supported.
  40. SMART capabilities: (0x0003) Saves SMART data before entering
  41. power-saving mode.
  42. Supports SMART auto save timer.
  43. Error logging capability: (0x01) Error logging supported.
  44. General Purpose Logging supported.
  45. Short self-test routine
  46. recommended polling time: ( 2) minutes.
  47. Extended self-test routine
  48. recommended polling time: ( 228) minutes.
  49. Conveyance self-test routine
  50. recommended polling time: ( 5) minutes.
  51. SCT capabilities: (0x3035) SCT Status supported.
  52. SCT Feature Control supported.
  53. SCT Data Table supported.
  55. SMART Attributes Data Structure revision number: 16
  56. Vendor Specific SMART Attributes with Thresholds:
  58. 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
  59. 3 Spin_Up_Time 0x0027 194 190 021 Pre-fail Always - 6283
  60. 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 719
  61. 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
  62. 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
  63. 9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 7488
  64. 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
  65. 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
  66. 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 707
  67. 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 180
  68. 193 Load_Cycle_Count 0x0032 126 126 000 Old_age Always - 222403
  69. 194 Temperature_Celsius 0x0022 114 083 000 Old_age Always - 33
  70. 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
  71. 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
  72. 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
  73. 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
  74. 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
  76. SMART Error Log Version: 1
  77. No Errors Logged
  79. SMART Self-test log structure revision number 1
  80. Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
  81. # 1 Short offline Completed without error 00% 7487 -
  83. SMART Selective self-test log data structure revision number 1
  85. 1 0 0 Not_testing
  86. 2 0 0 Not_testing
  87. 3 0 0 Not_testing
  88. 4 0 0 Not_testing
  89. 5 0 0 Not_testing
  90. Selective self-test flags (0x0):
  91. After scanning selected spans, do NOT read-scan remainder of disk.
  92. If Selective self-test is pending on power-up, resume after 0 minute delay.

And the fdisk -l output:

  1. Welcome - Parted Magic (Linux 3.5.6-pmagic)
  3. root@PartedMagic:~# fdisk -l
  5. Disk /dev/sda: 240.1 GB, 240057409536 bytes
  6. 255 heads, 63 sectors/track, 29185 cylinders, total 468862128 sectors
  7. Units = sectors of 1 * 512 = 512 bytes
  8. Sector size (logical/physical): 512 bytes / 512 bytes
  9. I/O size (minimum/optimal): 512 bytes / 512 bytes
  10. Disk identifier: 0x3f2e39b5
  12. Device Boot Start End Blocks Id System
  13. /dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
  14. /dev/sda2 206848 468858879 234326016 7 HPFS/NTFS/exFAT
  16. Disk /dev/sdb: 120.0 GB, 120034123776 bytes
  17. 255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
  18. Units = sectors of 1 * 512 = 512 bytes
  19. Sector size (logical/physical): 512 bytes / 512 bytes
  20. I/O size (minimum/optimal): 512 bytes / 512 bytes
  21. Disk identifier: 0x3f2e39cd
  23. Device Boot Start End Blocks Id System
  24. /dev/sdb1 2048 234438655 117218304 7 HPFS/NTFS/exFAT
  25. Note: sector size is 4096 (not 512)
  26. fdisk: unable to seek on /dev/sdc: Invalid argument
  27. root@PartedMagic:~#

When trying to access the bad HDD via File Manager, here is the error I get:

Run: Mount/dev/sdc1
Status: Finished with error (exit status 1)

udevil: error64: unable to determine device fstype - specify with -t