Windows 7 geeft bsod

[Luukg]

ok is gelukt. nu maar hopen. dat het goed komt.

 

[Luukg]

nee niet gelukt
weer een bsod

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112010-16265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*your local folder for symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c43e50
Debug session time: Sat Nov 20 15:23:12.504 2010 (UTC + 1:00)
System Uptime: 0 days 1:09:00.145
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 
+3061613762363632
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

EXCEPTION_RECORD:  fffff88002f1b7c8 -- (.exr 0xfffff88002f1b7c8)
ExceptionAddress: fffff80002a7d377 (nt!KeAccumulateTicks+0x0000000000000127)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f1b870 -- (.trap 0xfffff88002f1b870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=e5280d65435148cc rbx=0000000000000000 rcx=0000000000000011
rdx=0000000000009fff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a7d377 rsp=fffff88002f1ba00 rbp=0000000000000001
 r8=000000000000bebc  r9=0000000000000000 r10=000000000001cc00
r11=fffff880089cba90 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAccumulateTicks+0x127:
fffff800`02a7d377 85ff            test    edi,edi
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a6e46e to fffff80002a76710

STACK_TEXT:  
fffff880`02f1a8b8 fffff800`02a6e46e : 00000000`00000010 fffff880`01667124 fffff880`02f1b030 fffff800`02aa3668 : nt!KeBugCheck
fffff880`02f1a8c0 fffff800`02a9c40d : fffff800`02c84edc fffff800`02bbddac fffff800`02a06000 fffff880`02f1b7c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1a8f0 fffff800`02aa3a90 : fffff800`02bc5b14 fffff880`02f1a968 fffff880`02f1b7c8 fffff800`02a06000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1a920 fffff800`02ab09ef : fffff880`02f1b7c8 fffff880`02f1b030 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x410
fffff880`02f1b000 fffff800`02a75d82 : fffff880`02f1b7c8 fffff880`009e8180 fffff880`02f1b870 fffff880`009f2f40 : nt!KiDispatchException+0x16f
fffff880`02f1b690 fffff800`02a7468a : 00000000`00000000 fffffa80`0656da50 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02f1b870 fffff800`02a7d377 : fffffa80`05056800 fffffa80`00000000 00000000`00000001 ffff0000`0133ea3e : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1ba00 fffff800`02a83618 : 00000000`00000000 00002405`00000000 00000000`00002626 00000000`00000001 : nt!KeAccumulateTicks+0x127
fffff880`02f1ba90 fffff800`02a833a1 : 00000000`00000000 fffff880`02f1bb40 fffff880`009e8180 00000000`00000001 : nt!KeUpdateRunTime+0xb8
fffff880`02f1bac0 fffff880`03b399c2 : fffff800`02a8424a 00000000`0029c3d5 fffffa80`05059dd8 fffff880`009f2f40 : nt!KiSecondaryClockInterrupt+0x131
fffff880`02f1bc58 fffff800`02a8424a : 00000000`0029c3d5 fffffa80`05059dd8 fffff880`009f2f40 00000000`00000001 : intelppm+0x39c2
fffff880`02f1bc60 fffff800`02a7eebc : fffff880`009e8180 fffff880`00000000 00000000`00000000 fffff880`03c20480 : nt!PoIdle+0x53a
fffff880`02f1bd40 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd00 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`03b399c2 ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  intelppm+39c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x1E_0_intelppm+39c2

BUCKET_ID:  X64_0x1E_0_intelppm+39c2

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

waarschijnlijk licht het toch aan de hardware. Kan een netwerkkaart dit misschien veroorzaken? Graag help

 

[dnties]

Heb ik het goed gezien dat je een AMD processor gebruikt? Indien ja, dan kun je intelppm.sys uitschakelen (bijv. via AutoRuns).

Uitleg: Sommige fabrikanten (HP o.a.) maken een Windows7 image die verder geen rekening houdt met welke processor er in de pc gestopt is (AMD of Intel). Dus dan worden zowel AMD drivers als Intel drivers geïnstalleerd.

Maak wel eerst even een herstelpunt.

Succes,

Tijs.

 

[Luukg]

ik heb een intel e7400 processor.(in mijn eerste post staat mijn hardware) Maar het licht niet aan windows7 eerlijk gezegd. Ik heb al een volledige herinstallatie van windows 7 gedaan(niet van hp of iets). Verder draaide ik nu al een lange tijd windows 7 gewoon stabiel.

dus??