NR2003 rebooting Windows

I've seen that some others have this problem and I do as well. It's happened about 6 times since installing the sim on Friday. 3 times I was running a single race at Daytona, got through the practice, qualifying, and happy hour - click on the Drive button for the actual race, and ... just an empty black screen and the computer is rebooting! This is a new system I put together in December, so there's hardly been time to crap it up with demos and downloads and whatever. System specs: Intel D845PEBT2 motherboard (w/integrated audio) P4 2.53GHz CPU 512MB PC2700 DDR (Crucial) ATI Radeon 9500 Pro 128MB video card Pioneer DVD-106S slot-load DVD drive Windows XP Home DirectX 8.1a ATI Catalyst 2.5 drivers So, next I upgraded to DirectX 9, and the ATI Catalyst 3.1 drivers. Now I could actually run the Daytona race, but got two more rebooting incidents while in the middle of the race, both during accidents. Really strange. Finally, I was able to complete a 20-lap race, I think maybe because there were no accidents. ;-) This new sim has killer graphics and physics - easily the most realistic of any sim I've ever tried, but on the other hand, I've never seen any PC game reboot a system like this one is doing. I saw something on the Papy NR2003 forum, where some guys were experimenting with lowering the DirectX hardware sound acceleration until the problem stops. Does that sound right? I'm not sure I want to do that, but if that's the answer, then I guess I would. Anyone have other ideas? -Bill J.

Bill, I had this exact same issue....it was really annoying, anytime I clicked on Drive it would immediately reboot. I went and downloaded the latest VIA drivers for my mothervoard and it fixed the problem.....I don't think your board has the via chipset, but try downloading the latest drivers for your board (probably intel chipset). "Bill Jones" <[email hidden]> wrote in message news:6ej4a.2985$[email hidden]... > I've seen that some others have this problem and I do as well. It's > happened about 6 times since installing the sim on Friday. 3 times I was > running a single race at Daytona, got through the practice, qualifying,and > happy hour - click on the Drive button for the actual race, and ... justan > empty black screen and the computer is rebooting! > > This is a new system I put together in December, so there's hardly beentime

Quoted text (20 lines)

> to crap it up with demos and downloads and whatever. System specs: > > Intel D845PEBT2 motherboard (w/integrated audio) > P4 2.53GHz CPU > 512MB PC2700 DDR (Crucial) > ATI Radeon 9500 Pro 128MB video card > Pioneer DVD-106S slot-load DVD drive > Windows XP Home > DirectX 8.1a > ATI Catalyst 2.5 drivers > > So, next I upgraded to DirectX 9, and the ATI Catalyst 3.1 drivers. > > Now I could actually run the Daytona race, but got two more rebooting > incidents while in the middle of the race, both during accidents. Really > strange. > > Finally, I was able to complete a 20-lap race, I think maybe because there > were no accidents. ;-) This new sim has killer graphics and physics - > easily the most realistic of any sim I've ever tried, but on the other

hand, > I've never seen any PC game reboot a system like this one is doing. > > I saw something on the Papy NR2003 forum, where some guys wereexperimenting

Quoted text (13 lines)

> with lowering the DirectX hardware sound acceleration until the problem > stops. Does that sound right? I'm not sure I want to do that, but if > that's the answer, then I guess I would. > > Anyone have other ideas? > > > > -Bill J. > > > >

Bill, the solution you mention could be worth a try. It's at least a valid possibility. Achim

Integrated audio is meant for office beeps and bloops. If you intend to run games and sims, you should get a real sound card. In the meantime try lowering the acceleration and/or lowering the number of sounds in the game to 1 (as an experiment). If those don't cure the problem, it is most likely video-related, but you already have the drivers that cured most ATI video problems for the rest of the gang. Marc es" <[email hidden]> wrote in message news:6ej4a.2985$[email hidden]... > I've seen that some others have this problem and I do as well. It's > happened about 6 times since installing the sim on Friday. 3 times I was > running a single race at Daytona, got through the practice, qualifying,and > happy hour - click on the Drive button for the actual race, and ... justan > empty black screen and the computer is rebooting! > > This is a new system I put together in December, so there's hardly beentime

Quoted text (20 lines)

> to crap it up with demos and downloads and whatever. System specs: > > Intel D845PEBT2 motherboard (w/integrated audio) > P4 2.53GHz CPU > 512MB PC2700 DDR (Crucial) > ATI Radeon 9500 Pro 128MB video card > Pioneer DVD-106S slot-load DVD drive > Windows XP Home > DirectX 8.1a > ATI Catalyst 2.5 drivers > > So, next I upgraded to DirectX 9, and the ATI Catalyst 3.1 drivers. > > Now I could actually run the Daytona race, but got two more rebooting > incidents while in the middle of the race, both during accidents. Really > strange. > > Finally, I was able to complete a 20-lap race, I think maybe because there > were no accidents. ;-) This new sim has killer graphics and physics - > easily the most realistic of any sim I've ever tried, but on the other

hand, > I've never seen any PC game reboot a system like this one is doing. > > I saw something on the Papy NR2003 forum, where some guys wereexperimenting

Quoted text (12 lines)

> with lowering the DirectX hardware sound acceleration until the problem > stops. Does that sound right? I'm not sure I want to do that, but if > that's the answer, then I guess I would. > > Anyone have other ideas? > > > > -Bill J. > > >

That's a bit different from what I have read, and what I have experienced but only in that your computer is rebooting and not just dumping to the desktop as mine does. One thing has been in common. Every report I've read, and in my few cases, it has always happened when hitting the Drive button. Larry "Bill Jones" <[email hidden]> wrote in message news:6ej4a.2985$[email hidden]... > I've seen that some others have this problem and I do as well. It's > happened about 6 times since installing the sim on Friday. 3 times I was > running a single race at Daytona, got through the practice, qualifying,and > happy hour - click on the Drive button for the actual race, and ... justan > empty black screen and the computer is rebooting! > > This is a new system I put together in December, so there's hardly beentime

Quoted text (20 lines)

> to crap it up with demos and downloads and whatever. System specs: > > Intel D845PEBT2 motherboard (w/integrated audio) > P4 2.53GHz CPU > 512MB PC2700 DDR (Crucial) > ATI Radeon 9500 Pro 128MB video card > Pioneer DVD-106S slot-load DVD drive > Windows XP Home > DirectX 8.1a > ATI Catalyst 2.5 drivers > > So, next I upgraded to DirectX 9, and the ATI Catalyst 3.1 drivers. > > Now I could actually run the Daytona race, but got two more rebooting > incidents while in the middle of the race, both during accidents. Really > strange. > > Finally, I was able to complete a 20-lap race, I think maybe because there > were no accidents. ;-) This new sim has killer graphics and physics - > easily the most realistic of any sim I've ever tried, but on the other

hand, > I've never seen any PC game reboot a system like this one is doing. > > I saw something on the Papy NR2003 forum, where some guys wereexperimenting

Quoted text (12 lines)

> with lowering the DirectX hardware sound acceleration until the problem > stops. Does that sound right? I'm not sure I want to do that, but if > that's the answer, then I guess I would. > > Anyone have other ideas? > > > > -Bill J. > > >

I don't think it's video related on my machine. I've had it happen under both D3D and OpenGL, and with two different versions of nVidia drivers (30.xx and 41.xx). Since there isn't a whole lot in common that I've seen, I'm leaning towards a DX9 issue, the one thing I can't do anything about :( Larry "Marc Collins" <[email hidden]> wrote in message news:K5r4a.2884$[email hidden]... > Integrated audio is meant for office beeps and bloops. If you intend torun > games and sims, you should get a real sound card. In the meantime try > lowering the acceleration and/or lowering the number of sounds in the game > to 1 (as an experiment). If those don't cure the problem, it is mostlikely

Quoted text (11 lines)

> video-related, but you already have the drivers that cured most ATI video > problems for the rest of the gang. > > Marc > > > > es" <[email hidden]> wrote in message > news:6ej4a.2985$[email hidden]... > > I've seen that some others have this problem and I do as well. It's > > happened about 6 times since installing the sim on Friday. 3 times I

was > > running a single race at Daytona, got through the practice, qualifying, > and > > happy hour - click on the Drive button for the actual race, and ...just

Quoted text (20 lines)

> an > > empty black screen and the computer is rebooting! > > > > This is a new system I put together in December, so there's hardly been > time > > to crap it up with demos and downloads and whatever. System specs: > > > > Intel D845PEBT2 motherboard (w/integrated audio) > > P4 2.53GHz CPU > > 512MB PC2700 DDR (Crucial) > > ATI Radeon 9500 Pro 128MB video card > > Pioneer DVD-106S slot-load DVD drive > > Windows XP Home > > DirectX 8.1a > > ATI Catalyst 2.5 drivers > > > > So, next I upgraded to DirectX 9, and the ATI Catalyst 3.1 drivers. > > > > Now I could actually run the Daytona race, but got two more rebooting > > incidents while in the middle of the race, both during accidents.

Really > > strange. > > > > Finally, I was able to complete a 20-lap race, I think maybe becausethere

Quoted text (21 lines)

> > were no accidents. ;-) This new sim has killer graphics and physics - > > easily the most realistic of any sim I've ever tried, but on the other > hand, > > I've never seen any PC game reboot a system like this one is doing. > > > > I saw something on the Papy NR2003 forum, where some guys were > experimenting > > with lowering the DirectX hardware sound acceleration until the problem > > stops. Does that sound right? I'm not sure I want to do that, but if > > that's the answer, then I guess I would. > > > > Anyone have other ideas? > > > > > > > > -Bill J. > > > > > > > >

I had the exact same problem and I solved it by going to the start menu, clicking run, and then entering "dxdiag", after this loads, click on the "sound" tab and then move the acceleration slider 1 click to the left to select Standard Acceleration. This worked for me "Bill Jones" <[email hidden]> wrote in message news:<6ej4a.2985$[email hidden]>...

Quoted text (39 lines)

> I've seen that some others have this problem and I do as well. It's > happened about 6 times since installing the sim on Friday. 3 times I was > running a single race at Daytona, got through the practice, qualifying, and > happy hour - click on the Drive button for the actual race, and ... just an > empty black screen and the computer is rebooting! > > This is a new system I put together in December, so there's hardly been time > to crap it up with demos and downloads and whatever. System specs: > > Intel D845PEBT2 motherboard (w/integrated audio) > P4 2.53GHz CPU > 512MB PC2700 DDR (Crucial) > ATI Radeon 9500 Pro 128MB video card > Pioneer DVD-106S slot-load DVD drive > Windows XP Home > DirectX 8.1a > ATI Catalyst 2.5 drivers > > So, next I upgraded to DirectX 9, and the ATI Catalyst 3.1 drivers. > > Now I could actually run the Daytona race, but got two more rebooting > incidents while in the middle of the race, both during accidents. Really > strange. > > Finally, I was able to complete a 20-lap race, I think maybe because there > were no accidents. ;-) This new sim has killer graphics and physics - > easily the most realistic of any sim I've ever tried, but on the other hand, > I've never seen any PC game reboot a system like this one is doing. > > I saw something on the Papy NR2003 forum, where some guys were experimenting > with lowering the DirectX hardware sound acceleration until the problem > stops. Does that sound right? I'm not sure I want to do that, but if > that's the answer, then I guess I would. > > Anyone have other ideas? > > > > -Bill J.

"IQ_9" <[email hidden]> wrote in message news:[email hidden]... > I had the exact same problem and I solved it by going to the start > menu, clicking run, and then entering "dxdiag", after this loads, > click on the "sound" tab and then move the acceleration slider 1 click > to the left to select Standard Acceleration. This worked for me Yes! Thank you. That works. Do you also have integrated sound, or a sound card? -Bill J.

I have the same Intel D845PEBT2 and I am also using the integrated audio, If you disable "automatically restart on errors" you get a blue screen detailing an error with the "smwdm.sys" file which is the driver for the integrated Soundmax audio chip. The latest audio driver on Intel's website is dated Sept. 23, 2002, so it is getting a bit old. I hope that Papyrus/Intel/ADI can figure out what to do to correct this so that this does not happen again.

Quoted text (7 lines)

> > Yes! Thank you. That works. > > Do you also have integrated sound, or a sound card? > > > -Bill J.

"IQ_9" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (7 lines)

> I have the same Intel D845PEBT2 and I am also using the integrated > audio, If you disable "automatically restart on errors" you get a blue > screen detailing an error with the "smwdm.sys" file which is the > driver for the integrated Soundmax audio chip. The latest audio driver > on Intel's website is dated Sept. 23, 2002, so it is getting a bit > old. I hope that Papyrus/Intel/ADI can figure out what to do to > correct this so that this does not happen again.

I hope they are aware there is a problem, so they work on fixing it. I wonder if that driver was developed for DX9? In the meantime, lowering the DirectX sound hardware acceleration doesn't affect the sound quality, does it? Are there any adverse effects? -Bill J.

Interesting. I'll give that a try. Larry "IQ_9" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (8 lines)

> I had the exact same problem and I solved it by going to the start > menu, clicking run, and then entering "dxdiag", after this loads, > click on the "sound" tab and then move the acceleration slider 1 click > to the left to select Standard Acceleration. This worked for me > > > > "Bill Jones" <[email hidden]> wrote in message

news:<6ej4a.2985$[email hidden]>... > > I've seen that some others have this problem and I do as well. It's > > happened about 6 times since installing the sim on Friday. 3 times Iwas > > running a single race at Daytona, got through the practice, qualifying,and > > happy hour - click on the Drive button for the actual race, and ...just an > > empty black screen and the computer is rebooting! > > > > This is a new system I put together in December, so there's hardly beentime

Quoted text (15 lines)

> > to crap it up with demos and downloads and whatever. System specs: > > > > Intel D845PEBT2 motherboard (w/integrated audio) > > P4 2.53GHz CPU > > 512MB PC2700 DDR (Crucial) > > ATI Radeon 9500 Pro 128MB video card > > Pioneer DVD-106S slot-load DVD drive > > Windows XP Home > > DirectX 8.1a > > ATI Catalyst 2.5 drivers > > > > So, next I upgraded to DirectX 9, and the ATI Catalyst 3.1 drivers. > > > > Now I could actually run the Daytona race, but got two more rebooting > > incidents while in the middle of the race, both during accidents.

Really > > strange. > > > > Finally, I was able to complete a 20-lap race, I think maybe becausethere > > were no accidents. ;-) This new sim has killer graphics and physics - > > easily the most realistic of any sim I've ever tried, but on the otherhand, > > I've never seen any PC game reboot a system like this one is doing. > > > > I saw something on the Papy NR2003 forum, where some guys wereexperimenting

Quoted text (9 lines)

> > with lowering the DirectX hardware sound acceleration until the problem > > stops. Does that sound right? I'm not sure I want to do that, but if > > that's the answer, then I guess I would. > > > > Anyone have other ideas? > > > > > > > > -Bill J.