Overclock.net banner

1 - 17 of 17 Posts

·
Registered
Joined
·
12 Posts
Discussion Starter · #1 ·
Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7600.2.0.0.256.1
Locale ID:1033

Additional information about the problem:
BCCode:1a
BCP1:0000000000041287
BCP2:0000000000000000
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\\121210-21762-01.dmp
C:\\Users\\Thousand Sunny\\AppData\\Local\\Temp\\WER-41699-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
 

·
Registered
Joined
·
1,928 Posts
Could you please upload the .dmp file? I would be more than happy to take a look at it and tell you whats causing the BSOD's.
 
  • Rep+
Reactions: vigor07

·
Registered
Joined
·
1,928 Posts
Any news on that .dmp files?
 
  • Rep+
Reactions: vigor07

·
Registered
Joined
·
12 Posts
Discussion Starter · #12 ·
Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7600.2.0.0.256.1
Locale ID:1033

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

Files that help describe the problem:
C:\\Windows\\Minidump\\121410-17815-01.dmp
C:\\Users\\Thousand Sunny\\AppData\\Local\\Temp\\WER-41948-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
 

·
Registered
Joined
·
12 Posts
Discussion Starter · #13 ·
Problem signature:
Problem Event Name:BlueScreen
OS Version:6.1.7600.2.0.0.256.1
Locale ID:1033

Additional information about the problem:
BCCode:3b
BCP1:00000000C0000005
BCP2:FFFFF8800C0F2817
BCP3:FFFFF8800A3888E0
BCP4:0000000000000000
OS Version:6_1_7600
Service Pack:0_0
Product:256_1

Files that help describe the problem:
C:\\Windows\\Minidump\\121410-26067-01.dmp
C:\\Users\\Thousand Sunny\\AppData\\Local\\Temp\\WER-208323-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?link...8&clcid=0x0409
 

·
Registered
Joined
·
1,928 Posts
Quote:


......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2000, 2, 0, fffff80002a832d2}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000002000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a832d2, address which referenced memory

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

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cae0e0
0000000000002000

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiProcessExpiredTimerList+72
fffff800`02a832d2 803818 cmp byte ptr [rax],18h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff8800398f450 -- (.trap 0xfffff8800398f450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002000 rbx=0000000000000000 rcx=fffffa80054cdc00
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a832d2 rsp=fffff8800398f5e0 rbp=000000000000a9f7
r8=fffff88003969301 r9=0000000000000002 r10=00000000000000f7
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KiProcessExpiredTimerList+0x72:
fffff800`02a832d2 803818 cmp byte ptr [rax],18h ds:00000000`00002000=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a77469 to fffff80002a77f00

STACK_TEXT:
fffff880`0398f308 fffff800`02a77469 : 00000000`0000000a 00000000`00002000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0398f310 fffff800`02a760e0 : 00000000`00000008 fffffa80`054cac10 fffffa80`047bd9e8 00000000`0001094a : nt!KiBugCheckDispatch+0x69
fffff880`0398f450 fffff800`02a832d2 : fffffa80`054cac10 fffffa80`054d9920 fffffa80`054d9920 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0398f5e0 fffff800`02a83e7e : 00000001`94958bf2 fffff880`0398fc58 00000000`0000a9f7 fffff880`0396b468 : nt!KiProcessExpiredTimerList+0x72
fffff880`0398fc30 fffff800`02a83697 : 00000000`7723d5c1 00000000`0000a9f7 00000000`7723d5af 00000000`000000f7 : nt!KiTimerExpiration+0x1be
fffff880`0398fcd0 fffff800`02a806fa : fffff880`03967180 fffff880`039720c0 00000000`00000000 fffff800`02b2f1d0 : nt!KiRetireDpcList+0x277
fffff880`0398fd80 00000000`00000000 : fffff880`03990000 fffff880`0398a000 fffff880`0398fd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiProcessExpiredTimerList+72
fffff800`02a832d2 803818 cmp byte ptr [rax],18h

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!KiProcessExpiredTimerList+72

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+72

BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+72

Followup: MachineOwner


Quote:


************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

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

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
atikmdag+90817
fffff880`0c0f2817 8b4820 mov ecx,dword ptr [rax+20h]

CONTEXT: fffff8800a3888e0 -- (.cxr 0xfffff8800a3888e0)
rax=0000000000000000 rbx=fffffa8006dde110 rcx=fffffa8004168870
rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8003eb0240
rip=fffff8800c0f2817 rsp=fffff8800a3892c0 rbp=fffffa8004168870
r8=0000000000000015 r9=fffff8800c4b4970 r10=0000000000000000
r11=fffff8800a389410 r12=0000000000000000 r13=fffffa8006287860
r14=0000000000000001 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0x90817:
fffff880`0c0f2817 8b4820 mov ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800c0f2817

STACK_TEXT:
fffff880`0a3892c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x90817

FOLLOWUP_IP:
atikmdag+90817
fffff880`0c0f2817 8b4820 mov ecx,dword ptr [rax+20h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: atikmdag+90817

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4cef1f94

STACK_COMMAND: .cxr 0xfffff8800a3888e0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_atikmdag+90817

BUCKET_ID: X64_0x3B_atikmdag+90817

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

Both .dmp files stem from, what looks like a driver issue. The most common culprit of this is sound card and video card drivers.

Try uninstalling your video card driver using the following method and than reinstalling it.

-Uninstall using control panel
-Reboot
-Run "Driver Sweeper" to remove all remaining Registry entries
-Reboot
-Re-install video driver
-Reboot

Let me know if that helps out your BSOD issues.
 
  • Rep+
Reactions: vigor07
1 - 17 of 17 Posts
Top