Regular BSOD - Multiple Machines tested.

[Duskborn]

<p>Hey Folks, </p><p>Just wondering if anyone else is having an issue with BSOD's whilst gaming on EQ2? </p><p>I started to experience the issue earlier this week on one of my computers so I went through and ran a troubleshoot on all of my drivers and hardware, I've found no issues. I left it and started to play on another machine, which first showed no issues but earlier today - I had the same BSOD relating to a 'Physical Memory Dump' </p><p>I aren't completely computer literate but I thought it must be something related to the game as the only thing thats the same between the two computers is the 'net connection as they share a router and the EQ2 accts I was using to play. The OS, Virus Protection, hardware and everything else are different. </p><p>Thanks in advance, </p><p>Neriko</p>

[Lalen]

<p>I've actually had the client crash a few times when zoning, but no BSOD's -- generally this is an indicator of curruption somewhere, whether it be in your hard drive or memory.</p>

[TSR-JoshuaM]

<p>BSOD's are typically indicative of a driver or hardware failure.  It can also be caused by incompatible software but this should not be the case here.</p><p>What I'll need is the Event name and Stop code for the BSOD itself.  With this information I can help you pinpoint what failed.  This information is displayed on the BSOD itself.  You'll see 5 sets of numbers that read STOP: #x######## with more numbers in paranthesis.  I just need that first step right after the STOP: line and the Event name itself.</p>

[TSR-JoshuaM]

<p>To further explain, <span style="color: #cae0e6; font-family: verdana, arial, helvetica, sans-serif; background-color: #07161e;">Physical Memory Dump</span></p><p>This is an action that is taken when a BSOD occurs.  It dumps everything in memory to a physical file so that you can look in what data was being stored at the time of the error, among other recovery related reasonings.</p>

[Duskborn]

<p>Hey, </p><p>Thank You for the response, I'll post that info here tomorrow evening - It's been a busy few days IRL. </p><p>Neriko. </p>

[Duskborn]

<p>I've finally managed to pull some time aside for this, busy few days.</p><p>Anyway, I went through the System Events Viewer and found a load of criticals that said the same thing and correspond with the crash times.</p><p>'<span >The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80002ca7a95, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:WindowsMEMORY.DMP. Report Id: 082811-31168-01.' </span></p><p><span >There are a few that state the Eq2voiceservice.exe - Does that mean that my sound drivers are playing up and causing the crashes? The computer runs fine until I start EQ2 and join a group, perhaps it's when the group voice channel is created? </span></p><p><span >Thanks for the continued support. </span></p><p><span >Neriko. </span></p>

[TSR-JoshuaM]

<p>Neriko, please open a support ticket and give me the incident number.  Include your DXDIAG/MSINFO files as well please.</p>