Solved BSOD when playing games

[hurdygurdy]

Hi

I have past problems with this pc and never really got to the bottom of it. I have now just started playing SWTOR online and these blue screens are becoming very annoying.

Please could someone point me in the right dirrection in terms of clearing these up.

I have just tried a Windows 7 home Premium x64 re-install to see if that would help but i have had no luck with 3 blue screens in about 2 hours.

 

[writhziden]

[list=1]
[*]
Loading Dump File [H:\BSODDmpFiles\hurdygurdy\Windows_NT6_BSOD_jcgriff2\012512-16910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0325d000 PsLoadedModuleList = 0xfffff800`034a2670
Debug session time: Wed Jan 25 15:37:00.908 2012 (UTC - 7:00)
System Uptime: 0 days 0:10:19.891
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 0, fffff800032e55dc}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessTimerDpcTable+4c )

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

2: 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: 0000000000000004, 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: fffff800032e55dc, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350c100
 0000000000000004 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`032e55dc 458b4d04        mov     r9d,dword ptr [r13+4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  swtor.exe

TRAP_FRAME:  fffff88003393590 -- (.trap 0xfffff88003393590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=fffff88003364180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032e55dc rsp=fffff88003393720 rbp=0000000000000000
 r8=fffff880033937b0  r9=0000000003364180 r10=fffff8000325d000
r11=fffff88003393760 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessTimerDpcTable+0x4c:
fffff800`032e55dc 458b4d04        mov     r9d,dword ptr [r13+4] ds:00000000`00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d91e9 to fffff800032d9c40

STACK_TEXT:  
fffff880`03393448 fffff800`032d91e9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03393450 fffff800`032d7e60 : fffff880`03364180 00000000`00000000 00000000`00000000 fffff880`033937b0 : nt!KiBugCheckDispatch+0x69
fffff880`03393590 fffff800`032e55dc : 00000000`00000004 00000000`000000ff fffffa80`097cf600 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03393720 fffff800`032e5496 : fffffa80`0aa5ac68 fffffa80`0aa5ac68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x4c
fffff880`03393790 fffff800`0336e646 : 00000000`003c6c2d 00000000`00000000 fffff800`03476cc0 fffff800`032ddca6 : nt!KiProcessExpiredTimerList+0xc6
fffff880`03393de0 fffff800`03375f24 : fffffa80`079d01b0 00000006`000000ff 00000004`00000007 fffff880`031d9f68 : nt!PpmQueryTime+0x16
fffff880`03393e10 fffff800`032e537e : 00000001`717bfc7f fffff880`03393e88 00000000`00009b38 fffff880`03366c88 : nt!PpmSnapIdleAccumulation+0x94
fffff880`03393e60 fffff800`032e5167 : fffff880`033641c8 fffff880`00009b38 00000000`00000001 00000000`00000038 : nt!KiTimerExpiration+0x1be
fffff880`03393f00 fffff800`032dc765 : 4cc44cc4`a1a7a1a7 fffffa80`09b76760 00000000`00000000 fffff800`033f4b40 : nt!KiRetireDpcList+0x277
fffff880`03393fb0 fffff800`032dc57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0ab00060 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`032e55dc 458b4d04        mov     r9d,dword ptr [r13+4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiProcessTimerDpcTable+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

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

[*]
Loading Dump File [H:\BSODDmpFiles\hurdygurdy\Windows_NT6_BSOD_jcgriff2\012512-16738-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03217000 PsLoadedModuleList = 0xfffff800`0345c670
Debug session time: Wed Jan 25 15:26:04.550 2012 (UTC - 7:00)
System Uptime: 0 days 0:55:00.533
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )

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

7: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+6333343838393830
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

EXCEPTION_RECORD:  fffff88003592808 -- (.exr 0xfffff88003592808)
ExceptionAddress: fffff8000328a507 (nt!KeAccumulateTicks+0x0000000000000417)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880035928b0 -- (.trap 0xfffff880035928b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=263fb01374b4ab78 rbx=0000000000000000 rcx=0000000000000011
rdx=000000000000a574 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328a507 rsp=fffff88003592a40 rbp=0000000000000001
 r8=000000000000c4ec  r9=0000000000000000 r10=0000000000000f42
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAccumulateTicks+0x417:
fffff800`0328a507 418be9          mov     ebp,r9d
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000328b5fe to fffff80003293c10

STACK_TEXT:  
fffff880`035918e8 fffff800`0328b5fe : 00000000`00000000 fffff880`035918f0 fffff880`03592060 fffff800`032bf830 : nt!KeBugCheck
fffff880`035918f0 fffff800`032bf4fd : fffff800`0349d488 fffff800`033dbc8c fffff800`03217000 fffff880`03592808 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03591920 fffff800`032be2d5 : fffff800`033de0fc fffff880`03591998 fffff880`03592808 fffff800`03217000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03591950 fffff800`032cf361 : fffff880`03592808 fffff880`03592060 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x415
fffff880`03592030 fffff800`032932c2 : fffff880`03592808 fffff880`0356a180 fffff880`035928b0 fffff880`035750c0 : nt!KiDispatchException+0x135
fffff880`035926d0 fffff800`03291bca : fffffa80`062fd1a0 00000000`00000000 fffffa80`06310002 00000000`00000201 : nt!KiExceptionDispatch+0xc2
fffff880`035928b0 fffff800`0328a507 : 00000000`00000001 fffffa80`063327d0 00000000`00000001 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`03592a40 fffff800`0329ff58 : 00000000`00000000 fffff880`00c0c805 00000000`00002710 fffffa80`0631ca00 : nt!KeAccumulateTicks+0x417
fffff880`03592ad0 fffff800`0329fce1 : 00000000`00000000 fffff880`03592b80 fffff880`0356a180 00000000`00000001 : nt!KeUpdateRunTime+0xb8
fffff880`03592b00 fffff880`04dbf9c2 : fffff800`0329d4a9 00000000`003c1d19 fffffa80`0631cb38 fffff880`035750c0 : nt!KiSecondaryClockInterrupt+0x131
fffff880`03592c98 fffff800`0329d4a9 : 00000000`003c1d19 fffffa80`0631cb38 fffff880`035750c0 00000000`00000001 : intelppm+0x39c2
fffff880`03592ca0 fffff800`0328b93c : fffff880`0356a180 fffff880`00000000 00000000`00000000 fffff880`00c0bf5c : nt!PoIdle+0x52a
fffff880`03592d80 00000000`00000000 : fffff880`03593000 fffff880`0358d000 fffff880`03592d40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`04dbf9c2 ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  intelppm+39c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x1E_0_intelppm+39c2

BUCKET_ID:  X64_0x1E_0_intelppm+39c2

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

[*]
Loading Dump File [H:\BSODDmpFiles\hurdygurdy\Windows_NT6_BSOD_jcgriff2\012512-21528-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\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 Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03258000 PsLoadedModuleList = 0xfffff800`0349d670
Debug session time: Wed Jan 25 14:30:26.479 2012 (UTC - 7:00)
System Uptime: 0 days 1:32:23.352
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, d, 1, fffff800032cb507}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )

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

3: 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: 0000000000000000, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, 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: fffff800032cb507, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003507100
 0000000000000000 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KeAccumulateTicks+417
fffff800`032cb507 418be9          mov     ebp,r9d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880031fd8b0 -- (.trap 0xfffff880031fd8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=95f234a3f6b3f990 rbx=0000000000000000 rcx=0000000000000011
rdx=000000000001aa52 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032cb507 rsp=fffff880031fda40 rbp=0000000000000001
 r8=000000000001fb68  r9=0000000000000000 r10=0000000000000f44
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeAccumulateTicks+0x417:
fffff800`032cb507 418be9          mov     ebp,r9d
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d41e9 to fffff800032d4c40

STACK_TEXT:  
fffff880`031fd768 fffff800`032d41e9 : 00000000`0000000a 00000000`00000000 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff880`031fd770 fffff800`032d2e60 : fffffa80`063ab000 fffff880`031fd910 fffff880`031d5180 fffff880`031d5180 : nt!KiBugCheckDispatch+0x69
fffff880`031fd8b0 fffff800`032cb507 : fffff960`002fc000 fffff880`050cb000 fffff880`01503000 fffff880`011b9000 : nt!KiPageFault+0x260
fffff880`031fda40 fffff800`032e0f58 : 00000000`00000000 fffff880`031d5180 00000000`00002711 fffffa80`063ab000 : nt!KeAccumulateTicks+0x417
fffff880`031fdad0 fffff800`032e0ce1 : 00000000`00000000 fffff880`031fdb80 fffff880`031d5180 00000000`00000001 : nt!KeUpdateRunTime+0xb8
fffff880`031fdb00 fffff880`04a299c2 : fffff800`032de4a9 00000000`003b9960 fffffa80`063ab168 fffff880`031e00c0 : nt!KiSecondaryClockInterrupt+0x131
fffff880`031fdc98 fffff800`032de4a9 : 00000000`003b9960 fffffa80`063ab168 fffff880`031e00c0 00000000`00000001 : intelppm+0x39c2
fffff880`031fdca0 fffff800`032cc93c : fffff880`031d5180 fffff880`00000000 00000000`00000000 fffff800`03265dc8 : nt!PoIdle+0x52a
fffff880`031fdd80 00000000`00000000 : fffff880`031fe000 fffff880`031f8000 fffff880`031fdd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`04a299c2 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  intelppm+39c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0xA_intelppm+39c2

BUCKET_ID:  X64_0xA_intelppm+39c2

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


[/list]

1. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software... Overclocking...
2. Likely due to overclocking. Other possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
3. Likely due to overclocking. Other possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Antivirus Software...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking anything, please stop.
  

 

[hurdygurdy]

Thank you writhziden for the quick response.

I am very much a complete beginner when it comes to pc workings.

I have not overclocked anything personally but this would have been done by overclockers. Sorry to have to ask but how should I go about reverting all settings back to factory settings.(removing all overclocking)

I could do this then run for a night and if it does not clear up my issues I could take the new dump info and repost so I can get to the bottom of this.

I am sorry to be a pain but really do appreciate any help some of you more computer literate forum members can offer me.

Thanks Hurdy

 

[writhziden]

Thank you writhziden for the quick response.

I am very much a complete beginner when it comes to pc workings.

I have not overclocked anything personally but this would have been done by overclockers. Sorry to have to ask but how should I go about reverting all settings back to factory settings.(removing all overclocking)

I could do this then run for a night and if it does not clear up my issues I could take the new dump info and repost so I can get to the bottom of this.

I am sorry to be a pain but really do appreciate any help some of you more computer literate forum members can offer me.

Thanks Hurdy

Press delete as soon as your computer turns on (not boots into windows, but physically turns on) to start the BIOS. Go to the exit portion of the BIOS. Select Load Setup Defaults. Select Exit & Save Changes. I have attached a picture to help you.

Post back any crash reports if the system does not become more stable.

 

[hurdygurdy]

Thanks I will do this now

Fingers crossed its just down to it being poorly overclocked. If I have any errors I will post the data from them should inlet it happen two or three times or just after the first one?

Thanks in advance

Hurdy

 

[writhziden]

Let us know the outcome regardless. Best wishes!

 

[hurdygurdy]

Hi

Thats four hours down and no crash as of yet this is exteemely rare so i am now hoping you nailed it.

I will let you know after a few days if there are no more BOSD

Thank you

Hurdy

 

[writhziden]

You are very welcome. That is good news. Do run for a few days and post back.

 

[hurdygurdy]

Writhziden

I just wanted to thank you my P.C is now stable and running faster than i ever thought possible.

Thanks for your speedy replies and resolving my issues .

Best Regards

Hurdy

 

[writhziden]

You are very welcome, Hurdy. I am glad your system is performing exemplary.

If you would like to, you can mark the thread as solved by clicking the green button Mark as Solved at the top or bottom of the thread. The Mark as Solved button may be found next to the orange Post Reply button.