Random BSOD errors on new labtop

atmayoni said:

I am getting random BSOD errors on a newly purchased Packard Bell Labtop. I am not playing games neither using any heavy load programs. Once it happened while I was surfing. All the drivers are up to date.

I have attached the dumpfiles.

Any help would be appreciated.

All the best and thank you for making this forum available.

Hello !! Welcome to SF !!

The Dump files pointing to System files. Please follow the below steps.

Run the Memory Diagnostic & HD Diagnostic

Start > CMD > Right Click and Run as Administrator > SFC /SCANNOW

If you have an Antivirus / Firewall try uninstalling it and see whether it makes any difference. Update your BIOS Firmware. Uninstall all the Adobe Softwares completely.

Update the Following Drivers

Code:

 
PxHlpa64.sys Thu Mar 13 07:28:17 2008
adfs.SYS     Fri Jun 27 02:22:37 2008

Follow this link for Driver Updates: Drivers and Downloads

Code:

*******************************************************************************
*                                                                             *
*                        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: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002ea0e58
Debugging Details:
------------------
 
BUGCHECK_STR:  0x7f_8
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002ed7b69 to fffff80002ed8600
STACK_TEXT:  
fffff880`02fdbce8 fffff800`02ed7b69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdbcf0 fffff800`02ed6032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdbe30 fffff800`02ea0e58 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`058bef70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02ed6032 90              nop
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Hope this helps,
Captain