[Rozwiązany] Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
|
marciniak
Nowy
Liczba postów: 4
|
Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
Witam,
Mam pewien problem od pewnego czasu z PC ,od jakiegoś czasu(jakieś 2 tyg)pojawiają mi się blu screeny o kodzie błędu 1a,zawsze co parę dni(2/3),a co jest dość dziwne zawsze w określonym czasie(jakieś 5/10 min. po załadowaniu systemu)tylko za pierwszym razem po włączeniu, potem już nie(można siedzieć i cały dzień i już zero problemów),przeinstalowałem system i problem występuje nadal,sprawdzałem pamięci mam testem i nie wykryło żadnych błędów,zamieniłem pamięci miejscami i też nic to nie dało, gdzie może być problem i w czym?PC ma jakieś 2 miesiące niecałe ,dodam ze przez pierwszy miesiąc nie było problemów,jakby co wszystkie części mam na gwarancji
i jak nie znajdę rozwiązania problemu to oddam na reklamację,czego jednak wolałbym uniknąć z powodu braku czasu łażenia po sklepach,myślę ze problem tkwi w jakiś sterownikach /programach itp. może ktoś ogarnia troszku bardziej takie sprawy i coś podpowie co można jeszcze pokombinować...?
dołączam komunikat o błędzie jak i odczyt pliku mini dump:
Kod:
Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.256.1
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje o problemie:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8001B14670
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Pliki pomagające opisać problem:
C: \Windows\Minidump\090314-16754-01.dmp
C: \Users\marciniak\AppData\Local\Temp\WER-53414-0.sysdata.xml
Przeczytaj w trybie online nasze zasady zachowania poufności informacji:
http: //go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415
Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline:
C: \Windows\system32\pl-PL\erofflps.txt[/spoiler]
[spoiler]Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Windows\Minidump\090314-16754-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.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`0341a000 PsLoadedModuleList = 0xfffff800`03657e50
Debug session time: Wed Sep 3 17: 58: 09.188 2014 (GMT+2)
System Uptime: 0 days 0: 04: 10.484
*********************************************************************
* 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+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8001b14670, ffff, 0}
***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : ntoskrnl.exe ( nt+71f00 )
Followup: MachineOwner
---------
Dane PC:
-Płyta główna S1150 GIGABYTE GA-H81M-HD3 ddr3 1600 sata3 hdmi
-Procesor intel core i3-4130 3,4GHz s 1150
-pamieć ddram3 8GB/1600MHz kingston HyX (2 kosci po 4GB)
-Hdd 1TB wd caviar green 64mb
-Karta graficzna pci-e 2GB gf GT630 MSI ddr3/128bit DVI/HDMI
-Zasilacz pc atx 500w i-box
ps.Nie ukrywam ze już mnie to trochę irytuje,na tyg.jestem w stanie raczej wieczorami zajrzeć na forum ,Za wszystkie rady i podpowiedzi dziękuje z góry.[/php][/code]
(Ten post był ostatnio modyfikowany: 04.09.2014 16:13 przez marciniak.)
04.09.2014 06:41
|
 Podziękowania od: |
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Problem z PC (Blu Screen)
Nie baw się w znawcę tylko podeślij pliki mini zrzutów pamięci jądra (mini kernel dumps) z c:\windows\minidump
Ten debug jest nic nie warty bo źle wykonany.
Pierwszy niewybaczalny błąd - brak SP1. Kluczową rolą jest aby wszelki najnowsze sterowniki mogły poprawnie pracować na załatanym systemie. Jedno z drugim jest ze sobą powiązane. Certyfikowane sterowniki są wypuszczane po testach na w pełni aktualizowanym systemie.
Swoją drogą bardzo kiepsko dobrany zasilacz do tego budżetowego zestawu.
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
| Podziękowania od: |
marciniak
|
|
|
marciniak
Nowy
Liczba postów: 4
|
RE: Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
Temat poprawiłem proszę o wyrozumiałość...tutaj są 4 ostatnie zrzuty pamięci ostatnio zdarzyły się codziennie http://www.sendspace.pl/file/eba023aa5ac8db50cf4a399
więc co proponujesz na początek zainstalować SP1? zasilacz może i nie jest najlepszy ale może nie trzeba go wymieniać.
po zainstalowaniu SP1 problem występuje nadal ...co robić...?
(Ten post był ostatnio modyfikowany: 09.09.2014 19:08 przez marciniak.)
04.09.2014 16:18
|
| Podziękowania od: |
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
Memtest86+ jak długo leciał ? Nie ma zawsze 100% pewności iż memtest nie kłamie. Pamięci wcale nie muszą być uszkodzone a wystarczy nieodpowiednie napięcie vdimm.
Sprawdzałeś ustawienia pracy pamięci vdimm/timingi ?
Z bsodów wynika iż to jest zestaw dwóch zupełnie różnych modeli
KHX1600C10D3/8G
KHX1600C9D3/4GX
Wystarczy iż są zastosowane różne kości IC na płytkach PCB i zaczynają być czary. Zaleca się aby w dualu były to te same kości.
Coś tu jest również nie tak z systemem bo śmierdzi mi to, dosyć nowy sprzęt i nośnik bez SP1 - oem;a nie można przenosić a box'a mało kto kupuje z racji bardzo wysokiej ceny.
Zainstalować system oryginalny (nie modyfikowany). Potem sterowniki do komponentów (nie z aplikacji do automatycznego rozpoznawania, nie z Windows Update) z płyty instalacyjnej (tylko one bez dodatkowego zawartego softu). Następnie wszystkie poprawki. Build systemu ma być 7601.
Następnie na to kopia systemu w postaci wykonania obrazu za pomocą narzędzia kopii zapasowej i można dalej działać/testować. Nie instalować na razie Daemon Tools'a i AVG tylko ewentualnie inny AV.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c: \symbols*http: //msdl.microsoft.com/download/symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
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`03212000 PsLoadedModuleList = 0xfffff800`0344fe50
Debug session time: Sat Aug 30 13: 58: 25.654 2014 (UTC + 2: 00)
System Uptime: 0 days 0: 06: 27.950
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8001c4be30, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+339d6 )
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001c4be30
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800032f626e to fffff80003283f00
STACK_TEXT:
fffff880`0a102368 fffff800`032f626e : 00000000`0000001a 00000000`00041790 fffffa80`01c4be30 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0a102370 fffff800`032b75d9 : 00000000`00000000 00000000`24402fff fffff880`00000000 00000000`00000000 : nt! ? : FNODOBFM: `string'+0x339d6
fffff880`0a102530 fffff800`03599e50 : fffffa80`06db8850 0007ffff`00000000 fffffa80`0c7d6f90 fffffa80`0c7d6f90 : nt!MiRemoveMappedView+0xd9
fffff880`0a102650 fffff800`0359a25b : 00000980`00000000 00000000`24210000 fffffa80`00000001 00000000`02b5d601 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0a102710 fffff800`03283153 : 00000000`00000000 00000000`76e43650 fffffa80`0a3a5b30 00000000`3b010dd9 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a102760 00000000`76d6015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02b5d508 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d6015a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+339d6
fffff800`032f626e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+339d6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_: FNODOBFM: _string_+339d6
BUCKET_ID: X64_0x1a_41790_nt!_??_: FNODOBFM: _string_+339d6
Followup: MachineOwner
---------
CPUID: "Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz"
MaxSpeed: 3400
CurrentSpeed: 3392
[SMBIOS Data Tables v2.7]
[DMI Version - 39]
[2.0 Calling Convention - No]
[Table Size - 3137 bytes]
[BIOS Information (Type 0) - Length 24 - Handle 0000h]
Vendor American Megatrends Inc.
BIOS Version F3
BIOS Starting Address Segment f000
BIOS Release Date 01/20/2014
BIOS ROM Size 800000
BIOS Characteristics
07: - PCI Supported
11: - Upgradeable FLASH BIOS
12: - BIOS Shadowing Supported
15: - CD-Boot Supported
16: - Selectable Boot Supported
17: - BIOS ROM Socketed
19: - EDD Supported
23: - 1.2MB Floppy Supported
24: - 720KB Floppy Supported
25: - 2.88MB Floppy Supported
26: - Print Screen Device Supported
27: - Keyboard Services Supported
28: - Serial Services Supported
29: - Printer Services Supported
32: - BIOS Vendor Reserved
BIOS Characteristic Extensions
00: - ACPI Supported
01: - USB Legacy Supported
08: - BIOS Boot Specification Supported
10: - Specification Reserved
11: - Specification Reserved
BIOS Major Revision 4
BIOS Minor Revision 6
EC Firmware Major Revision 255
EC Firmware Minor Revision 255
[System Information (Type 1) - Length 27 - Handle 0001h]
Manufacturer Gigabyte Technology Co., Ltd.
Product Name H81M-HD3
Version To be filled by O.E.M.
Serial Number
UUID 00000000-0000-0000-0000-000000000000
Wakeup Type Power Switch
SKUNumber To be filled by O.E.M.
Family To be filled by O.E.M.
[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]
Manufacturer Gigabyte Technology Co., Ltd.
Product H81M-HD3
Version x.x
Serial Number
Asset Tag
Feature Flags 09h
263994740: - U6
263994700: - U6
Location To be filled by O.E.M.
Chassis Handle 0003h
Board Type 0ah - Processor/Memory Module
Number of Child Handles 0
[System Enclosure (Type 3) - Length 22 - Handle 0003h]
Manufacturer Gigabyte Technology Co., Ltd.
Chassis Type Desktop
Version To Be Filled By O.E.M.
Serial Number
Asset Tag Number
Bootup State Safe
Power Supply State Safe
Thermal State Safe
Security Status None
OEM Defined 0
Height 0U
Number of Power Cords 1
Number of Contained Elements 0
Contained Element Size 0
[Cache Information (Type 7) - Length 19 - Handle 0004h]
Socket Designation CPU Internal L1
Cache Configuration 0180h - WB Enabled Int NonSocketed L1
Maximum Cache Size 0080h - 128K
Installed Size 0080h - 128K
Supported SRAM Type 0002h - Unknown
Current SRAM Type 0002h - Unknown
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Other
Associativity 8-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 0005h]
Socket Designation CPU Internal L2
Cache Configuration 0181h - WB Enabled Int NonSocketed L2
Maximum Cache Size 0200h - 512K
Installed Size 0200h - 512K
Supported SRAM Type 0002h - Unknown
Current SRAM Type 0002h - Unknown
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Unified
Associativity 8-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 0006h]
Socket Designation CPU Internal L3
Cache Configuration 0182h - WB Enabled Int NonSocketed L3
Maximum Cache Size 0c00h - 3072K
Installed Size 0c00h - 3072K
Supported SRAM Type 0002h - Unknown
Current SRAM Type 0002h - Unknown
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Unified
Associativity Specification Reserved
[Physical Memory Array (Type 16) - Length 23 - Handle 0007h]
Location 03h - SystemBoard/Motherboard
Use 03h - System Memory
Memory Error Correction 03h - None
Maximum Capacity 33554432KB
Memory Error Inf Handle [Not Provided]
Number of Memory Devices 2
[Onboard Devices Information (Type 10) - Length 6 - Handle 0026h]
Number of Devices 1
01: Type Video [enabled]
01: Description To Be Filled By O.E.M.
[OEM Strings (Type 11) - Length 5 - Handle 0027h]
Number of Strings 5
1 To Be Filled By O.E.M.
2 To Be Filled By O.E.M.
3 To Be Filled By O.E.M.
4 To Be Filled By O.E.M.
5 To Be Filled By O.E.M.
[System Configuration Options (Type 12) - Length 5 - Handle 0028h]
[Processor Information (Type 4) - Length 42 - Handle 0040h]
Socket Designation SOCKET 0
Processor Type Central Processor
Processor Family c6h - Specification Reserved
Processor Manufacturer Intel
Processor ID c3060300fffbebbf
Processor Version Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
Processor Voltage 8bh - 1.1V
External Clock 100MHz
Max Speed 7000MHz
Current Speed 3400MHz
Status Enabled Populated
Processor Upgrade Other
L1 Cache Handle 0004h
L2 Cache Handle 0005h
L3 Cache Handle 0006h
Serial Number [String Not Specified]
Asset Tag Number
Part Number Fill By OEM
[Memory Device (Type 17) - Length 34 - Handle 0041h]
Physical Memory Array Handle 0007h
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelA-DIMM0
Bank Locator BANK 0
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer Kingston
Serial Number
Asset Tag Number
Part Number KHX1600C9D3/4GX
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 0042h]
Starting Address 00000000h
Ending Address 003fffffh
Memory Device Handle 0041h
Mem Array Mapped Adr Handle 0047h
Partition Row Position [Unknown]
Interleave Position [Unknown]
Interleave Data Depth [Unknown]
[Memory Device (Type 17) - Length 34 - Handle 0043h]
Physical Memory Array Handle 0007h
Memory Error Info Handle [Not Provided]
Total Width 0 bits
Data Width 0 bits
Size [Not Populated]
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelA-DIMM1
Bank Locator BANK 1
Memory Type 02h - Unknown
Type Detail 0000h -
Speed 0MHz
Manufacturer [Empty]
Serial Number
Asset Tag Number
Part Number [Empty]
[Memory Device (Type 17) - Length 34 - Handle 0044h]
Physical Memory Array Handle 0007h
Memory Error Info Handle [Not Provided]
Total Width 64 bits
Data Width 64 bits
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelB-DIMM0
Bank Locator BANK 2
Memory Type 18h - Specification Reserved
Type Detail 0080h - Synchronous
Speed 1600MHz
Manufacturer Kingston
Serial Number
Asset Tag Number
Part Number KHX1600C10D3/8G
[Memory Device Mapped Address (Type 20) - Length 35 - Handle 0045h]
Starting Address 00400000h
Ending Address 007fffffh
Memory Device Handle 0044h
Mem Array Mapped Adr Handle 0047h
Partition Row Position [Unknown]
Interleave Position [Unknown]
Interleave Data Depth [Unknown]
[Memory Device (Type 17) - Length 34 - Handle 0046h]
Physical Memory Array Handle 0007h
Memory Error Info Handle [Not Provided]
Total Width 0 bits
Data Width 0 bits
Size [Not Populated]
Form Factor 09h - DIMM
Device Set [None]
Device Locator ChannelB-DIMM1
Bank Locator BANK 3
Memory Type 02h - Unknown
Type Detail 0000h -
Speed 0MHz
Manufacturer [Empty]
Serial Number
Asset Tag Number
Part Number [Empty]
[Memory Array Mapped Address (Type 19) - Length 31 - Handle 0047h]
Starting Address 00000000h
Ending Address 007fffffh
Memory Array Handle 0007h
Partition Width 04
start end module name
fffff880`0506a000 fffff880`050b6000 a8jdk463 a8jdk463.SYS Wed Dec 28 10: 10: 52 2011 (4EFADD1C)
fffff880`01184000 fffff880`011db000 ACPI ACPI.sys Tue Jul 14 01: 19: 34 2009 (4A5BC106)
fffff880`04062000 fffff880`040ec000 afd afd.sys Tue Jul 14 01: 21: 40 2009 (4A5BC184)
fffff880`05abe000 fffff880`05ad4000 AgileVpn AgileVpn.sys Tue Jul 14 02: 10: 24 2009 (4A5BCCF0)
fffff880`0152b000 fffff880`01536000 amdxata amdxata.sys Tue May 19 19: 56: 59 2009 (4A12F2EB)
fffff880`04fd9000 fffff880`04fe1000 AppleCharger AppleCharger.sys Mon Oct 28 02: 59: 21 2013 (526DC4F9)
fffff880`00ea0000 fffff880`00ea9000 atapi atapi.sys Tue Jul 14 01: 19: 47 2009 (4A5BC113)
fffff880`00ea9000 fffff880`00ed3000 ataport ataport.SYS Tue Jul 14 01: 19: 52 2009 (4A5BC118)
fffff880`04fb0000 fffff880`04fd9000 avgdiska avgdiska.sys Mon Jun 30 12: 42: 59 2014 (53B13F33)
fffff880`04f6d000 fffff880`04fb0000 avgidsdrivera avgidsdrivera.sys Tue Jun 17 16: 06: 18 2014 (53A04B5A)
fffff880`01dc5000 fffff880`01df6000 avgidsha avgidsha.sys Tue Jun 17 16: 06: 20 2014 (53A04B5C)
fffff880`04f2f000 fffff880`04f6d000 avgldx64 avgldx64.sys Tue Jun 17 16: 21: 28 2014 (53A04EE8)
fffff880`01d50000 fffff880`01da3000 avgloga avgloga.sys Tue Jun 17 16: 06: 42 2014 (53A04B72)
fffff880`01da3000 fffff880`01dc5000 avgmfx64 avgmfx64.sys Tue Jun 17 16: 06: 17 2014 (53A04B59)
fffff880`01d46000 fffff880`01d50000 avgrkx64 avgrkx64.sys Tue Jun 17 16: 06: 04 2014 (53A04B4C)
fffff880`04647000 fffff880`0468c000 avgtdia avgtdia.sys Tue Jun 17 16: 06: 51 2014 (53A04B7B)
fffff880`04997000 fffff880`0499e000 Beep Beep.SYS Tue Jul 14 02: 00: 13 2009 (4A5BCA8D)
fffff880`04f1e000 fffff880`04f2f000 blbdrive blbdrive.sys Tue Jul 14 01: 35: 59 2009 (4A5BC4DF)
fffff880`08b9f000 fffff880`08bbd000 bowser bowser.sys Tue Jul 14 01: 23: 50 2009 (4A5BC206)
fffff960`00780000 fffff960`007a7000 cdd cdd.dll Tue Jul 14 03: 25: 40 2009 (4A5BDE94)
fffff880`08a9c000 fffff880`08ab9000 cdfs cdfs.sys Tue Jul 14 01: 19: 46 2009 (4A5BC112)
fffff880`04964000 fffff880`0498e000 cdrom cdrom.sys Tue Jul 14 01: 19: 54 2009 (4A5BC11A)
fffff880`00d40000 fffff880`00e00000 CI CI.dll Tue Jul 14 03: 32: 13 2009 (4A5BE01D)
fffff880`01d16000 fffff880`01d46000 CLASSPNP CLASSPNP.SYS Tue Jul 14 01: 19: 58 2009 (4A5BC11E)
fffff880`00ce2000 fffff880`00d40000 CLFS CLFS.SYS Tue Jul 14 01: 19: 57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c73000 cng cng.sys Tue Jul 14 01: 49: 40 2009 (4A5BC814)
fffff880`050b6000 fffff880`050c6000 CompositeBus CompositeBus.sys Tue Jul 14 02: 00: 33 2009 (4A5BCAA1)
fffff880`07956000 fffff880`07964000 crashdmp crashdmp.sys Tue Jul 14 02: 01: 01 2009 (4A5BCABD)
fffff880`04e7d000 fffff880`04f00000 csc csc.sys Tue Jul 14 01: 24: 26 2009 (4A5BC22A)
fffff880`04f00000 fffff880`04f1e000 dfsc dfsc.sys Tue Jul 14 01: 23: 44 2009 (4A5BC200)
fffff880`041e6000 fffff880`041f5000 discache discache.sys Tue Jul 14 01: 37: 18 2009 (4A5BC52E)
fffff880`01d00000 fffff880`01d16000 disk disk.sys Tue Jul 14 01: 19: 57 2009 (4A5BC11D)
fffff880`069a5000 fffff880`069c7000 drmk drmk.sys Tue Jul 14 03: 01: 25 2009 (4A5BD8E5)
fffff880`07964000 fffff880`0796e000 dump_diskdump dump_diskdump.sys Tue Jul 14 02: 01: 00 2009 (4A5BCABC)
fffff880`0796e000 fffff880`07981000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 01: 21: 51 2009 (4A5BC18F)
fffff880`0468c000 fffff880`04946000 dump_iaStorA dump_iaStorA.sys Fri Aug 02 03: 39: 52 2013 (51FB0DE8)
fffff880`07981000 fffff880`0798d000 Dxapi Dxapi.sys Tue Jul 14 01: 38: 28 2009 (4A5BC574)
fffff880`050d6000 fffff880`051ca000 dxgkrnl dxgkrnl.sys Tue Jul 14 01: 38: 56 2009 (4A5BC590)
fffff880`05000000 fffff880`05046000 dxgmms1 dxgmms1.sys Tue Jul 14 01: 38: 32 2009 (4A5BC578)
fffff880`01582000 fffff880`01596000 fileinfo fileinfo.sys Tue Jul 14 01: 34: 25 2009 (4A5BC481)
fffff880`01536000 fffff880`01582000 fltmgr fltmgr.sys Tue Jul 14 01: 19: 59 2009 (4A5BC11F)
fffff880`01611000 fffff880`0161b000 Fs_Rec Fs_Rec.sys Tue Jul 14 01: 19: 45 2009 (4A5BC111)
fffff880`01cc6000 fffff880`01d00000 fvevol fvevol.sys Tue Jul 14 01: 22: 15 2009 (4A5BC1A7)
fffff880`01800000 fffff880`0184a000 fwpkclnt fwpkclnt.sys Tue Jul 14 01: 21: 08 2009 (4A5BC164)
fffff880`08ab9000 fffff880`08ac2000 gdrv gdrv.sys Fri Mar 13 04: 22: 29 2009 (49B9D175)
fffff800`037ef000 fffff800`03838000 hal hal.dll Tue Jul 14 03: 27: 36 2009 (4A5BDF08)
fffff880`05046000 fffff880`0506a000 HDAudBus HDAudBus.sys Tue Jul 14 02: 06: 13 2009 (4A5BCBF5)
fffff880`078ea000 fffff880`07903000 HIDCLASS HIDCLASS.SYS Tue Jul 14 02: 06: 21 2009 (4A5BCBFD)
fffff880`07df2000 fffff880`07dfa080 HIDPARSE HIDPARSE.SYS Tue Jul 14 02: 06: 17 2009 (4A5BCBF9)
fffff880`07de4000 fffff880`07df2000 hidusb hidusb.sys Tue Jul 14 02: 06: 22 2009 (4A5BCBFE)
fffff880`08ad7000 fffff880`08b9f000 HTTP HTTP.sys Tue Jul 14 01: 22: 16 2009 (4A5BC1A8)
fffff880`01cbd000 fffff880`01cc6000 hwpolicy hwpolicy.sys Tue Jul 14 01: 19: 22 2009 (4A5BC0FA)
fffff880`0120f000 fffff880`014c9000 iaStorA iaStorA.sys Fri Aug 02 03: 39: 52 2013 (51FB0DE8)
fffff880`01cb2000 fffff880`01cbd000 iaStorF iaStorF.sys Fri Aug 02 03: 39: 54 2013 (51FB0DEA)
fffff880`0521c000 fffff880`05634000 igdkmd64 igdkmd64.sys Tue Sep 17 02: 08: 54 2013 (52379D96)
fffff880`07818000 fffff880`0788b000 IntcDAud IntcDAud.sys Thu Aug 29 16: 42: 53 2013 (521F5DED)
fffff880`05200000 fffff880`05216000 intelppm intelppm.sys Tue Jul 14 01: 19: 25 2009 (4A5BC0FD)
fffff880`01000000 fffff880`0100a000 iusb3hcs iusb3hcs.sys Fri Mar 29 13: 37: 59 2013 (51558B27)
fffff880`0788b000 fffff880`078ea000 iusb3hub iusb3hub.sys Fri Mar 29 13: 36: 15 2013 (51558ABF)
fffff880`05634000 fffff880`056f7000 iusb3xhc iusb3xhc.sys Fri Mar 29 13: 36: 19 2013 (51558AC3)
fffff880`065e8000 fffff880`065f7000 kbdclass kbdclass.sys Tue Jul 14 01: 19: 50 2009 (4A5BC116)
fffff880`07910000 fffff880`0791e000 kbdhid kbdhid.sys Tue Jul 14 02: 00: 20 2009 (4A5BCA94)
fffff800`00bd1000 fffff800`00bdb000 kdcom kdcom.dll Tue Jul 14 03: 31: 07 2009 (4A5BDFDB)
fffff880`06871000 fffff880`068b4000 ks ks.sys Tue Jul 14 02: 00: 31 2009 (4A5BCA9F)
fffff880`017e2000 fffff880`017fc000 ksecdd ksecdd.sys Tue Jul 14 01: 20: 54 2009 (4A5BC156)
fffff880`019cc000 fffff880`019f7000 ksecpkg ksecpkg.sys Tue Jul 14 01: 50: 34 2009 (4A5BC84A)
fffff880`069c7000 fffff880`069cc200 ksthunk ksthunk.sys Tue Jul 14 02: 00: 19 2009 (4A5BCA93)
fffff880`079df000 fffff880`079f4000 lltdio lltdio.sys Tue Jul 14 02: 08: 50 2009 (4A5BCC92)
fffff880`0799b000 fffff880`079be000 luafv luafv.sys Tue Jul 14 01: 26: 13 2009 (4A5BC295)
fffff880`00c8a000 fffff880`00cce000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 03: 29: 10 2009 (4A5BDF66)
fffff880`0798d000 fffff880`0799b000 monitor monitor.sys Tue Jul 14 01: 38: 52 2009 (4A5BC58C)
fffff880`04000000 fffff880`0400f000 mouclass mouclass.sys Tue Jul 14 01: 19: 50 2009 (4A5BC116)
fffff880`07903000 fffff880`07910000 mouhid mouhid.sys Tue Jul 14 02: 00: 20 2009 (4A5BCA94)
fffff880`00e86000 fffff880`00ea0000 mountmgr mountmgr.sys Tue Jul 14 01: 19: 54 2009 (4A5BC11A)
fffff880`08bbd000 fffff880`08bd5000 mpsdrv mpsdrv.sys Tue Jul 14 02: 08: 25 2009 (4A5BCC79)
fffff880`08a00000 fffff880`08a2c000 mrxsmb mrxsmb.sys Tue Jul 14 01: 23: 59 2009 (4A5BC20F)
fffff880`08a2c000 fffff880`08a79000 mrxsmb10 mrxsmb10.sys Tue Jul 14 01: 24: 08 2009 (4A5BC218)
fffff880`08a79000 fffff880`08a9c000 mrxsmb20 mrxsmb20.sys Tue Jul 14 01: 24: 05 2009 (4A5BC215)
fffff880`00ed3000 fffff880`00ede000 msahci msahci.sys Tue Jul 14 02: 01: 01 2009 (4A5BCABD)
fffff880`04600000 fffff880`0460b000 Msfs Msfs.SYS Tue Jul 14 01: 19: 47 2009 (4A5BC113)
fffff880`011e4000 fffff880`011ee000 msisadrv msisadrv.sys Tue Jul 14 01: 19: 26 2009 (4A5BC0FE)
fffff880`01596000 fffff880`015f4000 msrpc msrpc.sys Tue Jul 14 01: 21: 32 2009 (4A5BC17C)
fffff880`041db000 fffff880`041e6000 mssmbios mssmbios.sys Tue Jul 14 01: 31: 10 2009 (4A5BC3BE)
fffff880`01ca0000 fffff880`01cb2000 mup mup.sys Tue Jul 14 01: 23: 45 2009 (4A5BC201)
fffff880`0187a000 fffff880`0196c000 ndis ndis.sys Tue Jul 14 01: 21: 40 2009 (4A5BC184)
fffff880`057f4000 fffff880`05800000 ndistapi ndistapi.sys Tue Jul 14 02: 10: 00 2009 (4A5BCCD8)
fffff880`04e26000 fffff880`04e55000 ndiswan ndiswan.sys Tue Jul 14 02: 10: 11 2009 (4A5BCCE3)
fffff880`06920000 fffff880`06935000 NDProxy NDProxy.SYS Tue Jul 14 02: 10: 05 2009 (4A5BCCDD)
fffff880`0411b000 fffff880`0412a000 netbios netbios.sys Tue Jul 14 02: 09: 26 2009 (4A5BCCB6)
fffff880`0401d000 fffff880`04062000 netbt netbt.sys Tue Jul 14 01: 21: 28 2009 (4A5BC178)
fffff880`0196c000 fffff880`019cc000 NETIO NETIO.SYS Tue Jul 14 01: 21: 46 2009 (4A5BC18A)
fffff880`0460b000 fffff880`0461c000 Npfs Npfs.SYS Tue Jul 14 01: 19: 48 2009 (4A5BC114)
fffff880`041cf000 fffff880`041db000 nsiproxy nsiproxy.sys Tue Jul 14 01: 21: 02 2009 (4A5BC15E)
fffff800`03212000 fffff800`037ef000 nt ntkrnlmp.exe Tue Jul 14 01: 40: 48 2009 (4A5BC600)
fffff880`0163f000 fffff880`017e2000 Ntfs Ntfs.sys Tue Jul 14 01: 20: 47 2009 (4A5BC14F)
fffff880`0498e000 fffff880`04997000 Null Null.SYS Tue Jul 14 01: 19: 37 2009 (4A5BC109)
fffff880`06935000 fffff880`06968000 nvhda64v nvhda64v.sys Mon Feb 25 06: 27: 35 2013 (512AF647)
fffff880`05adc000 fffff880`065c4000 nvlddmkm nvlddmkm.sys Wed Jul 10 13: 44: 34 2013 (51DD4922)
fffff880`040f5000 fffff880`0411b000 pacer pacer.sys Tue Jul 14 02: 09: 41 2009 (4A5BCCC5)
fffff880`057d7000 fffff880`057f4000 parport parport.sys Tue Jul 14 02: 00: 40 2009 (4A5BCAA8)
fffff880`00e00000 fffff880`00e15000 partmgr partmgr.sys Tue Jul 14 01: 19: 58 2009 (4A5BC11E)
fffff880`00fc7000 fffff880`00ffa000 pci pci.sys Tue Jul 14 01: 19: 51 2009 (4A5BC117)
fffff880`00ede000 fffff880`00eee000 PCIIDEX PCIIDEX.SYS Tue Jul 14 01: 19: 48 2009 (4A5BC114)
fffff880`01600000 fffff880`01611000 pcw pcw.sys Tue Jul 14 01: 19: 27 2009 (4A5BC0FF)
fffff880`09607000 fffff880`096ad000 peauth peauth.sys Tue Jul 14 03: 01: 19 2009 (4A5BD8DF)
fffff880`06968000 fffff880`069a5000 portcls portcls.sys Tue Jul 14 02: 06: 27 2009 (4A5BCC03)
fffff880`00cce000 fffff880`00ce2000 PSHED PSHED.dll Tue Jul 14 03: 32: 23 2009 (4A5BE027)
fffff880`065c4000 fffff880`065e8000 rasl2tp rasl2tp.sys Tue Jul 14 02: 10: 11 2009 (4A5BCCE3)
fffff880`04e55000 fffff880`04e70000 raspppoe raspppoe.sys Tue Jul 14 02: 10: 17 2009 (4A5BCCE9)
fffff880`0161b000 fffff880`0163c000 raspptp raspptp.sys Tue Jul 14 02: 10: 18 2009 (4A5BCCEA)
fffff880`04fe1000 fffff880`04ffb000 rassstp rassstp.sys Tue Jul 14 02: 10: 25 2009 (4A5BCCF1)
fffff880`0417e000 fffff880`041cf000 rdbss rdbss.sys Tue Jul 14 01: 24: 09 2009 (4A5BC219)
fffff880`050c6000 fffff880`050d1000 rdpbus rdpbus.sys Tue Jul 14 02: 17: 46 2009 (4A5BCEAA)
fffff880`049e1000 fffff880`049ea000 RDPCDD RDPCDD.sys Tue Jul 14 02: 16: 34 2009 (4A5BCE62)
fffff880`049ea000 fffff880`049f3000 rdpencdd rdpencdd.sys Tue Jul 14 02: 16: 34 2009 (4A5BCE62)
fffff880`049f3000 fffff880`049fc000 rdprefmp rdprefmp.sys Tue Jul 14 02: 16: 35 2009 (4A5BCE63)
fffff880`01c66000 fffff880`01ca0000 rdyboost rdyboost.sys Tue Jul 14 01: 34: 34 2009 (4A5BC48A)
fffff880`07800000 fffff880`07818000 rspndr rspndr.sys Tue Jul 14 02: 08: 50 2009 (4A5BCC92)
fffff880`05a00000 fffff880`05abe000 Rt64win7 Rt64win7.sys Thu Oct 25 11: 20: 09 2012 (50890449)
fffff880`07a5e000 fffff880`07de3200 RTKVHD64 RTKVHD64.sys Tue Oct 29 11: 18: 58 2013 (526F8B92)
fffff880`051ca000 fffff880`051f9000 SCSIPORT SCSIPORT.SYS Tue Jul 14 02: 01: 04 2009 (4A5BCAC0)
fffff880`096ad000 fffff880`096b8000 secdrv secdrv.SYS Wed Sep 13 15: 18: 38 2006 (4508052E)
fffff880`057cb000 fffff880`057d7000 serenum serenum.sys Tue Jul 14 02: 00: 33 2009 (4A5BCAA1)
fffff880`0412a000 fffff880`04147000 serial serial.sys Tue Jul 14 02: 00: 40 2009 (4A5BCAA8)
fffff880`01c5e000 fffff880`01c66000 spldr spldr.sys Mon May 11 18: 56: 27 2009 (4A0858BB)
fffff880`06800000 fffff880`06871000 spsys spsys.sys Mon May 11 19: 20: 58 2009 (4A085E7A)
fffff880`01010000 fffff880`01184000 sptd sptd.sys Sat Aug 18 23: 05: 38 2012 (503003A2)
fffff880`09760000 fffff880`097f8000 srv srv.sys Tue Jul 14 01: 25: 11 2009 (4A5BC257)
fffff880`096f7000 fffff880`09760000 srv2 srv2.sys Tue Jul 14 01: 25: 02 2009 (4A5BC24E)
fffff880`096b8000 fffff880`096e5000 srvnet srvnet.sys Tue Jul 14 01: 24: 58 2009 (4A5BC24A)
fffff880`014c9000 fffff880`0152b000 storport storport.sys Tue Jul 14 02: 01: 18 2009 (4A5BCACE)
fffff880`05216000 fffff880`05217480 swenum swenum.sys Tue Jul 14 02: 00: 18 2009 (4A5BCA92)
fffff880`01a01000 fffff880`01bfe000 tcpip tcpip.sys Tue Jul 14 01: 25: 34 2009 (4A5BC26E)
fffff880`096e5000 fffff880`096f7000 tcpipreg tcpipreg.sys Tue Jul 14 02: 09: 49 2009 (4A5BCCCD)
fffff880`0463a000 fffff880`04647000 TDI TDI.SYS Tue Jul 14 01: 21: 18 2009 (4A5BC16E)
fffff880`0461c000 fffff880`0463a000 tdx tdx.sys Tue Jul 14 01: 21: 15 2009 (4A5BC16B)
fffff880`056f9000 fffff880`05715000 TeeDriverx64 TeeDriverx64.sys Thu Sep 05 20: 02: 18 2013 (5228C72A)
fffff880`0416a000 fffff880`0417e000 termdd termdd.sys Tue Jul 14 02: 16: 36 2009 (4A5BCE64)
fffff960`00550000 fffff960`0055a000 TSDDD TSDDD.dll unavailable (00000000)
fffff880`04e00000 fffff880`04e26000 tunnel tunnel.sys Tue Jul 14 02: 09: 37 2009 (4A5BCCC1)
fffff880`068b4000 fffff880`068c6000 umbus umbus.sys Tue Jul 14 02: 06: 56 2009 (4A5BCC20)
fffff880`07a3d000 fffff880`07a5a000 usbccgp usbccgp.sys Tue Jul 14 02: 06: 45 2009 (4A5BCC15)
fffff880`056f7000 fffff880`056f8f00 USBD USBD.SYS Tue Jul 14 02: 06: 23 2009 (4A5BCBFF)
fffff880`05715000 fffff880`05726000 usbehci usbehci.sys Tue Jul 14 02: 06: 30 2009 (4A5BCC06)
fffff880`068c6000 fffff880`06920000 usbhub usbhub.sys Tue Jul 14 02: 07: 09 2009 (4A5BCC2D)
fffff880`05726000 fffff880`0577c000 USBPORT USBPORT.SYS Tue Jul 14 02: 06: 31 2009 (4A5BCC07)
fffff880`0792f000 fffff880`0793b000 usbprint usbprint.sys Tue Jul 14 02: 38: 18 2009 (4A5BD37A)
fffff880`0791e000 fffff880`0792f000 usbscan usbscan.sys Tue Jul 14 02: 35: 32 2009 (4A5BD2D4)
fffff880`0793b000 fffff880`07956000 USBSTOR USBSTOR.SYS Tue Jul 14 02: 06: 34 2009 (4A5BCC0A)
fffff880`011ee000 fffff880`011fb000 vdrvroot vdrvroot.sys Tue Jul 14 02: 01: 31 2009 (4A5BCADB)
fffff880`0499e000 fffff880`049ac000 vga vga.sys Tue Jul 14 01: 38: 47 2009 (4A5BC587)
fffff880`07a00000 fffff880`07a3d000 ViaHub3 ViaHub3.sys Tue Mar 19 10: 04: 34 2013 (51482A22)
fffff880`049ac000 fffff880`049d1000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 01: 38: 51 2009 (4A5BC58B)
fffff880`0184a000 fffff880`0185a000 vmstorfl vmstorfl.sys Tue Jul 14 01: 42: 54 2009 (4A5BC67E)
fffff880`00e15000 fffff880`00e2a000 volmgr volmgr.sys Tue Jul 14 01: 19: 57 2009 (4A5BC11D)
fffff880`00e2a000 fffff880`00e86000 volmgrx volmgrx.sys Tue Jul 14 01: 20: 33 2009 (4A5BC141)
fffff880`01c12000 fffff880`01c5e000 volsnap volsnap.sys Tue Jul 14 01: 20: 08 2009 (4A5BC128)
fffff880`04147000 fffff880`04162000 wanarp wanarp.sys Tue Jul 14 02: 10: 21 2009 (4A5BCCED)
fffff880`049d1000 fffff880`049e1000 watchdog watchdog.sys Tue Jul 14 01: 37: 35 2009 (4A5BC53F)
fffff880`00ef5000 fffff880`00fb7000 Wdf01000 Wdf01000.sys Thu Jul 26 04: 25: 13 2012 (5010AA89)
fffff880`00fb7000 fffff880`00fc7000 WDFLDR WDFLDR.SYS Thu Jul 26 04: 29: 04 2012 (5010AB70)
fffff880`040ec000 fffff880`040f5000 wfplwf wfplwf.sys Tue Jul 14 02: 09: 26 2009 (4A5BCCB6)
fffff960`000d0000 fffff960`003df000 win32k win32k.sys Tue Jul 14 01: 40: 16 2009 (4A5BC5E0)
fffff880`011db000 fffff880`011e4000 WMILIB WMILIB.SYS Tue Jul 14 01: 19: 51 2009 (4A5BC117)
fffff880`079be000 fffff880`079df000 WudfPf WudfPf.sys Tue Jul 14 02: 05: 37 2009 (4A5BCBD1)
fffff880`069cd000 fffff880`069fe000 WUDFRd WUDFRd.sys Tue Jul 14 02: 06: 06 2009 (4A5BCBEE)
fffff880`0577c000 fffff880`057cb000 xhcdrv xhcdrv.sys Tue Mar 19 10: 04: 29 2013 (51482A1D)
Unloaded modules:
fffff880`01c00000 fffff880`01c0e000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`01df6000 fffff880`01e00000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000A000
fffff880`04697000 fffff880`04951000 dump_iaStorA
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 002BA000
fffff880`04951000 fffff880`04964000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00013000
fffff880`04162000 fffff880`0416a000 UsbCharger.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00008000
quit:
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
| Podziękowania od: |
marciniak
|
|
|
marciniak
Nowy
Liczba postów: 4
|
RE: Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
Memtest(86 v5.1) trwał ponad 4 godz.(na jednej kości około 2 godz.)
takie informacje znalazłem w biosie o pamięciach:
Memory:
Exstreme Memory Profile - Disabled
System Memory Multiplie 16.00 - Auto
Memory Frequency(MHz) - 1600MHz
Memory Enhancement se - Normal
Memory Timing Mode - Auto
Profile DDR Voltage - 1.50v
Chanel Intereaving - Auto
Rank Intereaving - Auto
Memory Status:
DDR Frequency - 1596.65 MHz
DRAM Voltage - (CH A/B) 1.524v
Memory Chanel A 10-10-10-30
Memory Chanel B 11-11-11-28
Mam nadzieje ze o te dane chodzi,może wyjąc jedną kość i potestować kilka dni czy będzie to samo?
System przeinstaluje i zastosuje się do wskazówek,dodam ze teraz(po zainstalowaniu SP1)zauważyłem że nie ma nowych zrzutów pamięci(w. C/ Windows /mini dump)i po bsodzie system sam nie wstaje tylko trzeba wybrać opcje uruchom system normalnie ,w trybie awaryjnym i takie tam...czego nie było wcześniej.
"Następnie wszystkie poprawki." - Rozumie ze chodzi o SP1,SP2,SP3?
(Ten post był ostatnio modyfikowany: 11.09.2014 06:43 przez marciniak.)
11.09.2014 06:29
|
| Podziękowania od: |
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
(11.09.2014 06:29)marciniak napisał(a): Memtest(86 v5.1) trwał ponad 4 godz.(na jednej kości około 2 godz.)
To wcale nie wiele mając na uwadze pojemność kości. Za mało pętli
Cytat:Memory Status:
DDR Frequency - 1596.65 MHz
DRAM Voltage - (CH A/B) 1.524v
Memory Chanel A 10-10-10-30
Memory Chanel B 11-11-11-28
Widać różne timingi. Masz różne rodzaje kości należące do dwóch różnych półek. Tą z kanału A można zluzować do tej samej co w B.
Z instrukcji masz jasno napisane
Due to CPU limitations, read the following guidelines before installing the memory in Dual Channel mode.
1. Dual Channel mode cannot be enabled if only one DDR3 memory module is installed.
2. When enabling Dual Channel mode with two memory modules, it is recommended that memory of
the same capacity, brand, speed, and chips be used for optimum performance.
Cytat:może wyjąc jedną kość i potestować kilka dni czy będzie to samo?
Jak najbardziej. Jedna kość 4GB wystarczy, żeby sobie pracować.
Możesz spróbować przynieść inną kość najlepiej zgodną z QVL na stronie tego produktu.
Ja nie wykluczam walniętej płyty głównej.
Cytat:dodam ze teraz(po zainstalowaniu SP1)zauważyłem że nie ma nowych zrzutów pamięci(w. C/ Windows /mini dump)i po bsodzie system sam nie wstaje tylko trzeba wybrać opcje uruchom system normalnie ,w trybie awaryjnym i takie tam...czego nie było wcześniej.
Wstanie z domyślną opcją ale po czasie.
Cytat:"Następnie wszystkie poprawki." - Rozumie ze chodzi o SP1,SP2,SP3?
Windows 7 to nie Windows XP. Tu jest tylko wydany jeden SP1 i potem jeszcze kolejno publikowane update'y aż do teraz.
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
| Podziękowania od: |
marciniak
|
|
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
Byłbym zapomniał
BugCheck 1A, {41790, fffffa8001c4be30, ffff, 0}
http://www.osronline.com/showthread.cfm?link=227574
http://www.osronline.com/article.cfm?article=520
Pochylę czoło jak to ktoś zdebuguje tak iż znajdzie dokładną przyczynę.
Takie bsody są trudne do analizy. Nie zawierają wielu danych które można znaleźć w pełnym zrzucie pamięci (bardzo spory plik jak i zawiera wiele poufnych informacji).
Na razie zrób to o czym jest napisane i daj znać.
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
| Podziękowania od: |
marciniak
|
|
|
marciniak
Nowy
Liczba postów: 4
|
RE: Prosze o Radę Blu Screen (1A) jak rozwiązać problem?
Przed zastosowaniem się do powyższych rad(testowaniem pojedynczo kości pamięci i reinstalacją systemu) zaktualizowałem jeszcze sterowniki do karty graficznej i o dziwo problem ustąpił(ponad tydz. bez blu screen)
zgadzało by się to z tym:
Kod:
Looks like this is a frequent complain for Windows 7. A quick search shows many
hits for this code.
This may be caused by some defective driver. Try to update your video driver.
If you have a crash dump, can you post 'lmi' command output here?
Dziękuję za pomoc i rady...temat(wątek,problem)uznaje za rozwiązany i mam nadzieję ze prędko nie zobaczę żadnych blu screenów.
Niestety po miesiącu blu screeny wróciły...po wielu testach i zjedzeniu nerwów okazało się ze jedna z kosci jest felerna ...po wymianie na sprawną wszystko działa na 100% jeszcze raz dziękuje za pomoc.
ps.mozna już zamknąć na amen.
(Ten post był ostatnio modyfikowany: 07.11.2014 19:28 przez marciniak.)
17.09.2014 19:44
|
| Podziękowania od: |
|
|
|
Post: #1
