BSOD in Elite Dangerous game only - Windows 7 x64

N

Nate

Member
Joined
Dec 17, 2014
Posts
7
Thank you for this website. So I got a new mother board about three weeks ago. Changed my cpu and got more ram. Updated my bios and drivers. Started playing this new space sim game Elite dangerous and it BSOD's on me. It's very strang because sometimes it will only take five minutes, yesterday I played for 4 hours just about. I didn't use the BSOD dump app that you guys had posted because it wasn't working for me. So I managed to get it with another program. Hopefully, you can still manage. Thanks for your help.

-Nate

pc:

OS: windows 7
MOBO: Z97 gaming 5
CPU: Intel core i5-4690k @3.50ghz
RAM: Corsair 2x4 8gb
GPUS: Nvidia 660ti
HDD:
 
Hi,

Thank you for this website.
Click to expand...

Thank you for the kind words.

I'm going to take a nap now but if there's no reply by the time I wake up, I'll take a look for you.
 
Hey Patrick. Can you manage with that zip I sent you guys? That the right format? Like I said, I couldn't use the program that John had posted in the instructions post.
 
Can you upload the latest crash dump? You don't need to run the app, just zip up the crash dumps manually and attach the zip here.
 
Yes, thank you.

BAD_POOL_HEADER (19)

This indicates that a pool header is corrupt.

Code: 
2: kd> .bugcheck
Bugcheck code 00000019
Arguments 00000000`00000020 fffffa80`07eea000 fffffa80`07eea440 00000000`04440000

Corrupt pool block header size.

Code: 
2: kd> !pool fffffa8007eea000
Bad previous allocation size @fffffa8007eea440, last size was 44

***
*** An error (or corruption) in the pool was detected;
*** Attempting to diagnose the problem.
***
*** Use !poolval fffffa8007eea000 for more details.


Pool page [ fffffa8007eea000 ] is __inVALID.

Analyzing linked list...
[ fffffa8007eea000 --> fffffa8007eeafc0 (size = 0xfc0 bytes)]: Corrupt region

Probably a buggy 3rd party driver causing it.


1. Uninstall AVG Secure Search.

2. Uninstall Daemon Tools.

3.

Code: 
2: kd> lmvm ppjoybus64
start             end                 module name
fffff880`06fe1000 fffff880`06feb000   PPJoyBus64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\PPJoyBus64.sys
    Image name: PPJoyBus64.sys
    Timestamp:        Fri Feb 19 23:38:17 2010

Your Joystick driver is probably an issue here, it's old. Look for an update - http://ppjoy.bossstation.dnsalias.org/

If not available, uninstall the software + remove the device.
 
Thank you very much Patrick. How do I uninstall PPjoy. I looked for it under the uninstal directory and I couldn't find it. This isn't the first time that driver has cause issues to my computer. I appreciate the quick response really.

Edit! I found the files.. apparently they're in use! haha! This is definitely causing the problem. Thank you Patrick. I'll let you know after I get rid of them if I BSOD again. Thank you sincerely.

-Nate
 
For now just remove the joystick and then navigate to C:\Windows\System32\Drivers and rename the PPJoyBus64.sys driver to PPJoyBus64.bak, and then restart the computer.
 
So far I've done the tasks you suggested and everything seemed to be going smoothly however, I just got another BSOD with a SYSTEM_SERVICE_EXCEPTION message. :banghead: There's now a file in my windows folder but it's labeled MEMORY.dmp and it's also a half gig. Can't even attach the zip.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top