Running out of ideas on what's causing the crash

imaginepc

Member
Nov 4, 2007
41
0
0
You know how it is build a new system (non ov erclocking) and trying to figure out how to get it rock solid stable. Well just rebuilt my media center and having issues trying to get it stable. I'm leaning towards it's a bad MOBo or the PCI EX[press is bad on the board.

Your take and thoughts are welcome.

ITEMS i'm SURE ARE OK:

Power Supply
Memory (memtest ran for about 1 hour plus no crashes or errors)
Cooling - Seems to be cooling fine.



Ambient Temp is about: 70.
It is not too dusty i do have a cat
All parts are new.

AMD X2 5600
Windows XP SP2
500 W Power Supply
2 Gigabytes Patriot 6400 Ram
ASUS M2A-Vm Motherboard
Silverstone LCO3 Media Case (tight fit)
2 small 60 mm fans, large fan on psu, front fan, and
new heat sink k989 (northbridge gets in the way of other heat sinks)
1 IDE 300 GB hard drive
1 Sata 3.0 I

7300 PCI E (evga card)
Hauppage PVR 1600 PCI

IDE hard drive is set to be Slave (of the cd rom and ahs the Os installed because windows would no install on the SATA for some reason?

So i installed the new heat sink and noticed temps are a lot cooler now. So I just let the system run fora few minutes all by itself and withing in about 40 minutes of just sitting idling in windows the error BSOD (PCIIDEX.SYS) was the stop code result.


I also have the following problem whihc is intermittent on bootup. NTLDR.SYS - basically the bootup sometimes just doesn't find the O'S (not sure of that one)


Hopefuly that's enough infO

Memory test is still running at 65% and no errors thus far
 

cozumel

Senior member
Nov 29, 2007
337
0
0
PCIIDEX.SYS is Microsofts PCI IDE Bus Driver Extension but without the full stop code (0x0000 etc etc) can't really help any further. It may be a memory error though and memtest may not identify it. Check your event logs for the this error and the NTLDR.SYS. (repairing your xp installation from your XP disk may resolve ther ntldr error. Also check the boot order is correct in the BIOS)
 

imaginepc

Member
Nov 4, 2007
41
0
0
I think i may have solved the NTLDR error. I am messaging from the computer

MEM test completed with abotu 10 passes and no fail codes. Memory seems to be fine.

The primary software i use on this system is Beyond TV. So i was testing the sytem few minutes ago and had a fatal crash but i can't seem to locate open the mini dump file to actually see what the problem is.

I should have WROTE DOWN that full stop code. GRR. I will get it if it happens again.

Temperatures Seem to not be the problem

MB 35C
CPU: 39 C - 42 - fluctuates

 

imaginepc

Member
Nov 4, 2007
41
0
0
Just as i finished typing that last message - the system crashed again. In the event log the folllowing error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/22/2007
Time: 4:52:17 PM
User: N/A
Computer: PMEDIA
Description:
Error code 1000000a, parameter1 09ebb1cf, parameter2 0000000a, parameter3 00000001, parameter4 8054471e.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 39 eters 09
0030: 65 62 62 31 63 66 2c 20 ebb1cf,
0038: 30 30 30 30 30 30 30 61 0000000a
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 31 2c 20 38 30 35 34 01, 8054
0050: 34 37 31 65 471e
 

cprince

Senior member
May 8, 2007
963
0
0
check your memory configuration. I had this weird problem where the system just randomly BSOD because the memory weren't in the correct slots for dual channel.
 

imaginepc

Member
Nov 4, 2007
41
0
0
Yep checked that memory is in
A1 & B1 for dual channel mode.

Does that error code help anyone up there? would a fresh install of windows help?
 

cozumel

Senior member
Nov 29, 2007
337
0
0
Okaly dokaly. It is most likely to be a driver problem. Download something like 'driver cleaner' and then unplug the internet. Uninstall all your drivers (I mean all) and that includes chipset drivers, audio, video and any others you have installed. Reboot into safe mode. When you reboot into safe mode if windows tries to find hardware and load drivers then try to cancel these. If that fails then uninstall them again while still in safe mode. Then run drivercleaner to remove any residue of the drivers (make sure AV software is switched off). Empty the recycle bin and then reboot. When you have rebooted into normal windows reload all the necessary drivers from disk and then you can reconnect to the internet and download any updates.

If that doeesn't work could you also post your stop codes for me please and run memtest continually overnight for at least 8/12 hours (that is the minimum required to ensure there are no memory problems although like I said memtest won't always identify a problem).
 

imaginepc

Member
Nov 4, 2007
41
0
0
seems like a wipe the hard drive and fresh install would be quicker:) lol

i have all the drivers on my backup.. I think I will do that... and check for stop codes. If that doesnt work I will run mem test over night.

Thanks for the suggestions. back in 2 1/2 hours lol...

 

cozumel

Senior member
Nov 29, 2007
337
0
0
Hey! Best make sure you don't restore any potentially bad drivers from backup dude...
 

imaginepc

Member
Nov 4, 2007
41
0
0
By backup i meant from the motherboard cd rom:)

I'm back up and running only 1 1/2 hours - still installing windows updates.. No crashes yet........
 

imaginepc

Member
Nov 4, 2007
41
0
0
Well it crashed again at 4:42 a.m. and then about 10 minutes ago with a stop code. regardless I am still wondering what this error is but it's a different error now on a fresh install. I'm pretty sure im taking this motherboard back and going with a gigabyte board brand i trust. Regardless for my information knowledge.

VER_IRQL_LESS_OR_EQUAL

0X000000D1 (0X00000060, 0X0000002, 0X000000, 0XBAB8B6E2)


Since this is a completely different stop code the board doesnt handle USB or PCI right I'm pretty sure this MOBO is thep problem.

Also this memory was switched initially for completely new sticks. So the memory slots on the board are problably bad. I highly doubt I got two sticks of bad memory both times.


Another item I discovered the RAm they sold me is 2.2V - currently the MOBO is set to auto. I can't even change the settings to support 2.2V the max is 2.10 that sounds like a big red flag to me.M I even went in to give it one last try set the mhz ddram to 800


 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Originally posted by: imaginepc
Well it crashed again at 4:42 a.m. and then about 10 minutes ago with a stop code. regardless I am still wondering what this error is but it's a different error now on a fresh install. I'm pretty sure im taking this motherboard back and going with a gigabyte board brand i trust. Regardless for my information knowledge.

VER_IRQL_LESS_OR_EQUAL

0X000000D1 (0X00000060, 0X0000002, 0X000000, 0XBAB8B6E2)


Since this is a completely different stop code the board doesnt handle USB or PCI right I'm pretty sure this MOBO is thep problem.

Also this memory was switched initially for completely new sticks. So the memory slots on the board are problably bad. I highly doubt I got two sticks of bad memory both times.


Another item I discovered the RAm they sold me is 2.2V - currently the MOBO is set to auto. I can't even change the settings to support 2.2V the max is 2.10 that sounds like a big red flag to me.M I even went in to give it one last try set the mhz ddram to 800

Don't do anything with driver cleaner yet.

Read my .sig, and read the Bluescreens section of my website, and download and install the debugger. Debug your dumpfile, and then post the results of '!analyze -v', and we can see why your box is crashing.

The IRQL error you're seeing is completely different from motherboard IRQs.
 

cozumel

Senior member
Nov 29, 2007
337
0
0
I agree 100% with clive. You need to find excatly what is causing. Is probably a driver but a dump file is likely to pinpoint accurately the culprit that is causing the crashes.
 

imaginepc

Member
Nov 4, 2007
41
0
0
I downloaded the tool in your signature - I also tried downloading win debugger before and Couldn't get the damn thing to show me the dump file. I'm reading through your instructions thanks.

the minidump folder is empty.
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
Can you be a bit more verbose? What do you mean by 'you couldn't get the damn thing to show you the dump file' ? /max verbosity=on, please.
 

imaginepc

Member
Nov 4, 2007
41
0
0
Meaning it couldn't find the DUMP file:)

Sorry.. it's early morning and you know after 2 days of this it wears on you. Thanks for your help:)



I installed windbg added symbol path & closed out windbg tc - reopened it and opened crash dump directory. but there is no file there.(cant fnd it).

 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
What do you mean "it" couldn't find the dump file? When you go to c:\windows\minidump are there files there or not? Is there a c:\windows\memory.dmp?

Is your Windows install set to write a dumpfile? Do you have a pagefile on c:, so that the dumpfile can be written?
 

imaginepc

Member
Nov 4, 2007
41
0
0
The os for some stupid reason is installed on D: no matter which way i switch it

But i have specified in the location for the minidump to be


D:\windows\minidump

and the directory does exist.
 

imaginepc

Member
Nov 4, 2007
41
0
0
Thanks for all you rhelp again

I can't seem to locate a page file on D:

I only see pagefileconfig in

windows\system32



dont actually see a page file..
 

dclive

Elite Member
Oct 23, 2003
5,626
2
81
You need to turn on the ability in Explorer to show all hidden files and all system files. Then you should have a pagefile.sys file in the root of your drives - is it in c: or d:?

If it's only in c: and not d: (d: is your systemdrive), then you won't be able to capture dumps, so thus you'll be in the situation you're in ...please let us know.