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

probook 4530s problems


  • Please log in to reply
6 replies to this topic

#1 faceofabum

faceofabum

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:53 AM

Posted 10 March 2014 - 11:06 AM

Hello, I am a highscool student. My laptop is giving me trouble. I always get the blue screen of death.

 

My computer is a windows 7 home premium service pack 1 hp probook 4530s.

It has intel core i3-2350m 2.30ghz

4.00gb

64 bit os

 

I don't know what to do. I have scanned it with malware bytes, I am running avg antivirus, and I have spyware blaster installed. Are there any suggestions as to what I should do? Or are there any ideas as to what is wrong with this computer? I am not very good with computers and I'm not sure how to fix this.



BC AdBot (Login to Remove)

 


#2 zingo156

zingo156

  • BC Advisor
  • 3,333 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:53 AM

Posted 10 March 2014 - 11:21 AM

Please run who crashed and speccy:

 

We need to analyze your operating system's crash dump files to further diagnose what could possibly be crashing your computer system.

Please download Who Crashed? and save it to your desktop.

Double click whocrashedSetup.exe and choose Run

On Windows Vista, 7, 8 and 8.1 machines, when User Account Control asks if you wish to install this program, say YES to install the program on your computer.

Program can also be installed by right click and choosing Run As An Administrator.

On the next screen choose Next and accept the agreement.

Install the program in it's default location C:\Program Files\WhoCrashed (If your primary drive is different from C:, choose your primary drive.)

Choose Next and allow program to create a Start Menu Folder called WhoCrashed and click Next.

Allow program to create desktop icon and click Next.

Now Click Install.

Once the program is installed on your computer system, look for the WhoCrashed icon.png desktop Icon and double click it.

Accept the User Account Control request and the program will open on your screen and should look something like this.

whocrashed.png

Next, Click the Analyze button. analyze.png

An Information Window should appear on your screen prompting you to scroll down your screen.

If a report was generated we would like to have a look at this report.

To do this, click File analyze.png and then choose Export.

Save as WhoCrashedOutput.htm to your desktop.

Open WhoCrashedOutput.htm and copy and paste all of the contents from System Information (local) and Crash Dump Analysis and the Conclusion into your next reply.

 

SPECCY:

 

[*] Go to [url=http://www.piriform.com/speccy]Piriform's website[/url], and click the big download.png button.[/*]

[*] Next, click [url=http://www.piriform.com/speccy/download/standard]Download from Piriform.com[/url] (the FileHippo link requires an extra click). Or if you want to use a portable version of Speccy (which doesn't require installation), click the builds page link and download the portable version.

[*] You will now be asked where you want to save the file. The best place to put it is the Desktop, as it will be easy to find later.

[*] After the file finishes downloading, you are ready to run Speccy. If you downloaded the installer, simply double-click on it and follow the prompts until installation is complete. If you downloaded the portable version, you will need to unzip it before use. Right-click the ZIP file and click [b]Extract all[/b]. Click [b]Next[/b]. Open up the extracted folder and double-click on Speccy.

[*] Once inside Speccy, it will look similar to this (with your computer's specifications, of course):
p22004369.gif

[*] Now, at the top, click File > Publish Snapshot

[*] You will see the following prompt:
p22004371.gif

[*] Click Yes > then Copy to Clipboard
p22004372.gif

[*] Now, once you are back in the forum topic you are posting in, click the p22004370.gif button. Right-click in the empty space of the Reply box and click Paste. Then, click Add Reply below the Reply box.

[*]Congrats! You have just posted your specs!


Edited by zingo156, 10 March 2014 - 11:21 AM.

If I am helping you with a problem and I have not responded within 48 hours please send me a PM.

#3 faceofabum

faceofabum
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:53 AM

Posted 10 March 2014 - 08:35 PM

Ok, i'm pretty sure that I did everything right. Here are the things that you asked for. I hope that they are the right things.

 

 

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Sun 3/9/2014 11:29:32 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\031014-53695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80048AB050, 0xFFFFF80000B9C3D8, 0xFFFFFA800C428B80)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 3/9/2014 11:29:32 PM GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80048AB050, 0xFFFFF80000B9C3D8, 0xFFFFFA800C428B80)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 2/5/2014 5:20:16 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\020514-74755-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC5005AFA8, 0xFFFFFFFFC00000B5, 0x122244820, 0xFFFFF8A00B5F5024)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 2/4/2014 5:22:28 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\020414-42744-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC5002BEF0, 0xFFFFFFFFC00000B5, 0x2B2E880, 0xFFFFF8A0057DE498)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 1/14/2014 10:47:46 PM GMT your computer crashed
crash dump file: C:\windows\Minidump\011414-49327-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0xFFFFF6FC80616D38, 0xFFFFFFFFC00000B5, 0x11B812880, 0xFFFFF900C2DA7000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/14/2013 3:22:48 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\121313-46815-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D025)
Bugcheck code: 0x7A (0xFFFFF6FC40021AC8, 0xFFFFFFFFC00000B5, 0xAA4D3860, 0xFFFFF88004359025)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



 

http://speccy.piriform.com/results/4wZEMLgkL3CRnLQVwxZ8dbR



#4 acerts04

acerts04

  • Members
  • 582 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:53 AM

Posted 11 March 2014 - 01:50 AM

hi! :hello: if you would, please follow this below step.

 

Upload the actual crash dump files.
 
You will find the crash dump files inside C:\Windows\Minidump folder. To copy the dumps, disable "User Account Control" first. Otherwise you may receive a permission error. After disabling UAC, copy and zip all the dumps using 7-zip ( http://www.7-zip.org ). Either attach the zip with next reply using "More reply options --> Attach files" or use a free file hosting site.
 
For example -> http://www.mediafire.com/

 

uploading the actual crash dump file makes it easier for me to analyze and possibly pull some more helpful information as to what is causing your crashes


"In real life, the hardest aspect of the battle between good and evil is determining which is which."


#5 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:11:23 AM

Posted 11 March 2014 - 03:29 AM

This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D025)
Bugcheck code: 0x7A (0xFFFFF6FC40021AC8, 0xFFFFFFFFC00000B5, 0xAA4D3860, 0xFFFFF88004359025)
Error: KERNEL_DATA_INPAGE_ERROR

BSOD KERNEL_DATA_INPAGE_ERROR is usually considered as a sign of storage related issues - ie, buggy controller driver, SSD firmware issue , failing hard drive etc.

 

Source http://msdn.microsoft.com/en-us/library/windows/hardware/ff559211(v=vs.85).aspx

 

=====================================================================================================

  • 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.

  • 0xC000000E, or STATUS_NO_SUCH_DEVICE, indicates a hardware failure or an incorrect drive configuration. Check your cables and check the drive with the diagnostic utility available from your drive manufacturer. If you are using older PATA (IDE) drives, this status code can indicate an incorrect master/subordinate drive configuration.

=====================================================================================================

 

The HDD SMART data collected by Speccy shows your hard drive is clearly failing.

C4 Reallocation Event Count: 099 (099) Data 0000000017
C5 Current Pending Sector Count: 100 (100) Data 0000000009

A non zero value of "Current Pending Sector" means the drive surface has bad/unstable sectors.

 

Source : http://kb.acronis.com/content/9133

 

 

 

This is a critical parameter. Degradation of this parameter may indicate imminent drive failure. Urgent data backup and hardware replacement is recommended.

 

 

Backup your data and replace the drive immediately !.

 

Btw, it might be possible to repair the drive by running manufacturer's diagnostic tool but the drive won't be reliable for critical data storage in my experience.   


Edited by Anshad Edavana, 11 March 2014 - 03:31 AM.


#6 zingo156

zingo156

  • BC Advisor
  • 3,333 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:12:53 AM

Posted 11 March 2014 - 07:21 AM

I agree with Anshad Edavana You have a failing hard drive from all of the indicators above. It would be recommended to backup all of your data, then replace the hard drive and reload windows etc.


If I am helping you with a problem and I have not responded within 48 hours please send me a PM.

#7 faceofabum

faceofabum
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:01:53 AM

Posted 11 March 2014 - 02:57 PM

Ok, thank you for your help. How would I go about replacing the hard drive?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users