BSoD on WC3 DotA

[Mark56]

This is the first time you have mentioned a noise coinciding with the screen fault, I have no idea what "ehhing" sounds like. Please discribe using more descriptive words, squeak, buzz, rattle, click, high pitch, low pitch, etc. Or compare it with a common noise that we would all recognise.

Unless the noise is coming from your systems speakers then we are probably looking at a faulty fan or hard drive.

 

[kokoro]

http://www.youtube.com/watch?v=rpz7d8T5ZaA

like this

 

[Mark56]

Is that video showing the same error message that you see on your screen?

I don't hear any noise on that video other than buzzing is that what you hear?

Try the troubleshooting steps in this guide: http://www.tech-faq.com/nmi-parity-check-memory-parity-error.html

As I have already suggested you most likely have a loose connection so all the internal connections need to be reseated to eliminate that possibility.

 

[kokoro]

I do not have any error messages, it simply freezes and restarts. I call it BSoD, because the earlier similar errors would have thrown me an error log which indicated it as Blue Screen.

I will try to fix the loose connection problem and then come back with he results. thanks.

 

[kokoro]

Is it possible that I am overclocking my LapTop? I used 2 browsers today and each had like more than 15 links, and it froze when I tried to download a torrent... which program I can use to see specific details of my errors?


some event viewer info:

A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Busevice:Function: 0x0:0x3:0x0
Vendor IDevice ID: 0x8086:0xd138
Class Code: 0x30400

The details view of this entry contains further information.

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 8/18/2011 5:14:01 AM
Event ID: 17
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: MagicBox
Description:
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Busevice:Function: 0x0:0x3:0x0
Vendor IDevice ID: 0x8086:0xd138
Class Code: 0x30400

The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
<EventID>17</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2011-08-18T09:14:01.017243700Z" />
<EventRecordID>53816</EventRecordID>
<Correlation ActivityID="{584F9D4F-3496-4BA2-815B-0FC88326CB0A}" />
<Execution ProcessID="1512" ThreadID="6592" />
<Channel>System</Channel>
<Computer>MagicBox</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">4</Data>
<Data Name="FRUId">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="FRUText">
</Data>
<Data Name="ValidBits">0xdf</Data>
<Data Name="PortType">4</Data>
<Data Name="Version">0x101</Data>
<Data Name="Command">0x10</Data>
<Data Name="Status">0x407</Data>
<Data Name="Bus">0x0</Data>
<Data Name="Device">0x3</Data>
<Data Name="Function">0x0</Data>
<Data Name="Segment">0x0</Data>
<Data Name="SecondaryBus">0x0</Data>
<Data Name="Slot">0x0</Data>
<Data Name="VendorID">0x8086</Data>
<Data Name="DeviceID">0xd138</Data>
<Data Name="ClassCode">0x30400</Data>
<Data Name="DeviceSerialNumber">0x0</Data>
<Data Name="BridgeControl">0x0</Data>
<Data Name="BridgeStatus">0x0</Data>
<Data Name="UncorrectableErrorStatus">0x0</Data>
<Data Name="CorrectableErrorStatus">0x1</Data>
<Data Name="HeaderLog">00000000000000000000000000000000</Data>
<Data Name="Length">672</Data>
<Data Name="RawData">435045521002FFFFFFFF02000200000002000000A0020000000E090012080B140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB571311FC093CF161AFC4DB8BC9C4DAF67C10421E25CA2845DCC0100000000000000000000000000000000000000000000000010010000D0000000010200000100000054E995D9C1BB0F43AD91B44DCB3C6F3500000000000000000000000000000000020000000000000000000000000000000000000000000000E0010000C00000000102000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000030000000000000000000000000000000000000000000000DF0000000000000004000000010100001000070400000000868038D100040300030000000000000000000000000000000000000010E042012180000007010100023D39034300013900009800C0030000080001000000000000000000000000000000000000000000000000000000000001000115000000000000000010200600010000000011000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000043010000000000000002000000000000E506010000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

 

[kokoro]

ok, i guess the log above is not really related to the major problem...

 

[Mark56]

The log above does mention PCI Express which is related to your graphics.

Just to put the record straight a BSOD is a blue screen of death and always shows a blue screen and creates a minidump file. When the system just freezes and reboots this is more like a power failure and does not produce a minidump. Overclocking is when you increase the voltage or frequency on the CPU or memory to increase it's speed. You cannot run too many processes and that should never cause a problem unless there is a hardware fault which is often caused by faulty RAM. All that will happen when running a lot of processes is that the system will slow down.

Mind how you go checking all the connections. While you have got the laptop apart try and locate the other RAM module, some laptops have one hidden under the keyboard.

I still think you might have a failing graphics chip and should contact the manufacturer to see if your PC was made when the faulty Nvidia chips were in production. I mentioned this back in post 12 but you made no comment.

 

[kokoro]

I still think you might have a failing graphics chip and should contact the manufacturer to see if your PC was made when the faulty Nvidia chips were in production. I mentioned this back in post 12 but you made no comment.

I will consider this when I will go to the manufacturer center.