Computer Crashing...possible Mouse Problem?

Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Important Announcement: The winners of the BC Million Post contest have been announced. You can read who the winners are at this post.

- BleepingComputer Management

BleepingComputer.com > Hardware > Internal Hardware

2 Pages

< 1 2

Computer Crashing...possible Mouse Problem?, Razer Copperhead

Options

hamluis View Member Profile	Aug 25 2008, 09:00 PM Post #16
Forum Addict Group: Members Posts: 6,545 Joined: 3-September 05 From: Killeen, TX Member No.: 33,068	In my experience...troubleshooting computer situations normally involves: a. Error messages which are documented somewhere on the Web. b. Situations which are documented on the Web which might apply to my particular set of circumstances. c. Personal experiences that my poor brain still remembers . d. Somewhat analytical guesswork by me. There is no magical program that's going to tell me what is wrong. I forgot my ultimate two alternatives: a. Repair install of the O/S, hoping that it will resolve whatever is wrong...or convince me that I just need to eliminate the O/S as the problem and start thinking hardware. I have never had a malware problem, so I never consider that. b. Clean install or reinstall of one of my system backups from my disk-imaging program. Based on the info you've provided...I don't know what else I could suggest as either a cure or even define what is problematical. Louis

niustat83 View Member Profile	Sep 19 2008, 11:00 PM Post #17
Member Group: Members Posts: 43 Joined: 20-June 08 Member No.: 217,480	Alright I've been back at work on this trying to figure it out. I downloaded the debugger tool. Here's one of my crash logs. Can someone help me make some sense of this? Loading Dump File [C:\WINDOWS\Minidump\Mini091808-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRVc:\websymbolshttp://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 2600.xpsp_sp2_gdr.070227-2254 Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Wed Sep 17 22:43:46.541 2008 (GMT-5) System Uptime: 0 days 0:05:51.188 Loading Kernel Symbols ................................................................................ .......................................................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 1000007F, {d, 0, 0, 0} Probably caused by : ntkrpamp.exe ( nt!NtQueryInformationFile+6e ) Followup: MachineOwner --------- 1: kd> !analyze -v ***************************************************************************** * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a portion of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: OUTLOOK.EXE LAST_CONTROL_TRANSFER: from 805798da to 0c31fa50 STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. f1486cb8 805798da 00000018 00000004 f1486d64 0xc31fa50 f1486d48 8054086c 00000980 0c31fa68 0c31fa50 nt!NtQueryInformationFile+0x6e f1486d48 7c90eb94 00000980 0c31fa68 0c31fa50 nt!KiFastCallEntry+0xfc 0c31fa24 7c90dfe8 7c813794 00000980 0c31fa68 0x7c90eb94 0c31fa78 35cb39c8 00000980 00000000 0c31fa98 0x7c90dfe8 0c31faa0 35d44f40 00000980 02e84400 00000200 0x35cb39c8 0c31fae8 35d454fc 0a6e2308 00000980 02e84400 0x35d44f40 0c31fb24 35d41af3 02e84400 00000000 02e84400 0x35d454fc 0c31fb98 35d45d0d 00000640 0c31fbb8 00000000 0x35d41af3 0c31fbd0 35d46dbf 0a825238 00000000 00000002 0x35d45d0d 0c31fc00 35d4785c 003aa1a1 0a825238 0c31fc60 0x35d46dbf 0c31fc20 35d478fd 003aa1a1 00000000 0c31fc34 0x35d4785c 0c31fc40 35d479b8 003aa1a1 00000000 35d46d13 0x35d478fd 0c31fc68 35d3e74c 003aa1a1 00000000 003aa194 0x35d479b8 0c31fcbc 35cc2fe7 00000000 00000001 0a6e5a58 0x35d3e74c 0c31fcdc 35cef7da 00000000 00000000 00000001 0x35cc2fe7 0c31fcfc 35fe4b35 00000001 0a6e55f8 00000001 0x35cef7da 0c31fd1c 35fe4b67 0a2e8174 0a474cf4 00000001 0x35fe4b35 0c31fd90 35fbd34c 056af178 057ab700 057ab6d8 0x35fe4b67 0c31fde0 35fbcd55 00000001 056f457c 057ab660 0x35fbd34c 0c31fe18 35fbbb1c 00000001 056f457c 057ab660 0x35fbcd55 0c31fe54 35fbba5a 054895e8 00000004 00000001 0x35fbbb1c 0c31feb4 35fbb752 05433fb4 056af014 35fbb9cb 0x35fbba5a 0c31fed0 35fbb8f0 056aeff8 05433f7c 057a15a0 0x35fbb752 0c31ff08 35fbb833 35fbb7c1 056fbd44 05433f60 0x35fbb8f0 0c31ff20 35fbb752 05433f60 056fbd40 35fbb714 0x35fbb833 0c31ff40 35fbabd7 05433f60 056fbd44 7c80c108 0x35fbb752 0c31ff64 35fbab6a 7c80c108 0a475440 35f76bfa 0x35fbabd7 0c31ffb0 35f766a0 7c80b683 056df538 00000001 0x35fbab6a 0c31ffec 00000000 35f76697 056df538 00000000 0x35f766a0 STACK_COMMAND: kb FOLLOWUP_IP: nt!NtQueryInformationFile+6e 805798da e861a90900 call nt!ProbeForWrite (80614240) SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!NtQueryInformationFile+6e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d FAILURE_BUCKET_ID: 0x7f_d_nt!NtQueryInformationFile+6e BUCKET_ID: 0x7f_d_nt!NtQueryInformationFile+6e Followup: MachineOwner --------- Thanks in advance.

cryptodan View Member Profile	Sep 20 2008, 04:46 AM Post #18
Distinguished Member Group: Members Posts: 674 Joined: 8-September 08 From: Laurel, Md Member No.: 237,030	Sounds to me like an over heating problem.

niustat83 View Member Profile	Sep 20 2008, 08:19 PM Post #19
Member Group: Members Posts: 43 Joined: 20-June 08 Member No.: 217,480	QUOTE(cryptodan @ Sep 20 2008, 04:46 AM) Sounds to me like an over heating problem. How can I be sure?

« Next Oldest · Internal Hardware · Next Newest »

2 Pages

< 1 2

1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)

0 Members:

Display Mode: Standard · Switch to: Linear+ · Switch to: Outline

Track this topic · Email this topic · Print this topic · Subscribe to this forum

Lo-Fi Version

Time is now: 22nd November 2008 - 01:49 PM

Advertise \| About Us \| Terms of Use \| Privacy Policy \| Contact Us \| Site Map \| Chat \| Tutorials \| Uninstall List
Discussion Forums \| The Computer Glossary \| Resources \| RSS Feeds \| Startups \| The File Database \| Malware Removal Guides