Jump to content
Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble

Recommended Posts

So I got a new computer early last month and the 90 day warranty has not expired yet. I have an Hp Pavilion dv6 and it works beautifully...HOWEVER, for the first time in the history of owning a few laptops, I have encountered a BSOD at least 3 if not 4 times in the past few days. Perhaps its a Windows 7 thing...the HP Pavilion is my first laptop with Windows 7. At the third or fourth restart after going in safe mode then restarting, it no longer notified me of recovering from an unexpected shut down even though the problem was the same. When I went itno safe mode and doing a check on the systems, the security loader processor is the only thing that seemed to be of concern.

The code is: BCCode: 7f ((whats that mean?))

I have searched online to try and get info on issues with the security processor loader, but many of those were for windows Vista and/or had a different BCCode.

Can someone explain to me what this means? I have not asked the HP help site what the deal is because I know this is a problem with the system. I don't even know what the security processor loader IS. Since I like to learn about computers where I can, explanations would be appreciated.

I downloaded the Windows SDK debugging tool. I have never used any debugging tools before so if this issue requires a debugging tool then I'm going to need step by step instructions to resolve this.

And my last question is: if this is a minor issue, should i just deal with it? I don't lose any raw data. It is certainly annoying that the BSOD pops up randomly though.

If anyone needs PC information, I can get it.

Minidump information is attached.

Thanks in advance,

~Jetta

Minidump_01-24_Pavdv6.zip

Share this post


Link to post
Share on other sites

What is different with the machine since all this BSOD business started, Jetta?

Any new programs, firewall and/or antivirus installed? New hardware? Damage? Overclocking?

:welcomewf:

Jobe

Share this post


Link to post
Share on other sites

Nice find Alan ! :)

We dont know where the poster lives but.............................

Under UK law, buyers in England and Wales can get a partial refund or full repair up to six years after the purchase was made (five years from discovery in Scotland). The refund should take into account how much use the customer has already had of a product. Ultimately, a county court would decide this.

However, the likelihood of getting such a refund is dramatically reduced after just six months. The reason is that for six months after the purchase, it is up to the retailer to show that a fault on an item is down to the actions or misuse of the buyer, rather than an inherent fault in the product.

After six months, the burden of proof switches to the buyer and it is they who must then show a fault is due to some inherent problem, something that can be almost impossible in all but the most straightforward cases.

Read more: http://www.thisismon...l#ixzz1keIj70AV

,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,=,

Both mini-dump files point to a probable Video driver fault as originally pointed out to poster over at this thread:

http://forums.window...showtopic=49304

Since I like to learn about computers where I can, explanations would be appreciated.

Click on the link above for explanation about BSOD's

if this is a minor issue, should i just deal with it?

Yes. - If you find you cannot deal with it, ask a friend or someone with computer knowledge, or as in this case, - return it to the retailer.

Hope that's of some help nickster.

John.

Share this post


Link to post
Share on other sites

Summary

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff8800158f9eb

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: b

LAST_CONTROL_TRANSFER: from fffff80002c8e1e9 to fffff80002c8ec40

STACK_TEXT:
fffff800`04b1fd28 fffff800`02c8e1e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`04b1fd30 fffff800`02c8c6b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04b1fe70 fffff880`0158f9eb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0f182fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmpag+0x49eb


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmpag+49eb
fffff880`0158f9eb e880f90100 call atikmpag+0x24370 (fffff880`015af370)

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: atikmpag+49eb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d7f6895

FAILURE_BUCKET_ID: X64_0x7f_8_atikmpag+49eb

BUCKET_ID: X64_0x7f_8_atikmpag+49eb

Followup: MachineOwner
---------

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e57670
Debug session time: Tue Jan 24 15:40:52.696 2012 (GMT-7)
System Uptime: 0 days 18:44:52.571

I see you have SP1, so that's all good. If you're overclocking anything I would recommend to STOP.

Here's the last instruction ran by your graphics driver here:

fffff880`0158f9eb e880f90100      call    atikmpag+0x24370 (fffff880`015af370)
fffff880`0158f9f0 33d2 xor edx,edx
fffff880`0158f9f2 4c8d4730 lea r8,[rdi+30h]
fffff880`0158f9f6 498b18 mov rbx,qword ptr [r8]
fffff880`0158f9f9 4885db test rbx,rbx
fffff880`0158f9fc 740a je atikmpag+0x4a08 (fffff880`0158fa08)
fffff880`0158f9fe 488b4308 mov rax,qword ptr [rbx+8]
fffff880`0158fa02 4c3b6020 cmp r12,qword ptr [rax+20h]

NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ed3240000000889f rbx=0000000000000000 rcx=b54100000280838b
rdx=0000a6840fc08501 rsi=0000000000000000 rdi=0000000000000000
rip=000931bb80410001 rsp=c3048b49c0034800 rbp=8b485824548b0000
r8=057305f883c93300 r9=58bb8308c74c8b48 r10=5024748b03000008
r11=8b077503fe830c75 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 ov up ei pl nz ac pe nc
000931bb`80410001 ?? ???

The driver itself seems up to date:

fffff880`0158b000 fffff880`015da000   atikmpag atikmpag.sys Tue Mar 15 07:24:37 2011 (4D7F6895)

This is common with hardware issues, and perhaps it's incompatible with your motherboard, else you might have a stack overflow with this issue, but that does NOT look like the case here as there's only 4 calls in the stack itself. So i'm going to assume that it's a hardware issue, and related to your graphics driver here.

What happened here was a double fault, so that means that the kernel tried to handle a past exception which essentially resulted in a new exception that could not be dealt with serially, which is why your crash was initiated.

Share this post


Link to post
Share on other sites

Yeah but all of that don't mean diddly squat to the average computer user, and for sure would hold him up on reporting a warranty fault within the prescribed time as laid out under EU Regs.

Looks impressive on paper but thats about all as far as getting a result quickly and avoiding parting with money.

John.

Share this post


Link to post
Share on other sites

Thank you for that.

Unfortunately in "Real Life" it's the chap with the hammer, wrench,screwdiver, who has to analyse, diagnose, and fix a faulty computer. When someone of your obvious excellent calibre is required they are nowhere to be seen. lol lol & another lol. :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy