johhnny

Ktoś ma może pomysł co u mnie (kilka postów powyżej) poradzić bo walczę z tym i nic ?

Po pierwszym włączaniu systemu, gdy komputer był wyłączony, za każdym razem spotyka mnie wątpliwa przyjemność oglądania BSOD'a. Najpierw zainstalowałem Win7 wersje 64bit gdzie był ten sam problem obecnie mam 32 bit i było dobrze po zainstalowaniu, po kilkukrotnych resetach system normalnie pracował. Dopiero gdy po nocy uruchomiłem go ponownie znowu ekran był niebieski. I teraz już nie wiem co to może być. Sterowniki są aktualne. Pamięć testowana Memtestem 10 testów przeszła bezbłędnie. Po kolejnych restartach systemu problem się już nie objawia tylko za pierwszym. Moja konfiguracja to: C2D E7200 2.5@3.0 1.18V MSI P45 NEO2-FIR A-Data Vitesta 2x 1GB 800Mhz 4-4-4-12-2T 2.1V Twintech GF 9600GT 512MB Zamieszczam zrzut pamięci z błędu: Loading Dump File [C:\Users\joHn_ny\Desktop\103109-18486-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: D:\Symbols;D:\Symbols2 Executable search path is: Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.x86fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0x82a44000 PsLoadedModuleList = 0x82b8c810 Debug session time: Sat Oct 31 13:27:04.544 2009 (GMT+1) System Uptime: 0 days 0:00:25.980 Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ ................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {9fbb9c18, 2, 1, 82adf168} *** WARNING: Unable to verify timestamp for win32k.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* Probably caused by : win32k.sys ( win32k!xxxSystemParametersInfo+3672 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) 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 a kernel debugger is available get the stack backtrace. Arguments: Arg1: 9fbb9c18, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 82adf168, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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 *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: win32k FAULTING_MODULE: 82a44000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc2a2 WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 9fbb9c18 CURRENT_IRQL: 0 FAULTING_IP: nt+9b168 82adf168 f00fba2900 lock bts dword ptr [ecx],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from 82adf168 to 82a8a7eb STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 96fa48e4 82adf168 badb0d00 0000005c c04b7ce0 nt+0x467eb 96fa496c 82ad05b6 82bad000 0000005c 00000001 nt+0x9b168 96fa49d8 82ad8273 0000005c 00000002 00000000 nt+0x8c5b6 96fa4a00 82ad28d5 0000005c 00000002 00000000 nt+0x94273 96fa4a48 82ad4979 00000001 fd776000 96fa4b68 nt+0x8e8d5 96fa4ac8 82acad56 fd776000 00000000 8aedbd70 nt+0x90979 96fa4b50 82a8a5f8 00000001 fd776000 00000000 nt+0x86d56 96fa4b68 82a82e85 badb0d00 00000000 00501000 nt+0x465f8 96fa4bf4 94d6db3e 0050014c 35316847 96fa4ca4 nt+0x3ee85 96fa4c10 94d83047 0050014c 00000005 00000001 win32k!xxxSystemParametersInfo+0x3672 96fa4c70 94d83a59 00001400 00000000 00000000 win32k!W32pServiceTable+0x1447 96fa4ccc 94d83400 00000500 00000400 00000001 win32k!W32pArgumentTable+0x13d 96fa4d18 82a8742a 00000500 00000400 00000001 win32k!W32pServiceTable+0x1800 96fa4d34 77f064f4 badb0d00 017af6e4 00000000 nt+0x4342a 96fa4d38 badb0d00 017af6e4 00000000 00000000 0x77f064f4 96fa4d3c 017af6e4 00000000 00000000 00000000 0xbadb0d00 96fa4d40 00000000 00000000 00000000 00000000 0x17af6e4 STACK_COMMAND: kb FOLLOWUP_IP: win32k!xxxSystemParametersInfo+3672 94d6db3e ?? ??? SYMBOL_STACK_INDEX: 9 SYMBOL_NAME: win32k!xxxSystemParametersInfo+3672 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: win32k.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- 1: kd> lmvm win32k start end module name 94cb0000 94efa000 win32k M (pdb symbols) d:\symbols\win32k.pdb\A9F6403F14074E9D8A07D0AA6F0C1CFF2\win32k.pdb Loaded symbol image file: win32k.sys Image path: \SystemRoot\System32\win32k.sys Image name: win32k.sys Timestamp: Tue Jul 14 01:26:26 2009 (4A5BC2A2) CheckSum: 00238A3F ImageSize: 0024A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 1: kd> lmvm nt start end module name 82a44000 82e54000 nt T (no symbols) Loaded symbol image file: ntkrnlpa.exe Image path: \SystemRoot\system32\ntkrnlpa.exe Image name: ntkrnlpa.exe Timestamp: Tue Jul 14 01:15:19 2009 (4A5BC007) CheckSum: 003C9503 ImageSize: 00410000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

Rozumiem, że wystarczy jednak ja bym wolał kupić coś z gwarancją bo będzie tak jak z moją poprzednią płytą, padnie i nic z nią potem nie zrobię. Dlatego wolę te nowe MSI co podałem a , że różnica pomiędzy P43 NEO3 a P45 NEO2 to 20 zł to wole dopłacić do lepszej. Tylko chciałbym zapytać czy w tej cenie to dobry wybór czy może jest coś lepszego ale też nowego?

a coś z nowych (w sensie nieużywanych) płyt? może ta http://www.comp4you.eu/pricelist/item.aspx?PID=C8700766 lub ta http://www.morele.net/plyta-glowna-msi-p43-neo3-fr-190152/ tylko jak z tą awaryjnością? Jestem na 99% zdecydowany na MSI P45 NEO2-FIR wyniesie mnie to ok 341zł razem z przesyłką. Czy to dobry wybór w tej cenie ? Zaznaczam, że podkręcał raczej nie będę jak już to symbolicznie.

Proszę o sugestie jaką płytę główną pod socket 775 mogę dostać za około 300zł? Myślałem nad MSI P45 NEO2-FR MOA już nawet zamówiłem w esc.pl ale dzwonił do mnie jeden ze sprzedawców z informacją, że nie mają jej i nawet nie chcą zamawiać bo 90% tych płyt które sprzedali poszło na serwis i teraz nie wiem czy to prawda. Stwierdził, że podobnie z wersją NEO2-FIR. I teraz nie wiem co za te pieniądze wybrać, aby być zadowolonym. Dziękuje za wszystkie propozycje. Reszta zestawu to: C2D E7200, GF 9600GT 512mb, 2x 1GB a-data vitesta. Poprzednia płyta to ASUS P5K PRO, obecnie ze spalonym chipsetem.

Jednak zostanę przy Asusie bo za nim stoi to, że już pewne doświadczenie w asusach mam i będzie mi łatwiej zacząć, a do DFI zniechęca mnie to że jest brzydka , że nie wszystkie kondensatory są polimerowe, ma gorszą dźwiękówke a ja głównie korzystam ze zintegrowanej. A tak poza tym to nie będę podkręcał jakoś ekstremalnie jak dobije na tym procku do 3,5GHz to już będzie aż nad to ;) Teraz tylko mam dylemat co do karty graficznej bo chciałbym przedewszystkim cichą i wydajną 8800GT a ten Twintech chyba za cichy nie jest. Prosiłbym o polecenie jeszcze jakiejś grafy do 540 zł na 8800GT warunkiem jest żeby miała ciche chłodzenie.

Patrzyłem na tego blood iron'a i stwierdzam ze strasznie uboga ta płyta nie wiem jak się na niej podkręca ale chłodzenia to ona prawie nie ma no i ma 4 fazy tylko co do podkręcania w przyszłości q6600 może być mało, a co do OC to będzie ono pewnie na poziomie maks 3.5-3.8 zależy jak procek się uda.

No narazie mnie nie stać na 4GB poczekam trochę może jeszcze potanieje ram. A tak to komp ma służyć głównie do grania ale nie w jakiś wielkich rozdzielczościach , do netu i normalnej pracy. Jeszcze mam takie pytania co do grafy: jak głośne jest chłodzenie na niej bo zależy mi na ciszy i traktora nie chce ?? i czy będzie ona kompatybilna z tą płytą którą wybrałem bo na benchzone w teście pisali, że nie ze wszystkimi płytami działa ta karta???

Jako ,że planuje zakup nowej konfiguracji a nie jestem jakiś super zaawansowany w dobieraniu komponentów (chociaż laikiem też nie jestem) proszę o ocenę zestawu który złożyłem i ewentualne sugestie. Z góry dzięki. Core 2 Duo E7200 /2.53GHz, 3MB, 1066MHz, BOX/ - 369zł ASUS P5K PRO - 320zł A-data 2GB (2x1GB) PC800 CL4 Extreme Edition - 140zł TwinTech GeForce 8800GT XT 512MB DDRIII HEATPIPE /256bit/ HDTV 2xDVI - 539zł (tu się najbardziej zastanawiam, ponieważ zależy mi na ciszy oraz wydajności) WD Caviar 320GB 7200rpm 16MB cache SATAII [3200AAKS] - 179zł Całość: 1547zł i w tej kwocie chciałbym pozostać. Reszta czyli: zasilacz, obudowa, nagrywarki CD i DVD zostawiam ze starego kompa. Zasilacz to DELTA DPS-400MB-1 A 400W.