locked
random restarts on a inspiron 580 running windows 7 RRS feed

  • Question

  • i bought a new inspiron 580 in march and began contacting tech support exactly two weeks later. my computer rebots randomly and shows the kernal power error and peer networking errors. alot of other errors too but i have no idea what they mean.

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
      <EventID>41</EventID>
      <Version>2</Version>
      <Level>1</Level>
      <Task>63</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000002</Keywords>
      <TimeCreated SystemTime="2010-08-18T18:15:23.019213200Z" />
      <EventRecordID>8474</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>spence-PC</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData>
      <Data Name="BugcheckCode">0</Data>
      <Data Name="BugcheckParameter1">0x0</Data>
      <Data Name="BugcheckParameter2">0x0</Data>
      <Data Name="BugcheckParameter3">0x0</Data>
      <Data Name="BugcheckParameter4">0x0</Data>
      <Data Name="SleepInProgress">false</Data>
      <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
      </Event>
    Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
      <EventID Qualifiers="49152">7023</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8080000000000000</Keywords>
      <TimeCreated SystemTime="2010-08-18T18:09:35.921097400Z" />
      <EventRecordID>8359</EventRecordID>
      <Correlation />
      <Execution ProcessID="552" ThreadID="700" />
      <Channel>System</Channel>
      <Computer>spence-PC</Computer>
      <Security />
      </System>
    - <EventData>
      <Data Name="param1">Peer Name Resolution Protocol</Data>
      <Data Name="param2">%%-2140993535</Data>
      </EventData>
      </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
      <EventID>1530</EventID>
      <Version>0</Version>
      <Level>3</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2010-08-18T18:07:59.586067500Z" />
      <EventRecordID>1670</EventRecordID>
      <Correlation />
      <Execution ProcessID="128" ThreadID="5436" />
      <Channel>Application</Channel>
      <Computer>spence-PC</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData Name="EVENT_HIVE_LEAK">
      <Data Name="Detail">1 user registry handles leaked from \Registry\User\S-1-5-21-171417813-3260141639-32715824-1000_Classes: Process 4700 (\Device\HarddiskVolume3\Program Files (x86)\Citrix\GoToAssist\514\g2acomm.exe) has opened key \REGISTRY\USER\S-1-5-21-171417813-3260141639-32715824-1000_CLASSES</Data>
      </EventData>
      </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
      <EventID>1530</EventID>
      <Version>0</Version>
      <Level>3</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000000</Keywords>
      <TimeCreated SystemTime="2010-08-18T18:07:58.962066400Z" />
      <EventRecordID>1669</EventRecordID>
      <Correlation />
      <Execution ProcessID="128" ThreadID="5436" />
      <Channel>Application</Channel>
      <Computer>spence-PC</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData Name="EVENT_HIVE_LEAK">
      <Data Name="Detail">2 user registry handles leaked from \Registry\User\S-1-5-21-171417813-3260141639-32715824-1000: Process 4700 (\Device\HarddiskVolume3\Program Files (x86)\Citrix\GoToAssist\514\g2acomm.exe) has opened key \REGISTRY\USER\S-1-5-21-171417813-3260141639-32715824-1000 Process 4700 (\Device\HarddiskVolume3\Program Files (x86)\Citrix\GoToAssist\514\g2acomm.exe) has opened key \REGISTRY\USER\S-1-5-21-171417813-3260141639-32715824-1000\Software\Microsoft\Windows\CurrentVersion\Internet Settings</Data>
      </EventData>
      </Event>
    and i have dozens more. dell keeps sending me on a round about to no where. i have run diagnostic checks so many times i beleive i could work for dell at this point. dell has in this order, replaced my hard drive, told me to reinstall windows, and then updated my bios, but the problem continues.
    someone please help.
    Wednesday, August 18, 2010 7:05 PM

Answers

  • You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging

    You may paste the result in your next post for analyzing.

    Meantime I suggest you upgrade your BIOS with the latest update.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Friday, August 27, 2010 9:28 AM
    Friday, August 20, 2010 8:17 AM

All replies

  • Nothing new - this is all over technet now.
    here is mine and I m bouncing between HP, Kingston, Microsoft :
    http://social.msdn.microsoft.com/Forums/en-US/windowssearch/thread/17e1a927-7552-45d8-bfd2-503cc89dd1c7/#1c27d212-c3d6-4f9a-83f6-1971fc939600

    some tested results from fellow techies on MSDN recommends : using RAM at 800Mhz and preferably you wont get these random restarts. It is the way the kernel is build in Win 7 supporting higher mem speeds.

    More thorough details on the same : You will possibly find this more surprising :
     http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/a611d79d-9865-4a8e-917b-74b0a891912f

    Cheers


    "Do it yourself, before you think someone else will" - Mani Babbar - 18.08.10
    Wednesday, August 18, 2010 9:29 PM
  • http://support.microsoft.com/kb/2028504
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, August 18, 2010 10:39 PM
  • Most probably MS is pointing it to be a H/w in this 2028504 unless you are very certain on your own H/w and have tried alternatives for the situation. you can try 2028504 and give it a go if you have OCed your system.

     


    "Do it yourself, before you think someone else will" - Mani Babbar - 18.08.10
    Thursday, August 19, 2010 2:58 PM
  • You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging

    You may paste the result in your next post for analyzing.

    Meantime I suggest you upgrade your BIOS with the latest update.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Friday, August 27, 2010 9:28 AM
    Friday, August 20, 2010 8:17 AM