BSOD After Shutdown

[Alkison]

Hello guys. My client has an Alienware machine that's been suffering from blue screens and I cannot solve the problem. Here's what I have so far.

- Memtest, No Errors
- HD Tune, No Errors
- Reimaged from Recovery, Still BSOD
- Replaced GPU, Still BSOD

It's happening must commonly when the computer gets shutdown. It hangs for 5-10 minutes. Upon boot, Windows will display the error. The DMP files are attached to this thread. Can anyone assist me. I am thinking about removing the two HDD's in RAID0 and installing a single drive, which I would then install a vanilla version of Windows on there to see if it solves any problems.

Please do let me know.

 

[blues_harp28]

Is this a continuation of your thread here or a different pc?
http://forums.techguy.org/windows-7/1139159-0x09f-bsod-dmp-file-included.html
======
The minidumps you posted are from the following dates.
12/1/2015
13/1/2015
27/1/2015
======

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
0: kd> !analyze -v
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f84000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2
STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_1394ohci_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_1394ohci_IMAGE_pci.sys

Followup: MachineOwner

This is either from the 12th or 13th of January 2015.
FAILURE_BUCKET_ID: X64_0x9F_3_1394ohci_IMAGE_pci.sys
1394ohci - relates to a firewire driver

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.
------------------
PROCESS_NAME: System

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

TRAP_FRAME: fffff80004ace280 -- (.trap 0xfffff80004ace280)

STACK_COMMAND: .trap 0xfffff80004ace280 ; kb

FOLLOWUP_IP:
athrx+129129
fffff880`05dea129 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: athrx+129129

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: athrx

IMAGE_NAME: athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d6419db

FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_athrx+129129

BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_athrx+129129

Followup: MachineOwner

FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_athrx+129129

This one dates from the 27/1/2015
Atheros Wireless LAN device driver

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffbc8077e0700f, 1, fffff800032b5caf, 7}

Could not read faulting driver name
Probably caused by : memory_corruption

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Debugging Details:
------------------
Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c3100
ffffbc8077e0700f

FAULTING_IP:
nt!RtlLookupFunctionEntry+304
fffff800`032b5caf 0f936cffff setae byte ptr [rdi+rdi*8-1]

MM_INTERNAL_CODE: 7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: CLHelper.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800d51c940 -- (.trap 0xfffff8800d51c940)

LAST_CONTROL_TRANSFER: from fffff8000330853b to fffff8000328bbc0

STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff800032b5cb0 - nt!RtlLookupFunctionEntry+305
[ 83:93 ]
1 error : !nt (fffff800032b5cb0)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption

======
This is either from the 12th or 13th of January 2015
PROCESS_NAME: CLHelper.exe
http://www.runscanner.net/lib/clhelper.exe.html
Do not run the free registry scan at the above link.

 

[Alkison]

Check the graphic card and drivers. If still the problem persist, then try booting into safe mode and run system restore.

Like I said, I've swapped the GPU twice including the graphics drivers. I've also formatted the system, but from the Dell/Alienware recovery, not the vanilla version of Windows.

Is this a continuation of your thread here or a different pc?
http://forums.techguy.org/windows-7/1139159-0x09f-bsod-dmp-file-included.html
======
The minidumps you posted are from the following dates.
12/1/2015
13/1/2015
27/1/2015
======


This is either from the 12th or 13th of January 2015.
FAILURE_BUCKET_ID: X64_0x9F_3_1394ohci_IMAGE_pci.sys
1394ohci - relates to a firewire driver



FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_athrx+129129

This one dates from the 27/1/2015
Atheros Wireless LAN device driver


======
This is either from the 12th or 13th of January 2015
PROCESS_NAME: CLHelper.exe
http://www.runscanner.net/lib/clhelper.exe.html
Do not run the free registry scan at the above link.

Yes, to answer your first question. The 9F stop code has been the most common and occurs upon shutdown intermittently. Any suggestions? Do you think my idea of removing the two drives in RAID0 and installing a testing a drive with a vanilla version of Windows is good?

Thanks in advance.

 

[blues_harp28]

Latest blue screen error from 27/1/2015
Atheros Wireless LAN device driver
I would go for the easier option and update the driver.

 

[Alkison]

Latest blue screen error from 27/1/2015
Atheros Wireless LAN device driver
I would go for the easier option and update the driver.

Okay, great, I'll give this a shot. Do you recommend going through the PC's manufacturer or component manufacturer for the latest drivers? Also, are there any applications that aren't gimmicky, which can help track and/or update older drivers?

 

[blues_harp28]

Check the pc's manufacturer website they may have said driver.
Some use online driver scans but they can find and ask you to install an outdated driver.

http://support.alienware.com/Support_Pages/Restricted_Pages/driver_downloads.aspx
======
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Memory corruption is also listed from the 12th or 13th of January 2015 linked to CyberLink Player.
Re-install the above.
Did you run the Memtest overnight or for a least 8 passes?
It is best to run a full scan on individual Ram sticks if you can.
Or run the test but if any errors are shown - then remove all sticks of Ram and test each Ram stick one at a time and in different slots.