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

Frequent BSOD leads to OS Not Found


  • Please log in to reply
3 replies to this topic

#1 ceezo66

ceezo66

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:33 AM

Posted 08 February 2010 - 05:47 AM

I randomly get BSODs which either cause:

1. CHKDSK

2. Restart into Windows Boot Manager trying to fix the problem (system

restore/repairing windows files)

3. PXE-E61: Media test failure. Check cable
PXE-MOF: Exiting Broadcom PXE ROM
Operating System not found


===Attempted & Failed Solutions===

1. Memtest
2. Sea Tools
3. Temp File Cleaner
4. Malwarebytes' Anti-Malware Scan
5. GMER Rootkit Scanner
6. Avast Antivirus Scan
7. Chkdsk /r

===Error Reports===

1.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: f4
BCP1: 00000003
BCP2: 865287C0
BCP3: 8652892C
BCP4: 829F37B0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020210-19656-01.dmp
C:\Windows\Temp\WER-26656-0.sysdata.xml


2.

Windows Boot Manager

Status: 0xc000000e9
Info: An unexpected I/O error has occured

3.

PXE-E61: Media test failure. Check cable
PXE-M0F: Exiting Broadcom PXE ROM.
Operating System not found

4.

==================================================
Dump File : 020510-68453-01.dmp
Crash Time : 2/5/2010 4:36:43 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : 0x8bd5f973
Parameter 2 : 0x00000000
Parameter 3 : 0x82a1fc1e
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5ec46
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\020510-68453-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
==================================================

5.

==================================================
Dump File : 020810-16828-01.dmp
Crash Time : 2/8/2010 3:20:20 AM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 0xc020abec
Parameter 2 : 0xc000000e
Parameter 3 : 0x408cd860
Parameter 4 : 0x82afb24c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+d1574
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : 32-bit
Computer Name :
Full Path : C:\Windows\minidump\020810-16828-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 7600
==================================================

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,698 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:10:33 PM

Posted 08 February 2010 - 12:35 PM

Is the computer bootable/operable?

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#3 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:01:33 AM

Posted 08 February 2010 - 01:26 PM

Boot from the Windows 7 disk.
Let all the drivers load.
Choose repair (not install or it will wipe your hard drive.)
let it repair.
or at prompt type fixmbr it will fix the Master Boot Record.
then type fixboot it will fix the boot.ini file.
Restart.
Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 55,742 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:33 AM

Posted 09 February 2010 - 01:35 PM

Check your boot options in the BIOS...what you listed indicates that the system is trying a network boot. Since there is none, the error message is generated.

Check your time/date in the BIOS...if incorrect, you may have a weak/dying CMOS battery.

Sometimes, the network boot option is the default for a system. Slipping back to it indicates a CMOS battery change is probably needed.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users