BSOD's

[Watson]

Ok I ran a disk check. Unfortunately didn;t see the results as I was afk. Where can I find the results? I downloaded the seagate hard drive check. It passed all basic tests. It blue screened as I tried to start advanced tests.

Dump result from that one is below. I will try the advance tests again.

 

[CarlTR6]

Try to run the advanced test Seagate test again.

This dump is error code A pointing to memory corruption.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp2_dump.zip\080110-29109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL]http://msdl.microsoft.com/download/symbols[/URL]
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`0280f000 PsLoadedModuleList = 0xfffff800`02a4ce50
Debug session time: Sun Aug  1 12:04:06.993 2010 (GMT-4)
System Uptime: 0 days 5:07:30.523
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, fffff800028b1410}

Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+120 )

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

1: 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: 000042228030694d, 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: fffff800028b1410, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab70e0
 000042228030694d 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiResolveTransitionFault+120
fffff800`028b1410 488b08          mov     rcx,qword ptr [rax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  SearchIndexer.

TRAP_FRAME:  fffff880037ae6f0 -- (.trap 0xfffff880037ae6f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000042228030694d rbx=0000000000000000 rcx=0000000000000044
rdx=0000058000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028b1410 rsp=fffff880037ae880 rbp=fffff8a002cbdcd0
 r8=0000000000000000  r9=800000003fdaa882 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiResolveTransitionFault+0x120:
fffff800`028b1410 488b08          mov     rcx,qword ptr [rax] ds:00004222`8030694d=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000287eb69 to fffff8000287f600

STACK_TEXT:  
fffff880`037ae5a8 fffff800`0287eb69 : 00000000`0000000a 00004222`8030694d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`037ae5b0 fffff800`0287d7e0 : 00000000`00000000 80000000`3fdaa882 fffffa80`01be7b60 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69
fffff880`037ae6f0 fffff800`028b1410 : 9ee00000`3ffa5825 80000000`3ffa5921 fffffa80`00bfeef0 0000000f`ffffffff : nt!KiPageFault+0x260
fffff880`037ae880 fffff800`028a5c99 : 00000000`00000000 80000000`3fdaa882 fffffa80`01be7c20 fffffa80`04b79ec8 : nt!MiResolveTransitionFault+0x120
fffff880`037ae910 fffff800`0289b49e : 00000000`00000000 00000000`02e2b000 fffff680`00017158 fffffa80`04b79ec8 : nt!MiResolveProtoPteFault+0x419
fffff880`037ae9b0 fffff800`02899623 : ffffffff`ffffff00 00000000`02e2b000 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1de
fffff880`037aeac0 fffff800`0287d6ee : 00000000`00000000 00000000`e23bbead fffff880`00000001 00000000`01c76d00 : nt!MmAccessFault+0x343
fffff880`037aec20 000007fe`f6e4f06e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`03bbf430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f6e4f06e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiResolveTransitionFault+120
fffff800`028b1410 488b08          mov     rcx,qword ptr [rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiResolveTransitionFault+120

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+120

BUCKET_ID:  X64_0xA_nt!MiResolveTransitionFault+120

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

Lets see what the advanced hard drive test tells us.

I still see this driver in your dump.

DB3G.sys Mon Nov 07 01:33:11 2005 If you downloaded an updated driver, uninstall the old driver and install the updated one. Then reboot.

 

[Watson]

Ok I removed the old mouse driver. Thanks for pointing that out Advanced tests are not available according to the tester. But viewing the website tells me that the tests that it is put through are fairly tough and that if something was wrong it would almost certainly of found it. So it looks like the blue screen was totally unrelated to me clicking on advance tests and coincidental.

Where can I view the results of my disk check from earlier?

Is it worth running the driver verifier as well seeing as the mouse issue has now been resolved?

Thanks again

 

[CarlTR6]

Let's see what your system does without driver verifier.

Check disk does not yield a saved report automatically. Below are the check disk commands.

Checks a disk and displays a status report.

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]

volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for fragmentation.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every file
on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F).
/L:size NTFS only: Changes the log file size to the specified number
of kilobytes. If size is not specified, displays current
size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index entries.
/C NTFS only: Skips checking of cycles within the folder
structure.
/B NTFS only: Re-evaluates bad clusters on the volume
(implies /R)

The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.

The preferred command is shown below.
View attachment 88726
You can always run it again. I am pretty sure since your Drive passed the Seagate tester it is OK.

 

[Watson]

Time for some Empire Total War I'll see if I get anymore.

Thanks

 

[CarlTR6]

Let us know - and good job with the mouse driver.

 

[Watson]

Random one this afternoon while browsing the net.

 

[Tews]

Your .dmp file is still showing Memory Corruption as the cause of your crashes... Rerun memtest and post the results..

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {42228030694d, 2, 0, fffff80002927a2f}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )

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

1: 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: 000042228030694d, 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: fffff80002927a2f, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aad0e0
 000042228030694d 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+23f
fffff800`02927a2f 4c8b7500        mov     r14,qword ptr [rbp]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff8800260a4f0 -- (.trap 0xfffff8800260a4f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=0a00000000000020
rdx=000000000003fdaa rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002927a2f rsp=fffff8800260a680 rbp=000042228030694d
 r8=0000000000035fab  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiIdentifyPfn+0x23f:
fffff800`02927a2f 4c8b7500        mov     r14,qword ptr [rbp] ss:0018:00004222`8030694d=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002874b69 to fffff80002875600

STACK_TEXT:  
fffff880`0260a3a8 fffff800`02874b69 : 00000000`0000000a 00004222`8030694d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0260a3b0 fffff800`028737e0 : 00000000`42506650 22112205`1b06050c 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0260a4f0 fffff800`02927a2f : 00000000`00000000 02000000`00045c76 00000000`000018c0 fffff800`02b3d1af : nt!KiPageFault+0x260
fffff880`0260a680 fffff800`0292870b : 00000000`00000000 00000000`00000004 fffffa80`02c1a778 fffffa80`02c1a000 : nt!MiIdentifyPfn+0x23f
fffff880`0260a720 fffff800`02c87c55 : fffffa80`02c1a000 fffff880`0260aca0 fffff880`0260a7f8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`0260a760 fffff800`02bccf18 : 00000000`00000006 00000000`00000000 fffffa80`02c1a000 fffff800`02805001 : nt!PfpPfnPrioRequest+0x115
fffff880`0260a7b0 fffff800`02b73fb3 : 00000000`00000000 fffff800`02805000 fffffa80`026a5000 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x4759d
fffff880`0260a840 fffff800`02b75149 : 00000000`00f0bd88 00000000`00001101 00000000`00f0bde0 00000000`00f0bda8 : nt!ExpQuerySystemInformation+0x11c2
fffff880`0260abe0 fffff800`02874853 : fffffa80`04577b60 00000000`01a05030 00000000`00000001 00000000`03c215c0 : nt!NtQuerySystemInformation+0x4d
fffff880`0260ac20 00000000`779500ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00f0bca8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779500ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+23f
fffff800`02927a2f 4c8b7500        mov     r14,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiIdentifyPfn+23f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f

BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f

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

 

[ttran]

DB3G     DB3G.sys     Mon Nov 07 13:33:11 2005 (436EF527)

It is still there, please update it or remove it. You said you remove it, how did you remove it? Please go to C-->Window-->System32-->Driver and change the name to .BAK instead of .sys
http://www.razersupport.com/index.php?_m=downloads&_a=viewdownload&downloaditemid=74

 

[Watson]

Done. Deleted for sure now. I was sure I had deleted it. I had already done a memtest. Is there no way to pull the results from somewhere? if not I will run it again tonight.

 

[CarlTR6]

Tews is asking you to rerun it just to double check. How is your system doing since you got rid of that obsolete driver?

 

[Watson]

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.

 

[CarlTR6]

That is good - it certainly is an improvement.

 

[Watson]

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.

 

[ttran]

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.

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
---------

 

[Watson]

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?

 

[zigzag3143]

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?

IF Memtest froze there is something wrong. Either memory, or motherboard slots probably

 

[Watson]

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?

 

[ttran]

You can use speedfan: SpeedFan - Access temperature sensor in your computer
Are you overclocking at all? If so, restore to defaults

 

[Watson]

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.