random freezing

aund · 24 Jan 2011

hey my pc seems to randomly crash for no reason at all i know its not the hard disk or psu or graphics card that is causing the problem as i have just replaced them and the problem still occurs

any idea how i can figure out what is causing me this problem

i have windows 7 7600 x64
AMD Phenom II X4 955
8.0GB Dual-Channel DDR2 @ 333MHz (5-5-5-15)
ASRock K10N78 (CPUSocket)
NVIDIA GT 220
x86 (32-bit) or x64 ? x64
- the original installed OS on the system? yes
- an OEM or full retail version?
- OEM = came pre-installed on system no
- Full Retail = you purchased it from retailer yes

- What is the age of system (hardware)? about a year but psu graphic card and hard disk 2 months
- What is the age of OS installation (have you re-installed the OS?) 1 year tried reinstalling few times

thanks for the help

aund

fimble · 26 Jan 2011

Hi aund and Welcome.

No Dump files have been generated.

To ensure minidumps are enabled:

Go to Start and type in sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box.
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

The .dmp files are located at C:\Windows\Minidump. Until a .dmp file is generated, the Minidump folder may not even exist.

Jonathan_King · 26 Jan 2011

No dumps exist because no BSODs have occurred.

I am seeing some network issues here:

Code:

Event[72]:
  Log Name: System
  Source: NetBT
  Date: 2011-01-24T21:19:39.504
  Event ID: 4321
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Aund-PC
  Description: 
The name "AUND-PC        :0" could not be registered on the interface with IP address 192.168.2.2. The computer with the IP address 192.168.2.4 did not allow the name to be claimed by this computer.

Event[56]:
  Log Name: System
  Source: Server
  Date: 2011-01-24T21:19:51.000
  Event ID: 2505
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Aund-PC
  Description: 
The server could not bind to the transport \Device\NetBT_Tcpip_{1E62CD92-494C-43AD-BE2D-B90B06AD7F18} because another computer on the network has the same name.  The server could not start.

I notice you are trying the give your computer the name "AUND-PC :0". Try removing the spaces and the emoticon; the name "AUND-PC" will suffice.

There are repeated errors reporting a problem with a hardware device:

Code:

Event[120]:
  Log Name: System
  Source: atapi
  Date: 2011-01-24T21:04:57.683
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Aund-PC
  Description: 
The driver detected a controller error on \Device\Ide\IdePort2.

I don't know what device that is, but if I had to guess, it would be your Seagate hard drive. Use SeaTools, and run the "Short DST" and "Long DST" on all your hard drives.

Finally, run driver verifier: Driver Verifier - Enable and Disable

Perhaps that will flag a 3rd-party driver and cause a BSOD, resulting in the dumps Fimble is looking for.

Start with that; there is more we can try, but that's a start for now.

aund · 26 Jan 2011

thanks for the reply currently running seatools when it shows my internal hard drives it lists each drive twice is that normal?

aund

Jonathan_King · 26 Jan 2011

That doesn't happen all the time, that's for sure; I don't know why it's doing it for you, but I don't think it indicates a problem or anything.

aund · 26 Jan 2011

ahh okay still running long dst only one thats failed both so far is seagate usb hard disk

will keep you updated

Jonathan_King · 26 Jan 2011

I suggest you remove the drive that failed the test; see if that solves the problem.

aund · 29 Jan 2011

done what you said still having random crashes most of them seem to be when i turn my pc on first five mins or so very strange

any other ideas ? :O

aund · 29 Jan 2011

also been having random disk read errors on start up but cant be the hard disk as i got it replaced last week becasue it was doing the same thing with the old one :/

Jonathan_King · 30 Jan 2011

Run SeaTools on the new drive (and all of your drives). If it reports failure again, we can investigate a motherboard problem.