Windows 7: BSOD

Cibo01 · 12 Mar 2010

Computer was built 2months ago with GB P55A UD3P Mother Board, I5-650 CPU, Radeon 5770 graphics card, 4 GB Patriot G-Series 1600Hz RAM. Had some initial stability problems but after reading another thread I removed the DLink network card and replaced with a TP link card and these issues were resolved.

Started having frequent crashes about a month ago, seems to be no pattern to it and some days it will run fine for hours but generally it will crash after 10min no matter what I am doing on the computer and after a crash the computer will not turn on properly. It has also crashed in safe mode. Have updated all of the drivers, have removed the network card, tried another 5770 card and then an old NVIDIA card and although they appear to resolve the stability issue it was short lived (ie. 1 day). Have run prime95 for a few hours and have wanted to run it again for a longer period of time but the computer is not stable enough. Have also checked for over heating but the temp alarm has not gone off and the graphics temp also remains stable.

I have attached the minidump file, please help!

zigzag3143 · 12 Mar 2010

Quote: Originally Posted by Cibo01

Computer was built 2months ago with GB P55A UD3P Mother Board, I5-650 CPU, Radeon 5770 graphics card, 4 GB Patriot G-Series 1600Hz RAM. Had some initial stability problems but after reading another thread I removed the DLink network card and replaced with a TP link card and these issues were resolved.

Started having frequent crashes about a month ago, seems to be no pattern to it and some days it will run fine for hours but generally it will crash after 10min no matter what I am doing on the computer and after a crash the computer will not turn on properly. It has also crashed in safe mode. Have updated all of the drivers, have removed the network card, tried another 5770 card and then an old NVIDIA card and although they appear to resolve the stability issue it was short lived (ie. 1 day). Have run prime95 for a few hours and have wanted to run it again for a longer period of time but the computer is not stable enough. Have also checked for over heating but the temp alarm has not gone off and the graphics temp also remains stable.

I have attached the minidump file, please help!

These are pretty straight forward. The cause of these was memory corruption.

I would download memtestx86 and run it dor 5 passes.

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\Minidump\031210-21949-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5be50
Debug session time: Fri Mar 12 05:04:34.614 2010 (GMT-5)
System Uptime: 0 days 0:01:43.723
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff88006be67d9}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88006be67d9

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c8f469 to fffff80002c8ff00

STACK_TEXT:  
fffff880`02fdbce8 fffff800`02c8f469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdbcf0 fffff800`02c8d932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdbe30 fffff880`06be67d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`071f82d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mouhid!MouHid_ReadComplete+0x1fd


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !mouhid
8 errors : !mouhid (fffff88006be67c0-fffff88006be67f8)
fffff88006be67c0 *32  45  33  c0  89  44  24  38 *e3  8b  46  68  8b  d5  48  89 2E3..D$8..Fh..H.
fffff88006be67d0 *6c  24  30  48  8b  46  20  33 *e6  48  89  44  24  28  4c  89 l$0H.F 3.H.D$(L.
fffff88006be67e0 *a3  24  20  e8  c2  1b  00  00 *78  06  00  11  c0  75  15  83 .$ .....x....u..
fffff88006be67f0 *da  70  02  0f  b7  0e  8b  d5 *11  cd  44  8a  e5  d3  e2  2b .p........D....+

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88006be67d9

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c8f469 to fffff80002c8ff00

STACK_TEXT:  
fffff880`02fdbce8 fffff800`02c8f469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdbcf0 fffff800`02c8d932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdbe30 fffff880`06be67d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`071f82d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mouhid!MouHid_ReadComplete+0x1fd


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !mouhid
8 errors : !mouhid (fffff88006be67c0-fffff88006be67f8)
fffff88006be67c0 *32  45  33  c0  89  44  24  38 *e3  8b  46  68  8b  d5  48  89 2E3..D$8..Fh..H.
fffff88006be67d0 *6c  24  30  48  8b  46  20  33 *e6  48  89  44  24  28  4c  89 l$0H.F 3.H.D$(L.
fffff88006be67e0 *a3  24  20  e8  c2  1b  00  00 *78  06  00  11  c0  75  15  83 .$ .....x....u..
fffff88006be67f0 *da  70  02  0f  b7  0e  8b  d5 *11  cd  44  8a  e5  d3  e2  2b .p........D....+

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88006be67d9

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c8f469 to fffff80002c8ff00

STACK_TEXT:  
fffff880`02fdbce8 fffff800`02c8f469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdbcf0 fffff800`02c8d932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdbe30 fffff880`06be67d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`071f82d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mouhid!MouHid_ReadComplete+0x1fd


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !mouhid
8 errors : !mouhid (fffff88006be67c0-fffff88006be67f8)
fffff88006be67c0 *32  45  33  c0  89  44  24  38 *e3  8b  46  68  8b  d5  48  89 2E3..D$8..Fh..H.
fffff88006be67d0 *6c  24  30  48  8b  46  20  33 *e6  48  89  44  24  28  4c  89 l$0H.F 3.H.D$(L.
fffff88006be67e0 *a3  24  20  e8  c2  1b  00  00 *78  06  00  11  c0  75  15  83 .$ .....x....u..
fffff88006be67f0 *da  70  02  0f  b7  0e  8b  d5 *11  cd  44  8a  e5  d3  e2  2b .p........D....+

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88006be67d9

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c8f469 to fffff80002c8ff00

STACK_TEXT:  
fffff880`02fdbce8 fffff800`02c8f469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdbcf0 fffff800`02c8d932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdbe30 fffff880`06be67d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`071f82d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mouhid!MouHid_ReadComplete+0x1fd


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !mouhid
8 errors : !mouhid (fffff88006be67c0-fffff88006be67f8)
fffff88006be67c0 *32  45  33  c0  89  44  24  38 *e3  8b  46  68  8b  d5  48  89 2E3..D$8..Fh..H.
fffff88006be67d0 *6c  24  30  48  8b  46  20  33 *e6  48  89  44  24  28  4c  89 l$0H.F 3.H.D$(L.
fffff88006be67e0 *a3  24  20  e8  c2  1b  00  00 *78  06  00  11  c0  75  15  83 .$ .....x....u..
fffff88006be67f0 *da  70  02  0f  b7  0e  8b  d5 *11  cd  44  8a  e5  d3  e2  2b .p........D....+

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Jonathan_King · 12 Mar 2010

These ones look like bad RAM.

Download a copy of Memtest86 and burn the ISO to a CD using ImgBurn. Boot from the CD, and run at least 5 passes.

Code:

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


Loading Dump File [C:\Users\Jonathan\Desktop\Minidump\031210-21949-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c1e000 PsLoadedModuleList = 0xfffff800`02e5be50
Debug session time: Fri Mar 12 05:04:34.614 2010 (GMT-5)
System Uptime: 0 days 0:01:43.723
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff88006be67d9}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff88006be67d9

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002c8f469 to fffff80002c8ff00

STACK_TEXT:  
fffff880`02fdbce8 fffff800`02c8f469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02fdbcf0 fffff800`02c8d932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fdbe30 fffff880`06be67d9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`071f82d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mouhid!MouHid_ReadComplete+0x1fd


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !mouhid
8 errors : !mouhid (fffff88006be67c0-fffff88006be67f8)
fffff88006be67c0 *32  45  33  c0  89  44  24  38 *e3  8b  46  68  8b  d5  48  89 2E3..D$8..Fh..H.
fffff88006be67d0 *6c  24  30  48  8b  46  20  33 *e6  48  89  44  24  28  4c  89 l$0H.F 3.H.D$(L.
fffff88006be67e0 *a3  24  20  e8  c2  1b  00  00 *78  06  00  11  c0  75  15  83 .$ .....x....u..
fffff88006be67f0 *da  70  02  0f  b7  0e  8b  d5 *11  cd  44  8a  e5  d3  e2  2b .p........D....+

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

Cibo01 · 12 Mar 2010

Thanks I will try and let you know

Cibo01 · 14 Mar 2010

Alright. I ran Memtest86 as suggested. The first time errors appeared during the first pass. I then checked the memory timing for my ram and changed the BIOS setting to match this. I reran the memory test and it ran for 12hours without any errors. I turned the computer on again today and it crashed again after about 10minutes. I ran memory test again and no errors after 6 hours.

The Ram is 1600MHz and the motherboard is only detecting 1066MHz. Apparently my motherboard is not compatible with 1600MHz speeds (but I have heard otherwise) and so tomorrow I will put in some ram that is compatible and hopefully that works.

Windows 7: BSOD

BSOD problems?