Fatherdeath
New member
- Local time
- 5:27 PM
- Messages
- 23
The game crashed and then from what I saw it also managed to cause BSOD.
My Computer
At a glance
Windows 7 Home Premium 64 bit
- Computer type
- PC/Desktop
- OS
- Windows 7 Home Premium 64 bit
rb:Start → Run → type MSINFO32 then hit Enter.When done with the testing procedure take a picture and upload it here.Test and Diagnose RAM Issues with Memtest86+:
Tip
- :info: Pay close attention to part 3 of the tutorial "If you have errors"
- :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
First run it with all the existing/installed RAM modules. If it comes with no error, all is good.
But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.
How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
It is a RAM, a bad RAM.test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good
But if you have got a result like that:
It is a motherboard issue. The particular slot is bad.test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good
World of Warcraft appears to be causing some issues at the moment as we see more it
being mentioned in more threads recently.
So that might be a part of it, did the game receive any sort of update lately?
As for now a single bugcheck isn't much to go on except a several suspects, which are BitDefender
which was mentioned as the active process but that doesn't mean it was the cause.
Other suspects are your Razer peripherals, an apple device driver (usbaapl64.sys) and RAM/Driver.
Code 39
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
Cause
There are several causes of Code 39 errors:
Recommended resolution
- A required device driver is missing.
- A required binary file is corrupted.
- There is a problem with the file I/O process.
- A driver that is referencing an entry point in another binary file is unable to load.
Uninstall and reinstall the driver
Uninstall the driver from Device Manager, and then scan for new hardware to install the driver again.
Note You may be prompted to provide the path of the driver. Windows may have the driver built-in, or may still have the driver files installed from the last time that you set up the device. However, sometimes, it will open the New Hardware Wizard which may ask for the driver. If you are asked for the driver and you do not have it, you can try to download the latest driver from the hardware vendor's website.
- In the device's Properties dialog box, click the Driver tab, and then click Uninstall. Follow the instructions.
- Restart your computer.
- Open Device Manager, click Action, and then click Scan for hardware changes. Follow the instructions.