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

Random BSOD


  • Please log in to reply
1 reply to this topic

#1 cupofjava

cupofjava

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:11 PM

Posted 31 January 2014 - 07:33 PM

Hi guys,

 

I found this forum whilst trying to do a google search on a blue screen error code. I've been getting a few lately, probably 2-3 this month, which is really unusual as i've never had any with this build in the year and a half that i've had it.

 

I'm not sure how to go about interpreting the dump file, so i was hoping for some assistance?

 

I've uploaded the most recent BSOD here: https://www.dropbox.com/s/2bp9ty8poqvnxuo/020114-4180-01.dmp

 

Any help is greatly appreciated, thanks!

 

 



BC AdBot (Login to Remove)

 


#2 TsVk!

TsVk!

    penguin farmer


  • Members
  • 6,230 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Antipodes
  • Local time:04:11 AM

Posted 31 January 2014 - 09:17 PM

  1. Insert the your Windows disc, restart your PC, and press any key to boot from the CD.
  2. Once the setup files have finished loading, press the "R" key to repair the error using the Recovery Console utility.
  3. Once inside, type in the following command "expand d:\i386\hal.dl_ c:\windows\system32\hal.dll" and press enter.
  4. When you are prompted to overwrite the file, press the "Y" key for Yes.
  5. Exit and then press "Enter" at the command prompt.
  6. Reboot your computer and see if the error returns. If it does, the issue is probably related to a damaged or corrupted partition.

hope this helps.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users