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

Shutting down at Start Up


  • Please log in to reply
65 replies to this topic

#1 Unfortunato

Unfortunato

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 09 August 2010 - 06:01 PM

Hi All,

I'm looking for a bit of advice on a problem I'm having, and a poster who'd helped eliminate malware as a cause suggested that I make a post in here.

The original thread is here:

http://www.bleepingcomputer.com/forums/ind...p;#entry1878421


The current situation has not changed since I last posted an update on the problem earlier today, and I'm hoping maybe someone can provide some insight.

Cheers for reading!

BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,770 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:51 AM

Posted 09 August 2010 - 09:53 PM

Does the same thing happen, if you try to start in safe mode?
Laptop, or desktop?

My Website

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

 


#3 Unfortunato

Unfortunato
  • Topic Starter

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 10 August 2010 - 09:31 PM

Hi Broni, it's a desktop, and I'm able to get in to safe mode. I've copied this from a post I made in the original thread, just to give you some info:




Right, I think I might be getting somewhere here...

Something that I had forgotten about was that I had also noticed another item flagged in Device Manager under Other Devices, listed as 'Other PCI Bridge Device'.

What I'd done was to fire up the new HDD mentioned in post #4, and obviously the same crash occurred at the same point, and I booted into safe mode to have a look at Device Manager. And I see the big yellow question mark over Other Devices, and when I click to expand the tree it lists 'Other PCI Bridge Device', as well as two other items both listed as 'PCI Device', a fourth item 'SM Bus controller' and lastly 'Video Controller (VGA Compatible)'.

I copied some information from the 'Details' tab for the 'Other PCI Bridge Device' on the older machine, as follows:

Device instance ID: PCI\VEN_10DE&DEV_03EF&SUBSYS_26021019&REV_A2\3&2411E6FE&0&38
Hardware IDs: PCI\VEN_10DE&DEV_03EF&SUBSYS_26021019&REV_A2
PCI\VEN_10DE&DEV_03EF&SUBSYS_26021019
PCI\VEN_10DE&DEV_03EF&CC_068000
PCI\VEN_10DE&DEV_03EF&CC_0680


Those IDs are exactly the same as the 'Other PCI Bridge Device' which is being flagged in Device Manager on the new HDD:

1. Other PCI Bridge Device
Device instance ID: PCI\VEN_10DE&DEV_03EF&SUBSYS_26021019&REV_A2\3&2411E6FE&0&38
Hardware IDs: PCI\VEN_10DE&DEV_03EF&SUBSYS_26021019&REV_A2
PCI\VEN_10DE&DEV_03EF&SUBSYS_26021019
PCI\VEN_10DE&DEV_03EF&CC_068000
PCI\VEN_10DE&DEV_03EF&CC_0680

These were the other items flagged in the new HDD under 'Other Devices':

2. PCI device
Device instance ID: PCI\VEN_1002&DEV_AA08&SUBSYS_AA081462&REV_00\4&228469D0&0&0148
Hardware IDs: PCI\VEN_1002&DEV_AA08&SUBSYS_AA081462&REV_00
PCI\VEN_1002&DEV_AA08&SUBSYS_AA081462
PCI\VEN_1002&DEV_AA08&cc_040300
PCI\VEN_1002&DEV_AA08&cc_0403


3. PCI device
Device instance ID: PCI\VEN_10DE&DEV_03F0&SUBSYS_A88D1019&REV_A2\3&2411E6FE&0&28
Hardware IDs: PCI\VEN_10DE&DEV_03F0&SUBSYS_A88D1019&REV_A2
PCI\VEN_10DE&DEV_03F0&SUBSYS_A88D1019
PCI\VEN_10DE&DEV_03F0&cc_040300
PCI\VEN_10DE&DEV_03F0&cc_0403


4. SM Bus controller
Device instance ID: PCI\VEN_10DE&DEV_03EB&SUBSYS_26021019&REV_A2\3&2411E6FE&0&09
Hardware IDs: PCI\VEN_10DE&DEV_03EB&SUBSYS_26021019&REV_A2
PCI\VEN_10DE&DEV_03EB&SUBSYS_26021019
PCI\VEN_10DE&DEV_03EB&cc_0c0500
PCI\VEN_10DE&DEV_03EB&cc_0c05


5. Video Controller (VGA Compatible)
Device inStance ID: PCI\VEN_1002&DEV_9589&SUBSYS_09301462&REV_00\4&228469D0&0&0048
Hardware IDs: PCI\VEN_1002&DEV_9589&SUBSYS_09301462&REV_00
PCI\VEN_1002&DEV_9589&SUBSYS_09301462
PCI\VEN_1002&DEV_9589&cc_030000
PCI\VEN_1002&DEV_9589&0300


Having googled some of these ID numbers it looks as if it's a graphics card issue, as they're coming up as NVIDIA drivers. I have a MSI radeon RX2600PRO. Have I found a likely cause for the problem here? And if so, would I be better off trying to download the drivers as they're listed above, or maybe there are updated drivers that would be the option?

#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,770 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:51 AM

Posted 10 August 2010 - 09:35 PM

It looks like have to start with installing chipset driver.

Is it a stock computer, or self-built?

My Website

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

 


#5 Unfortunato

Unfortunato
  • Topic Starter

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 10 August 2010 - 09:41 PM

It's a self built machine.

#6 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,770 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:51 AM

Posted 10 August 2010 - 09:44 PM

Well, we have a lot of work to do then...

Download System Information for Windows: http://www.gtopala.com/siw-download.html to your Desktop.
Get SIW Standalone (English-Only).
Double click on siw.exe to run the program.
Go File>Create Report File>HTML
Save the file to known location.
Zip the file, and attach it to your next reply.

My Website

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

 


#7 Unfortunato

Unfortunato
  • Topic Starter

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 10 August 2010 - 10:00 PM

I've downloaded it, but when I run it, it says that it isn't suitable for safe mode (which is all I can get into at the moment)

It did let me create the HTML file however, so I've attached it.

#8 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,770 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:51 AM

Posted 10 August 2010 - 10:17 PM

You forgot to attach it :thumbsup:

My Website

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

 


#9 Unfortunato

Unfortunato
  • Topic Starter

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 10 August 2010 - 10:26 PM

You forgot to attach it :thumbsup:


Duh...!

There we go!

Attached Files



#10 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,770 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:51 AM

Posted 10 August 2010 - 10:32 PM

It looks like this is your chipset driver: http://www.nvidia.com/object/nforce_nf4_wi...8.26_11.09.html
Install it and see how are things in Device Manager.

Let's be clear, that your initial problem may not be cured and may be caused by something else (power supply, overheating, etc.), but we have to start somewhere.

My Website

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

 


#11 Unfortunato

Unfortunato
  • Topic Starter

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 10 August 2010 - 10:40 PM

Ok, I've downloaded that so I'll give it a spin and see how things are.

I shall report back soon!

#12 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,770 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:51 AM

Posted 10 August 2010 - 10:46 PM

OK :thumbsup:

My Website

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

 


#13 Unfortunato

Unfortunato
  • Topic Starter

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 10 August 2010 - 10:57 PM

Device Manger is now showing the device as 'NVIDIA Network Bus Enumerator', and it's listed as working properly. I'm still getting the shutdown at startup though. I could be wrong, but I'm sure it has something to do with this - it seems too much of a coincidence that the same thing happened with the other drive, and that the same device was flagged in device manager. Maybe there is an up to date driver package?

#14 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,770 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:03:51 AM

Posted 10 August 2010 - 11:02 PM

I'm not sure, if I understand.
Does NVIDIA Network Bus Enumerator have any error listed, or are there any errors at all in Device Manager?

My Website

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

 


#15 Unfortunato

Unfortunato
  • Topic Starter

  • Members
  • 135 posts
  • OFFLINE
  •  
  • Local time:12:51 PM

Posted 10 August 2010 - 11:12 PM

According to Device Manager, NVIDIA Network Bus Enumerator has no errors and is working properly.

The only thing I can see that is flagged by device manager is when I click 'view hidden devices', and under 'non-plug and play drivers' there is an item called 'srescan' which is flagged.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users