BSOD

N

nite01

Member
Joined
Jan 7, 2014
Posts
5
Hi. I recently purchased an Acer Aspire V5-552G-X414 and have experienced about four random bsod and the error "irql not less than or equal to". I also experienced one or two spontaneous reboots.
· OS - Windows 8
· x64
· Originally windows 8 (pre-installed)
· have not reinstalled

· CPU- AMD A10-5757M APU with Radeon(tm) graphics
· Video Card- AMD Radeon HD 8650G + 8750M Dual HD Graphics (4CPUs), ~2.5GHz
· MotherBoard- Acer Dazzle_RL

· System Manufacturer- Acer
· Exact model number- (chinese characters followed by) ZRI
 

Attachments

Code: 
[COLOR=#ff0000]BugCheck A[/COLOR], {67dcef6f8, f, 0, fffff8008ad973c0}

Probably caused by : [COLOR=#ff0000]cpuz136_x64.sys[/COLOR] ( cpuz136_x64+2073 )

It seems like a easy bugcheck, the Unicode string for the driver seems to have been found on the stack. The reason for this bugcheck seems to a result of accessing a invalid memory address (can be many different reasons), or executing a instruction at the wrong IRQL Level.

Code: 
3: kd> [COLOR=#008000].trap 0xfffff8801ded7130[/COLOR]
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffffffffd0e000
[COLOR=#0000cd]rdx=000000067dcef6f8[/COLOR] rsi=0000000000000000 rdi=0000000000000000
rip=fffff8008ad973c0 rsp=fffff8801ded72c8 rbp=ffffffffffd0e000
 r8=000000000000008c  r9=000000000000008c r10=0000000000000000
r11=fffff8008ada2f60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
[COLOR=#ff0000]hal!HalpPciWriteMmConfigUlong[/COLOR]:
fffff800`8ad973c0 8b02            mov     eax,dword ptr [[COLOR=#0000cd]rdx[/COLOR]] ds:00000006`7dcef6f8=????????

The referenced address seems to be a non-paged pool address, and therefore we can rule out any problems regarding pool types.

Here's an example of the _POOL_TYPE enumeration:

Code: 
3: kd> [COLOR=#008000]dt nt!_POOL_TYPE[/COLOR]
   NonPagedPool = 0n0
   NonPagedPoolExecute = 0n0
   PagedPool = 0n1
   NonPagedPoolMustSucceed = 0n2
   DontUseThisType = 0n3
   NonPagedPoolCacheAligned = 0n4
   PagedPoolCacheAligned = 0n5
   NonPagedPoolCacheAlignedMustS = 0n6
   MaxPoolType = 0n7
   NonPagedPoolBase = 0n0
   NonPagedPoolBaseMustSucceed = 0n2
   NonPagedPoolBaseCacheAligned = 0n4
   NonPagedPoolBaseCacheAlignedMustS = 0n6
   NonPagedPoolSession = 0n32
   PagedPoolSession = 0n33
   NonPagedPoolMustSucceedSession = 0n34
   DontUseThisTypeSession = 0n35
   NonPagedPoolCacheAlignedSession = 0n36
   PagedPoolCacheAlignedSession = 0n37
   NonPagedPoolCacheAlignedMustSSession = 0n38
   NonPagedPoolNx = 0n512
   NonPagedPoolNxCacheAligned = 0n516
   NonPagedPoolSessionNx = 0n544

Code: 
3: kd> [COLOR=#008000]!irql[/COLOR]
Debugger saved IRQL for processor 0x3 -- [COLOR=#ff0000]15[/COLOR] (HIGH_LEVEL)

Code: 
3: kd> [COLOR=#008000]knL[/COLOR]
  *** Stack trace for last set context - .thread/.cxr resets it                   [COLOR=#008000]//(Set to context of the trap frame)[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff880`1ded72c8 fffff800`8ad88915 [COLOR=#ff0000]hal!HalpPciWriteMmConfigUlong[/COLOR] <-- Related to PCI Configuration Space?
01 fffff880`1ded72d0 fffff800`8ad87bbb hal!HalpPCIPerformConfigAccess+0x55
02 fffff880`1ded7300 fffff800`8ad886b7 hal!HalpPciAccessMmConfigSpace+0x19f
03 fffff880`1ded7350 fffff800`8ad8853b hal!HalpPCIConfig+0x5f
04 fffff880`1ded73c0 fffff800`8ad883a6 hal!HalpWritePCIConfig+0x4f
05 fffff880`1ded7400 fffff800`8ad87179 hal!HalpSetPCIData+0x182
06 fffff880`1ded7530 fffff880`1be48073 hal!HalSetBusDataByOffset+0x89
07 fffff880`1ded7640 00000000`00000004 [COLOR=#ff0000]cpuz136_x64[/COLOR]+0x2073
08 fffff880`1ded7648 00000000`00000000 0x4

What interests me the most, is the hal!HalpPciWriteMmConfigUlong function which belongs to the HAL.dll library. I'm assuming that the function writes some form of configuration data into the configuration space of the PCI bus. I'll probably read into this tomorrow. For those interested, I'll also advise checking the latest PCI Express documentation.

Anyhow, your CPUID CPU-Z driver seems to be causing problems, please update to the latest version of the program, and report back if the issue persists or not. CPU-Z CPUID - System & hardware benchmark, monitoring, reporting

Code: 
3: kd> [COLOR=#008000]lmvm cpuz136_x64[/COLOR]
start             end                 module name
fffff880`1be46000 fffff880`1be4f000   cpuz136_x64 T (no symbols)           
    Loaded symbol image file: cpuz136_x64.sys
    Image path: \??\C:\Windows\TEMP\cpuz136\cpuz136_x64.sys
    Image name: cpuz136_x64.sys
    Timestamp:        [COLOR=#ff0000]Sat Oct 27 18:24:41 2012[/COLOR] (508C18D9)
    CheckSum:         0000F097
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Further Reading:

PCI - OSDev Wiki
PCI configuration space - Wikipedia, the free encyclopedia
 
x BlueRobot said:
Code: 
[COLOR=#ff0000]BugCheck A[/COLOR], {67dcef6f8, f, 0, fffff8008ad973c0}

Probably caused by : [COLOR=#ff0000]cpuz136_x64.sys[/COLOR] ( cpuz136_x64+2073 )

It seems like a easy bugcheck, the Unicode string for the driver seems to have been found on the stack. The reason for this bugcheck seems to a result of accessing a invalid memory address (can be many different reasons), or executing a instruction at the wrong IRQL Level.

Code: 
3: kd> [COLOR=#008000].trap 0xfffff8801ded7130[/COLOR]
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffffffffd0e000
[COLOR=#0000cd]rdx=000000067dcef6f8[/COLOR] rsi=0000000000000000 rdi=0000000000000000
rip=fffff8008ad973c0 rsp=fffff8801ded72c8 rbp=ffffffffffd0e000
 r8=000000000000008c  r9=000000000000008c r10=0000000000000000
r11=fffff8008ada2f60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
[COLOR=#ff0000]hal!HalpPciWriteMmConfigUlong[/COLOR]:
fffff800`8ad973c0 8b02            mov     eax,dword ptr [[COLOR=#0000cd]rdx[/COLOR]] ds:00000006`7dcef6f8=????????

The referenced address seems to be a non-paged pool address, and therefore we can rule out any problems regarding pool types.

Here's an example of the _POOL_TYPE enumeration:

Code: 
3: kd> [COLOR=#008000]dt nt!_POOL_TYPE[/COLOR]
   NonPagedPool = 0n0
   NonPagedPoolExecute = 0n0
   PagedPool = 0n1
   NonPagedPoolMustSucceed = 0n2
   DontUseThisType = 0n3
   NonPagedPoolCacheAligned = 0n4
   PagedPoolCacheAligned = 0n5
   NonPagedPoolCacheAlignedMustS = 0n6
   MaxPoolType = 0n7
   NonPagedPoolBase = 0n0
   NonPagedPoolBaseMustSucceed = 0n2
   NonPagedPoolBaseCacheAligned = 0n4
   NonPagedPoolBaseCacheAlignedMustS = 0n6
   NonPagedPoolSession = 0n32
   PagedPoolSession = 0n33
   NonPagedPoolMustSucceedSession = 0n34
   DontUseThisTypeSession = 0n35
   NonPagedPoolCacheAlignedSession = 0n36
   PagedPoolCacheAlignedSession = 0n37
   NonPagedPoolCacheAlignedMustSSession = 0n38
   NonPagedPoolNx = 0n512
   NonPagedPoolNxCacheAligned = 0n516
   NonPagedPoolSessionNx = 0n544

Code: 
3: kd> [COLOR=#008000]!irql[/COLOR]
Debugger saved IRQL for processor 0x3 -- [COLOR=#ff0000]15[/COLOR] (HIGH_LEVEL)

Code: 
3: kd> [COLOR=#008000]knL[/COLOR]
  *** Stack trace for last set context - .thread/.cxr resets it                   [COLOR=#008000]//(Set to context of the trap frame)[/COLOR]
 # Child-SP          RetAddr           Call Site
00 fffff880`1ded72c8 fffff800`8ad88915 [COLOR=#ff0000]hal!HalpPciWriteMmConfigUlong[/COLOR] <-- Related to PCI Configuration Space?
01 fffff880`1ded72d0 fffff800`8ad87bbb hal!HalpPCIPerformConfigAccess+0x55
02 fffff880`1ded7300 fffff800`8ad886b7 hal!HalpPciAccessMmConfigSpace+0x19f
03 fffff880`1ded7350 fffff800`8ad8853b hal!HalpPCIConfig+0x5f
04 fffff880`1ded73c0 fffff800`8ad883a6 hal!HalpWritePCIConfig+0x4f
05 fffff880`1ded7400 fffff800`8ad87179 hal!HalpSetPCIData+0x182
06 fffff880`1ded7530 fffff880`1be48073 hal!HalSetBusDataByOffset+0x89
07 fffff880`1ded7640 00000000`00000004 [COLOR=#ff0000]cpuz136_x64[/COLOR]+0x2073
08 fffff880`1ded7648 00000000`00000000 0x4

What interests me the most, is the hal!HalpPciWriteMmConfigUlong function which belongs to the HAL.dll library. I'm assuming that the function writes some form of configuration data into the configuration space of the PCI bus. I'll probably read into this tomorrow. For those interested, I'll also advise checking the latest PCI Express documentation.

Anyhow, your CPUID CPU-Z driver seems to be causing problems, please update to the latest version of the program, and report back if the issue persists or not. CPU-Z CPUID - System & hardware benchmark, monitoring, reporting

Code: 
3: kd> [COLOR=#008000]lmvm cpuz136_x64[/COLOR]
start             end                 module name
fffff880`1be46000 fffff880`1be4f000   cpuz136_x64 T (no symbols)           
    Loaded symbol image file: cpuz136_x64.sys
    Image path: \??\C:\Windows\TEMP\cpuz136\cpuz136_x64.sys
    Image name: cpuz136_x64.sys
    Timestamp:        [COLOR=#ff0000]Sat Oct 27 18:24:41 2012[/COLOR] (508C18D9)
    CheckSum:         0000F097
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Further Reading:

PCI - OSDev Wiki
PCI configuration space - Wikipedia, the free encyclopedia
Click to expand...

Thanks alot xBlueRobot, I'll update and monitor for any crashes.
 
x BlueRobot said:
Thanks, will look forward for an update.
Click to expand...
Hi again. The same problem occured again..about 5 minutes ago. Got the same "system needs to restart...irql not less than or equal error". Bluescreen viewer says the crash was caused by hal.dll driver and some other stuff I dont understand at all lol.
 
Sorry for double posting Im not sure how to edit or if it was even possible. Can overheating be a cause of the problem? From the first very time I turned on the laptop, straight from the box, I realized it was extremely hot so I downloaded some temperature monitoring programs (speccy, CPU Z etc) and on each one my cpu temps were between 87 and 110..never lower, while the temps for the other parts where no higher than 40. When I play games it climbs to high 90s or 100 but even when I'm not gaming the lowest temp is high 80s. Someone told me to ignore the temp monitoring programs as the laptop would shutdown if it reached those temps and the laptop only started crashing about a week now. Any thoughts? Oh and btw when the crashes occurred the only programs I opened were chrome in most cases and in one case control panel... lol
 
Hi,

Yes, definitely. Overheating is a large cause of most computer issues. Since it has been this way since you purchased the laptop, I would go ahead and return it and get a replacement or repair if warranty permits. It sounds as if there's a fan malfunctioning, and opening the laptop would void your warranty.

Regards,

Patrick
 
I agree with Patrick, overheating is a contributor to BSODs and other issues, as said before do not open the case of the laptop since this can void your warranty. It may be a broken fan, or a fan which isn't working correctly.
 
x BlueRobot said:
I agree with Patrick, overheating is a contributor to BSODs and other issues, as said before do not open the case of the laptop since this can void your warranty. It may be a broken fan, or a fan which isn't working correctly.
Click to expand...
Thanks alot guys. I'm working on returning it, have to check the warranty, I was warned smh.... lol.
 

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

Back
Top