Hallo zusammen,
Ich habe folgendes Problem, mein PC schafft es nicht ordentlich zu booten. Es braucht meist 3 oder mehr Anläufe bis das System stabil läuft. Dabei bekommt mein PC entweder einen Bluescreen, Freeze oder er startet einfach neu.
Wenn er die ersten 10 min überstanden hat läuft er ordentlich, außer dass er das Netzwerk- und Freigabecenter erst nach ca. 3 Minuten öffnet und man dort verschiedene Fenster nicht mehr öffnen kann.
Ich habe diesen PC von einem Freund günstig abgekauft, dieser hatte keine Probleme. Einzige Änderung, ich habe Windows 7 aufgespielt.
Ich weiß nicht, ob dass eine Rolle spielt, aber im Winter bekomme ich weit mehr Bluescreens als im Sommer, wobei dir Zimmertemparatur sich kaum ändert.
Infos zu meinem System:
Motherboard: Fujitsu Siemens MS-7504VP-PV
Grafikkarte: NVIDIA GeForce GT 120
RAM: 4GB DDR2 RAM
Betriebssystem: Windows 7 x64
CPU: Intel Core 2 Quad Q8200
CPU-Z:
Software "Who Crashed":
Windows Debugger
analysiert wurde 101013-57143-01.dmp
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88006dac526, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE ***
*** ***
*************************************************************************
// Ich habe Wiederholungen von Type referenced: nt!_KPRCB rausgelöscht.
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: USBPORT
FAULTING_MODULE: fffff80002c49000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 52272387
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000020
CURRENT_IRQL: 0
FAULTING_IP:
USBPORT!USBPORT_AssertListEntryLog+16
fffff880`06dac526 418b4820 mov ecx,dword ptr [r8+20h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from fffff80002cbe169 to fffff80002cbebc0
STACK_TEXT:
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
USBPORT!USBPORT_AssertListEntryLog+16
fffff880`06dac526 418b4820 mov ecx,dword ptr [r8+20h]
SYMBOL_NAME: USBPORT!USBPORT_AssertListEntryLog+16
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: USBPORT.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Frage ist jetzt, wo liegt das Problem? Lohnt sich der Aufwand es zu lösen? Und kann mir jmd die Schritte möglichst einfach erklären
?
Danke im Vorraus
Ich habe folgendes Problem, mein PC schafft es nicht ordentlich zu booten. Es braucht meist 3 oder mehr Anläufe bis das System stabil läuft. Dabei bekommt mein PC entweder einen Bluescreen, Freeze oder er startet einfach neu.
Wenn er die ersten 10 min überstanden hat läuft er ordentlich, außer dass er das Netzwerk- und Freigabecenter erst nach ca. 3 Minuten öffnet und man dort verschiedene Fenster nicht mehr öffnen kann.
Ich habe diesen PC von einem Freund günstig abgekauft, dieser hatte keine Probleme. Einzige Änderung, ich habe Windows 7 aufgespielt.
Ich weiß nicht, ob dass eine Rolle spielt, aber im Winter bekomme ich weit mehr Bluescreens als im Sommer, wobei dir Zimmertemparatur sich kaum ändert.
Infos zu meinem System:
Motherboard: Fujitsu Siemens MS-7504VP-PV
Grafikkarte: NVIDIA GeForce GT 120
RAM: 4GB DDR2 RAM
Betriebssystem: Windows 7 x64
CPU: Intel Core 2 Quad Q8200
CPU-Z:
Software "Who Crashed":
Windows Debugger
analysiert wurde 101013-57143-01.dmp
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88006dac526, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_MMPTE ***
*** ***
*************************************************************************
// Ich habe Wiederholungen von Type referenced: nt!_KPRCB rausgelöscht.
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: USBPORT
FAULTING_MODULE: fffff80002c49000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 52272387
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000020
CURRENT_IRQL: 0
FAULTING_IP:
USBPORT!USBPORT_AssertListEntryLog+16
fffff880`06dac526 418b4820 mov ecx,dword ptr [r8+20h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from fffff80002cbe169 to fffff80002cbebc0
STACK_TEXT:
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
USBPORT!USBPORT_AssertListEntryLog+16
fffff880`06dac526 418b4820 mov ecx,dword ptr [r8+20h]
SYMBOL_NAME: USBPORT!USBPORT_AssertListEntryLog+16
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: USBPORT.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Frage ist jetzt, wo liegt das Problem? Lohnt sich der Aufwand es zu lösen? Und kann mir jmd die Schritte möglichst einfach erklären
? Danke im Vorraus
