Bsod - hp hpe / nvidia gt320

jasonhunt · 15 Jun 2012

Hi,

Newbie here, and PC novice so please be gentle.

The spec of the new PC is as folows:

HP Elite 340uk
Intel i3 550 (3.07GHz)
nVidia GT320 (1GB)
Windows 7 Home Premium 64 bit - OEM (original)

I have attached the BSOD troubleshooting siles you recommend (I think).
Seems like the RAM, NVIDIA or HD would be the most likely candidates, but I don't know.

Have tried to run MS memory test, but it sometimes crashes?

Hope someone can help.

Many thanks.
Jason

yowanvista · 15 Jun 2012

Your McAfee software was involved, uninstall it and use MSE

Update your Nvidia Drivers, install only the Driver & PhysX, uncheck all other components.
http://www.nvidia.com/object/win7-wi...ql-driver.html

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
Note that this test may overheat the CPU, ensure proper cooling.

Test your RAM, RAM - Test with Memtest86+

Post back with your results.

Code:

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8800311ba58 -- (.exr 0xfffff8800311ba58)
ExceptionAddress: fffff88001002c53 (intelppm+0x0000000000002c53)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800311bb00 -- (.trap 0xfffff8800311bb00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=effffa80046c4000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001002c53 rsp=fffff8800311bc98 rbp=0000000000000000
 r8=fffffa8006cff320  r9=0000000023a12f20 r10=000000000000ab3b
r11=0000000000000063 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
intelppm+0x2c53:
fffff880`01002c53 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e72d6e to fffff80002e7b010

STACK_TEXT:  
fffff880`0311ab48 fffff800`02e72d6e : 00000000`00000000 fffff880`10241d9a fffff880`0311b2c0 fffff800`02ea79a8 : nt!KeBugCheck
fffff880`0311ab50 fffff800`02ea075d : fffff800`03088e70 fffff800`02fc6ff4 fffff800`02e0b000 fffff880`0311ba58 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0311ab80 fffff800`02ea7dd0 : fffff800`02fc9a64 fffff880`0311abf8 fffff880`0311ba58 fffff800`02e0b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0311abb0 fffff800`02eb4dff : fffff880`0311ba58 fffff880`0311b2c0 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff880`0311b290 fffff800`02e7a682 : fffff880`0311ba58 00000000`00000002 fffff880`0311bb00 fffff880`009f0180 : nt!KiDispatchException+0x16f
fffff880`0311b920 fffff800`02e78f8a : fffff880`100b7978 fffffa80`06f7e000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0311bb00 fffff880`01002c53 : fffff800`02e88aba 00000000`002d95ec fffffa80`046c6dd8 fffff880`009f0180 : nt!KiGeneralProtectionFault+0x10a
fffff880`0311bc98 fffff800`02e88aba : 00000000`002d95ec fffffa80`046c6dd8 fffff880`009f0180 00000000`00000000 : intelppm+0x2c53
fffff880`0311bca0 fffff800`02e8374c : fffff880`009f0180 fffff880`00000002 00000000`00000000 fffff800`00000000 : nt!PoIdle+0x53a
fffff880`0311bd80 00000000`00000000 : fffff880`0311c000 fffff880`03116000 fffff880`0311bd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+2c53
fffff880`01002c53 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  intelppm+2c53

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x1E_intelppm+2c53

BUCKET_ID:  X64_0x1E_intelppm+2c53

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