Now i have an even more annoying situation.
Less BSOD's but more freezes and sudden re-boots. Problem with this is they don't produce a dumpfile!
Still i got one.
What i did so far:
found and replaced with a newer version: secdrv.SYS
ran mem test (5+ passes) with no errors found
I cannot seem to find a same or newer version of the USBSTOR.SYS file. Anyone, tips plz?
i have one more dump and the version details of the USBSTOR.SYS file.
Thanks you guys!!
I hate tp say this but this one was caused by memory corruption. How long did you run memtest for?
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\051010-30825-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03086e50
Debug session time: Mon May 10 12:37:13.938 2010 (GMT-4)
System Uptime: 0 days 0:31:13.125
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050033, 6f8, fffff80002eb4750}
*** 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
---------
6: 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: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002eb4750
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002eb5e69 to fffff80002eb6900
STACK_TEXT:
fffff880`032fdde8 fffff800`02eb5e69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`032fddf0 fffff800`02eb4332 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`032fdf30 fffff800`02eb4750 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0a1d7f40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
31 errors : !nt (fffff80002eb4782-fffff80002eb67ba)
fffff80002eb4780 25 88 *41 00 00 41 f6 42 03 80 *1c 3c b9 02 01 00 %.A..A.B...<....
fffff80002eb4790 c0 0f *1c 48 c1 e2 20 48 0b c2 *e8 39 82 b8 00 00 ...H.. H...9....
fffff80002eb47a0 00 74 *90 49 39 82 b0 01 00 00 *f0 1c 49 8b 92 b8 .t.I9.......I...
fffff80002eb47b0 01 00 *b9 41 0f ba 6a 4c 0b 66 *fc ff 8a c4 01 00 ...A..jL.f......
...
fffff80002eb4800 29 6d *01 8b 05 77 f0 1f 00 89 *74 0c 01 00 00 8b )m...w....t.....
fffff80002eb4810 85 e0 *32 00 00 48 f7 85 f8 00 *49 00 00 02 00 00 ..2..H....I.....
fffff80002eb4820 74 01 *25 b9 01 00 00 10 ba 02 *74 00 00 44 8b 8d t.%.......t..D..
fffff80002eb4830 e0 00 00 00 41 81 e1 ff ff 00 *41 4d 33 d2 4c 8b ....A.....AM3.L.
...
fffff80002eb6680 48 83 *00 68 4c 89 45 80 4c 89 *eb 88 4c 89 55 90 H..hL.E.L...L.U.
fffff80002eb6690 4c 89 *00 98 4c 8d 44 24 70 49 *00 08 49 89 50 08 L...L.D$pI..I.P.
fffff80002eb66a0 65 48 *00 0c 25 88 01 00 00 48 *5a 49 28 48 8d 49 eH..%....HZI(H.I
fffff80002eb66b0 50 48 *eb 4c 24 40 0f ae 01 48 *ee 85 10 01 00 00 PH.L$@...H......
...
fffff80002eb6780 48 81 *3f 38 01 00 00 0f 29 74 *d4 30 0f 29 7c 24 H.?8....)t.0.)|$
fffff80002eb6790 40 44 *7b 29 44 24 50 44 0f 29 *3f 24 60 44 0f 29 @D{)D$PD.)?$`D.)
fffff80002eb67a0 54 24 *7b 44 0f 29 9c 24 80 00 *aa 00 44 0f 29 a4 T${D.).$....D.).
fffff80002eb67b0 24 90 *3f 00 00 44 0f 29 ac 24 *7b 00 00 00 44 0f $.?..D.).${...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
---------
6: 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: 0000000080050033
Arg3: 00000000000006f8
Arg4: fffff80002eb4750
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002eb5e69 to fffff80002eb6900
STACK_TEXT:
fffff880`032fdde8 fffff800`02eb5e69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff880`032fddf0 fffff800`02eb4332 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`032fdf30 fffff800`02eb4750 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0a1d7f40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
31 errors : !nt (fffff80002eb4782-fffff80002eb67ba)
fffff80002eb4780 25 88 *41 00 00 41 f6 42 03 80 *1c 3c b9 02 01 00 %.A..A.B...<....
fffff80002eb4790 c0 0f *1c 48 c1 e2 20 48 0b c2 *e8 39 82 b8 00 00 ...H.. H...9....
fffff80002eb47a0 00 74 *90 49 39 82 b0 01 00 00 *f0 1c 49 8b 92 b8 .t.I9.......I...
fffff80002eb47b0 01 00 *b9 41 0f ba 6a 4c 0b 66 *fc ff 8a c4 01 00 ...A..jL.f......
...
fffff80002eb4800 29 6d *01 8b 05 77 f0 1f 00 89 *74 0c 01 00 00 8b )m...w....t.....
fffff80002eb4810 85 e0 *32 00 00 48 f7 85 f8 00 *49 00 00 02 00 00 ..2..H....I.....
fffff80002eb4820 74 01 *25 b9 01 00 00 10 ba 02 *74 00 00 44 8b 8d t.%.......t..D..
fffff80002eb4830 e0 00 00 00 41 81 e1 ff ff 00 *41 4d 33 d2 4c 8b ....A.....AM3.L.
...
fffff80002eb6680 48 83 *00 68 4c 89 45 80 4c 89 *eb 88 4c 89 55 90 H..hL.E.L...L.U.
fffff80002eb6690 4c 89 *00 98 4c 8d 44 24 70 49 *00 08 49 89 50 08 L...L.D$pI..I.P.
fffff80002eb66a0 65 48 *00 0c 25 88 01 00 00 48 *5a 49 28 48 8d 49 eH..%....HZI(H.I
fffff80002eb66b0 50 48 *eb 4c 24 40 0f ae 01 48 *ee 85 10 01 00 00 PH.L$@...H......
...
fffff80002eb6780 48 81 *3f 38 01 00 00 0f 29 74 *d4 30 0f 29 7c 24 H.?8....)t.0.)|$
fffff80002eb6790 40 44 *7b 29 44 24 50 44 0f 29 *3f 24 60 44 0f 29 @D{)D$PD.)?$`D.)
fffff80002eb67a0 54 24 *7b 44 0f 29 9c 24 80 00 *aa 00 44 0f 29 a4 T${D.).$....D.).
fffff80002eb67b0 24 90 *3f 00 00 44 0f 29 ac 24 *7b 00 00 00 44 0f $.?..D.).${...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
---------