What could be the cause

[Paul]

If you get a BSOD, but there's no text??

On the other computer here, this has happened 2-3 times in the last 2-3
weeks.

It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
drivers / stop error etc, and sometimes, the screen is blue and blank, and
there's nothing on the screen?

I'm pretty sure the main cause, is the ATI drivers.

But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The funny
thing is, I've installed and use both on this system, and its never crashed

It has only crashed whle playing games like bejeweled, Gin, and te other day
on a website, while the person was on it. The games are that graphic
intensive. The card is an ASUS 9550 256mb.

Most days its fine (besides the above).

And lately it keeps on coming up with your system has recovered from a
serious error.

Heres a few of the logs for the crashes

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 11/07/2008
Time: 7:52:09 a.m.
User: N/A
Computer: BELLE
Description:
Error code 1000008e, parameter1 c0000005, parameter2 bf92696d, parameter3
a722cc30, parameter4 00000000.

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 38 1000008
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 62 66 39 32 36 39 36 64 bf92696d
0040: 2c 20 61 37 32 32 63 63 , a722cc
0048: 33 30 2c 20 30 30 30 30 30, 0000
0050: 30 30 30 30 0000


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 10/07/2008
Time: 3:00:40 p.m.
User: N/A
Computer: BELLE
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
(0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
C:\WINDOWS\Minidump\Mini071008-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 10/07/2008
Time: 7:12:18 a.m.
User: N/A
Computer: BELLE
Description:
Error code 1000007e, parameter1 c0000005, parameter2 f732d560, parameter3
f6d2fa34, parameter4 f6d2f730.

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 37 1000007
0020: 65 20 20 50 61 72 61 6d e Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 30 30 30 30 30 35 2c 20 000005,
0038: 66 37 33 32 64 35 36 30 f732d560
0040: 2c 20 66 36 64 32 66 61 , f6d2fa
0048: 33 34 2c 20 66 36 64 32 34, f6d2
0050: 66 37 33 30 f730


Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 9/07/2008
Time: 2:11:45 p.m.
User: N/A
Computer: BELLE
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
(0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
C:\WINDOWS\Minidump\Mini070908-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

 

[Bazzer Smith]

Re: What could be the cause

Maybe it is related to hardware, like my problem the other day?
Can't do any harm to check everything is seated correctly, cards
mamory etc.
Would it appear to be related to heat rellated?
Seem a bit similar to the symptoms I got when I over clocked
my old computer. Although I think I got reboots.



"Paul" <noone@home.com> wrote in message news:4876c63f@news01.wxnz.net...
> If you get a BSOD, but there's no text??
>
> On the other computer here, this has happened 2-3 times in the last 2-3
> weeks.
>
> It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
> drivers / stop error etc, and sometimes, the screen is blue and blank, and
> there's nothing on the screen?
>
> I'm pretty sure the main cause, is the ATI drivers.
>
> But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The funny
> thing is, I've installed and use both on this system, and its never
> crashed
>
> It has only crashed whle playing games like bejeweled, Gin, and te other
> day on a website, while the person was on it. The games are that graphic
> intensive. The card is an ASUS 9550 256mb.
>
> Most days its fine (besides the above).
>
> And lately it keeps on coming up with your system has recovered from a
> serious error.
>
> Heres a few of the logs for the crashes
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 11/07/2008
> Time: 7:52:09 a.m.
> User: N/A
> Computer: BELLE
> Description:
> Error code 1000008e, parameter1 c0000005, parameter2 bf92696d, parameter3
> a722cc30, parameter4 00000000.
>
> 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 38 1000008
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 63 30 eters c0
> 0030: 30 30 30 30 30 35 2c 20 000005,
> 0038: 62 66 39 32 36 39 36 64 bf92696d
> 0040: 2c 20 61 37 32 32 63 63 , a722cc
> 0048: 33 30 2c 20 30 30 30 30 30, 0000
> 0050: 30 30 30 30 0000
>
>
> Event Type: Information
> Event Source: Save Dump
> Event Category: None
> Event ID: 1001
> Date: 10/07/2008
> Time: 3:00:40 p.m.
> User: N/A
> Computer: BELLE
> Description:
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
> C:\WINDOWS\Minidump\Mini071008-01.dmp.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 10/07/2008
> Time: 7:12:18 a.m.
> User: N/A
> Computer: BELLE
> Description:
> Error code 1000007e, parameter1 c0000005, parameter2 f732d560, parameter3
> f6d2fa34, parameter4 f6d2f730.
>
> 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 37 1000007
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 63 30 eters c0
> 0030: 30 30 30 30 30 35 2c 20 000005,
> 0038: 66 37 33 32 64 35 36 30 f732d560
> 0040: 2c 20 66 36 64 32 66 61 , f6d2fa
> 0048: 33 34 2c 20 66 36 64 32 34, f6d2
> 0050: 66 37 33 30 f730
>
>
> Event Type: Information
> Event Source: Save Dump
> Event Category: None
> Event ID: 1001
> Date: 9/07/2008
> Time: 2:11:45 p.m.
> User: N/A
> Computer: BELLE
> Description:
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
> C:\WINDOWS\Minidump\Mini070908-01.dmp.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
>
>
>
>
>
>
>

 

[Paul]

Re: What could be the cause

Nope AFAIK its not overheating,

I'm pretty sure the ram isnt the prob. It has only been crashing say in the
2-3 weeks.

And the ram thats in it, has been there for 2yrs +

And has been fine no prob till now.

But, I'll do a check with memtest or MS's windiag program to see what one of
these say

It just seems funny that its these annoying ATI drivers, everytime it does
crash (when you see something), its pointing to different ATI driver files.
It doesnt matter what version I use, it crashes

I dont overclock, so its definitely not that.

The videocard fan was a bit dusty the other week, so I removed it and
cleaned it out. It still crashed.

I'll try reseating the ram and CPU. Theres only 2 cards in it (a modem, and
the vidcard). The vidcard is in properly.

Thanx


"Bazzer Smith" <me@invalid.net> wrote in message
news:TBAdk.5232$xs1.829@newsfe28.ams2...
> Maybe it is related to hardware, like my problem the other day?
> Can't do any harm to check everything is seated correctly, cards
> mamory etc.
> Would it appear to be related to heat rellated?
> Seem a bit similar to the symptoms I got when I over clocked
> my old computer. Although I think I got reboots.
>
>
>
> "Paul" <noone@home.com> wrote in message news:4876c63f@news01.wxnz.net...
>> If you get a BSOD, but there's no text??
>>
>> On the other computer here, this has happened 2-3 times in the last 2-3
>> weeks.
>>
>> It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
>> drivers / stop error etc, and sometimes, the screen is blue and blank,
>> and there's nothing on the screen?
>>
>> I'm pretty sure the main cause, is the ATI drivers.
>>
>> But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The funny
>> thing is, I've installed and use both on this system, and its never
>> crashed
>>
>> It has only crashed whle playing games like bejeweled, Gin, and te other
>> day on a website, while the person was on it. The games are that graphic
>> intensive. The card is an ASUS 9550 256mb.
>>
>> Most days its fine (besides the above).
>>
>> And lately it keeps on coming up with your system has recovered from a
>> serious error.
>>
>> Heres a few of the logs for the crashes
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 11/07/2008
>> Time: 7:52:09 a.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> Error code 1000008e, parameter1 c0000005, parameter2 bf92696d, parameter3
>> a722cc30, parameter4 00000000.
>>
>> 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 38 1000008
>> 0020: 65 20 20 50 61 72 61 6d e Param
>> 0028: 65 74 65 72 73 20 63 30 eters c0
>> 0030: 30 30 30 30 30 35 2c 20 000005,
>> 0038: 62 66 39 32 36 39 36 64 bf92696d
>> 0040: 2c 20 61 37 32 32 63 63 , a722cc
>> 0048: 33 30 2c 20 30 30 30 30 30, 0000
>> 0050: 30 30 30 30 0000
>>
>>
>> Event Type: Information
>> Event Source: Save Dump
>> Event Category: None
>> Event ID: 1001
>> Date: 10/07/2008
>> Time: 3:00:40 p.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
>> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
>> C:\WINDOWS\Minidump\Mini071008-01.dmp.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 10/07/2008
>> Time: 7:12:18 a.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> Error code 1000007e, parameter1 c0000005, parameter2 f732d560, parameter3
>> f6d2fa34, parameter4 f6d2f730.
>>
>> 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 37 1000007
>> 0020: 65 20 20 50 61 72 61 6d e Param
>> 0028: 65 74 65 72 73 20 63 30 eters c0
>> 0030: 30 30 30 30 30 35 2c 20 000005,
>> 0038: 66 37 33 32 64 35 36 30 f732d560
>> 0040: 2c 20 66 36 64 32 66 61 , f6d2fa
>> 0048: 33 34 2c 20 66 36 64 32 34, f6d2
>> 0050: 66 37 33 30 f730
>>
>>
>> Event Type: Information
>> Event Source: Save Dump
>> Event Category: None
>> Event ID: 1001
>> Date: 9/07/2008
>> Time: 2:11:45 p.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
>> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
>> C:\WINDOWS\Minidump\Mini070908-01.dmp.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>

 

[Bazzer Smith]

Re: What could be the cause

Are the cards in each machine the same?

If so you could swop them over, that should tell you something.

I guess if it crashes with a different card in it tells you it is not the
card.
If the other machine crashes with that card you have the culprite!!

Maybe it is the drivers, but if as you they work on the other machine,
there
must be more too it.

I am assuming they are the same card model.

Dunno if you can swop memory too?


"Paul" <noone@home.com> wrote in message news:4876e035@news01.wxnz.net...
> Nope AFAIK its not overheating,
>
> I'm pretty sure the ram isnt the prob. It has only been crashing say in
> the 2-3 weeks.
>
> And the ram thats in it, has been there for 2yrs +
>
> And has been fine no prob till now.
>
> But, I'll do a check with memtest or MS's windiag program to see what one
> of these say
>
> It just seems funny that its these annoying ATI drivers, everytime it does
> crash (when you see something), its pointing to different ATI driver
> files. It doesnt matter what version I use, it crashes
>
> I dont overclock, so its definitely not that.
>
> The videocard fan was a bit dusty the other week, so I removed it and
> cleaned it out. It still crashed.
>
> I'll try reseating the ram and CPU. Theres only 2 cards in it (a modem,
> and the vidcard). The vidcard is in properly.
>
> Thanx
>
>
> "Bazzer Smith" <me@invalid.net> wrote in message
> news:TBAdk.5232$xs1.829@newsfe28.ams2...
>> Maybe it is related to hardware, like my problem the other day?
>> Can't do any harm to check everything is seated correctly, cards
>> mamory etc.
>> Would it appear to be related to heat rellated?
>> Seem a bit similar to the symptoms I got when I over clocked
>> my old computer. Although I think I got reboots.
>>
>>
>>
>> "Paul" <noone@home.com> wrote in message news:4876c63f@news01.wxnz.net...
>>> If you get a BSOD, but there's no text??
>>>
>>> On the other computer here, this has happened 2-3 times in the last 2-3
>>> weeks.
>>>
>>> It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
>>> drivers / stop error etc, and sometimes, the screen is blue and blank,
>>> and there's nothing on the screen?
>>>
>>> I'm pretty sure the main cause, is the ATI drivers.
>>>
>>> But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The funny
>>> thing is, I've installed and use both on this system, and its never
>>> crashed
>>>
>>> It has only crashed whle playing games like bejeweled, Gin, and te other
>>> day on a website, while the person was on it. The games are that graphic
>>> intensive. The card is an ASUS 9550 256mb.
>>>
>>> Most days its fine (besides the above).
>>>
>>> And lately it keeps on coming up with your system has recovered from a
>>> serious error.
>>>
>>> Heres a few of the logs for the crashes
>>>
>>> Event Type: Error
>>> Event Source: System Error
>>> Event Category: (102)
>>> Event ID: 1003
>>> Date: 11/07/2008
>>> Time: 7:52:09 a.m.
>>> User: N/A
>>> Computer: BELLE
>>> Description:
>>> Error code 1000008e, parameter1 c0000005, parameter2 bf92696d,
>>> parameter3 a722cc30, parameter4 00000000.
>>>
>>> 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 38 1000008
>>> 0020: 65 20 20 50 61 72 61 6d e Param
>>> 0028: 65 74 65 72 73 20 63 30 eters c0
>>> 0030: 30 30 30 30 30 35 2c 20 000005,
>>> 0038: 62 66 39 32 36 39 36 64 bf92696d
>>> 0040: 2c 20 61 37 32 32 63 63 , a722cc
>>> 0048: 33 30 2c 20 30 30 30 30 30, 0000
>>> 0050: 30 30 30 30 0000
>>>
>>>
>>> Event Type: Information
>>> Event Source: Save Dump
>>> Event Category: None
>>> Event ID: 1001
>>> Date: 10/07/2008
>>> Time: 3:00:40 p.m.
>>> User: N/A
>>> Computer: BELLE
>>> Description:
>>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
>>> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
>>> C:\WINDOWS\Minidump\Mini071008-01.dmp.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>> Event Type: Error
>>> Event Source: System Error
>>> Event Category: (102)
>>> Event ID: 1003
>>> Date: 10/07/2008
>>> Time: 7:12:18 a.m.
>>> User: N/A
>>> Computer: BELLE
>>> Description:
>>> Error code 1000007e, parameter1 c0000005, parameter2 f732d560,
>>> parameter3 f6d2fa34, parameter4 f6d2f730.
>>>
>>> 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 37 1000007
>>> 0020: 65 20 20 50 61 72 61 6d e Param
>>> 0028: 65 74 65 72 73 20 63 30 eters c0
>>> 0030: 30 30 30 30 30 35 2c 20 000005,
>>> 0038: 66 37 33 32 64 35 36 30 f732d560
>>> 0040: 2c 20 66 36 64 32 66 61 , f6d2fa
>>> 0048: 33 34 2c 20 66 36 64 32 34, f6d2
>>> 0050: 66 37 33 30 f730
>>>
>>>
>>> Event Type: Information
>>> Event Source: Save Dump
>>> Event Category: None
>>> Event ID: 1001
>>> Date: 9/07/2008
>>> Time: 2:11:45 p.m.
>>> User: N/A
>>> Computer: BELLE
>>> Description:
>>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
>>> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
>>> C:\WINDOWS\Minidump\Mini070908-01.dmp.
>>>
>>> For more information, see Help and Support Center at
>>> http://go.microsoft.com/fwlink/events.asp.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>

 

[Paul]

Re: What could be the cause

The vidcards are the same (9550), except mine doesnt have a fan. The other
has a fan

The ram is exactly the same (PQI or something).

The mobos (this is an Asrock 2.4 800 fsb) and CPU arent the same (the other
an ASUS 2.4 533 fsb)

I'll rather not swap ram, since I use this more than the other. For most of
the day. For business

"Bazzer Smith" <me@invalid.net> wrote in message
news:KABdk.5251$xs1.1752@newsfe28.ams2...
> Are the cards in each machine the same?
>
> If so you could swop them over, that should tell you something.
>
> I guess if it crashes with a different card in it tells you it is not the
> card.
> If the other machine crashes with that card you have the culprite!!
>
> Maybe it is the drivers, but if as you they work on the other machine,
> there
> must be more too it.
>
> I am assuming they are the same card model.
>
> Dunno if you can swop memory too?
>
>
> "Paul" <noone@home.com> wrote in message news:4876e035@news01.wxnz.net...
>> Nope AFAIK its not overheating,
>>
>> I'm pretty sure the ram isnt the prob. It has only been crashing say in
>> the 2-3 weeks.
>>
>> And the ram thats in it, has been there for 2yrs +
>>
>> And has been fine no prob till now.
>>
>> But, I'll do a check with memtest or MS's windiag program to see what one
>> of these say
>>
>> It just seems funny that its these annoying ATI drivers, everytime it
>> does crash (when you see something), its pointing to different ATI driver
>> files. It doesnt matter what version I use, it crashes
>>
>> I dont overclock, so its definitely not that.
>>
>> The videocard fan was a bit dusty the other week, so I removed it and
>> cleaned it out. It still crashed.
>>
>> I'll try reseating the ram and CPU. Theres only 2 cards in it (a modem,
>> and the vidcard). The vidcard is in properly.
>>
>> Thanx
>>
>>
>> "Bazzer Smith" <me@invalid.net> wrote in message
>> news:TBAdk.5232$xs1.829@newsfe28.ams2...
>>> Maybe it is related to hardware, like my problem the other day?
>>> Can't do any harm to check everything is seated correctly, cards
>>> mamory etc.
>>> Would it appear to be related to heat rellated?
>>> Seem a bit similar to the symptoms I got when I over clocked
>>> my old computer. Although I think I got reboots.
>>>
>>>
>>>
>>> "Paul" <noone@home.com> wrote in message
>>> news:4876c63f@news01.wxnz.net...
>>>> If you get a BSOD, but there's no text??
>>>>
>>>> On the other computer here, this has happened 2-3 times in the last 2-3
>>>> weeks.
>>>>
>>>> It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
>>>> drivers / stop error etc, and sometimes, the screen is blue and blank,
>>>> and there's nothing on the screen?
>>>>
>>>> I'm pretty sure the main cause, is the ATI drivers.
>>>>
>>>> But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The
>>>> funny thing is, I've installed and use both on this system, and its
>>>> never crashed
>>>>
>>>> It has only crashed whle playing games like bejeweled, Gin, and te
>>>> other day on a website, while the person was on it. The games are that
>>>> graphic intensive. The card is an ASUS 9550 256mb.
>>>>
>>>> Most days its fine (besides the above).
>>>>
>>>> And lately it keeps on coming up with your system has recovered from a
>>>> serious error.
>>>>
>>>> Heres a few of the logs for the crashes
>>>>
>>>> Event Type: Error
>>>> Event Source: System Error
>>>> Event Category: (102)
>>>> Event ID: 1003
>>>> Date: 11/07/2008
>>>> Time: 7:52:09 a.m.
>>>> User: N/A
>>>> Computer: BELLE
>>>> Description:
>>>> Error code 1000008e, parameter1 c0000005, parameter2 bf92696d,
>>>> parameter3 a722cc30, parameter4 00000000.
>>>>
>>>> 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 38 1000008
>>>> 0020: 65 20 20 50 61 72 61 6d e Param
>>>> 0028: 65 74 65 72 73 20 63 30 eters c0
>>>> 0030: 30 30 30 30 30 35 2c 20 000005,
>>>> 0038: 62 66 39 32 36 39 36 64 bf92696d
>>>> 0040: 2c 20 61 37 32 32 63 63 , a722cc
>>>> 0048: 33 30 2c 20 30 30 30 30 30, 0000
>>>> 0050: 30 30 30 30 0000
>>>>
>>>>
>>>> Event Type: Information
>>>> Event Source: Save Dump
>>>> Event Category: None
>>>> Event ID: 1001
>>>> Date: 10/07/2008
>>>> Time: 3:00:40 p.m.
>>>> User: N/A
>>>> Computer: BELLE
>>>> Description:
>>>> The computer has rebooted from a bugcheck. The bugcheck was:
>>>> 0x1000008e (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was
>>>> saved in: C:\WINDOWS\Minidump\Mini071008-01.dmp.
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>>
>>>> Event Type: Error
>>>> Event Source: System Error
>>>> Event Category: (102)
>>>> Event ID: 1003
>>>> Date: 10/07/2008
>>>> Time: 7:12:18 a.m.
>>>> User: N/A
>>>> Computer: BELLE
>>>> Description:
>>>> Error code 1000007e, parameter1 c0000005, parameter2 f732d560,
>>>> parameter3 f6d2fa34, parameter4 f6d2f730.
>>>>
>>>> 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 37 1000007
>>>> 0020: 65 20 20 50 61 72 61 6d e Param
>>>> 0028: 65 74 65 72 73 20 63 30 eters c0
>>>> 0030: 30 30 30 30 30 35 2c 20 000005,
>>>> 0038: 66 37 33 32 64 35 36 30 f732d560
>>>> 0040: 2c 20 66 36 64 32 66 61 , f6d2fa
>>>> 0048: 33 34 2c 20 66 36 64 32 34, f6d2
>>>> 0050: 66 37 33 30 f730
>>>>
>>>>
>>>> Event Type: Information
>>>> Event Source: Save Dump
>>>> Event Category: None
>>>> Event ID: 1001
>>>> Date: 9/07/2008
>>>> Time: 2:11:45 p.m.
>>>> User: N/A
>>>> Computer: BELLE
>>>> Description:
>>>> The computer has rebooted from a bugcheck. The bugcheck was:
>>>> 0x1000007e (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was
>>>> saved in: C:\WINDOWS\Minidump\Mini070908-01.dmp.
>>>>
>>>> For more information, see Help and Support Center at
>>>> http://go.microsoft.com/fwlink/events.asp.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

 

[Rey Santos]

RE: What could be the cause

Event 1003 see this link:
http://www.microsoft.com/technet/su...=5.2&EvtID=1003&EvtSrc=System Error&LCID=1033

The matching Event ID's:

Event ID: 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
(0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
C:\WINDOWS\Minidump\Mini070908-01.dmp.
See this:
Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
http://msdn.microsoft.com/en-us/library/ms795746.aspx

Event ID: 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
(0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
C:\WINDOWS\Minidump\Mini071008-01.dmp.
See this:
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
http://msdn.microsoft.com/en-us/library/ms794023.aspx

Your two dump files C:\WINDOWS\Minidump\Mini070908-01.dmp and
C:\WINDOWS\Minidump\Mini071008-01.dmp.
You can analyze this files using debugging tools:

How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263

Minidump Analysis
http://www.memecode.com/docs/minidump.php (Post Mortem)
--
Rey


"Paul" wrote:

> If you get a BSOD, but there's no text??
>
> On the other computer here, this has happened 2-3 times in the last 2-3
> weeks.
>
> It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
> drivers / stop error etc, and sometimes, the screen is blue and blank, and
> there's nothing on the screen?
>
> I'm pretty sure the main cause, is the ATI drivers.
>
> But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The funny
> thing is, I've installed and use both on this system, and its never crashed
>
> It has only crashed whle playing games like bejeweled, Gin, and te other day
> on a website, while the person was on it. The games are that graphic
> intensive. The card is an ASUS 9550 256mb.
>
> Most days its fine (besides the above).
>
> And lately it keeps on coming up with your system has recovered from a
> serious error.
>
> Heres a few of the logs for the crashes
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 11/07/2008
> Time: 7:52:09 a.m.
> User: N/A
> Computer: BELLE
> Description:
> Error code 1000008e, parameter1 c0000005, parameter2 bf92696d, parameter3
> a722cc30, parameter4 00000000.
>
> 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 38 1000008
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 63 30 eters c0
> 0030: 30 30 30 30 30 35 2c 20 000005,
> 0038: 62 66 39 32 36 39 36 64 bf92696d
> 0040: 2c 20 61 37 32 32 63 63 , a722cc
> 0048: 33 30 2c 20 30 30 30 30 30, 0000
> 0050: 30 30 30 30 0000
>
>
> Event Type: Information
> Event Source: Save Dump
> Event Category: None
> Event ID: 1001
> Date: 10/07/2008
> Time: 3:00:40 p.m.
> User: N/A
> Computer: BELLE
> Description:
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
> C:\WINDOWS\Minidump\Mini071008-01.dmp.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 10/07/2008
> Time: 7:12:18 a.m.
> User: N/A
> Computer: BELLE
> Description:
> Error code 1000007e, parameter1 c0000005, parameter2 f732d560, parameter3
> f6d2fa34, parameter4 f6d2f730.
>
> 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 37 1000007
> 0020: 65 20 20 50 61 72 61 6d e Param
> 0028: 65 74 65 72 73 20 63 30 eters c0
> 0030: 30 30 30 30 30 35 2c 20 000005,
> 0038: 66 37 33 32 64 35 36 30 f732d560
> 0040: 2c 20 66 36 64 32 66 61 , f6d2fa
> 0048: 33 34 2c 20 66 36 64 32 34, f6d2
> 0050: 66 37 33 30 f730
>
>
> Event Type: Information
> Event Source: Save Dump
> Event Category: None
> Event ID: 1001
> Date: 9/07/2008
> Time: 2:11:45 p.m.
> User: N/A
> Computer: BELLE
> Description:
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
> C:\WINDOWS\Minidump\Mini070908-01.dmp.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
>
>
>
>
>
>
>
>

 

[Paul]

Re: What could be the cause

Cheers Rey, checking the links now

"Rey Santos" <ReySantos@discussions.microsoft.com> wrote in message
newsCCDD4EB-05B9-4DDB-AFDF-FF5DF65C071B@microsoft.com...
> Event 1003 see this link:
> http://www.microsoft.com/technet/su...=5.2&EvtID=1003&EvtSrc=System Error&LCID=1033
>
> The matching Event ID's:
>
> Event ID: 1001
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
> C:\WINDOWS\Minidump\Mini070908-01.dmp.
> See this:
> Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
> http://msdn.microsoft.com/en-us/library/ms795746.aspx
>
> Event ID: 1001
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
> C:\WINDOWS\Minidump\Mini071008-01.dmp.
> See this:
> Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
> http://msdn.microsoft.com/en-us/library/ms794023.aspx
>
> Your two dump files C:\WINDOWS\Minidump\Mini070908-01.dmp and
> C:\WINDOWS\Minidump\Mini071008-01.dmp.
> You can analyze this files using debugging tools:
>
> How to read the small memory dump files that Windows creates for debugging
> http://support.microsoft.com/kb/315263
>
> Minidump Analysis
> http://www.memecode.com/docs/minidump.php (Post Mortem)
> --
> Rey
>
>
> "Paul" wrote:
>
>> If you get a BSOD, but there's no text??
>>
>> On the other computer here, this has happened 2-3 times in the last 2-3
>> weeks.
>>
>> It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
>> drivers / stop error etc, and sometimes, the screen is blue and blank,
>> and
>> there's nothing on the screen?
>>
>> I'm pretty sure the main cause, is the ATI drivers.
>>
>> But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The funny
>> thing is, I've installed and use both on this system, and its never
>> crashed
>>
>> It has only crashed whle playing games like bejeweled, Gin, and te other
>> day
>> on a website, while the person was on it. The games are that graphic
>> intensive. The card is an ASUS 9550 256mb.
>>
>> Most days its fine (besides the above).
>>
>> And lately it keeps on coming up with your system has recovered from a
>> serious error.
>>
>> Heres a few of the logs for the crashes
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 11/07/2008
>> Time: 7:52:09 a.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> Error code 1000008e, parameter1 c0000005, parameter2 bf92696d, parameter3
>> a722cc30, parameter4 00000000.
>>
>> 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 38 1000008
>> 0020: 65 20 20 50 61 72 61 6d e Param
>> 0028: 65 74 65 72 73 20 63 30 eters c0
>> 0030: 30 30 30 30 30 35 2c 20 000005,
>> 0038: 62 66 39 32 36 39 36 64 bf92696d
>> 0040: 2c 20 61 37 32 32 63 63 , a722cc
>> 0048: 33 30 2c 20 30 30 30 30 30, 0000
>> 0050: 30 30 30 30 0000
>>
>>
>> Event Type: Information
>> Event Source: Save Dump
>> Event Category: None
>> Event ID: 1001
>> Date: 10/07/2008
>> Time: 3:00:40 p.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
>> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
>> C:\WINDOWS\Minidump\Mini071008-01.dmp.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 10/07/2008
>> Time: 7:12:18 a.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> Error code 1000007e, parameter1 c0000005, parameter2 f732d560, parameter3
>> f6d2fa34, parameter4 f6d2f730.
>>
>> 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 37 1000007
>> 0020: 65 20 20 50 61 72 61 6d e Param
>> 0028: 65 74 65 72 73 20 63 30 eters c0
>> 0030: 30 30 30 30 30 35 2c 20 000005,
>> 0038: 66 37 33 32 64 35 36 30 f732d560
>> 0040: 2c 20 66 36 64 32 66 61 , f6d2fa
>> 0048: 33 34 2c 20 66 36 64 32 34, f6d2
>> 0050: 66 37 33 30 f730
>>
>>
>> Event Type: Information
>> Event Source: Save Dump
>> Event Category: None
>> Event ID: 1001
>> Date: 9/07/2008
>> Time: 2:11:45 p.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
>> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
>> C:\WINDOWS\Minidump\Mini070908-01.dmp.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>

 

[Paul]

Re: What could be the cause

I checked some of the dmp files with MS's debugging programm.

Thats what told me, the ATI drivers were causing most of the crashes.

I've tried the latest drivers, older ATI drivers, ASUS ATI drivers since
these are ASUS cards.

It doesnt matter both crash. I still cant figure out why, when I've got the
same version of the drivers on this, its never crashed once.

It doesnt matter, what I do.

Other only option is to check the ram, if thats fine, I'll chuck the mobo,
and get another



"Rey Santos" <ReySantos@discussions.microsoft.com> wrote in message
newsCCDD4EB-05B9-4DDB-AFDF-FF5DF65C071B@microsoft.com...
> Event 1003 see this link:
> http://www.microsoft.com/technet/su...=5.2&EvtID=1003&EvtSrc=System Error&LCID=1033
>
> The matching Event ID's:
>
> Event ID: 1001
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
> C:\WINDOWS\Minidump\Mini070908-01.dmp.
> See this:
> Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
> http://msdn.microsoft.com/en-us/library/ms795746.aspx
>
> Event ID: 1001
> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
> C:\WINDOWS\Minidump\Mini071008-01.dmp.
> See this:
> Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
> http://msdn.microsoft.com/en-us/library/ms794023.aspx
>
> Your two dump files C:\WINDOWS\Minidump\Mini070908-01.dmp and
> C:\WINDOWS\Minidump\Mini071008-01.dmp.
> You can analyze this files using debugging tools:
>
> How to read the small memory dump files that Windows creates for debugging
> http://support.microsoft.com/kb/315263
>
> Minidump Analysis
> http://www.memecode.com/docs/minidump.php (Post Mortem)
> --
> Rey
>
>
> "Paul" wrote:
>
>> If you get a BSOD, but there's no text??
>>
>> On the other computer here, this has happened 2-3 times in the last 2-3
>> weeks.
>>
>> It seems to be intermittent. Sometimes, it'll bring up a BSOD with the
>> drivers / stop error etc, and sometimes, the screen is blue and blank,
>> and
>> there's nothing on the screen?
>>
>> I'm pretty sure the main cause, is the ATI drivers.
>>
>> But, I've tried the ATI drivers, and ASUS drivers. BOTH crash. The funny
>> thing is, I've installed and use both on this system, and its never
>> crashed
>>
>> It has only crashed whle playing games like bejeweled, Gin, and te other
>> day
>> on a website, while the person was on it. The games are that graphic
>> intensive. The card is an ASUS 9550 256mb.
>>
>> Most days its fine (besides the above).
>>
>> And lately it keeps on coming up with your system has recovered from a
>> serious error.
>>
>> Heres a few of the logs for the crashes
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 11/07/2008
>> Time: 7:52:09 a.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> Error code 1000008e, parameter1 c0000005, parameter2 bf92696d, parameter3
>> a722cc30, parameter4 00000000.
>>
>> 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 38 1000008
>> 0020: 65 20 20 50 61 72 61 6d e Param
>> 0028: 65 74 65 72 73 20 63 30 eters c0
>> 0030: 30 30 30 30 30 35 2c 20 000005,
>> 0038: 62 66 39 32 36 39 36 64 bf92696d
>> 0040: 2c 20 61 37 32 32 63 63 , a722cc
>> 0048: 33 30 2c 20 30 30 30 30 30, 0000
>> 0050: 30 30 30 30 0000
>>
>>
>> Event Type: Information
>> Event Source: Save Dump
>> Event Category: None
>> Event ID: 1001
>> Date: 10/07/2008
>> Time: 3:00:40 p.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e
>> (0xc0000005, 0xbf92696d, 0xa722cc30, 0x00000000). A dump was saved in:
>> C:\WINDOWS\Minidump\Mini071008-01.dmp.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> Event Type: Error
>> Event Source: System Error
>> Event Category: (102)
>> Event ID: 1003
>> Date: 10/07/2008
>> Time: 7:12:18 a.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> Error code 1000007e, parameter1 c0000005, parameter2 f732d560, parameter3
>> f6d2fa34, parameter4 f6d2f730.
>>
>> 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 37 1000007
>> 0020: 65 20 20 50 61 72 61 6d e Param
>> 0028: 65 74 65 72 73 20 63 30 eters c0
>> 0030: 30 30 30 30 30 35 2c 20 000005,
>> 0038: 66 37 33 32 64 35 36 30 f732d560
>> 0040: 2c 20 66 36 64 32 66 61 , f6d2fa
>> 0048: 33 34 2c 20 66 36 64 32 34, f6d2
>> 0050: 66 37 33 30 f730
>>
>>
>> Event Type: Information
>> Event Source: Save Dump
>> Event Category: None
>> Event ID: 1001
>> Date: 9/07/2008
>> Time: 2:11:45 p.m.
>> User: N/A
>> Computer: BELLE
>> Description:
>> The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e
>> (0xc0000005, 0xf732d560, 0xf6d2fa34, 0xf6d2f730). A dump was saved in:
>> C:\WINDOWS\Minidump\Mini070908-01.dmp.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>

 

[Daave]

Re: What could be the cause

"Paul" <noone@home.com> wrote in message
news:487744ee@news01.wxnz.net...
>I checked some of the dmp files with MS's debugging programm.
>
> Thats what told me, the ATI drivers were causing most of the crashes.
>
> I've tried the latest drivers, older ATI drivers, ASUS ATI drivers
> since these are ASUS cards.
>
> It doesnt matter both crash. I still cant figure out why, when I've
> got the same version of the drivers on this, its never crashed once.
>
> It doesnt matter, what I do.
>
> Other only option is to check the ram, if thats fine, I'll chuck the
> mobo, and get another

Did you rule out a bad graphics card?

If your mobo has onboard video, I would take the ASUS card out of the
equation and alter your BIOS to use the onboard graphics.

 

[Paul]

Re: What could be the cause

It doesnt have onboard video

I havent got another card to see if the card maybe
the prob

"Daave" <dcwashNOSPAM@myrealboxXYZ.invalid> wrote in message
news:ehx$xR24IHA.784@TK2MSFTNGP04.phx.gbl...
> "Paul" <noone@home.com> wrote in message news:487744ee@news01.wxnz.net...
>>I checked some of the dmp files with MS's debugging programm.
>>
>> Thats what told me, the ATI drivers were causing most of the crashes.
>>
>> I've tried the latest drivers, older ATI drivers, ASUS ATI drivers since
>> these are ASUS cards.
>>
>> It doesnt matter both crash. I still cant figure out why, when I've got
>> the same version of the drivers on this, its never crashed once.
>>
>> It doesnt matter, what I do.
>>
>> Other only option is to check the ram, if thats fine, I'll chuck the
>> mobo, and get another
>
> Did you rule out a bad graphics card?
>
> If your mobo has onboard video, I would take the ASUS card out of the
> equation and alter your BIOS to use the onboard graphics.
>