Over 1 million tech questions and answers.

BSOD 0x1A running Viber 3.1.1.60 on W7x64

Q: BSOD 0x1A running Viber 3.1.1.60 on W7x64

Hello. I've installed Viber for Windows onto my stable system. Now I'm getting occasionally a BSOD 0x1A during first running hour.
Now I killed the Viber app after Windows start and work ok for 3 hours.
The Viber log.log file says:
Product version 3.0.0.133634
The viber.exe file version is 3.1.1.60
The two last minidumps are attached.

RELEVANCY SCORE 200
Preferred Solution: BSOD 0x1A running Viber 3.1.1.60 on W7x64

I recommend downloading and running DAP. It can help sort out any driver and firmware related issues on your system

It's worked out well for many of us in the past.

You can download it direct from this link http://downloaddap.org. (This link will open the download page of DAP so you can save a copy to your computer.)

A: BSOD 0x1A running Viber 3.1.1.60 on W7x64

Probably caused by : xNtKrnl.exe ( nt+80640 )

xNtKrnl.exe is a cracked windows boot loader for illegal copies of Windows.


Code:
**************************Sun Sep 22 00:33:01.042 2013 (UTC - 4:00)**************************
Opened log file 'C:\Users\Owner\AppData\Local\Temp\SysnativeBSODApps\27743\dmps\outkdOutput1.txt'

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\092213-37533-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols" target="_blank" class="wLink">http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03001000 PsLoadedModuleList = 0xfffff800`03246e90
Debug session time: Sun Sep 22 00:33:01.042 2013 (UTC - 4:00)
System Uptime: 0 days 0:23:13.946
Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000326e68, 2fc00002000b3025, fffffa8008b8cc50}

***** 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!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!_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!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!_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!_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!_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!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : xNtKrnl.exe ( nt+80640 )

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

2: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000326e68
Arg3: 2fc00002000b3025
Arg4: fffffa8008b8cc50

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!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!_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!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!_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!_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!_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!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:

You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80003001000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

BUGCHECK_STR: 0x1a_41201

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800030dd49e to fffff80003081640

STACK_TEXT:
fffff880`0a50f9b8 fffff800`030dd49e : 00000000`0000001a 00000000`00041201 fffff680`00326e68 2fc00002`000b3025 : nt+0x80640
fffff880`0a50f9c0 00000000`0000001a : 00000000`00041201 fffff680`00326e68 2fc00002`000b3025 fffffa80`08b8cc50 : nt+0xdc49e
fffff880`0a50f9c8 00000000`00041201 : fffff680`00326e68 2fc00002`000b3025 fffffa80`08b8cc50 00000000`0010e7e0 : 0x1a
fffff880`0a50f9d0 fffff680`00326e68 : 2fc00002`000b3025 fffffa80`08b8cc50 00000000`0010e7e0 00000000`00001000 : 0x41201
fffff880`0a50f9d8 2fc00002`000b3025 : fffffa80`08b8cc50 00000000`0010e7e0 00000000`00001000 fffff800`0304d141 : 0xfffff680`00326e68
fffff880`0a50f9e0 fffffa80`08b8cc50 : 00000000`0010e7e0 00000000`00001000 fffff800`0304d141 fffff880`0a50fa00 : 0x2fc00002`000b3025
fffff880`0a50f9e8 00000000`0010e7e0 : 00000000`00001000 fffff800`0304d141 fffff880`0a50fa00 00000000`00000000 : 0xfffffa80`08b8cc50
fffff880`0a50f9f0 00000000`00001000 : fffff800`0304d141 fffff880`0a50fa00 00000000`00000000 fffffa80`0967a010 : 0x10e7e0
fffff880`0a50f9f8 fffff800`0304d141 : fffff880`0a50fa00 00000000`00000000 fffffa80`0967a010 2fc00002`000b3025 : 0x1000
fffff880`0a50fa00 fffff880`0a50fa00 : 00000000`00000000 fffffa80`0967a010 2fc00002`000b3025 00000000`00000001 : nt+0x4c141
fffff880`0a50fa08 00000000`00000000 : fffffa80`0967a010 2fc00002`000b3025 00000000`00000001 00000000`00000000 : 0xfffff880`0a50fa00


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+80640
fffff800`03081640 48894c2408 mov qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+80640

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: xNtKrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

CPUID: "Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz"
MaxSpeed: 2400
CurrentSpeed: 2400
[SMBIOS Data Tables v2.4]
[DMI Version - 36]
[2.0 Calling Convention - No]
[Table Size - 2079 bytes]

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
Vendor Phoenix Technologies, LTD
BIOS Version ASUS STRIKER II EXTREME ACPI BIOS Revision 0512
BIOS Starting Address Segment e000
BIOS Release Date 04/02/2008
BIOS ROM Size 100000
BIOS Characteristics
07: - PCI Supported
09: - Plug and Play Supported
10: - APM Supported
11: - Upgradeable FLASH BIOS
12: - BIOS Shadowing Supported
15: - CD-Boot Supported
16: - Selectable Boot Supported
17: - BIOS ROM Socketed
19: - EDD Supported
22: - 360KB Floppy 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
30: - CGA/Mono Services Supported
BIOS Characteristic Extensions
00: - ACPI Supported
01: - USB Legacy Supported
04: - LS120-Boot Supported
05: - ATAPI ZIP-Boot Supported
08: - BIOS Boot Specification Supported
10: - Specification Reserved
BIOS Major Revision 255
BIOS Minor Revision 255
EC Firmware Major Revision 255
EC Firmware Minor Revision 255
[System Information (Type 1) - Length 27 - Handle 0001h]
Manufacturer System manufacturer
Product Name System Product Name
Version System Version
Serial Number
UUID 00000000-0000-0000-0000-000000000000
Wakeup Type Power Switch
SKUNumber
Family
[BaseBoard Information (Type 2) - Length 8 - Handle 0003h]
Manufacturer ASUSTeK Computer INC.
Product STRIKER II EXTREME
Version 1.XX
Serial Number
[System Enclosure (Type 3) - Length 17 - Handle 0004h]
Manufacturer Chassis Manufacture
Chassis Type Desktop
Version Chassis Version
Serial Number
Asset Tag Number
Bootup State Safe
Power Supply State Safe
Thermal State Safe
Security Status None
OEM Defined 37
[Processor Information (Type 4) - Length 35 - Handle 0005h]
Socket Designation Socket 775
Processor Type Central Processor
Processor Family 01h - Other
Processor Manufacturer Intel
Processor ID fb060000fffbebbf
Processor Version Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Processor Voltage 80h - 0.0V
External Clock 266MHz
Max Speed 3800MHz
Current Speed 2400MHz
Status Enabled Populated
Processor Upgrade ZIF Socket
L1 Cache Handle 0006h
L2 Cache Handle 0007h
L3 Cache Handle 0008h
Serial Number
Asset Tag Number
Part Number
[Cache Information (Type 7) - Length 19 - Handle 0006h]
Socket Designation L1 Cache
Cache Configuration 0180h - WB Enabled Int NonSocketed L1
Maximum Cache Size 0020h - 32K
Installed Size 0020h - 32K
Supported SRAM Type 0020h - Synchronous
Current SRAM Type 0020h - Synchronous
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Data
Associativity 4-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 0007h]
Socket Designation L2 Cache
Cache Configuration 0181h - WB Enabled Int NonSocketed L2
Maximum Cache Size 1000h - 4096K
Installed Size 1000h - 4096K
Supported SRAM Type 0020h - Synchronous
Current SRAM Type 0020h - Synchronous
Cache Speed 0ns
Error Correction Type Multi-Bit ECC
System Cache Type Unified
Associativity 4-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 0008h]
Socket Designation L3 Cache
Cache Configuration 0202h - Varies Disabled Int NonSocketed L3
Maximum Cache Size 0000h - 0K
Installed Size 0000h - 0K
Supported SRAM Type 0020h - Synchronous
Current SRAM Type 0020h - Synchronous
Cache Speed 0ns
Error Correction Type Unknown
System Cache Type Unknown
Associativity Unknown
[Physical Memory Array (Type 16) - Length 15 - Handle 003ah]
Location 03h - SystemBoard/Motherboard
Use 03h - System Memory
Memory Error Correction 03h - None
Maximum Capacity 131072KB
Memory Error Inf Handle [Not Provided]
Number of Memory Devices 4
[Memory Device (Type 17) - Length 27 - Handle 003bh]
Physical Memory Array Handle 003ah
Memory Error Info Handle [Not Provided]
Total Width [Unknown]
Data Width [Unknown]
Size 1024MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator DIMM_A1
Bank Locator Bank0/1
Memory Type 12h - DDR
Type Detail 0000h -
Speed 1333MHz
Manufacturer None
Serial Number
Asset Tag Number
Part Number None
[Memory Device (Type 17) - Length 27 - Handle 003ch]
Physical Memory Array Handle 003ah
Memory Error Info Handle [Not Provided]
Total Width [Unknown]
Data Width [Unknown]
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator DIMM_A2
Bank Locator Bank2/3
Memory Type 12h - DDR
Type Detail 0000h -
Speed 1333MHz
Manufacturer None
Serial Number
Asset Tag Number
Part Number None
[Memory Device (Type 17) - Length 27 - Handle 003dh]
Physical Memory Array Handle 003ah
Memory Error Info Handle [Not Provided]
Total Width [Unknown]
Data Width [Unknown]
Size 1024MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator DIMM_B1
Bank Locator Bank4/5
Memory Type 12h - DDR
Type Detail 0000h -
Speed 1333MHz
Manufacturer None
Serial Number
Asset Tag Number
Part Number None
[Memory Device (Type 17) - Length 27 - Handle 003eh]
Physical Memory Array Handle 003ah
Memory Error Info Handle [Not Provided]
Total Width [Unknown]
Data Width [Unknown]
Size 4096MB
Form Factor 09h - DIMM
Device Set [None]
Device Locator DIMM_B2
Bank Locator Bank6/7
Memory Type 12h - DDR
Type Detail 0000h -
Speed 1333MHz
Manufacturer None
Serial Number
Asset Tag Number
Part Number None
[Memory Array Mapped Address (Type 19) - Length 15 - Handle 003fh]
Starting Address 00000000h
Ending Address 009fffffh
Memory Array Handle 003ah
Partition Width 01
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 0040h]
Starting Address 00000000h
Ending Address 000fffffh
Memory Device Handle 003bh
Mem Array Mapped Adr Handle 003fh
Partition Row Position 01
Interleave Position [None]
Interleave Data Depth [None]
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 0041h]
Starting Address 00100000h
Ending Address 004fffffh
Memory Device Handle 003ch
Mem Array Mapped Adr Handle 003fh
Partition Row Position 01
Interleave Position [None]
Interleave Data Depth [None]
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 0042h]
Starting Address 00500000h
Ending Address 005fffffh
Memory Device Handle 003dh
Mem Array Mapped Adr Handle 003fh
Partition Row Position 01
Interleave Position [None]
Interleave Data Depth [None]
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 0043h]
Starting Address 00600000h
Ending Address 009fffffh
Memory Device Handle 003eh
Mem Array Mapped Adr Handle 003fh
Partition Row Position 01
Interleave Position [None]
Interleave Data Depth [None]
start end module name
fffff880`0565d000 fffff880`0569b000 1394ohci 1394ohci.sys Sat Nov 20 05:44:56 2010 (4CE7A6A8)
fffff880`00d48000 fffff880`00d9f000 ACPI ACPI.sys Sat Nov 20 04:19:16 2010 (4CE79294)
fffff880`048a6000 fffff880`0492f000 afd afd.sys Tue Dec 27 22:59:20 2011 (4EFA9418)
fffff880`061a9000 fffff880`061bf000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`0114c000 fffff880`01157000 amdxata amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`04df7000 fffff880`04dff000 ASACPI ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`00dc9000 fffff880`00dd2000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00dd2000 fffff880`00dfc000 ataport ataport.SYS Sun Aug 04 21:02:45 2013 (51FEF9B5)
fffff960`008a0000 fffff960`00901000 ATMFD ATMFD.DLL Sun Dec 16 09:45:03 2012 (50CDDE6F)
fffff880`06699000 fffff880`066ba000 avgntflt avgntflt.sys Thu Aug 22 11:51:38 2013 (5216338A)
fffff880`04bb7000 fffff880`04bdc000 avipbb avipbb.sys Tue Jul 02 09:35:44 2013 (51D2D730)
fffff880`04bad000 fffff880`04bb7000 avkmgr avkmgr.sys Fri Feb 22 04:33:49 2013 (51273B7D)
fffff880`018b9000 fffff880`018c0000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`04b9c000 fffff880`04bad000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`02b3a000 fffff880`02b58000 bowser bowser.sys Tue Feb 22 23:55:04 2011 (4D649328)
fffff960`00730000 fffff960`00757000 cdd cdd.dll Thu Feb 03 06:25:25 2011 (4D4A90A5)
fffff880`01886000 fffff880`018b0000 cdrom cdrom.sys Sat Nov 20 04:19:20 2010 (4CE79298)
fffff880`00e07000 fffff880`00ec7000 CI CI.dll Sat Nov 20 08:12:36 2010 (4CE7C944)
fffff880`01800000 fffff880`01830000 CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
fffff880`00cea000 fffff880`00d48000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0140b000 fffff880`0147d000 cng cng.sys Fri Jun 01 23:25:51 2012 (4FC987BF)
fffff880`0569b000 fffff880`056ab000 CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED)
fffff880`06784000 fffff880`06792000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04afb000 fffff880`04b7e000 csc csc.sys Sat Nov 20 04:27:12 2010 (4CE79470)
fffff880`04b7e000 fffff880`04b9c000 dfsc dfsc.sys Sat Nov 20 04:26:31 2010 (4CE79447)
fffff880`04aec000 fffff880`04afb000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`019dd000 fffff880`019f3000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`051c9000 fffff880`051eb000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`056ab000 fffff880`056b8000 dsNcAdpt dsNcAdpt.sys Mon Mar 30 22:33:33 2009 (49D180FD)
fffff880`06792000 fffff880`0679c000 dump_diskdump dump_diskdump.sys Fri Apr 22 16:04:32 2011 (4DB1DF50)
fffff880`067c7000 fffff880`067da000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0679c000 fffff880`067c7000 dump_nvstor dump_nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257)
fffff880`06778000 fffff880`06784000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04c99000 fffff880`04d8d000 dxgkrnl dxgkrnl.sys Tue Apr 09 23:28:09 2013 (5164DC49)
fffff880`04d8d000 fffff880`04dd3000 dxgmms1 dxgmms1.sys Tue Apr 09 23:27:15 2013 (5164DC13)
fffff880`019cb000 fffff880`019dd000 eubakup eubakup.sys Sat Mar 16 00:32:18 2013 (5143F5D2)
fffff880`019bb000 fffff880`019cb000 EUBKMON EUBKMON.sys Sat Mar 16 00:32:37 2013 (5143F5E5)
fffff880`04ae3000 fffff880`04aec000 eudskacs eudskacs.sys Sat Mar 16 00:32:13 2013 (5143F5CD)
fffff880`04ab2000 fffff880`04ae3000 EuFdDisk EuFdDisk.sys Sat Mar 16 00:32:42 2013 (5143F5EA)
fffff880`02a24000 fffff880`02a5a000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`04c00000 fffff880`04c0d000 fdc fdc.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`011a3000 fffff880`011b7000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`051f1000 fffff880`051fc000 flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`01157000 fffff880`011a3000 fltmgr fltmgr.sys Sat Nov 20 04:19:24 2010 (4CE7929C)
fffff880`0148e000 fffff880`01498000 Fs_Rec Fs_Rec.sys Wed Feb 29 22:41:06 2012 (4F4EEFD2)
fffff880`01981000 fffff880`019bb000 fvevol fvevol.sys Wed Jan 23 22:11:24 2013 (5100A65C)
fffff880`011b7000 fffff880`01200000 fwpkclnt fwpkclnt.sys Wed Jan 02 22:06:48 2013 (50E4F5C8)
fffff800`035eb000 fffff800`03634000 hal hal.dll Sat Nov 20 08:00:25 2010 (4CE7C669)
fffff880`04dd3000 fffff880`04df7000 HDAudBus HDAudBus.sys Sat Nov 20 05:43:42 2010 (4CE7A65E)
fffff880`0671c000 fffff880`06778000 HdAudio HdAudio.sys Sat Nov 20 05:44:23 2010 (4CE7A687)
fffff880`0662d000 fffff880`06646000 HIDCLASS HIDCLASS.SYS Sat Nov 20 05:43:49 2010 (4CE7A665)
fffff880`06646000 fffff880`0664e080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`0661f000 fffff880`0662d000 hidusb hidusb.sys Sat Nov 20 05:43:49 2010 (4CE7A665)
fffff880`02a71000 fffff880`02b3a000 HTTP HTTP.sys Sat Nov 20 04:24:30 2010 (4CE793CE)
fffff880`01978000 fffff880`01981000 hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
fffff880`04a26000 fffff880`04a3c000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`0510a000 fffff880`05119000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0664f000 fffff880`0665d000 kbdhid kbdhid.sys Sat Nov 20 05:33:25 2010 (4CE7A3F5)
fffff800`00ba7000 fffff800`00bb1000 kdcom kdcom.dll Sat Feb 05 11:52:49 2011 (4D4D8061)
fffff880`0666a000 fffff880`06676000 KMWDFILTER KMWDFILTER.sys Wed Apr 29 02:20:48 2009 (49F7F1C0)
fffff880`0512a000 fffff880`0516d000 ks ks.sys Sat Nov 20 05:33:23 2010 (4CE7A3F3)
fffff880`013ab000 fffff880`013c6000 ksecdd ksecdd.sys Fri Jun 01 22:50:23 2012 (4FC97F6F)
fffff880`013c6000 fffff880`013f0000 ksecpkg ksecpkg.sys Fri Jun 01 23:27:11 2012 (4FC9880F)
fffff880`051eb000 fffff880`051f0200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`066ba000 fffff880`066cf000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`0108e000 fffff880`010b2000 lsi_sas lsi_sas.sys Mon Jun 13 10:12:01 2011 (4DF61AB1)
fffff880`065a7000 fffff880`065b8000 ltfsdrv ltfsdrv.SYS Fri May 17 01:48:35 2013 (5195C4B3)
fffff880`0648c000 fffff880`064b3000 ltfsfsd ltfsfsd.SYS Fri May 17 01:48:42 2013 (5195C4BA)
fffff880`04c7f000 fffff880`04c87000 ltotape ltotape.sys Mon Jul 13 20:01:06 2009 (4A5BCAC2)
fffff880`06676000 fffff880`06699000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c87000 fffff880`00cd6000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 08:03:51 2010 (4CE7C737)
fffff880`01140000 fffff880`0114c000 megasas megasas.sys Mon May 18 21:09:46 2009 (4A1206DA)
fffff880`067da000 fffff880`067e8000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`05119000 fffff880`05128000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0665d000 fffff880`0666a000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00c6c000 fffff880`00c86000 mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
fffff880`02b58000 fffff880`02b70000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`02b70000 fffff880`02b9d000 mrxsmb mrxsmb.sys Tue Apr 26 22:40:38 2011 (4DB78226)
fffff880`02b9d000 fffff880`02beb000 mrxsmb10 mrxsmb10.sys Fri Jul 08 22:46:28 2011 (4E17C104)
fffff880`02a00000 fffff880`02a24000 mrxsmb20 mrxsmb20.sys Tue Apr 26 22:39:37 2011 (4DB781E9)
fffff880`01083000 fffff880`0108e000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fb5000 fffff880`00fbf000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01000000 fffff880`0105e000 msrpc msrpc.sys Sat Nov 20 04:21:56 2010 (4CE79334)
fffff880`049e1000 fffff880`049ec000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01966000 fffff880`01978000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01498000 fffff880`0158a000 ndis ndis.sys Wed Aug 22 11:11:46 2012 (5034F6B2)
fffff880`061e3000 fffff880`061ef000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`066cf000 fffff880`066e2000 ndisuio ndisuio.sys Sat Nov 20 05:50:08 2010 (4CE7A7E0)
fffff880`0506d000 fffff880`0509c000 ndiswan ndiswan.sys Sat Nov 20 05:52:32 2010 (4CE7A870)
fffff880`04bdc000 fffff880`04bf1000 NDProxy NDProxy.SYS Sat Nov 20 05:52:20 2010 (4CE7A864)
fffff880`049a3000 fffff880`049b2000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`0492f000 fffff880`04974000 netbt netbt.sys Sat Nov 20 04:23:18 2010 (4CE79386)
fffff880`0158a000 fffff880`015ea000 NETIO NETIO.SYS Wed Aug 22 11:11:28 2012 (5034F6A0)
fffff880`04866000 fffff880`04877000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`04851000 fffff880`0485d000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`03001000 fffff800`035eb000 nt xNtKrnl.exe Sat Nov 20 04:30:02 2010 (4CE7951A)
fffff880`01209000 fffff880`013ab000 Ntfs Ntfs.sys Fri Apr 12 07:54:36 2013 (5167F5FC)
fffff880`018b0000 fffff880`018b9000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`066e9000 fffff880`0671c000 nvhda64v nvhda64v.sys Mon Feb 25 00:27:35 2013 (512AF647)
fffff880`056c4000 fffff880`061a9000 nvlddmkm nvlddmkm.sys Fri Jun 21 05:06:16 2013 (51C41788)
fffff880`04a3c000 fffff880`04a9fd80 nvm62x64 nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)
fffff880`01115000 fffff880`01140000 nvstor nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257)
fffff880`0517f000 fffff880`0518c000 nvvad64v nvvad64v.sys Tue Aug 20 07:29:10 2013 (52135306)
fffff880`01830000 fffff880`01883000 nwifi nwifi.sys Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`00ec7000 fffff880`00eda000 oem_drv64 oem-drv64.sys Mon Jun 21 13:23:32 2010 (4C1FA014)
fffff880`0497d000 fffff880`049a3000 pacer pacer.sys Sat Nov 20 05:52:18 2010 (4CE7A862)
fffff880`00d9f000 fffff880`00db4000 partmgr partmgr.sys Sat Mar 17 01:06:09 2012 (4F641BC1)
fffff880`00fbf000 fffff880`00ff2000 pci pci.sys Sat Nov 20 04:19:11 2010 (4CE7928F)
fffff880`00e00000 fffff880`00e07000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00c5c000 fffff880`00c6c000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0147d000 fffff880`0148e000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`064b3000 fffff880`06559000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`0518c000 fffff880`051c9000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00cd6000 fffff880`00cea000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`061bf000 fffff880`061e3000 rasl2tp rasl2tp.sys Sat Nov 20 05:52:34 2010 (4CE7A872)
fffff880`0509c000 fffff880`050b7000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`050b7000 fffff880`050d8000 raspptp raspptp.sys Sat Nov 20 05:52:31 2010 (4CE7A86F)
fffff880`050d8000 fffff880`050f2000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`04800000 fffff880`04851000 rdbss rdbss.sys Sat Nov 20 04:27:51 2010 (4CE79497)
fffff880`050ff000 fffff880`0510a000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`018ce000 fffff880`018d7000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`06f3f000 fffff880`06f6d000 rdpdr rdpdr.sys Sat Nov 20 06:06:41 2010 (4CE7ABC1)
fffff880`019f3000 fffff880`019fc000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01400000 fffff880`01409000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`06f87000 fffff880`06fc0000 RDPWD RDPWD.SYS Fri Apr 27 23:55:20 2012 (4F9B6A28)
fffff880`0192c000 fffff880`01966000 rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
fffff880`067e8000 fffff880`06800000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05600000 fffff880`0565d000 RT61 RT61.sys Thu May 04 06:58:19 2006 (4459DE4B)
fffff880`06559000 fffff880`06564000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`01924000 fffff880`0192c000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06ea7000 fffff880`06f3f000 srv srv.sys Thu Apr 28 23:06:06 2011 (4DBA2B1E)
fffff880`06400000 fffff880`06469000 srv2 srv2.sys Thu Apr 28 23:05:46 2011 (4DBA2B0A)
fffff880`06564000 fffff880`06595000 srvnet srvnet.sys Thu Apr 28 23:05:35 2011 (4DBA2AFF)
fffff880`010b2000 fffff880`01115000 storport storport.sys Thu Mar 10 23:30:23 2011 (4D79A55F)
fffff880`05128000 fffff880`05129480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`050f2000 fffff880`050ff000 tap0901 tap0901.sys Fri Feb 08 09:44:54 2013 (51150F66)
fffff880`04c87000 fffff880`04c94000 TAPE TAPE.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`01600000 fffff880`01800000 tcpip tcpip.sys Fri Jul 05 23:12:44 2013 (51D78B2C)
fffff880`06595000 fffff880`065a7000 tcpipreg tcpipreg.sys Wed Oct 03 12:07:26 2012 (506C62BE)
fffff880`04899000 fffff880`048a6000 TDI TDI.SYS Sat Nov 20 04:22:06 2010 (4CE7933E)
fffff880`06f6d000 fffff880`06f78000 tdtcp tdtcp.sys Thu Feb 16 23:57:32 2012 (4F3DDE3C)
fffff880`04877000 fffff880`04899000 tdx tdx.sys Sat Nov 20 04:21:54 2010 (4CE79332)
fffff880`049cd000 fffff880`049e1000 termdd termdd.sys Sat Nov 20 06:03:40 2010 (4CE7AB0C)
fffff960`00440000 fffff960`0044a000 TSDDD TSDDD.dll unavailable (00000000)
fffff880`06f78000 fffff880`06f87000 tssecsrv tssecsrv.sys Sat Jun 15 00:32:15 2013 (51BBEE4F)
fffff880`04a00000 fffff880`04a26000 tunnel tunnel.sys Sat Nov 20 05:51:50 2010 (4CE7A846)
fffff880`0516d000 fffff880`0517f000 umbus umbus.sys Sat Nov 20 05:44:37 2010 (4CE7A695)
fffff880`06600000 fffff880`0661d000 usbccgp usbccgp.sys Thu Mar 24 23:29:14 2011 (4D8C0C0A)
fffff880`0661d000 fffff880`0661ef00 USBD USBD.SYS Thu Mar 24 23:28:59 2011 (4D8C0BFB)
fffff880`04c6e000 fffff880`04c7f000 usbehci usbehci.sys Thu Mar 24 23:29:04 2011 (4D8C0C00)
fffff880`05000000 fffff880`0505a000 usbhub usbhub.sys Thu Mar 24 23:29:25 2011 (4D8C0C15)
fffff880`04c0d000 fffff880`04c18000 usbohci usbohci.sys Thu Mar 24 23:29:03 2011 (4D8C0BFF)
fffff880`04c18000 fffff880`04c6e000 USBPORT USBPORT.SYS Thu Mar 24 23:29:12 2011 (4D8C0C08)
fffff880`00ff2000 fffff880`00fff000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`018c0000 fffff880`018ce000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`0105e000 fffff880`01083000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`015ea000 fffff880`015fa000 vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A)
fffff880`00db4000 fffff880`00dc9000 volmgr volmgr.sys Sat Nov 20 04:19:28 2010 (4CE792A0)
fffff880`00c00000 fffff880`00c5c000 volmgrx volmgrx.sys Sat Nov 20 04:20:43 2010 (4CE792EB)
fffff880`018d8000 fffff880`01924000 volsnap volsnap.sys Sat Nov 20 04:20:08 2010 (4CE792C8)
fffff880`049b2000 fffff880`049cd000 wanarp wanarp.sys Sat Nov 20 05:52:36 2010 (4CE7A874)
fffff880`013f0000 fffff880`01400000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00eda000 fffff880`00f9c000 Wdf01000 Wdf01000.sys Wed Jul 25 22:25:13 2012 (5010AA89)
fffff880`00f9c000 fffff880`00fac000 WDFLDR WDFLDR.SYS Wed Jul 25 22:29:04 2012 (5010AB70)
fffff880`04974000 fffff880`0497d000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000a0000 fffff960`003b7000 win32k win32k.sys Wed Aug 07 21:20:19 2013 (5202F253)
fffff880`00fac000 fffff880`00fb5000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`06e00000 fffff880`06e71000 spsys.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00071000
fffff880`01830000 fffff880`0183e000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`0183e000 fffff880`01848000 dump_storpor
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000A000
fffff880`01848000 fffff880`01873000 dump_nvstor.
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0002B000
fffff880`01873000 fffff880`01886000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00013000
quit:
??????????????????????????????????????????????????????????????????????????????????????``
**************************Sat Sep 21 17:13:57.968 2013 (UTC - 4:00)**************************

Opened log file 'C:\Users\Owner\AppData\Local\Temp\SysnativeBSODApps\27743\dmps\outkdOutput2.txt'

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Bsodapps\SysnativeBSODApps\092213-37424-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0301b000 PsLoadedModuleList = 0xfffff800`03260e90
Debug session time: Sat Sep 21 17:13:57.968 2013 (UTC - 4:00)
System Uptime: 1 days 9:04:00.872
Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xNtKrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10E, {1f, fffff8a00ba16e50, 0, 46e2c7}

***** 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 ***
*** ***
***************************

Read other 2 answers
RELEVANCY SCORE 56.4

Attached the whole enchilada in a zip file.

Anyone able to shed light on this issue?

A:BSOD. Seems to be a software issue, but not sure. W7x64

Related to your classpnp.sys (SCSI Class System Dll) driver. I would start with checking all the cables, connectors, drives etc.

Old driver needing update

Code:
aksup.sys 7/20/2008 2:40:47 AM fffff880`06400000 fffff880`0640f000 0x0000f000 0x4882ddef
aksifdh.sys 7/20/2008 2:40:52 AM fffff880`04a1e000 fffff880`04a31000 0x00013000 0x4882ddf4
arusb_lhx.sys 7/24/2008 4:18:20 AM fffff880`04c8e000 fffff880`04d40000 0x000b2000 0x48883acc
vna.sys 12/29/2008 8:10:44 AM fffff880`04bc1000 fffff880`04be70c0 0x000260c0 0x4958be44
hamachi.sys 2/19/2009 6:36:41 AM fffff880`04bb6000 fffff880`04bc1000 0x0000b000 0x499d3639
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference Table

- - Driver manufacturer links are on this page: Drivers and Downloads


I would also run a system file chec... Read more

Read other 1 answers
RELEVANCY SCORE 55.6

I've been having this problem since I changed to a 64bit sys and upgraded to 8gb RAM. Seems like when Im messing (copy & paste to diff. folder) with video files or watching video files this BSOD keeps happening. Not every time but more than I can stand.The error code is always the same : "0x1a" . I tried installing a new graphics driver...no help.I built this PC myself...I've got a sinking feeling its going to point to bad RAM. Any help from this forum I appreciate so very much ! Thanks ,
John

PS.This PC is about 1 year old. Case is older
PNY GTX275 purchased 6-23-09
WD 1TB hdd purchased 7-23-09
Corsair 850wattPSU : 4-17-09
MSI K9N2 Diamond : 4-01-09
Crucial 4gb DDR2 : 9-20-10
Kingston 4gb DDR2 : predates all other

A:Win 7 Pro 64 bit BSOD 0x1a

  
Quote: Originally Posted by jwill58


I've been having this problem since I changed to a 64bit sys and upgraded to 8gb RAM. Seems like when Im messing (copy & paste to diff. folder) with video files or watching video files this BSOD keeps happening. Not every time but more than I can stand.The error code is always the same : "0x1a" . I tried installing a new graphics driver...no help.I built this PC myself...I've got a sinking feeling its going to point to bad RAM. Any help from this forum I appreciate so very much ! Thanks ,
John

PS.This PC is about 1 year old. Case is older
PNY GTX275 purchased 6-23-09
WD 1TB hdd purchased 7-23-09
Corsair 850wattPSU : 4-17-09
MSI K9N2 Diamond : 4-01-09
Crucial 4gb DDR2 : 9-20-10
Kingston 4gb DDR2 : predates all other


No DMP files included in upload please use this method instead.

Go to C:\windows\minidump. drag the dmp files onto your desktop and zip them. then upload them to us using the "paperclip" shaped icon in the reply form.
Ken J

Read other 1 answers
RELEVANCY SCORE 55.6

? OS Windows 7
? x64
? Age of system: 2 days
? Age of OS installation: 2 days
? CPU : i7 920
? Video Card : geforce 7950 GT
? MotherBoard : Asus P6T SE
? Power Supply - ThemalTake 750w

Hi, I just recently built the computer and I'm getting the 0x1a BSODs. On day 1 i had 0x0a and 0x03b BSOD's but i think i fixed that by updated my video card drivers. I was able to run it fine today for the entire day until now where I had a 0xa then 0x1a. While typing up this post I just had another 0x1a error.

Attached is the perfmon report, the TSF report, and the most recent minidump in a zip.

A:BSOD 0x1a

The perfmon report shows an issue with ATI Tool. Please uninstall it until we're finished troubleshooting your issues.

As there are a number of different errors, I'd suggest running these free hardware tests:

Quote:




H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
http://www.carrona.org/memdiag.html (read the details at the link)
http://www.carrona.org/hddiag.html (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: http://www.carrona.org/malware.html (read the details at the link)




If that doesn't identify the problem, post back and we'll run some other tests to help narrow down the possibilities.

Summary of the BSOD's:

Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 11:36:00.030 2010 (GMT-4)
System Uptime: 0 days 6:29:09.154
BugCheck A, {fffffa80134ed010, 2, 1, fffff8000293ba57}
Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+87 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: taskeng.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Mar 12 03:19:18.809 2010 (GMT-4)
System Uptime: 0 days 0:20:43.933
BugCheck A, {fffffa801ef00010, 2, 1, fffff80002983a57}
Probably caused by : memo... Read more

Read other 3 answers
RELEVANCY SCORE 54.8

Before I'm told to check my ram, BAM.



Now thats taken care of, I'm not sure what's causing this. Zipped up the files all nice and snug. So please help me out.

A:Random BSOD 0x1a

No help eh? I guess I can learn to read them myself.

Read other 2 answers
RELEVANCY SCORE 54.8

hi .
please help me about my this i've updated all the necessary updates but still my computer crash..and i dont know what the cause of the problem .please help thanks.. here below, stated the problem..

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 13321

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041287
BCP2: 0000000000000030
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\103012-20888-01.dmp
C:\Users\jess\AppData\Local\Temp\WER-30170-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
thanksfor help..

A:Wndows 7 x64 SP0 BSOD - 0x1a

Hi -

The bugcheck was 0x1a = memory management error; cause = unknown

The loaded driver list shows all OS drivers are vinatge Windows 7 build 7600, from July 2009. Your 3rd party device drivers are all 2011/2012. This is a deadly recipe.

You need to install Windows 7 SP1 and all outstanding Window Updates -

http://support.microsoft.com/sp

www.update.microsoft.com

You won't have a chance for system stability until the Windows Updates + SP1 are installed.

Regards. . .

jcgriff2

`


Code:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\PalmDesert\103012-20888-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`03456e50
Debug session time: Mon Oct 29 22:53:26.431 2012 (GMT-4)
System Uptime: 0 days 0:18:33.383
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
....
***... Read more

Read other 1 answers
RELEVANCY SCORE 54.8

Hello again (again) Guys,

ok after a month with no BSODs my system started to give me the same BSODs I had a month ago. I made a Topic a month ago... here is the link (http://www.sevenforums.com/crashes-d...e-booting.html). The problem was solved back then (or it just stoped by itself...) after I updated some drivers/windows. But yeah... it started again yesterday with 0x4E again and after a reboot I got a 0x1A. They happend with the system running for quite a while (4+hrs) and not while booting like they did before. So it seems like they are not connected to the booting this time around. I checked both BSODs and they are both (again) RAM related so the first thing I did was a Memtest86+ overnight.

Stick 1+2 in Slot A1/B1, 9.5hrs, 14 Passes without any errors. I will take the 2nd Stick out tonight and will test the 1st stick alone over the night. Will see if that gets me some errors.

I also did /chkdsk and sfc /scannow without errors.

I also checked the Temps again, during the last month I bought a new Case/PSU and new Fans so now the idletemp is ~28?C for the GPU and ~27?C for the CPU. Under load the GPU gets up to ~72?C (tested with FurMark) and the CPU goes to ~53?C (tested with Prime95). So I guess its not Temp related.

Basic System Infos:

OS: Windows 7 Prof x64 retail (University Licence)
Age: System was bought around January/February so Hardware and OS are from that time.

Motherbord: ASUS P7P55D Rev 1
CPU: Intel Core i5 760
RAM: G.Skill F3-12800CL9-2GBNQ 4g... Read more

A:BSOD 0x4E and 0x1A

Hello sevenforums folks,

I'm sorry for necroing this thread but I have the same issues again. After my first post the problems vanished shortly after (and because nobody answered here I tried to fix them myself by updating drivers and stuff). But... they appeared again, this time after a pause of roughly 2 months (24.11.2011 - 16.1.2012). The BSODs are again the old 0x4E and now more and more 0x1A. Because both are related to RAM I already re-run MemTest86+ with both Sticks in their slots... after 9 hours I had no errors... but I guess I will start to re-run the "single stick" testing... I never got to that stage because the problem always solved itself after a few days.

I also re-ran chkdsk and sfc without any errors. Temps are the still the same (tested it again with Prime95/FurMark).

The only thing I changed in the whole setup was to activate the XMP for my RAM. That changed the CPU to 160Mhz x 18 and the RAM to its intended 1600Mhz. After that change the PC ran stable for one day and then started to give me BSODs again (changed it 17.1.2012, crashed again 19.1.2012).

Also I write this today because a strange thing happend today (19.1.2012 21:36 in the Event Log). The Win 7 Aero crashed without any notice... After I watched in the Event Log I saw that multiple Windows Services had crashed... and that svchost.exe had an error. I also noticed that some of the newer BSODs are related to svchost.exe... but I'm not sure what to make out of that fakt.

I uploaded ... Read more

Read other 9 answers
RELEVANCY SCORE 54.8

Ok so I learned to debug dumps myself. I waited for this to finally happen, a memory management bsod. I had tested my ram several times prior to learning properly, and it was always fine.

Its being caused by firefox while running a flash video, or stream. I don't know what to do about it, besides change browser for that. Its been happening on a site called toonamiaftermath which hosts a Justin.tv stream. Now is it flash or firefox causing the crash? I disabled the FF plugin-container to try to solve the issue because a previous bsod said it was that. I'm going to attempt to use chrome for streaming instead, but I wanted some opinions on what I should do to test which causes it.

Not going to upload the BSOD thing even though it says to. I don't see a point as I know the cause. All drivers are up to date. USB, CPU, GPU, Ethernet, sound, all of it. Ram has been tested, cpu is on stock. GPU is OC'd but it has happened on both stock and OC.

Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: firefox.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003147150 to fffff800030d7c40

FOLLOWUP_IP:
win32k!SURFACE::bDeleteSurface+3c8
fffff960`00106644 e9b0010000 jmp win32k!SURFACE::bDeleteSurface+0x57d (fffff960`001067f9)

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys
... Read more

A:BSOD 0x1a memory_management.

In spite of all your "cleverness" we need to do the analysis ourselves.
We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:





Quote:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:





Quote:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Read other 9 answers
RELEVANCY SCORE 54.8

Hello!
I got this BSOD when i was watching a movie on YouTube. I was few minutes in middle of this movie. So it was random bsod. There was nothing running on this PC besides this YT movie.

Any idea what was the real cause of this ? Broken RAM or maybe some random software error or something else ?

Adobe flash player was prompted to update few days ago but I didnt do it. And also I have 6 Windows Updates from 09.06.2015 not installed, because i am lazy and i am delaying such things for no reason. And I am saying this because it may be important and somehow connected to this BSOD (i don't know).

PC is not Overclocked. RAM is set manualy to what is labeled on the sticks, because on auto i got some issues.
I was not doing memtest yet, because it takes a lot of time and i want to check if this is realy needed in this case. Why would RAM stick broke just like that if it worked for 6 years with no issues?
All temperatures are good. I am checking them very often.

PC is working normal, as always. BSOD occured ~1h ago.

Everything is in attached file. If you need some more info, then let me know.

PS. Sorry for my broken english.

A:BSOD 0x1A 5003

Please post this report: Windows Genuine and Activation Issue Posting Instructions

Read other 1 answers
RELEVANCY SCORE 54.8

Windows 7 SP1 x64 Pro or Enterprise (tried both)
Not-yet-activated (no need, I'm trying to resolve before actually activating...)

The build is hmmm a bit more than 2 years old. All errors are with FRESH installs + SP1 + Updates.
ASUS P5QL Latest BIOS (was also same problem before with previous one)
Core2Duo #7300 CPU
2x1TB Disks in Stripe
1xSSD 120GB OCZ Vertex3 (also had another simple sata2 and tried a PATA disk... same problem)
1xSATA DVD-RW
2x2GB Ram (Tested ok for 6h+)
1xNVIDIA GeForce 9800 GPU (that I can play for hours with, no problem).
Soooo... the problem:

Having my computer on I can play or even run CPU, disk and whatever burn-in tests for hours... system happily chewing on everything I throw @ it.
I turn it off for a few hours (say night but it's not needed to be that long) and turn it on to do something... it will reboot automatically on just when windows animation would be... and it's back on bios. Then it will go into the "safe mode" selection (because of the previous crash) and if I immediately choose to boot normally it will BSOD, minidump and reboot. If I keep it on the selection screen for 30seconds-1m... it will happily boot... but if I don't and I constantly immediately "normal boot" it can reboot like 10 times before it will actually work...

Same thing happens with waking from sleep...

Please help! Proper help files attached and will happily try anything you need and haven't already done!
Andreas - McX

A:P5QL-CM Fresh W7x64 BSOD after COLD Wake/Start

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
1-Memtest.





Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.



RAM - Test with Memtest86+

2-Driver verifier






Quote:
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in &q... Read more

Read other 9 answers
RELEVANCY SCORE 54.4

Hi,

I've recently installed windows 7 and have a had a couple of bsod's today. Was browsing at the time, and the pc just froze the first time and I got no bsod so had to hold the power button to reboot. Then after rebooting a few minutes later I got the 1st bsod and then the 2nd. I've attached ur diagnostic tool dump below.

Any help would be appreciated.

Many thanks

A:BSOD - stop 0x1A & 0x101

Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b3180, 4}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------
Follow this guide: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Read other 6 answers
RELEVANCY SCORE 54.4

Hello,

I have a computer that gets a BSOD. It appears to be random. The only thing that I can think of that we did different at the time this started happening was plug in and install a Western Digital external hard drive. I have uploaded the dump files and system information for you to view.

Thank you,

Joshua Davis

A:BSOD, random, error 0x1A

Welcome to the forum acog,

I've checked 3 of your dumps generally and the bugchecks are the same in each of them.

BugCheck 1A, {41790, fffffa80067fb6c0, ffff, 0} MEMORY_MANAGEMENT (1a)

Please carry out the steps below:

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.Startup Programs - Change

OR

Perform a clean boot:Troubleshoot Application Conflicts by Performing a Clean Startup
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow
Full tutorial here:SFC /SCANNOW Command - System File Checker
Then take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.RAM - Test with Memtest86+





Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard s... Read more

Read other 1 answers
RELEVANCY SCORE 54.4

Recently started getting these messages. I've ran memtest 86 for over 12+ hours with 9 passes and 0 errors multiple times.

A:BSOD Errors 0x4e & 0x1a

Please follow http://www.sevenforums.com/crashes-d...tructions.html so we can help you further.

-Justin

Read other 3 answers
RELEVANCY SCORE 54.4

Hi! My computer's been randomly bluescreening for a long time now and it's exhausting, i'm almost to the point of getting a new computer. It happens out of the blue, sometimes while playing world of warcraft, sometimes while cruising the internet, it doesnt necessarily happen while running any one program.

On Mon 10/29/2012 3:35:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-33852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFFA8056D900C8, 0x0, 0xFFFFF80002D9ADEC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 10/29/2012 3:35:56 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFA8056D900C8, 0x0, 0xFFFFF80002D9ADEC, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a t... Read more

A:BSOD while doing various tasks, error 0x1A

http://www.sevenforums.com/crashes-d...tructions.html

Read other 4 answers
RELEVANCY SCORE 54.4

We're a bit stumped on a customer's PC that was brought in for random BSODs. They claimed it would happen every 10 minutes no matter what they were running, but we had the hardest time reproducing it until recently. It can bluescreen during Prime95, running COD, or even just on idle. We've tried each RAM stick individually, swapping RAM slots, running MemTest for a day with no errors, and tested the hard drive with Seagate SeaTools. I've updated all drivers for the motherboard that seemed to do with USB 3.0, chipset, or any other Intel drivers. Monitored the CPU and never see it go to an overtemp.
 
Attached are the requested zip files.
 
Windows 10 x64 - not sure what previous OS was, it was upgraded
Probably retail version since it is a custom build
Guessing only a few years old
 
Intel Core i5 6570K (Ivy Bridge)
MSI Radeon HD7900
ASRock Z77 Extreme6
Corsair TX750 PSU
 
OS Install from systeminfo: 12/19/15 (don't know if that reports the Windows 10 upgrade date or original install)
 
Custom build desktop.
 
I'm suspecting USB ports/drivers, we've tried swapping devices around and had less BSODs when nothing is plugged into the USB 3.0 ports, but I'd like confirmation to make sure we're not fighting the wrong cause. I'm out of RAM to try swapping at the moment, so it may be a few days to get stock before I can try that.
 
I've started DriverVerifier, and it didn't crash on boot. It did BSOD after sitting for awhile, but it was the same 0x1A... Read more

Read other answers
RELEVANCY SCORE 54.4

Hi,
i have been getting BSOD lately and not sure what has caused them
normally i can google it and work out the problem but havent been able to fix this
so thinking it could be hardware as i cant recall installing anything lately (not saying i havent though)

i also received a 0x7E? i think

also i was having an issue where it wasnt saving the dmp files so had to change the directory for it to work

Cheers

A:BSOD - Random 0x0A, 0x1A

Hello and welcome Bert some system specs would be good mate System Info - See Your System Specs

If you haven't already try these

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< DO NOT runon a SSD

http://www.superantispyware.com/

http://www.malwarebytes.org/products/malwarebytes_free/

http://www.bleepingcomputer.com/download/adwcleaner/

download from bleeping computer ? delete any rubbish these find.

Read other 9 answers
RELEVANCY SCORE 54.4

Installed memory upgrade in my Toshiba Qosmio x505 Q887 laptop. Upgraded with compatible memory from 4g to 8g ram.

Experiencing repeated BSOD on boot now.

Downloaded SF Diagnostic Tool as instructed

WhoCrashed report included:

Attachment 259652

A:Repeated BSOD on boot 0x1A

Please upload the required files, using these instructions:Blue Screen of Death (BSOD) Posting Instructions

Read other 3 answers
RELEVANCY SCORE 54.4

Hey, New computer, reinstalled windows twice but still getting these BSOD's:
0x1E, 0x3B, 0x1A

Not sure what to do, or what information you need.

CPU: AMD FX-6300
Mobo: 970 Pro3 R2.0
RAM: 8GB (2x4GB)
GPU: 2GB AMD Radeon R9 270
PSU: Antec Neo Eco 520C Bronze
Win 7 64 is installed on a 1tb HDD
(ALL NEW HARDWARE)

Ran memtest once with no errors

Thanks for your help.

A:New PC, BSOD 0x1E, 0x3B, 0x1A

Win 7 is installed on a 1tb HDD, (also new)

Read other 1 answers
RELEVANCY SCORE 54.4

Hello, i'm new to the forums! Anyways, I had this BSOD just recently. The blue screen usually occurs randomly after a cold boot. It sometimes BSOD on the first restart boot. On the second restart boot, the computer runs fine with no BSOD.
(Here are my computer specs)

Intel i7 950 3.06 (OC to 4.2)
Radeon 6870 Crossfire (XFX + Sapphire)
G Skill Sniper Series 1600 8GB
1TB + 500GB
Rosewill 1000W PSU

As for the overclocking, the over is stable and ran prime 95 with no issues and temperatures below 75C. I've been running my overclock for more than 2 months with no problems what-so-ever. The very first type of BSOD that happened was a video driver issue (ATIKMPAG.SYS) which I believe I managed to fix. Then after that, the memory management BSOD occurred. I re-installed my memory cards into the socket with no luck.

Also, another problem arose, all my dump files are not being recorded like they should. I have been getting BSOD around the 20ish area of December 2011 but the dump files latest record was on December 8th. Any chance for help? I'll post my dump files into here and a look at my overclock BIOS setting which may have something to do with it. Thank you so much for your help!

A:BSOD memory management 0x1A

Correct me if I'm wrong but 1600mhz ram is already OC, and if you OC it more its higher right? Its also possible your ram is dying. It happens. Test with memtest86+ for 5 tests or more. Thats how I rooted out my ram being an issue. It went about 6 hours without 1 error of constant test.

Read other 4 answers
RELEVANCY SCORE 53.6

Hi
I built this PC for a friend of mine nearly 12 months ago. Since then it has suffered random BSOD's at her place and which I cannot reproduce at my place.
The BSOD message is usually
Module: ntkrnlpa.exe (nt + 0x8E3BF)
Bug check code: 0x1A (0x41287, 0x83, 0x0,0x0)
Error: Memory Management

I have swapped the single ram stick from dimm1 to dimm2, ran memtest for 9 error free passes, installed all updates from Windows download, error checked the HDD, scanned the HDD with Avira anti virus, malwarebytes, spybot, microsoft online security scanner and TDSS killer. All were clean. I have run driver verifier for days with no BSOD, stress tested the cpu and monitored its tempretures all to no avail. I have researched the bcc code and parameter 1 but found nothing definitive.

O.S.: Windows 7 x86 sp1
Clean Install
Retail version
Approx. 12 months (both hardware & O.S.)
Original Install still

CPU: Intel I3 2100
Video Card: Onboard Intel
Motherboard: ECS H67H2-M3
Ram: single stick 4Gb DDR3 1333
Power Supply: PI 550W (2006) note: M/B has a 24 pin ATX connecter but PSU only has a 20 pin connector.
System Manufacturer: Generic

As you will see in the mini dumps there is a gap of approx 3 months between BSOD (march to june) where she was away on holidays.

Im stumped...heres hoping you can point me in the right direction
Many thanks for your time and efforts

A:Random BSOD (0x1a Memory Management)

Obviously memory management. You seem to have done a lot of work. ALl We can say at this point is that you have 2 loading malware apps (never a good idea), and Apple daemon (known to cause bsods but not memory management usually) and Incredimail shows up as the active thread in most of these.

I would remove both malware apps, replace with Microsoft Security Essentials, take the Apple daemon out of start up, and use something other than Indredimail AT LEAST TO TEST.

Read other 2 answers
RELEVANCY SCORE 53.6

I've experiencing the Blue Screen of Death errors recently
I followed the posting steps and attached the .zip files on this thread
All help will be appreciated

A:What's causing this BSOD (0x50, 0x1a, 0x7f)?

Hello, Welcome to SF!


Code:
Probably caused by :memory_corruption ( nt!MiAgeWorkingSet+1d1 )
BugCheck 50, {fffff6837f7e0df8, 0, fffff80002c7e55b, 5}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
BugCheck 50 can actually be caused by quite a lot of things. Memory, device drivers, corrupt installs, and anti-virus.

After looking at the MSINFO32 file, I found this line:

Code:
Security Processor Loader Driver ROOT\LEGACY_SPLDR\0000 This device is not present, is not working properly, or does not have all its drivers installed.
This basically means that the anti-virus you currently have is corrupt. From the looks of it, you are just using Windows Defender:

Code:
msmpeng.exe c:\program files\microsoft security client\msmpeng.exe
I suggest disabling it(you can follow this tutorial: Windows Defender - Turn On or Off), as it also has some application errors, and just installing Download Microsoft Security Essentials from Official Microsoft Download Center

This is weird to me because I have never seen a problem with Windows Defender before, but that does not mean it isn't possible.

And to be on the safe side, lets run a RAM - Test with Memtest86+


   Tip
Run Memtest86 for a minimum of 8 passes
Post back results.
-Justin

Read other 9 answers
RELEVANCY SCORE 53.6

Hi All,

I built this new Win7 Pro x64 system a month ago, and have been having multiple BSODs every day. It usually happens when I'm downloading files, or using newsgroups. I'm pretty technically savvy, and here's what I've tried so far:
Updating BIOS
Different versions of drivers (mfr website vs MS Update)
Moving HDDs to different SATA ports
Ran MemTest86+ for 18 hours

I can sometimes run for 8 hours without one, other times it happens within half an hour of booting. The BSODs are usually MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL, which makes me hope that it might be a driver issue or something besides the RAM/Motherboard.

Any help would be greatly appreciated!

A:BSOD Transferring Files, 0x1A and 0x0A

Problem Devices:
Code:
Universal Serial Bus (USB) Controller PCI\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\4&18803EC9&0&00E4 The drivers for this device are not installed.
Universal Serial Bus (USB) Controller PCI\VEN_1B6F&DEV_7023&SUBSYS_50071458&REV_01\4&1B0D22A2&0&00E5 The drivers for this device are not installed.
These are important to have installed, so please fill out your system specs so we may help find them. Use System Info - See Your System Specs to fill out your specs.

Is this the support site for your board: GIGABYTE - Motherboard - Socket 1155 - GA-P67X-UD3-B3 (rev. 1.0) ?

Make sure your Chipset and USB 3.0 drivers are installed from that site.
Security Software (this is just to make sure it is installed and working properly; nothing needs to be done with this information at this time):
Code:
msmpeng.exe c:\program files\microsoft security client\antimalware\msmpeng.exe 844 8 200 1380 15/04/2012 7:01 PM 3.0.8402.0 12.48 KB (12,784 bytes) 27/04/2011 5:21 PM
nissrv.exe c:\program files\microsoft security client\antimalware\nissrv.exe 864 8 200 1380 15/04/2012 7:01 PM 3.0.8402.0 281.52 KB (288,272 bytes) 27/04/2011 5:21 PM
msseces.exe c:\program files\microsoft security client\msseces.exe 2432 8 200 1380 15/04/2012 7:05 PM 2.1.1116.0 1.37 MB (1,436,736 bytes) 15/06/2011 2:35 PM
sbiectrl.exe c:\program files\sandboxie\sbiectrl.exe 2032 8 200 1380 15/04/2012 7:05 PM 3.68.0.0 653.27 KB (668,944 bytes) 10/04/... Read more

Read other 1 answers
RELEVANCY SCORE 53.6

(IN THE TITLE I ACCIDENTALLY PUT 0X1A TWICE!! I MEANT 0X1A AND 0X1E )

Lately I have been getting tons of blue screens and it is making me want to smash my computer. This is the second time trying to post this because I got a blue screen while typing this up the first time. I got the error MEMORY_MANAGEMENT stop 0x0000001A 2 times today. ONe was while installing the new amd graphics driver (14.4 I think) and the other was when I was starting up a game.

Then, when I was posting about getting stop 0x0000001A I got another bluescreen on 0x0000001E!!!!

I don't know if this is a coincidence or not, but I got these blue screens after downloading the latest amd driver.


Pc specs on profile if needed and I am not overclocking.

A:BSOD error, STOP 0x0000001A and 0x1A

Thanks for uploading the minidump files, but please follow the Blue Screen of Death (BSOD) Posting Instructions so we can get the rest of the files we need to find a solution to this.

-Gamer

Read other 8 answers
RELEVANCY SCORE 53.6

So we hashed out an issue with my G19 keyboard causing 0xC1 and other BSOD's (0xC1 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION on new build) last week and the week before... Thank you Golden! I now have a new issue...

I am now receiving seemingly random 0x1A Memory Management BSOD's starting on 1/11/2015 (Everything before 1/11 is most likely linked to the keyboard). One started seemed to start on video playback on a website, the others seemed random.

Troubleshooting I have run both Win 7 Memory Diagnostic (Full Check) and Memtestx86+ (12 Hours and 10 Passes) and both came back clean.

Any ideas?

A:Random BSOD Memory Management - 0x1A

Follow:
1. Log in as administrator, open Windows Explorer and go to C:\Windows\Minidump
2. Delete all .dmp files in that folder
3. Run Driver Verifier as follows:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal, re-run the DM Log Collector, and upload the new ZIP file here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

Read other 4 answers
RELEVANCY SCORE 53.6

I seem to be getting this intermittent BSOD and the errors all seem to be different. I have tested my RAM for a duration of 10 passes with memtest86 and it had no problems. I was wondering if it is a dodgy motherboard and was going to see what you guys thought?

My Spec is:

Win7 x64 Ultimate SP1
2500K CPU
Z68 Gigabyte UD3P F8 Bios
Auzentech Forte Sound Card
SSD Sata 3 64Gb HDD
3x2TB Sata 3 HDD
GTX580 video card
Here is the report and mini dmp folder:

Thanks!

A:BSOD playing games, error 0x1A

not on a machine with a debugger right now, but 1a is a memory management error.
either a bad driver, or bad memory.

Read other 5 answers
RELEVANCY SCORE 53.6

Hey, New computer, reinstalled windows twice but still getting these BSOD's:
0x1E, 0x3B, 0x1A, 0xFE

Not sure what to do, or what information you need.

CPU: AMD FX-6300
Mobo: 970 Pro3 R2.0
RAM: 8GB (2x4GB)
GPU: 2GB AMD Radeon R9 270
PSU: Antec Neo Eco 520C Bronze
Win 7 64 is installed on a 1tb HDD
(ALL NEW HARDWARE)

Ran mem test once with no errors

Thanks for your help.

A:New PC, BSOD 0x1E, 0x3B, 0x1A, 0xFE

As there are various different bugchecks, the first thing you need to do is to test your RAM modules for possible errors. How to Test and Diagnose RAM Issues with Memtest86+
Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. A camera snap before exiting memtest86+ would be nice.

Read other 1 answers
RELEVANCY SCORE 53.6

Good Morning Guys,

i have a Problem with a Windows 7 32 Bit Sysem. Since 6. Mai 2014 i Receive varius BSODs.
I attached some of them. I think that could be a RAM Issue, because i found a lot of memory corruptions.
The Dump Files are in the attached ZIP File.

Maybe we found a solution?

The Machine is a Thinkpad T540
Windows 7 32 Bit, Latest SP and Hotfix.

Cheers
Heiko

A:Varius BSOD 0x1a, NTFS_FILE_SYSTEM (24) IRQL_NOT_LESS_OR_EQUAL (a)

Hi HeikoW.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

Read other 1 answers
RELEVANCY SCORE 53.6

Acer Aspire M3910, Intel(R) Core(TM) i3 CPU, [email protected] 3.20GHz, 3.00GB RAM, 64-Bit Operating System, WIN 7. The original installed OS on the system, OEM.

I think I've had this comp about 2 years, I reinstalled the OS about 6 months ago.

The last few days my computer has been BSODing during game play. I'm unable to catch all the error codes as they were either too fast or the BSOD screen didn't happen and the comp just crashed. Thank you for reading.

A:BSOD randomly while gaming, error 0x1A

These were related to your Kaspersky. I would remove and replace with MSE

Kaspersky is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST.

http://support.kaspersky.com/downloa...vremover10.zip

Microsoft Security Essentials - Free Antivirus for Windows
Old drivers needing updating

Code:
jswpslwfx.sys 5/15/2008 6:28:50 AM fffff880`01bec000 fffff880`01bf9000 0x0000d000 0x482c1062
xusb21.sys 4/8/2009 10:28:44 AM fffff880`08382000 fffff880`08392d80 0x00010d80 0x49dcb49c
spsys.sys 5/11/2009 1:20:58 PM fffff880`06d29000 fffff880`06d9a000 0x00071000 0x4a085e7a
GEARAspiWDM.sys 5/18/2009 8:17:04 AM fffff880`079a4000 fffff880`079b1000 0x0000d000 0x4a1151c0
mwlPSDFilter.sys 6/2/2009 6:07:30 AM fffff880`04b00000 fffff880`04b09000 0x00009000 0x4a24f9e2
mwlPSDNServ.sys 6/2/2009 6:07:39 AM fffff880`017f0000 fffff880`017f8000 0x00008000 0x4a24f9eb
mwlPSDVDisk.sys 6/2/2009 6:15:29 AM fffff880`01400000 fffff880`01413000 0x00013000 0x4a24fbc1
How To Find Drivers:




Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
... Read more

Read other 9 answers
RELEVANCY SCORE 53.6

Hello Again,
Still getting blue screens and massive program crashing and errors, going from indexing to not even able to open the program.
BSOD's 0x1a, 0x107e 0x24
Today (aug 22) I swapped out the video card which had been considered the cause of the problem failing all stress tests and in fact not even allowing a new drive to get the drivers installed.

Have swapped Video
Have scanned HDD's via Chksk and Seatools 1.2.0.5 (since the current version has a JIT error and wont run)
Have scanned memory with the windows memory tool

Cannot scan via seatools for DOS or spinwrite because the drive is larger than 650gigs (size 2tb)
Cannot scan via memcheck because again amount of ram is too larg (32 gigs)

All except the previous video card passed clean with no problems. I have included the dump files

Any help appreciated.

A:BSOD's still rampant 0x1a 0x107e 0x24

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the syteminfo.txt file. If you have difficulties with making this work, please post back. Then zip up the .txt file and upload/attach the .zip file with your next post.

Read other 9 answers
RELEVANCY SCORE 53.6

Hello,

Link to my previous thread: BSoD during gaming, 0xd1

I do not really know what to do. I am getting bluescreens every 2-3 hours now. I had a problem 2 weeks ago which was fixed by a driver reinstall. (I do not think this one is connected to that)
I want to do a clean Windows install, but I do not have anything to save my files to, so I'd rather see if this can be fixed without formating my hard drive.

I will run memtest, prime95, heaven and chkdsk starting now. Will post results.
Malwarebytes have not found any malware.

Error codes: 0x50, 0xa, 0x1000007e, 0x1a, 0x4e, 0x9c, 0x3b, 0x124
Caused by: Ntfs.sys, ntoskrnl.exe, usbaudio.sys, dump_dumpfve.sys, HWiNFO64A.sys, hal.dll, nvlddmkm.sys
Happening during: internet browsing, PC shutdown
Additional notes: Internet browsers are crashing frequently (Chrome and Firefox). Sometimes only shockwave is crashing on Chrome.

After my last BSOD (0x50, ntfs.sys) I seem to have lost some user settings:
Programs like Skype, ObjectDock reverted to default 'factory' settings.

Thanks for the help in advance. Any help is appreciated.

A:Frequent BSOD, without pattern, 0x50, 0xa, 0x1a and many more

Hi minimalis91

Lets start with this to see what is going on with your PC .

Click here DDS

Click on Download Now button

Right-click the DDS icon choose Run as administrator to run the tool.

Place a check next to attact.txt and click Start . When done, DDS will open two logs
DDS.txt
Attach.txt

Save two logs onto your desktop and upload them with your reply

Read other 7 answers
RELEVANCY SCORE 53.2

Over the past couple of weeks my computer has suffered many BSOD of errors. I will be working and out of the blue I will see one. I have ran tests on my memory and my hard drives but did not find any errors. I think it could be a driver but all of mine are up to date! Any help would be greatly appreciated. Thanks and have a nice day! Here is everything that WhoCrashed has told me.... Also attached is the DM Log.

System Information (local)
--------------------------------------------------------------------------------

computer name: GRAYSON-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: MS-7850, MSI, B85-G41 PC Mate(MS-7850)
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8514437120 total


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/22/2015 3:48:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012215-5444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x76E80)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF80002A85161)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description... Read more

A:Multiple BSOD Errors 0x19, 0x1A, 0x3B,

Please update your system specs in the 'My System Specs' in the bottom left of your last post. That way it will be available with every post and we don't have to hunt for it. Also, please be as detailed as possible as we many times have to look up a component and need Manufacturer and model number sometimes. Please include your PSU and CPU cooler as well. This is what I usually post. Maybe something in it will make it easy for you. Thanks.
Please fill out your System Specs


   Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

Read other 9 answers
RELEVANCY SCORE 53.2

I have been facing this problem ever since I first assembled my pc. I am not an expert but I don't think I have messed my hardware. The PC is 10 days old.
I am not sure but maybe there is some sort of incompatibility with my hardware and Win7.
I am currently running Win7 Ultimate x64. My pc spec are as follow:
MoBo: GA-X58A-UD5 (Link)
CPU: Intel i7 970 (Link)
RAM: G.Skill 8GB (2x4GB) (Link)
GPU: Nvidia GTX 580 (Link)
PSU: Corsair TX950 (Link)
SSD: Crucial C300 128GB (Link)
HDD: WD Caviar Black 1TB (Link)
Optical Drive: LG Blu-ray (Link)

As for my Win7 installations, I did about 3 clean installations on my SSD. Last one was yesterday.
I really need to know if I am having incompatibilities with my hardware or am I facing driver errors.
I attached the log of my BSODs, the last three happened while I was trying to install Win7 SP1.
I will try a CHKDSK

A:BSOD on newly built PC (0x24, 0x7E, 0x1A)

Well they are file system errors.
Have you looked for new firmware for you ssd?
Crucial.com Product Downloads - Firmware Updates
it's apparently at version 6 now.


Code:
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x24

PROCESS_NAME: des2svr.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff880070bb930 -- (.trap 0xfffff880070bb930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800c673250 rbx=0000000000000000 rcx=0000000002831000
rdx=0000000002830000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000338edf2 rsp=fffff880070bbac0 rbp=fffff880070bbca0
r8=fffffa800d0a9b10 r9=0000000000000155 r10=fffffa800673cc90
r11=000000000012019f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!NtReadFile+0x142:
fffff800`0338edf2 0fb602 movzx eax,byte ptr [rdx] ds:0001:00000000`02830000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff88001210e95 to fffff80003073740

STACK_TEXT:
fffff880`070bb3c8 fffff880`... Read more

Read other 9 answers
RELEVANCY SCORE 52.4

Gents,

Running into a few problems with my new computer build (details in profile) and would appreciate it if someone could point me in the right direction.

Quickly, its a new build and a fresh Windows 10 x64 install.

I have ran memtest86 for about 6 hours without any errors yet, I plan to let it run for atleast 12 hours next round.
I have taken out my graphics card (Strix 970) and still get blue screens.
It seems to happen no matter if i'm idle or stressing the system with Prime95.
I'm also running Driver Versifier without a BSOD yet.

Can anyone tell from my dump file if it seems to be a driver or hardware issue?
I have a limited amount of time to RMA stuff!

Edit: I spoke too soon, still getting multiple BSOD.
I had to restore my system so I lost some of the dump files but i'll post the most recent before my computer crashes again.

Thanks.

A:BSOD Memory Management 0x1a New Build, Fresh OS Install

Has any crash occured more then 1 time?
If not, then it isn't something to worry about. Windows fixes crashes that occurs 1 time

Read other 0 answers
RELEVANCY SCORE 52.4

I have been getting the 0x1A and 0x1E BSODS for some time now and i have decided to do something about it. I noticed that this happens when i exit a game or whilst playing it(when stressing the ram/pc). If i play a non-demanding game no BSODs happen, i tried memtest but it froze on test 13 the last time i used it. Also Driver Verifier doesn't seem to find any problems when i run it. i uploaded the Minidumps for 0x1A and 0x1E. Any help is appreciated! uploaded that specs thingy as well.

A:BSOD Playing or Exiting Demanding Games 0x1A 0x1E

Hello, Soteris1234 and welcome to the forums. I will try to help. I looked at your last 4 or 5 dump files.


Code:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000130803001
Arg3: 00000000000e6db4
Arg4: fffff70001080000

Code:
BugCheck A, {fffff87fd45d5a41, 2, 1, fffff80002020d50}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption

Code:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002cdf10e, Address of the instruction which caused the bugcheck
Arg3: fffff8800ed177e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Code:
BugCheck 1E, {ffffffffc0000005, fffff80002c8e530, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4845d )
Followup: MachineOwner
Please uninstall Dameon Tools. It is a known cause of BSODs this will help you.

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause of BSOD's.





1. Uninstall Daemon Tools.


2. Download the SPTD standalone installer and follow these st... Read more

Read other 7 answers
RELEVANCY SCORE 52.4

PC specs:
i5-2400 @ 3.10ghz
4gb corsair vengeance ram
1gb nvidia gtx 550ti
2tb seagate baracuda @ 7200rpm

BSOD\s are totally random, can happen anytime from listening to music or just browsing the internet.
Most of the time it is 0x1a but sometimes it is also 0x01.
It will be great if someone can read the minidumps and give more info as I dont know how to read the minidumps.
Thanks.

A:BSOD 0x1A when browsing internet or randomly [minidumps included]

It appears that this install of Windows is counterfeit, your product ID matches an Asus key while the motherboard is an intel board, this is only possible through a hackers exploit, please purchase a legal copy of windows, format, and re-install with the new legal copy of windows.

Read other 1 answers
RELEVANCY SCORE 52.4

Attachment 345181
Started with no reason.. week before i updated graphics card driver. When i ran Memtest86, its shows lots of errors. Is it RAM false and why it started? Thanks to all before!

A:Lots off BSOD like 0x3b,0x24,0x1a,0X7e,0x50 etc

  
Quote: Originally Posted by Murmulis8


Attachment 345181
Started with no reason.. week before i updated graphics card driver. When i ran Memtest86, its shows lots of errors. Is it RAM false and why it started? Thanks to all before!


Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
testSlot1Slot2RAM1ErrorErrorRAM2GoodGoodIt is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2RAM1ErrorGoodRAM2ErrorGoodIt is a motherboard issue. The particular slot is bad.

Why it started? Hardware fails, like anything else.

Read other 4 answers
RELEVANCY SCORE 52.4

Heya,

As the title states: I get BSOD when i'm doing anything with LoL, I have reinstalled a clean OS, and downloaded/installed the game. After that I finished installing the drivers and now LoL cant seem to play a game, it will run but I will BSOD as soon as the game starts.

I have uninstalled many drivers that I installed at start except three: 2 GPU drivers, and one intel chipset one. The rest I have uninstalled through device manager, and unfortunately I still BSOD in-game.

I have done checkdisk twice, came out clean, did a memory test with the windows application also came out clean.

The BSOD unfortunately starts only when downloading anything from the game or playing a game.
I would be really grateful if someone could help me out with this, its becoming really bothersome and I am planning on reinstalling the OS again if it continues like this.

A:BSOD League Of Legends, Memory management error 0X1a

Hello asif343.

Your issue is the display drivers here ... both of them are failing.

Intel HD Graphics driver ...

Code:
fffff880`07f47c68 fffff880`04ba9737Unable to load image igdkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
igdkmd64+0xef737
Nvidia display driver .....

Code:
fffff880`07f47a68 fffff880`0595fae5Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0xb4ae5
At this point, I would suggest you to first try a clean reinstall. Clean Reinstall - Factory OEM Windows 7 .

Suggesting it, coz the pre-installed laptops with dual graphics uses some complicated settings for display usage, which itself may cause those errors.

While installing the display driver, perform a clean install only.

Let us know the results when done.

Read other 9 answers
RELEVANCY SCORE 52.4

Hi Win7 Forum!

My girlfriend has been having problems with her newly bought (previously used though) computer. She's gotten two BSOD while playing Aion. Both of them occurring after only a couple of minutes of gaming. Minidump also shows two other BSOD registered (first two) that she hasn't noticed.

I've uploaded the files from SF Debug Tool.
I'd be truly grateful if you guys could help me help her!

A:BSOD playing Aion, error 0x50, 0x3b and 0x1a

Welcome to the Forum.

Please carry out the steps below:

AVG contributes to BSOD's.

Code:
Start Menu\Programs\AVG Public:Start Menu\Programs\AVG Public





Quote:
Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.


Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Install all updates including service pack 1: Learn how to install Windows 7 Service Pack 1 (SP1)

Run Disk Check on your Hard Drive(s): Disk Check

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums


Code:
AODDriver2.sys Thu Sep 12 09:36:40 2013 (523136C8)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys





Quote:
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.



... Read more

Read other 1 answers
RELEVANCY SCORE 52

I downloaded the legit Windows 7 x64 Iso without an activation to test the build before my OS order arrives. I have been getting multiple BSODs including MEMORY_MANAGEMENT, DRIVER_VERIFIER_DETECTED_VIOLATION, and PFN_LIST_CORRUPT. I have installed windows multiple times with similar problems. I also switched the HDD with another to rule out a bad HDD and got the same problems.

Also: Memtested 7 passes so I don't think its the memory itself that is the problem. I did read from another thread it could be voltage issues between the RAM and motherboard. I also could not finish installing the Nvidia driver due to the Driver_verifier BSOD. All other drivers are updated from the manufacturer website.

I have encountered the BSOD randomly while installing programs but most often with the windows installer and windows update.

I am running out of ideas and have narrowed it down to voltage issues (can't think of anything else) but I am unsure as how to fix it, so any help is greatly appreciated.

BTW: no antivirus yet, or any installed programs besides CPUZ, 9,9,9,24, 1600 for RAM

A:0x1a, 0xc4, 0x4e BSOD on custom build, possible ram voltage problem

Hello BSOD4EVER.

Follow the Option Two: To Disable Driver Verier of the tutorial
Driver Verifier - Enable and Disable

Let us know if it is BSODing anymore or not.

If BSODs are continuing there, post it following the Blue Screen of Death (BSOD) Posting Instructions.

Read other 9 answers
RELEVANCY SCORE 52

Recently I have been getting BSODs on my computer. Most of them are from startup where they point their fingers at ntoskrnl.exe

Today, one interrupted me in the middle of League of Legends, pointing at clfs.sys

I've attached the the stuff the sticky page told me to, containing 4 dump files.

Attachment 312246

A:BSOD playing video games, startup occasionally Error 0x1a

Where did you get your copy of windows from?
Do you know how it was activated?

Read other 4 answers
RELEVANCY SCORE 51.6

Hi SF dudes

Just seeking some help with a bsod problem, iv followed the SF bsod posting guide and have collected the dump files(attached), if iv missed something please let me know.

Buils as follows:

CPU: AMD FX 8150 8-core (stock not OC)
Mobo: ASUS Sabertooth 990fx (latest firmware flashed, shows all system correctly)
RAM: Corair Vengence 1600mhz (cmz16gx3m4a1600c9)16gb 4x4gb
GPU: Gigabyte GF GTX670 OC 2gb (as factory, not OC)
PSU: Antec HCG 900w (SLi down the track)
SSD: OCZ vertex 3 240gb
Hdd-1: WD Green 2TB (WD20EARX)
Hdd-2: Old Hitachie 300gb 2.5inch (as per cutomer request)
ODD: LG BD-DVDRW combo (CH12LS28)
WiFi adpt: TP-Link Wireless N pci-e(TL-WN881ND)
OS: Win7 pro 64bit with SP1 Retail with key(not burnt,DLed or USB)
Aftermarket CPU cooler: Corsair H80

So i went through quite abit of ram testing, each dim and each slot tested with win7 memtest, clear with 10 passes each.
Done all win updates, 3 .net framework updates failed(could be a lead)
Device list shows all driver working, (no(!))
I dont want to rant but there are other details that could help so just ask for the specific info/data/spec and ill post.
I checked out the SF tool files but...
So if a few minidump & debug gurus could jump in here and take a look it would be great.
Thanks in advance and happy computing

Ronyart

A:New Build, Bsod at randow. Stop:0x1a sub:41790 table page corrupted

A few extra details:\

Temp:
CPU: Idel 30-35 Load 42-46
MoBo: Load 36-42
GPU: Load 36-48
Collected using Asus Ai Suit(UptoDate)

All Bsod are Memery_Managment, stop:0x0000001a
with almost all 1st sub codes being 41790-table page corrupted

The GPU driver has me worried, everytime i go into device manager and hit the auto update button for the GPU the screen flickers and jumps but to generic stock resolution and fails to even see the driver, just shows generic driver,to resolve this i must uninstall then reinstall the driver but the same thing still happens with the update button even after the reinstall
Lets Go SF, hit me!

Read other 4 answers
RELEVANCY SCORE 51.6

Hi,

I have a Dell Optiplex 9020 Lab with about 30 computers in there. The computers are running Windows 7 64 bit. There is one computer that has about 5 different types of bluescreens happening over the last few months. I attached a SF Diag Tool Zip. Any help on what could be the problem? I have run a system diagnostic test by Dell and it has passed perfectly.

A:Multiple BSOD 0x0a, 0x1a, 0x4e, 0x50, 0x3b (IRQL, SYS_SERV_EXC, etc)

Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\skywalker89\SF_28-01-2015\012715-14851-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`03017000 PsLoadedModuleList = 0xfffff800`0325a890
Debug session time: Wed Jan 28 01:06:13.285 2015 (UTC + 6:00)
System Uptime: 0 days 0:00:30.081
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* ... Read more

Read other 3 answers
RELEVANCY SCORE 50.8

How can I use Viber on PC if I don't have a smartphone? It keeps asking for my smartphone, and I don't know to log in.
 

Read other answers
RELEVANCY SCORE 49.6

Recently released Viber desktop for PC is rather disappointing with their support info. The system requirements page has no info on the required hard drive space needed. I am currently installing this app on a lenovo G560 running windows 8 pro x86 and so far over 0.5GB has been downloaded and the installation has not even started. Can someone who has this software inform me on how much HDD space is required for download /installation /running of this application?

A:Viber PC system requirements

Doing a search for Viber PC I find what looks like 2 different products

Viber for PC donwload and install Viber PC on windows or Mac
Viber for Windows PC | Viber Desktop

Which one are you referring to?

Read other 10 answers
RELEVANCY SCORE 48.8

My Laptop OS is Windows 7 Starter. I can't install Viber software. Can you guide which viber software is suitable for windows 7 Starter?
Thank you.

A:Viber Software for Windows 7 Starter

Doesn't seem to be computer software, see http://en.wikipedia.org/wiki/Viber .

Win 7 Starter is for netbooks.

Louis

Read other 6 answers
RELEVANCY SCORE 48.8

My parents don't have smartphones and from the "new technology" they're just using a laptop(Win 10). Viber will be very handy, considering that we live in a different countries. Is it possible to install it on a laptop without a smartphone? Bluestacks use to do the trick, but not any more. Any ideas?
 

Read other answers