FDC

Utenti
  • Numero contenuti

    12
  • Iscritto

  • Ultima visita

Su FDC

  • Livello
    Iniziato
  1. ora ho riacceso il pc il problema persiste... soprattutto dopo averlo spento per qualke ora.. non riesco a capire veramente il motivo di tutto cio... vi prego aiutatemi
  2. ragazzi ho trovato un altra persona con il mio stesso problema http://forum.novatech.co.uk/showthread.php?p=229762 cosa dice di fare??? vi ringrazio x tutti gli aiuti che mi state riservando.. ma ho bisogno di un forte aiuto... grazie ancora
  3. ok installati gli ultimi driver del chipset riavviato ora sto installando gli ultimi catalyst... poi spegnerò il computer per un bel po e vi faro sapere... intanto grazie 1000
  4. dove devo vedere la versione di chipset driver di intel???
  5. ho inserito solo la parte riguardante le parte video ------------------ System Information ------------------ Time of this report: 2/8/2010, 16:33:39 Machine name: FDC-DESKTOP Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255) Language: Italian (Regional Setting: Italian) System Manufacturer: System manufacturer System Model: System Product Name BIOS: BIOS Date: 11/13/09 15:53:33 Ver: 08.00.15 Processor: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (4 CPUs), ~2.7GHz Memory: 8192MB RAM Available OS Memory: 8184MB RAM Page File: 1720MB used, 14643MB available Windows Dir: C:\Windows DirectX Version: DirectX 11 DX Setup Parameters: Not found User DPI Setting: Using System DPI System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled DxDiag Version: 6.01.7600.16385 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Sound Tab 3: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: ATI Radeon HD 4670 Manufacturer: ATI Technologies Inc. Chip type: ATI display adapter (0x9490) DAC type: Internal DAC(400MHz) Device Key: Enum\PCI\VEN_1002&DEV_9490&SUBSYS_22681787&REV_00 Display Memory: 4083 MB Dedicated Memory: 1015 MB Shared Memory: 3067 MB Current Mode: 1440 x 900 (32 bit) (60Hz) Monitor Name: Monitor generico Plug and Play Monitor Model: ASUS VH196 Monitor Id: ACI19E5 Native Mode: 1440 x 900(p) (59.887Hz) Output Type: HD15 Driver Name: atiumd64.dll,atidxx64.dll,atiumdag,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll Driver File Version: 8.14.0010.0678 (English) Driver Version: 8.632.1.2000 DDI Version: 10.1 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 8/18/2009 02:15:58, 4059648 bytes WHQL Logo'd: Yes WHQL Date Stamp: Device Identifier: {D7B71EE2-D7D0-11CF-9176-6202A1C2C535} Vendor ID: 0x1002 Device ID: 0x9490 SubSys ID: 0x22681787 Revision ID: 0x0000 Driver Strong Name: oem2.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_R7X:8.632.1.2000:pci\ven_1002&dev_9490 Rank Of Driver: 00E62001 Video Accel: ModeMPEG2_A ModeMPEG2_C Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Not Supported DXVA-HD: Not Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled
  6. ecco lo stamp di blue scree view. se posso fare qualche altra cosa fatemi sapere.
  7. mi sorge un dubbio io ho due ati in crossfire hd4670... (con w7 32 bit) non ho mai avuto nessuno problema. ora da quando ho messo il 64 bit per sfruttare tutte e 8 gb di ram sono iniziate a sorgere questi problemi. prima della formattazione possedevo gia quei driver. e comunque mi riportava lo stesso errore. ora provo ad avviare blue screen view e vi posto il log e mi dite cosa ne pensate. grazie ancora per tutto l'aiuto che mi state dedicando.
  8. allora ho fatto l'analisi con il software di windows e mi ha riportato questo log Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50 Debug session time: Mon Feb 8 15:19:58.008 2010 (GMT+1) System Uptime: 0 days 0:00:34.429 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols ............................................................... ....................................................... Loading User Symbols Loading unloaded module list .... *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys - ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8009f19010, fffff8800485f7f8, 0, 2} *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.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 *** *** *** ************************************************************************* *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : atikmdag.sys ( atikmdag+127f8 ) Followup: MachineOwner
  9. ora mi e uscito di nuovo mi da queste informazioni BCCode 116 BCP1 FFFFFA8009F19010 BCP2 FFFFF8800485F7F8 BCP3 0000000000000000 BCP4 0000000000000002 OS VERSIONE 6_1_7600 SERVICE PACK 0_0 PRODUCT 256_1 file che contribuiscono alla risoluzione del problema C:\Windows\Minidump\020810-23696-01.dmp C:\Windows\FDC\AppData\Local\Temp\WER-32666-0.sysdata.xml vi prego aiutatemi :|:|:| inoltre sullo schermo ci sono una serie di puntini blu in movimento... sono entrato in modalita provvisoria.
  10. la prossima volta che lo fa vi darò il numero di errore... ora sono con il portatile sto aspettando prima di riaccendere il fisso... spero che qualcuno di voi mi possa aiutare... perché è nuovissimo e non usarlo è davvero un peccato
  11. EDIT: (scrittura non abbreviata) sorry non ero al corrente ok tengo un scheda madre p7p55d della asus intel core i5 memoria ram 8gb quindi ho montato un sistema operativo a 64 bit poichè il commerciante che me l'aveva venduto aveva installato il sistema operativo a 32 bit. pero non mi dava questi problemi... vi ripeto che questo problema non capita tutte le volte che accendo il pc ma solo alcune volte ed e questa la cosa più inquietante :| EDIT: gli unici programmi che ho installato sono daemon tools lite e avast antivirus... entrambi compatibili con windows7 64bit
  12. ragazzi sn nuovo e vi saluto tutti... volevo porvi una questione... ho un problema su un fisso. praticamente ho installato w7 64 bit ed ogni tanto all'accensione mi escono delle righe rosse sullo skermo e il monitor inizia a mostrare un sfarfallio. e successivamente quando esce la skermata di avvio di windows esce la blue screen. riavviando manualmente col tasto reset il pc parte normalmente. questo capita soprattutto quando il pc rimane spento x diverse ore... non capisco cosa possa essere ho formattato + volte. ma l'errore mi ricapita sempre... aspetto vostre notizie grazie infinite. sto uscendo pazzo :\