New
#31
Tews is asking you to rerun it just to double check. How is your system doing since you got rid of that obsolete driver?
BSOD's
-
-
New #32
Yeah was playing a game for a few hours this afternoon with no problems. Its been on afk until now as well. I'll rerun the memtest tonight.
-
-
New #34
Within 2 minutes of me posting, while still on the forums it blue screened again. I then started it up again to find that removing the mouse driver file had meant my mouse would no longer move. The new driver must not have kicked in properly. After painfully navigating around with the keyboard, the pc crashed again while trying to post here. Since then I have reinstalled the mouse driver so I can move again. Gonna run the memtest immediatly.
Here are the latest dump files.
-
New #35
Yes, please do the memtest to confirm nothing is wrong with the Ram. But personally, I think all of these thing go wrong because of the mouse. See if you can have another mouse to test on your system, with the driver date from 2005, it's hard to say that it is compatible with window 7, even if you still can run your mouse, it will not stable at all, especially when you turned on Driver Verifier, all the crash dump point to that mouse.
Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.666\080210-22417-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`0280b000 PsLoadedModuleList = 0xfffff800`02a48e50 Debug session time: Tue Aug 3 04:41:29.608 2010 (UTC + 7:00) System Uptime: 0 days 1:44:50.137 Loading Kernel Symbols ............................................................... ................................................................ ...... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {42228030694d, 2, 0, fffff8000292da2f} Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f ) Followup: MachineOwner ---------
-
New #36
Seems the memtest froze during the night. It had only done 2 passes with no errors. Does it mean there is something wrong? Or coincidence?
-
New #37
-
New #38
New one while trying to comb the razer forums to sort my mouse.
Could any of this be due to overheating? It's a problem I have had before. Anything I can download to check my temperature?
-
New #39
You can use speedfan: SpeedFan - Access temperature sensor in your computer
Are you overclocking at all? If so, restore to defaults
-
New #40
Seems normal temperature wise. I am not overclocking.
I am going to try memtest again. The first time I ran it. When I came down before it had frozen as well now I think back. At the time, not knowing how it worked I assumed it had finished when it said no errors at the bottom. But thinking back, I remember it was in the middle of a test and unresponsive. So looks like there is a problem. I'll post back with the results.
Quote