Solved BSOD with buzzing sounds, error 0x00007A

[elroikendo]

Hello guys im new here, im here seeking for help
My laptop got BSOD that happens everyday and almost hourly.
BSOD message is :
KERNEL_DATA_INPAGE_ERROR
Stop 0x00007A (
Physical Dump Failed with status 0XC0000010
(sorry my editor seem to stuck on Italy)

Sometime the BSOD message is instead :
KERNEL_DATA_INPAGE_ERROR
Stop 0x00007A
ACPI.sys - Address fffff88000ff3818 base at fffff88000FA5000, Date stamp 4ce79294
Physical Dump Failed with stats 0xC0000009C
(sometime it also NTFS.sys)

Also my laptop got short buzz/beep sound every once in a while and then a long buzz sound then bsod come. After the BSOD come the buzz stops.

I have tried googling but i cant find anyone with similar case

no minidump can be found

My OS is Windows 7 Home Basic 64-bit
It was genuine pre-installed when i bought the laptop

my System :
intel i3 M380
ATI mobility 550v
4 gb RAM @1033 mhz
WDC-WD3200BEKT-75KA9T0 HDD (I assume HDD might be causing it )

the laptop is DELL inspiron n4010

Here is the link for buzzing sound if u wuld like to hear it
https://mail.google.com/mail/?ui=2&ik=91bf44a975&view=att&th=1383c901fc7d14b7&attid=0.1&disp=safe&zw

EDIT :
Done CHKDSK and found 1 error Volume Bitmap, corrected and still happening
Windows Memory Diagnostic says my memory is fine

 

[writhziden]

The perfmon report does little good without all the other crash report information. Please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to help us help you.

 

[elroikendo]

Thanks for the reply Here is the other file View attachment 219147

 

[writhziden]

Your crashes are not generating .dmp files, which make them difficult to debug. However, the BugCheck code you give does yield some insight:

BugCheck 0x7A

0x7A:

Cause

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:

• 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
  
  
• 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.
  
  
• 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
  
  
• 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.

Resolution

Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.

The above was taken from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.​

Check Hard Disk Connection:

The first thing to check is whether the hard disk is physically connected to the motherboard properly. To do so:

• Shut down and turn off the computer
• Remove the AC Adapter
• Remove the battery
• Hold down the power button for 15-30 seconds to close the circuit and drain any residual power
• Remove the panel on the underside of the laptop where the hard disk is housed
• Remove and re-insert the hard disk by sliding it away from the connector and then gently but firmly pressing it back into the connector (no screws should need to be removed to do this step)
• Replace the panel on the underside of the laptop to cover the hard disk
• Replace the battery
• Replace the AC Adapter
• Turn on the computer and see how it responds

Post back once these steps have been implemented whether the system is stable. Sometimes these crashes can occur due to a loose connection.​

Check for other Hard Disk problems:

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Check Windows for corruption. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the http://www.sevenforums.com/system-s...-system-security-combination.html#post1732627 for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[elroikendo]

I have run CHKDSK once and it has found error with Volume Bitmap, which I have fixed and BSOD Still happening.
I have run Windows Memory Diagnostic and it didnt find anything.
I have run S.M.A.R.T Test by WD and it doesnt find any error.
My status codes are always 0xC000010 and once it is 0x0000009A

I cant check my HardDisk connection because DELL put the HDD sticking at bottom surface of the mobo, (and im no good at this thing)


Run malwarebyte full scan and found 1 infected file which is my keygen.
Run sfc /scannow for 3 times with restart and no integrity violation
just run HDtune check for bad block and i found none . There is no bad blocks

 

[writhziden]

Windows Memory Diagnostics are not the most reliable. Memtest86+ stresses the RAM more and is more likely to find errors if there are any, but even it is not 100% reliable enough to say the RAM is fine if it comes back clean.

Further reading: Finicky RAM.


You still need to run SeaTools. You should also find someone who is comfortable taking off the hard disk panel and re-seating your hard disk.

 

[elroikendo]

I passed all SEA test, im gonna run memtest overnight will update tommorow
also some more info :
When i first boot my computer my HDD seem to be noisy and got some beep/buzz sounds, after 1 hour there is no beep/buzz sound again, for these 2 days i havent got any bsod just yet :/.

 

[writhziden]

If your hard disk is making noise, you should backup any important data to an external drive, and replace your current drive as soon as you are able to do so.

 

[elroikendo]

I think the noise is not from hard drive, the last time it buzz I stick my ear to my laptop and I heard that the harddisk is still spinning normally. I think the beep/buzz sounds come from the machine itself indicating error. Also i cant run memtest cuz i just remember that my disk drive is faulty :/.
I think its either faulty ram or faulty windows.
How do I reinstall windows ? my windows is preinstalled and i got no disc.

EDIT :just when i thought my bsod is fixed, it comes again. this time i was spinning my laptoparound (an ant just walk through my screen and i dunt want the ant to get inside my laptop). As i check around and spin my laptop around, the bsod comes. Maybe its a loose HDD cable ? im not sure though.

 

[writhziden]

You will need to have a friend check the hard disk connection and re-seat the drive as I said in my previous post. Until you do that, we will not be able to properly assist you with the "loose HDD cable" issue.


http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164

 

[elroikendo]

I got minidump, it says on of the system kernel been terminated and stopped suddenly. I am sure the system kernel stopped because the HDD paging file got inaccessible. I listened closely to the hard disk, i found that actually the hard disk somehow stopped reading/writing thus making the noise (not sure what making the noise, couldnt be head crash since i see now data corrupt). After the buzz ends i can hear the sound of restarting hard disk.

Just one last question, any ideas what might be the problem with my HDD ?

 

[writhziden]

Could be a bad connection or a failing drive. It could also be the motherboard controller is damaged on the motherboard. Hard to say for sure.

Since you cannot easily access the drive due to that model's design flaw, you will have to let the manufacturer of the PC, DELL, take a look at it.

 

[elroikendo]

Thanks a lot for all ur answers really help me I appreciate it
I guess im just gonna enjoy the remaining life of my HDD and meanwhile waiting till i get enough money to buy an SSD

 

[writhziden]

Make sure to keep your data backed up in the meantime. Best of luck!