Quantcast
Viewing all articles
Browse latest Browse all 6058

Help bsod dump file! bluescreen on startup

hi i bought a new pc from cyberpowerpc about a month ago
i get these randoms bluescreens that started about 2 weeks after on start up
it only happens maybe every other day or so on start up

can someone help me understand whats going on in these dump files?
im really new too this
thanks!

PC specs Microsoft(R) Windows 7 Home Premium (64-bit Edition)

CPU: AMD FX-8320 3.50 GHz Eight-Core
IGABYTE GC-WB867D-I 802.11AC Wi-Fi up to 867 Mbps + Bluetooth 4.0 Combo w/ Dual Antenna PCI-E Adapter
128GB SanDisk SSD + 1TB SATA III Hard Drive Combo [+46] (Single Drive)
16GB (8GBx2) DDR3/1866MHz Dual Channel Memory [+100] (ADATA XPG V2)
GIGABYTE 990FXA-UD3 AMD 990 ATX w/ Ultra Durable 3, On/Off Charge, GbLAN, 4 PCIe x16, 2 PCIe x1, 1 PCI [+71]
750 Watts - EVGA SuperNOVA NEX750B 80 Plus Bronze Modular Power Supply [+28]
XFX Double D AMD Radeon R9 280 3GB GDDR5 PCIe 3.0 x16 Video Card (Single Card)





Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*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 Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034a8890
Debug session time: Tue Sep 23 15:56:40.842 2014 (UTC - 7:00)
System Uptime: 0 days 0:00:11.904
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols

Loading unloaded module list
...
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc000001d, fffff88000000101, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for ViaHub3.sys
Probably caused by : ViaHub3.sys ( ViaHub3+14eb7 )

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

1: kd> !analyze -v
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff88000000101, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
+3cbd580
fffff880`00000101 ff ???

BUGCHECK_STR: 0x1E_c000001d

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER: from fffff80003325738 to fffff800032dabc0

FAILED_INSTRUCTION_ADDRESS:
+3cbd580
fffff880`00000101 ff ???

STACK_TEXT:
fffff880`033bce28 fffff800`03325738 : 00000000`0000001e ffffffff`c000001d fffff880`00000101 00000000`00000000 : nt!KeBugCheckEx
fffff880`033bce30 fffff800`032da242 : fffff880`033bd608 fffffa80`103232b0 fffff880`033bd6b0 00000000`00000170 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`033bd4d0 fffff800`032d839f : fffff880`033bd6b0 00000000`00000000 fffffa80`0ce55000 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`033bd6b0 fffff880`00000101 : fffffa80`103232b0 00000000`00000002 00000000`00000002 00000000`00100103 : nt!KiInvalidOpcodeFault+0x11f
fffff880`033bd840 fffffa80`103232b0 : 00000000`00000002 00000000`00000002 00000000`00100103 fffff880`033bd8a8 : 0xfffff880`00000101
fffff880`033bd848 00000000`00000002 : 00000000`00000002 00000000`00100103 fffff880`033bd8a8 0000057f`efcdcff8 : 0xfffffa80`103232b0
fffff880`033bd850 00000000`00000002 : 00000000`00100103 fffff880`033bd8a8 0000057f`efcdcff8 fffff880`033bda50 : 0x2
fffff880`033bd858 00000000`00100103 : fffff880`033bd8a8 0000057f`efcdcff8 fffff880`033bda50 00000000`00000958 : 0x2
fffff880`033bd860 fffff880`033bd8a8 : 0000057f`efcdcff8 fffff880`033bda50 00000000`00000958 0000057f`efcdcff8 : 0x100103
fffff880`033bd868 0000057f`efcdcff8 : fffff880`033bda50 00000000`00000958 0000057f`efcdcff8 fffff880`056e4eb7 : 0xfffff880`033bd8a8
fffff880`033bd870 fffff880`033bda50 : 00000000`00000958 0000057f`efcdcff8 fffff880`056e4eb7 fffffa80`10a0b090 : 0x0000057f`efcdcff8
fffff880`033bd878 00000000`00000958 : 0000057f`efcdcff8 fffff880`056e4eb7 fffffa80`10a0b090 00000000`00000002 : 0xfffff880`033bda50
fffff880`033bd880 0000057f`efcdcff8 : fffff880`056e4eb7 fffffa80`10a0b090 00000000`00000002 00000000`00000170 : 0x958
fffff880`033bd888 fffff880`056e4eb7 : fffffa80`10a0b090 00000000`00000002 00000000`00000170 fffffa80`103232b0 : 0x0000057f`efcdcff8
fffff880`033bd890 fffff880`056e5dbd : fffffa80`103232b0 00000000`00000001 00000000`00000002 fffffa80`10a0b090 : ViaHub3+0x14eb7
fffff880`033bd930 fffff880`056e02b0 : 00000000`00000018 00000000`00000000 00000000`00000000 00000000`00000002 : ViaHub3+0x15dbd
fffff880`033bd9a0 fffff880`056db250 : fffffa80`103232b0 00000000`00000000 fffff880`033bda60 00000000`00000000 : ViaHub3+0x102b0
fffff880`033bda10 fffff880`056dd1fc : fffffa80`10752630 fffffa80`10752603 fffff800`03480201 fffffa80`10752703 : ViaHub3+0xb250
fffff880`033bdaa0 fffff880`00e4b456 : fffffa80`10752630 fffff800`034802d8 00000000`00000000 fffffa80`10752630 : ViaHub3+0xd1fc
fffff880`033bdb10 fffff800`035d1c93 : fffffa80`10324270 00000000`00000000 fffffa80`0ce55040 fffffa80`0ce55040 : Wdf01000!FxWorkItem::WorkItemThunk+0x10a
fffff880`033bdb40 fffff800`032e4261 : fffff800`03480200 fffff800`035d1c01 fffffa80`0ce55000 1206090f`0000055a : nt!IopProcessWorkItem+0x23
fffff880`033bdb70 fffff800`0357673a : ab7e81ab`7c7daa75 fffffa80`0ce55040 00000000`00000080 fffffa80`0ccee840 : nt!ExpWorkerThread+0x111
fffff880`033bdc00 fffff800`032cb8e6 : fffff880`03189180 fffffa80`0ce55040 fffff880`031940c0 94dede94`dede96dc : nt!PspSystemThreadStartup+0x5a
fffff880`033bdc40 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bd540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
ViaHub3+14eb7
fffff880`056e4eb7 8bd8 mov ebx,eax

SYMBOL_STACK_INDEX: e

SYMBOL_NAME: ViaHub3+14eb7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ViaHub3

IMAGE_NAME: ViaHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 520852ca

FAILURE_BUCKET_ID: X64_0x1E_c000001d_BAD_IP_ViaHub3+14eb7

BUCKET_ID: X64_0x1E_c000001d_BAD_IP_ViaHub3+14eb7

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x1e_c000001d_bad_ip_viahub3+14eb7

FAILURE_ID_HASH: {09cf2087-3fa3-fd9a-67c0-cb528370544d}

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

Viewing all articles
Browse latest Browse all 6058

Trending Articles