Computer keeps Blue Screening, can't figure out why

Anonymous
2012-05-21T04:18:47+00:00

I just finished building my own gaming PC the other day. And yesterday my computer BSODed while playing Just Cause 2, and today it did again while playing the same game. The Event Viewer says it's an Error 41 (Kernel-Power). I really have no idea what to do. All my drivers are up to date, my power supply is defiantly big enough, and all my hardware is more then enough to handle anything I'm doing. What should I do?

EDIT: I should clarify that I know it's not a problem with overheating as well. My video card (Radeon 6950) has stayed under 60(c) the whole time, as well as my processor (AMD8150 8 core) staying under 40(c).

Windows for home | Windows 11 | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-05-21T18:10:02+00:00

Just FYI - sometimes lower level drivers (such as AMD Overdrive or Gigabyte EasyTune) can cause systems to act as if there is a hardware problem.  So, we're still not certain if this is hardware or software - so please continue to run the diagnostics suggested previously.

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.  This driver is known to cause BSOD's on some Win7 systems.  If doesn't appear to be installed on your system, then it may be a part of the Gigabyte EasyTune6 program (another one that's known to cause BSOD's on Win7 systems).

*******

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program

Then, download and install a fresh copy of the ATI drivers from http://www.ati.com (in the upper right corner of the page)

  • Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)

Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC).  This is a separate issue and isn't required for the AMD OverDrive removal.

If the device (AODDriver or AODDriver4.01) remains a problem in perfmon /report, open Device Manager, select the "View" item.

Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.

Locate the AODDriver entry, right click on it and select "Uninstall".  Reboot for changes to take affect.

*******

Sometimes the driver remains and continues to cause BSOD's.  If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Also, please uninstall the Gigabyte Easy Saver - mobo power utility driver and the Gigabyte EasyTune6 program (it may contain the AMD Overdrive program).  Both are known to cause BSOD's on some Win7 systems.

I am suspicious of the Applecharger program also, but have no firm evidence for it.  Please just keep an eye on it for now.

If that doesn't stop the BSOD's, please run Driver Verifier according to these directions:  http;//www.carrona.org/verifier.html

*****************************************************************************

BSOD BUGCHECK SUMMARY

Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\051912-22464-01.dmp]

Built by: 7600.16988.amd64fre.win7_gdr.120401-1505

Debug session time: Sat May 19 16:39:43.993 2012 (UTC - 4:00)

System Uptime: 0 days 0:31:58.600

BugCheck A, {6, 2, 0, fffff80003095a93}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+e3 )

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+e3

Bugcheck code 0000000A

Arguments 0000000000000006 0000000000000002 0000000000000000 fffff80003095a93

BiosVersion = F7

BiosReleaseDate = 10/13/2011

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Loading Dump File [C:\Users\FUBAR\jcgriff2_\dbug\_Kernel__\052012-25287-01.dmp]

Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504

Debug session time: Mon May 21 00:00:30.836 2012 (UTC - 4:00)

System Uptime: 0 days 0:29:47.101

BugCheck 101, {19, 0, fffff8800316d180, 7}

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

Bugcheck code 00000101

Arguments 0000000000000019 0000000000000000 fffff8800316d180 0000000000000007

BiosVersion = F7

BiosReleaseDate = 10/13/2011

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Was this answer helpful?

1 person found this answer helpful.
0 comments

65 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-06-04T04:10:07+00:00

    You're welcome. Unless the motherboard is faulty (very, very rare), the new memory will work well for you.

    Good luck and yep, please tell us how it goes.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-06-04T04:08:26+00:00

    Doing both those things made no difference, I submitted an RMA request on the memory, I plan to go with a Corsair model that was on the list of compatible RAM. I will update this thread when I receive the new memory. Thank you very much for your help and for all the time you've put in here to help me. It is very much appreciated.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-06-04T03:25:36+00:00

    It's insignificant about ntsokrnl.exe.

    2 things:

    1. Install latest USB 3.0 driver from following link
    2. Install AMD SATA RAID Driver (Preinstall driver, press F6 during Windows* setup to read from floppy) using the device manager.

    http://www.gigabyte.com/products/product-page.aspx?pid=3908#dl

    Latest crash dump is this, involving a page fault:

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    An attempt was made to access a pageable (or completely invalid) address at an

    interrupt request level (IRQL) that is too high.  This is usually

    caused by drivers using improper addresses.

    If kernel debugger is available get stack backtrace.

    Arguments:

    Arg1: 0000000000000068, memory referenced

    Arg2: 0000000000000002, IRQL

    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

    Arg4: fffff88000e3d227, address which referenced memory

    Debugging Details:

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c1100

     0000000000000068

    CURRENT_IRQL:  2

    FAULTING_IP:

    ataport!IdeStartNextDeviceRequest+7f

    fffff880`00e3d227 488b8e98000000  mov     rcx,qword ptr [rsi+98h]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  fffff88003192770 -- (.trap 0xfffff88003192770)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000000 rbx=0000000000000000 rcx=fffff88000e491a0

    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff88000e3d227 rsp=fffff88003192900 rbp=fffffa80048187d0

     r8=fffff88003192960  r9=0000000000000000 r10=fffffa80047fe620

    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0         nv up ei pl zr na po nc

    ataport!IdeStartNextDeviceRequest+0x7f:

    fffff88000e3d227 488b8e98000000  mov     rcx,qword ptr [rsi+98h] ds:1ea0:0000000000000098=????????????????

    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80003091769 to fffff800030921c0

    STACK_TEXT: 

    fffff88003192628 fffff80003091769 : 000000000000000a 0000000000000068 0000000000000002 0000000000000000 : nt!KeBugCheckEx

    fffff88003192630 fffff800030903e0 : fffffa80047fd1a0 fffff800035ff71f fffffa8003be2c20 0000000000000001 : nt!KiBugCheckDispatch+0x69

    fffff88003192770 fffff88000e3d227 : 0000000000000001 fffffa80048187d0 fffffa80048189f0 fffffa80049d6b80 : nt!KiPageFault+0x260

    fffff88003192900 fffff88000e3f59a : fffffa8003992c01 0000000000000000 fffffa80048187d0 fffffa80049d6b80 : ataport!IdeStartNextDeviceRequest+0x7f

    fffff880031929a0 fffff88000e3f104 : fffffa80047fd1a0 0000000000000000 fffffa80047fd1a0 fffffa80049d6b80 : ataport!IdeProcessCompletedRequests+0x26a

    fffff88003192ad0 fffff8000309c8fc : fffff8800316a180 00000000162dee9c fffffa80047fd050 fffffa80047fd118 : ataport!IdePortCompletionDpc+0x1a8

    fffff88003192b90 fffff80003089eca : fffff8800316a180 fffff880031750c0 0000000000000000 fffff88000e3ef5c : nt!KiRetireDpcList+0x1bc

    fffff88003192c40 0000000000000000 : fffff88003193000 fffff8800318d000 fffff88003192c00 0000000000000000 : nt!KiIdleLoop+0x5a

    STACK_COMMAND:  kb

    FOLLOWUP_IP:

    ataport!IdeStartNextDeviceRequest+7f

    fffff880`00e3d227 488b8e98000000  mov     rcx,qword ptr [rsi+98h]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  ataport!IdeStartNextDeviceRequest+7f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ataport

    IMAGE_NAME:  ataport.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79293

    FAILURE_BUCKET_ID:  X64_0xD1_ataport!IdeStartNextDeviceRequest+7f

    BUCKET_ID:  X64_0xD1_ataport!IdeStartNextDeviceRequest+7f

    Followup: MachineOwner

    Very likely still memory, but you can also try moving your HDD(s) to different unused ports if there are any available. If you have old IDE hard drive(s) attached, remove them for now,

    If you can't get anything going well after this, then return the memory to the store or GSkill themselves. They will replace it and request a matching set in return. (You already have matched set, but good to tell them anyway.)

    Tell them about your motherboard and ask for compatible memory. Your current memory is not on the list, although it is very close to one that is.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2012-06-04T03:12:09+00:00

    So would you say that I just have 2 defective sticks of memory? Or would you say that it sounds like something else is the problem?

    Was this answer helpful?

    0 comments