BSOD 0x8000000000000002

I recently built a new system, and I am getting intermittent BSODs. I think I may need to simply bump up my cpu-nb voltage a bit to stabilize my overclock, but I wanted to rule out graphics card driver conflicts first. I appreciate the help in interpreting this info. Thanks!

-Both the relevant files are zipped together.


1090T @4.1ghz (1.44V) / NB @2.6ghz (1.9V) - On Air (Zalman 9500A-LED)
MSI 890FXA-GD70
XFX BE 750W PSU
2 X 4gb GSkill 1333mhz
2 X Zalman S64GB (1 for OS & 1 for Main Gaming)
2 X Samsung HD502HJ (striped)
1 X WDC WD3200AAKS
2 X 6850 Cyclones / Catalyst 11.3 / Acer G245H (1920x1080)
Asus Xonar DX
Win 7 x64 Home Premium

ProfesorScience said:

I recently built a new system, and I am getting intermittent BSODs. I think I may need to simply bump up my cpu-nb voltage a bit to stabilize my overclock, but I wanted to rule out graphics card driver conflicts first. I appreciate the help in interpreting this info. Thanks!

-Both the relevant files are zipped together.


1090T @4.1ghz (1.44V) / NB @2.6ghz (1.9V) - On Air (Zalman 9500A-LED)
MSI 890FXA-GD70
XFX BE 750W PSU
2 X 4gb GSkill 1333mhz
2 X Zalman S64GB (1 for OS & 1 for Main Gaming)
2 X Samsung HD502HJ (striped)
1 X WDC WD3200AAKS
2 X 6850 Cyclones / Catalyst 11.3 / Acer G245H (1920x1080)
Asus Xonar DX
Win 7 x64 Home Premium

Difficult to diagnose from a single crash. The active thread at time of crash was aion.bin, but I suspect a hardware problem (ram).

I would run these two tests.


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Old drivers needing update

Code:

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
 The error that generates this bug check usually occurs after the  installation of a faulty device driver, system service, or BIOS.
 If you encounter bug check 0xA while upgrading to a later version of  Windows, this error might be caused by a device driver, a system  service, a virus scanner, or a backup tool that is incompatible with the  new version.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Thanks for the advice. I will run driver verifier to see if anything is up on that end. Memory checks out perfectly, unless there is something Memtest is missing...

Ran Driver verifier and BSOD on restart, so I restored. Must be a driver then I guess?

zigzag3143 said:

ProfesorScience said:

I recently built a new system, and I am getting intermittent BSODs. I think I may need to simply bump up my cpu-nb voltage a bit to stabilize my overclock, but I wanted to rule out graphics card driver conflicts first. I appreciate the help in interpreting this info. Thanks!

-Both the relevant files are zipped together.


1090T @4.1ghz (1.44V) / NB @2.6ghz (1.9V) - On Air (Zalman 9500A-LED)
MSI 890FXA-GD70
XFX BE 750W PSU
2 X 4gb GSkill 1333mhz
2 X Zalman S64GB (1 for OS & 1 for Main Gaming)
2 X Samsung HD502HJ (striped)
1 X WDC WD3200AAKS
2 X 6850 Cyclones / Catalyst 11.3 / Acer G245H (1920x1080)
Asus Xonar DX
Win 7 x64 Home Premium

Difficult to diagnose from a single crash. The active thread at time of crash was aion.bin, but I suspect a hardware problem (ram).

I would run these two tests.


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Old drivers needing update

Code:

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
 The error that generates this bug check usually occurs after the  installation of a faulty device driver, system service, or BIOS.
 If you encounter bug check 0xA while upgrading to a later version of  Windows, this error might be caused by a device driver, a system  service, a virus scanner, or a backup tool that is incompatible with the  new version.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Ok - after I BSOD'd running Driver Verifier, I updated all suspect drivers, returned my pagefile to the OS drive (had it on a separate drive but have hear of people having problems by not retaining on OS) and perfmon reports nothing now. Assuming that all driver issues have been rectified, I can assume that the issue has been resolved? Again RAM checks out. The only other culprit may be Avast, although this would be the first build I have encountered such issues with...

Thanks again for the assist, and I'll post dump files if this reoccurs.

For whatever it's worth, after a careful search it seems that the culprit was the Mad Catz software associated with their Cyborg Mouse series. The drivers are ok, but the software which is used to adjust dpi and custom profiles doesn't seem to play nice with Win7 x64. I had the latest version of it too, and sure enough when the software is stressed through verifier - immediate bsod...