Sign in with
Sign up | Sign in
Your question

Cannot solve BSOD issue

Last response: in Motherboards
Share
April 8, 2010 8:04:30 AM

Hi everybody,
this is my first message here, I usually post on the Italian forum but I wasn't able to find out any solution for my problem.
Here it is.

System Config:
- Asus Rampage II Gene
- Intel i7 920
- Ati HD3870X2
- 3x WD RE3 raid 0
- 6GB DDR3 Gskill Trident 1600 6-7-6-18 (compatible with motherboard)
- Windows 7 64 ultimate

Problem:
I had and i'm still having BSOD or freeze while surfing, playing, using photoshop and sometime (rarely) doing nothing.
BSOD tipically is verified after the system slows down and the mouse pointer starts moving slowly.
In addition to this, if I save a work while the system is "telling me" that it is going to freeze, it won't be saved: i mean that it appears to be saved (and icon is present in the folder) but the file is not available after bsod.
Finally, raid disks appear to have errors when restarting after BSOD (intel Rapid Storage Technology can correct these errors).

possible solutions already tested
- driver update (chipset, sata, raid, lan, graphic);
- formatted and re-installed SO;
- tried different hard disk (2xRaptor, 1xRaptor, 1xMatrox, 3xWDRE3 with and without raid configuration);
- tried different ram module in single channel (1GB DDR3);
- disabled windows media player networrk service;
- memtest all ram module used > no error;
- checked all hard disk used > no error;

BSOD dump
here i got different BSOD, starting from the older one, ending with the most recent.
I got different errors, most common are:
- An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval.
- iaStorV.sys

1
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\021910-20326-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows 7 Kernel Version 7600 MP (8 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
  13. Machine Name:
  14. Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
  15. Debug session time: Fri Feb 19 19:26:19.431 2010 (GMT+1)
  16. System Uptime: 0 days 20:37:43.461
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. ................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. ......
  24. *******************************************************************************
  25. * *
  26. * Bugcheck Analysis *
  27. * *
  28. *******************************************************************************
  29.  
  30. Use !analyze -v to get detailed debugging information.
  31.  
  32. BugCheck 7A, {fffff6fc5001bd40, ffffffffc0000185, bdd2b880, fffff8a0037a87a8}
  33.  
  34. Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
  35.  
  36. Followup: MachineOwner
  37. ---------
  38.  
  39. 3: kd> !analyze -v
  40. *******************************************************************************
  41. * *
  42. * Bugcheck Analysis *
  43. * *
  44. *******************************************************************************
  45.  
  46. KERNEL_DATA_INPAGE_ERROR (7a)
  47. The requested page of kernel data could not be read in. Typically caused by
  48. a bad block in the paging file or disk controller error. Also see
  49. KERNEL_STACK_INPAGE_ERROR.
  50. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
  51. it means the disk subsystem has experienced a failure.
  52. If the error status is 0xC000009A, then it means the request failed because
  53. a filesystem failed to make forward progress.
  54. Arguments:
  55. Arg1: fffff6fc5001bd40, lock type that was held (value 1,2,3, or PTE address)
  56. Arg2: ffffffffc0000185, error status (normally i/o status code)
  57. Arg3: 00000000bdd2b880, current process (virtual address for lock type 3, or PTE)
  58. Arg4: fffff8a0037a87a8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
  59.  
  60. Debugging Details:
  61. ------------------
  62.  
  63.  
  64. ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
  65.  
  66. DISK_HARDWARE_ERROR: There was error with disk hardware
  67.  
  68. BUGCHECK_STR: 0x7a_c0000185
  69.  
  70. CUSTOMER_CRASH_COUNT: 1
  71.  
  72. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  73.  
  74. PROCESS_NAME: wmpnetwk.exe
  75.  
  76. CURRENT_IRQL: 0
  77.  
  78. TRAP_FRAME: fffff880098cd720 -- (.trap 0xfffff880098cd720)
  79. NOTE: The trap frame does not contain all registers.
  80. Some register values may be zeroed or incorrect.
  81. rax=fffffa80059c0e90 rbx=0000000000000000 rcx=fffffa8008a47ad0
  82. rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
  83. rip=fffff80002d540a2 rsp=fffff880098cd8b0 rbp=0000000000000000
  84. r8=0000000000000ced r9=fffff8a0037a2040 r10=0000000000000000
  85. r11=fffff8a0037a87a8 r12=0000000000000000 r13=0000000000000000
  86. r14=0000000000000000 r15=0000000000000000
  87. iopl=0 nv up ei pl zr na po nc
  88. nt!MiRelocateImagePfn+0x3a:
  89. fffff800`02d540a2 4d3923 cmp qword ptr [r11],r12 ds:a850:fffff8a0`037a87a8=0000000000000000
  90. Resetting default scope
  91.  
  92. LAST_CONTROL_TRANSFER: from fffff80002af5438 to fffff80002a81f00
  93.  
  94. STACK_TEXT:
  95. fffff880`098cd408 fffff800`02af5438 : 00000000`0000007a fffff6fc`5001bd40 ffffffff`c0000185 00000000`bdd2b880 : nt!KeBugCheckEx
  96. fffff880`098cd410 fffff800`02a73d8b : fffffa80`08894010 fffff880`098cd580 fffff800`02c0cb40 00800000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34cde
  97. fffff880`098cd4f0 fffff800`02a9cda4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff8a0`034105c0 : nt!MiIssueHardFault+0x28b
  98. fffff880`098cd5c0 fffff800`02a7ffee : 00000000`00000000 00000000`000095de 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x11c4
  99. fffff880`098cd720 fffff800`02d540a2 : fffffa80`059c0e90 fffffa80`059c0e00 fffffa80`08a60000 fffffa80`08a845c1 : nt!KiPageFault+0x16e
  100. fffff880`098cd8b0 fffff800`02a734ac : fffffa80`001c19a0 fffffa80`059c0f50 00000000`00000000 fffffa80`08410400 : nt!MiRelocateImagePfn+0x3a
  101. fffff880`098cd910 fffff800`02a73d8b : fffffa80`059c0e90 fffff880`098cda80 fffffa80`08a4dec8 fffffa80`08a4db30 : nt!MiWaitForInPageComplete+0x89c
  102. fffff880`098cd9f0 fffff800`02a9d09b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
  103. fffff880`098cdac0 fffff800`02a7ffee : 00000000`00000000 00000000`006b3dd4 00000000`00000001 000007fe`fe6bd900 : nt!MmAccessFault+0x14bb
  104. fffff880`098cdc20 00000000`76d6548f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
  105. 00000000`009be4e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d6548f
  106.  
  107.  
  108. STACK_COMMAND: kb
  109.  
  110. FOLLOWUP_IP:
  111. nt! ?? ::FNODOBFM::`string'+34cde
  112. fffff800`02af5438 cc int 3
  113.  
  114. SYMBOL_STACK_INDEX: 1
  115.  
  116. SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34cde
  117.  
  118. FOLLOWUP_NAME: MachineOwner
  119.  
  120. MODULE_NAME: nt
  121.  
  122. IMAGE_NAME: ntkrnlmp.exe
  123.  
  124. DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
  125.  
  126. FAILURE_BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
  127.  
  128. BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
  129.  
  130. Followup: MachineOwner
  131. ---------
2
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\021910-20326-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows 7 Kernel Version 7600 MP (8 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
  13. Machine Name:
  14. Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
  15. Debug session time: Fri Feb 19 19:26:19.431 2010 (GMT+1)
  16. System Uptime: 0 days 20:37:43.461
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. ................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. ......
  24. *******************************************************************************
  25. * *
  26. * Bugcheck Analysis *
  27. * *
  28. *******************************************************************************
  29.  
  30. Use !analyze -v to get detailed debugging information.
  31.  
  32. BugCheck 7A, {fffff6fc5001bd40, ffffffffc0000185, bdd2b880, fffff8a0037a87a8}
  33.  
  34. Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )
  35.  
  36. Followup: MachineOwner
  37. ---------
  38.  
  39. 3: kd> !analyze -v
  40. *******************************************************************************
  41. * *
  42. * Bugcheck Analysis *
  43. * *
  44. *******************************************************************************
  45.  
  46. KERNEL_DATA_INPAGE_ERROR (7a)
  47. The requested page of kernel data could not be read in. Typically caused by
  48. a bad block in the paging file or disk controller error. Also see
  49. KERNEL_STACK_INPAGE_ERROR.
  50. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
  51. it means the disk subsystem has experienced a failure.
  52. If the error status is 0xC000009A, then it means the request failed because
  53. a filesystem failed to make forward progress.
  54. Arguments:
  55. Arg1: fffff6fc5001bd40, lock type that was held (value 1,2,3, or PTE address)
  56. Arg2: ffffffffc0000185, error status (normally i/o status code)
  57. Arg3: 00000000bdd2b880, current process (virtual address for lock type 3, or PTE)
  58. Arg4: fffff8a0037a87a8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
  59.  
  60. Debugging Details:
  61. ------------------
  62.  
  63.  
  64. ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
  65.  
  66. DISK_HARDWARE_ERROR: There was error with disk hardware
  67.  
  68. BUGCHECK_STR: 0x7a_c0000185
  69.  
  70. CUSTOMER_CRASH_COUNT: 1
  71.  
  72. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  73.  
  74. PROCESS_NAME: wmpnetwk.exe
  75.  
  76. CURRENT_IRQL: 0
  77.  
  78. TRAP_FRAME: fffff880098cd720 -- (.trap 0xfffff880098cd720)
  79. NOTE: The trap frame does not contain all registers.
  80. Some register values may be zeroed or incorrect.
  81. rax=fffffa80059c0e90 rbx=0000000000000000 rcx=fffffa8008a47ad0
  82. rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
  83. rip=fffff80002d540a2 rsp=fffff880098cd8b0 rbp=0000000000000000
  84. r8=0000000000000ced r9=fffff8a0037a2040 r10=0000000000000000
  85. r11=fffff8a0037a87a8 r12=0000000000000000 r13=0000000000000000
  86. r14=0000000000000000 r15=0000000000000000
  87. iopl=0 nv up ei pl zr na po nc
  88. nt!MiRelocateImagePfn+0x3a:
  89. fffff800`02d540a2 4d3923 cmp qword ptr [r11],r12 ds:a850:fffff8a0`037a87a8=0000000000000000
  90. Resetting default scope
  91.  
  92. LAST_CONTROL_TRANSFER: from fffff80002af5438 to fffff80002a81f00
  93.  
  94. STACK_TEXT:
  95. fffff880`098cd408 fffff800`02af5438 : 00000000`0000007a fffff6fc`5001bd40 ffffffff`c0000185 00000000`bdd2b880 : nt!KeBugCheckEx
  96. fffff880`098cd410 fffff800`02a73d8b : fffffa80`08894010 fffff880`098cd580 fffff800`02c0cb40 00800000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34cde
  97. fffff880`098cd4f0 fffff800`02a9cda4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff8a0`034105c0 : nt!MiIssueHardFault+0x28b
  98. fffff880`098cd5c0 fffff800`02a7ffee : 00000000`00000000 00000000`000095de 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x11c4
  99. fffff880`098cd720 fffff800`02d540a2 : fffffa80`059c0e90 fffffa80`059c0e00 fffffa80`08a60000 fffffa80`08a845c1 : nt!KiPageFault+0x16e
  100. fffff880`098cd8b0 fffff800`02a734ac : fffffa80`001c19a0 fffffa80`059c0f50 00000000`00000000 fffffa80`08410400 : nt!MiRelocateImagePfn+0x3a
  101. fffff880`098cd910 fffff800`02a73d8b : fffffa80`059c0e90 fffff880`098cda80 fffffa80`08a4dec8 fffffa80`08a4db30 : nt!MiWaitForInPageComplete+0x89c
  102. fffff880`098cd9f0 fffff800`02a9d09b : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
  103. fffff880`098cdac0 fffff800`02a7ffee : 00000000`00000000 00000000`006b3dd4 00000000`00000001 000007fe`fe6bd900 : nt!MmAccessFault+0x14bb
  104. fffff880`098cdc20 00000000`76d6548f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
  105. 00000000`009be4e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d6548f
  106.  
  107.  
  108. STACK_COMMAND: kb
  109.  
  110. FOLLOWUP_IP:
  111. nt! ?? ::FNODOBFM::`string'+34cde
  112. fffff800`02af5438 cc int 3
  113.  
  114. SYMBOL_STACK_INDEX: 1
  115.  
  116. SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34cde
  117.  
  118. FOLLOWUP_NAME: MachineOwner
  119.  
  120. MODULE_NAME: nt
  121.  
  122. IMAGE_NAME: ntkrnlmp.exe
  123.  
  124. DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
  125.  
  126. FAILURE_BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
  127.  
  128. BUCKET_ID: X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+34cde
  129.  
  130. Followup: MachineOwner
  131. ---------
3
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\022110-18517-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows 7 Kernel Version 7600 MP (8 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
  13. Machine Name:
  14. Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02ca5e50
  15. Debug session time: Sun Feb 21 19:14:11.640 2010 (GMT+1)
  16. System Uptime: 0 days 0:08:27.671
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. ...............................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. ...
  24. Unable to load image \SystemRoot\system32\DRIVERS\iaStorV.sys, Win32 error 0n2
  25. *** WARNING: Unable to verify timestamp for iaStorV.sys
  26. *** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
  27. *******************************************************************************
  28. * *
  29. * Bugcheck Analysis *
  30. * *
  31. *******************************************************************************
  32.  
  33. Use !analyze -v to get detailed debugging information.
  34.  
  35. BugCheck 1000007E, {ffffffffc0000005, fffff8800124435d, fffff88003932858, fffff880039320b0}
  36.  
  37. Probably caused by : iaStorV.sys ( iaStorV+2b35d )
  38.  
  39. Followup: MachineOwner
  40. ---------
  41.  
  42. 5: kd> !analyze -v
  43. *******************************************************************************
  44. * *
  45. * Bugcheck Analysis *
  46. * *
  47. *******************************************************************************
  48.  
  49. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  50. This is a very common bugcheck. Usually the exception address pinpoints
  51. the driver/function that caused the problem. Always note this address
  52. as well as the link date of the driver/image that contains this address.
  53. Some common problems are exception code 0x80000003. This means a hard
  54. coded breakpoint or assertion was hit, but this system was booted
  55. /NODEBUG. This is not supposed to happen as developers should never have
  56. hardcoded breakpoints in retail code, but ...
  57. If this happens, make sure a debugger gets connected, and the
  58. system is booted /DEBUG. This will let us see why this breakpoint is
  59. happening.
  60. Arguments:
  61. Arg1: ffffffffc0000005, The exception code that was not handled
  62. Arg2: fffff8800124435d, The address that the exception occurred at
  63. Arg3: fffff88003932858, Exception Record Address
  64. Arg4: fffff880039320b0, Context Record Address
  65.  
  66. Debugging Details:
  67. ------------------
  68.  
  69.  
  70. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  71.  
  72. FAULTING_IP:
  73. iaStorV+2b35d
  74. fffff880`0124435d 88907e010000 mov byte ptr [rax+17Eh],dl
  75.  
  76. EXCEPTION_RECORD: fffff88003932858 -- (.exr 0xfffff88003932858)
  77. ExceptionAddress: fffff8800124435d (iaStorV+0x000000000002b35d)
  78. ExceptionCode: c0000005 (Access violation)
  79. ExceptionFlags: 00000000
  80. NumberParameters: 2
  81. Parameter[0]: 0000000000000001
  82. Parameter[1]: 000000000000017e
  83. Attempt to write to address 000000000000017e
  84.  
  85. CONTEXT: fffff880039320b0 -- (.cxr 0xfffff880039320b0)
  86. rax=0000000000000000 rbx=fffffa8006bbc398 rcx=0000000000000001
  87. rdx=0000000000000001 rsi=fffffa80062edc00 rdi=fffffa800681f818
  88. rip=fffff8800124435d rsp=fffff88003932a98 rbp=0000000000000080
  89. r8=fffffa800681f760 r9=0000000000000003 r10=0000000000000120
  90. r11=fffffa8006bbc398 r12=0000000000000000 r13=fffff88001249e64
  91. r14=0000000000000000 r15=fffff880009b7040
  92. iopl=0 nv up ei pl zr na po nc
  93. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
  94. iaStorV+0x2b35d:
  95. fffff880`0124435d 88907e010000 mov byte ptr [rax+17Eh],dl ds:002b:00000000`0000017e=??
  96. Resetting default scope
  97.  
  98. CUSTOMER_CRASH_COUNT: 1
  99.  
  100. PROCESS_NAME: System
  101.  
  102. CURRENT_IRQL: 0
  103.  
  104. ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  105.  
  106. EXCEPTION_PARAMETER1: 0000000000000001
  107.  
  108. EXCEPTION_PARAMETER2: 000000000000017e
  109.  
  110. WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d100e0
  111. 000000000000017e
  112.  
  113. FOLLOWUP_IP:
  114. iaStorV+2b35d
  115. fffff880`0124435d 88907e010000 mov byte ptr [rax+17Eh],dl
  116.  
  117. BUGCHECK_STR: 0x7E
  118.  
  119. DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
  120.  
  121. LAST_CONTROL_TRANSFER: from fffff88001244858 to fffff8800124435d
  122.  
  123. STACK_TEXT:
  124. fffff880`03932a98 fffff880`01244858 : fffffa80`062edcf0 00000000`00000080 fffffa80`06bdd798 fffff880`01238b74 : iaStorV+0x2b35d
  125. fffff880`03932aa0 fffffa80`062edcf0 : 00000000`00000080 fffffa80`06bdd798 fffff880`01238b74 fffff880`009b7040 : iaStorV+0x2b858
  126. fffff880`03932aa8 00000000`00000080 : fffffa80`06bdd798 fffff880`01238b74 fffff880`009b7040 00000000`00000000 : 0xfffffa80`062edcf0
  127. fffff880`03932ab0 fffffa80`06bdd798 : fffff880`01238b74 fffff880`009b7040 00000000`00000000 fffffa80`062edce0 : 0x80
  128. fffff880`03932ab8 fffff880`01238b74 : fffff880`009b7040 00000000`00000000 fffffa80`062edce0 fffffa80`074b9b40 : 0xfffffa80`06bdd798
  129. fffff880`03932ac0 fffff880`009b7040 : 00000000`00000000 fffffa80`062edce0 fffffa80`074b9b40 fffffa80`062edc00 : iaStorV+0x1fb74
  130. fffff880`03932ac8 00000000`00000000 : fffffa80`062edce0 fffffa80`074b9b40 fffffa80`062edc00 00000000`00000080 : 0xfffff880`009b7040
  131.  
  132.  
  133. SYMBOL_STACK_INDEX: 0
  134.  
  135. SYMBOL_NAME: iaStorV+2b35d
  136.  
  137. FOLLOWUP_NAME: MachineOwner
  138.  
  139. MODULE_NAME: iaStorV
  140.  
  141. IMAGE_NAME: iaStorV.sys
  142.  
  143. DEBUG_FLR_IMAGE_TIMESTAMP: 49dcd76d
  144.  
  145. STACK_COMMAND: .cxr 0xfffff880039320b0 ; kb
  146.  
  147. FAILURE_BUCKET_ID: X64_0x7E_iaStorV+2b35d
  148.  
  149. BUCKET_ID: X64_0x7E_iaStorV+2b35d
  150.  
  151. Followup: MachineOwner
  152. ---------
4
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\022210-23415-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows 7 Kernel Version 7600 MP (8 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
  13. Machine Name:
  14. Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c94e50
  15. Debug session time: Mon Feb 22 21:36:54.587 2010 (GMT+1)
  16. System Uptime: 0 days 0:22:44.618
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. ...............................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. ...
  24. Unable to load image \SystemRoot\system32\DRIVERS\iaStorV.sys, Win32 error 0n2
  25. *** WARNING: Unable to verify timestamp for iaStorV.sys
  26. *** ERROR: Module load completed but symbols could not be loaded for iaStorV.sys
  27. *******************************************************************************
  28. * *
  29. * Bugcheck Analysis *
  30. * *
  31. *******************************************************************************
  32.  
  33. Use !analyze -v to get detailed debugging information.
  34.  
  35. BugCheck 1000007E, {ffffffffc0000005, fffff8800130835d, fffff88003932818, fffff88003932070}
  36.  
  37. Probably caused by : iaStorV.sys ( iaStorV+2b35d )
  38.  
  39. Followup: MachineOwner
  40. ---------
  41.  
  42. 2: kd> !analyze -v
  43. *******************************************************************************
  44. * *
  45. * Bugcheck Analysis *
  46. * *
  47. *******************************************************************************
  48.  
  49. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  50. This is a very common bugcheck. Usually the exception address pinpoints
  51. the driver/function that caused the problem. Always note this address
  52. as well as the link date of the driver/image that contains this address.
  53. Some common problems are exception code 0x80000003. This means a hard
  54. coded breakpoint or assertion was hit, but this system was booted
  55. /NODEBUG. This is not supposed to happen as developers should never have
  56. hardcoded breakpoints in retail code, but ...
  57. If this happens, make sure a debugger gets connected, and the
  58. system is booted /DEBUG. This will let us see why this breakpoint is
  59. happening.
  60. Arguments:
  61. Arg1: ffffffffc0000005, The exception code that was not handled
  62. Arg2: fffff8800130835d, The address that the exception occurred at
  63. Arg3: fffff88003932818, Exception Record Address
  64. Arg4: fffff88003932070, Context Record Address
  65.  
  66. Debugging Details:
  67. ------------------
  68.  
  69.  
  70. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  71.  
  72. FAULTING_IP:
  73. iaStorV+2b35d
  74. fffff880`0130835d 88907e010000 mov byte ptr [rax+17Eh],dl
  75.  
  76. EXCEPTION_RECORD: fffff88003932818 -- (.exr 0xfffff88003932818)
  77. ExceptionAddress: fffff8800130835d (iaStorV+0x000000000002b35d)
  78. ExceptionCode: c0000005 (Access violation)
  79. ExceptionFlags: 00000000
  80. NumberParameters: 2
  81. Parameter[0]: 0000000000000001
  82. Parameter[1]: 000000000000017e
  83. Attempt to write to address 000000000000017e
  84.  
  85. CONTEXT: fffff88003932070 -- (.cxr 0xfffff88003932070)
  86. rax=0000000000000000 rbx=fffffa8006955890 rcx=0000000000000000
  87. rdx=0000000000000000 rsi=fffffa80062e7cf0 rdi=fffffa8006487800
  88. rip=fffff8800130835d rsp=fffff88003932a58 rbp=0000000000000080
  89. r8=fffffa8006487760 r9=0000000000000000 r10=0000000000000048
  90. r11=fffffa8006955890 r12=0000000000000000 r13=fffff8800130de64
  91. r14=0000000000000000 r15=fffff880009b7040
  92. iopl=0 nv up ei pl zr na po nc
  93. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
  94. iaStorV+0x2b35d:
  95. fffff880`0130835d 88907e010000 mov byte ptr [rax+17Eh],dl ds:002b:00000000`0000017e=??
  96. Resetting default scope
  97.  
  98. CUSTOMER_CRASH_COUNT: 1
  99.  
  100. PROCESS_NAME: System
  101.  
  102. CURRENT_IRQL: 0
  103.  
  104. ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  105.  
  106. EXCEPTION_PARAMETER1: 0000000000000001
  107.  
  108. EXCEPTION_PARAMETER2: 000000000000017e
  109.  
  110. WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cff0e0
  111. 000000000000017e
  112.  
  113. FOLLOWUP_IP:
  114. iaStorV+2b35d
  115. fffff880`0130835d 88907e010000 mov byte ptr [rax+17Eh],dl
  116.  
  117. BUGCHECK_STR: 0x7E
  118.  
  119. DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
  120.  
  121. LAST_CONTROL_TRANSFER: from fffff88001308858 to fffff8800130835d
  122.  
  123. STACK_TEXT:
  124. fffff880`03932a58 fffff880`01308858 : 00000000`00000002 00000000`00000000 fffffa80`07703a2b fffff800`02acb516 : iaStorV+0x2b35d
  125. fffff880`03932a60 00000000`00000002 : 00000000`00000000 fffffa80`07703a2b fffff800`02acb516 fffff880`009b7040 : iaStorV+0x2b858
  126. fffff880`03932a68 00000000`00000000 : fffffa80`07703a2b fffff800`02acb516 fffff880`009b7040 00000000`00000000 : 0x2
  127.  
  128.  
  129. SYMBOL_STACK_INDEX: 0
  130.  
  131. SYMBOL_NAME: iaStorV+2b35d
  132.  
  133. FOLLOWUP_NAME: MachineOwner
  134.  
  135. MODULE_NAME: iaStorV
  136.  
  137. IMAGE_NAME: iaStorV.sys
  138.  
  139. DEBUG_FLR_IMAGE_TIMESTAMP: 49dcd76d
  140.  
  141. STACK_COMMAND: .cxr 0xfffff88003932070 ; kb
  142.  
  143. FAILURE_BUCKET_ID: X64_0x7E_iaStorV+2b35d
  144.  
  145. BUCKET_ID: X64_0x7E_iaStorV+2b35d
  146.  
  147. Followup: MachineOwner
  148. ---------
5
Dump non analizzabile con il tool microsoft. Inserisco quanto ottenuto con Blue Screen view.

  1. Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 Caused By Driver Caused By Address File Description Product Name Company File Version Processor Computer Name Full Path Processors Count Major Version Minor Version 032410-17160-01.dmp25/03/2010 00:04:20SYSTEM_THREAD_EXCEPTION_NOT_HANDLED0x1000007effffffff`c0000005fffff880`012cc2edfffff880`03b2b648fffff880`03b2aea0iaStor.sysiaStor.sys+2b7ecx64C:\Windows\minidump\032410-17160-01.dmp8157600
  2.  
  3. [urlExt=http://img24.imageshack.us/i/captureqj.png/][IMG]http://img24.imageshack.us/img24/7610/captureqj.png[/IMG][/urlExt]

6
  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\032810-21684-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows 7 Kernel Version 7600 MP (8 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
  13. Machine Name:
  14. Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50
  15. Debug session time: Sun Mar 28 19:25:19.584 2010 (GMT+2)
  16. System Uptime: 0 days 1:59:12.615
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. .......................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. ......
  24. *******************************************************************************
  25. * *
  26. * Bugcheck Analysis *
  27. * *
  28. *******************************************************************************
  29.  
  30. Use !analyze -v to get detailed debugging information.
  31.  
  32. BugCheck 101, {19, 0, fffff880009b2180, 4}
  33.  
  34. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
  35.  
  36. Followup: MachineOwner
  37. ---------
  38.  
  39. 0: kd> !analyze -v
  40. *******************************************************************************
  41. * *
  42. * Bugcheck Analysis *
  43. * *
  44. *******************************************************************************
  45.  
  46. CLOCK_WATCHDOG_TIMEOUT (101)
  47. An expected clock interrupt was not received on a secondary processor in an
  48. MP system within the allocated interval. This indicates that the specified
  49. processor is hung and not processing interrupts.
  50. Arguments:
  51. Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
  52. Arg2: 0000000000000000, 0.
  53. Arg3: fffff880009b2180, The PRCB address of the hung processor.
  54. Arg4: 0000000000000004, 0.
  55.  
  56. Debugging Details:
  57. ------------------
  58.  
  59.  
  60. BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
  61.  
  62. CUSTOMER_CRASH_COUNT: 1
  63.  
  64. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  65.  
  66. PROCESS_NAME: System
  67.  
  68. CURRENT_IRQL: d
  69.  
  70. STACK_TEXT:
  71. fffff800`00b9c088 fffff800`02a80443 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`009b2180 : nt!KeBugCheckEx
  72. fffff800`00b9c090 fffff800`02adc5f7 : 00000000`00000000 fffff800`00000004 00000000`00002710 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
  73. fffff800`00b9c120 fffff800`02a23895 : fffff800`02a48460 fffff800`00b9c2d0 fffff800`02a48460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
  74. fffff800`00b9c220 fffff800`02ad03f3 : 00000000`766b7ed2 fffff800`00b9c2d0 fffffa80`06373118 fffff800`02c4f080 : hal!HalpHpetClockInterrupt+0x8d
  75. fffff800`00b9c250 fffff800`02a95aa0 : fffff800`00b9cc00 00000000`00000000 fffff800`00b9c500 00000000`00000801 : nt!KiInterruptDispatchNoLock+0x163
  76. fffff800`00b9c3e0 fffff800`02adcba9 : 00000000`00000002 fffff880`01575abd 00000000`00000000 fffffa80`063bd008 : nt!KxWaitForSpinLockAndAcquire+0x20
  77. fffff800`00b9c410 fffff880`031a8f3a : fffffa80`08eb2cf0 fffff800`02c4f080 fffff800`00b9c4c0 fffffa80`063721a0 : nt!KeAcquireSpinLockRaiseToDpc+0x89
  78. fffff800`00b9c460 fffff880`031aa131 : fffffa80`08bf21a0 fffff880`031b8e7d fffffa80`0a14d7a0 fffffa80`06372050 : USBPORT!USBPORT_AcquireEpListLock+0x2e
  79. fffff800`00b9c490 fffff880`031c3723 : fffffa80`0a14d7a0 fffffa80`063721a0 fffffa80`06372050 fffffa80`0b285010 : USBPORT!USBPORT_ReferenceEndpoint+0x29
  80. fffff800`00b9c4e0 fffff880`031cc2e4 : fffffa80`0b285010 fffffa80`0b285010 00000000`00000001 fffffa80`0b285010 : USBPORT!USBPORT_Ev_Rh_IntrEp_Invalidate+0xf3
  81. fffff800`00b9c540 fffff800`02adffa6 : fffff800`00b9c600 00000000`00000001 00000000`00000000 00000000`00000000 : USBPORT!USBPORT_AsyncTimerDpc+0xb8
  82. fffff800`00b9c570 fffff800`02adf326 : fffffa80`0b285030 00000000`0006fc08 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
  83. fffff800`00b9c5e0 fffff800`02adfe7e : 00000010`a0353077 fffff800`00b9cc58 00000000`0006fc08 fffff800`02c4f388 : nt!KiProcessExpiredTimerList+0xc6
  84. fffff800`00b9cc30 fffff800`02adf697 : 00000004`5601a5c1 00000004`0006fc08 00000004`5601a533 00000000`00000008 : nt!KiTimerExpiration+0x1be
  85. fffff800`00b9ccd0 fffff800`02adc6fa : fffff800`02c4ce80 fffff800`02c5ac40 00000000`00000000 fffffa80`061f30a0 : nt!KiRetireDpcList+0x277
  86. fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
  87.  
  88.  
  89. STACK_COMMAND: kb
  90.  
  91. SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
  92.  
  93. FOLLOWUP_NAME: MachineOwner
  94.  
  95. MODULE_NAME: Unknown_Module
  96.  
  97. IMAGE_NAME: Unknown_Image
  98.  
  99. DEBUG_FLR_IMAGE_TIMESTAMP: 0
  100.  
  101. FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
  102.  
  103. BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
  104.  
  105. Followup: MachineOwner
  106. ---------



Any suggestion is appreciated.
I seriously hope to solve this problem.

Thank you very much

I Spot the Not

More about : solve bsod issue

April 8, 2010 8:10:52 AM

I'm sorry, but i cannot edit the message.
The BSOD 5 Italian sentence means: Cannot analyze Dump whit Microsoft debug tool. Analyzed with Blue Screen view.
m
0
l
April 8, 2010 8:27:02 AM

Try here http://aumha.org/a/stop.htm

Your errors are 7A, 7E, and 101. Points to a Hardware incompatibility, perhaps a wrong jumper setting, etc.
m
0
l
Related resources
a b Ĉ ASUS
a b V Motherboard
April 8, 2010 8:31:52 AM

Quote:
Problem:
I had and i'm still having BSOD or freeze while surfing, playing, using photoshop and sometime (rarely) doing nothing.
BSOD tipically is verified after the system slows down and the mouse pointer starts moving slowly.
In addition to this, if I save a work while the system is "telling me" that it is going to freeze, it won't be saved: i mean that it appears to be saved (and icon is present in the folder) but the file is not available after bsod.
Finally, raid disks appear to have errors when restarting after BSOD (intel Rapid Storage Technology can correct these errors).


Try using all new SATA cables connecting the HD to MB headers. Replace all of the ones you are currently using with new.
m
0
l
April 8, 2010 9:51:00 AM

why do you suggest this? Is there any evolution in sata cables?
m
0
l
a b V Motherboard
April 8, 2010 3:36:08 PM

The Velociraptors are notorious for having problems. I have 3 of them and have had to get 2 replaced for the very same issue. They send you back a different version of the drive. There is a known bios issue for the hard drives failing after 49 hrs of use.
m
0
l
April 8, 2010 5:22:23 PM

Thankyou for the answer.
I tried with the raptors (i used them for years with a DFI motherboard without any problem), and i got BSODs eg. first 3 but than i definely switch to western digital re3 but i still have problems.
Does WD caviar re3 320GB have any incompatibility issue?
I also tried an old maxtor but i had BSOD too.

Finally i tried Linux environment on the single maxtor but it crashes
m
0
l
April 8, 2010 8:50:17 PM

Update: New BSOD report, different from previous ones:

7

  1. Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\040810-16364-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: SRV*c:\Windows\symbols*http://msdl.microsoft.com/download/symbols
  9. Executable search path is:
  10. Windows 7 Kernel Version 7600 MP (8 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS
  12. Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
  13. Machine Name:
  14. Kernel base = 0xfffff800`02a08000 PsLoadedModuleList = 0xfffff800`02c45e50
  15. Debug session time: Thu Apr 8 21:48:05.359 2010 (GMT+2)
  16. System Uptime: 0 days 23:06:09.390
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. ......................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. .......
  24. *******************************************************************************
  25. * *
  26. * Bugcheck Analysis *
  27. * *
  28. *******************************************************************************
  29.  
  30. Use !analyze -v to get detailed debugging information.
  31.  
  32. BugCheck 3B, {c0000005, 96000000008, fffff8800989f850, 0}
  33.  
  34. Probably caused by : ntkrnlmp.exe ( nt!HvWriteHive+4e1 )
  35.  
  36. Followup: MachineOwner
  37. ---------
  38.  
  39. 6: kd> !analyze -v
  40. *******************************************************************************
  41. * *
  42. * Bugcheck Analysis *
  43. * *
  44. *******************************************************************************
  45.  
  46. SYSTEM_SERVICE_EXCEPTION (3b)
  47. An exception happened while executing a system service routine.
  48. Arguments:
  49. Arg1: 00000000c0000005, Exception code that caused the bugcheck
  50. Arg2: 0000096000000008, Address of the exception record for the exception that caused the bugcheck
  51. Arg3: fffff8800989f850, Address of the context record for the exception that caused the bugcheck
  52. Arg4: 0000000000000000, zero.
  53.  
  54. Debugging Details:
  55. ------------------
  56.  
  57.  
  58. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  59.  
  60. FAULTING_IP:
  61. +13
  62. 00000960`00000008 ?? ???
  63.  
  64. CONTEXT: fffff8800989f850 -- (.cxr 0xfffff8800989f850)
  65. rax=fffff880098a0330 rbx=fffff8a008990010 rcx=fffff8a008990010
  66. rdx=0000000000000000 rsi=fffff8a000fd9000 rdi=0000000000000000
  67. rip=0000096000000008 rsp=fffff880098a0238 rbp=fffff880098a05f0
  68. r8=fffff880098a0298 r9=0000000000000001 r10=fffff80002bf37c0
  69. r11=fffffa8006515320 r12=fffff880098a0388 r13=fffff8a008e60180
  70. r14=0000000000000200 r15=000000000095e000
  71. iopl=0 nv up ei pl zr na po nc
  72. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
  73. 00000960`00000008 ?? ???
  74. Resetting default scope
  75.  
  76. CUSTOMER_CRASH_COUNT: 1
  77.  
  78. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  79.  
  80. BUGCHECK_STR: 0x3B
  81.  
  82. PROCESS_NAME: TrustedInstall
  83.  
  84. CURRENT_IRQL: 0
  85.  
  86. LAST_CONTROL_TRANSFER: from fffff80002e3d001 to 0000096000000008
  87.  
  88. STACK_TEXT:
  89. fffff880`098a0238 fffff800`02e3d001 : 00000000`00000960 fffff880`098a05f0 fffff8a0`38334d43 00000000`00000719 : 0x960`00000008
  90. fffff880`098a0240 fffff800`02ddf701 : fffff8a0`00000001 fffff880`098a0388 01cad694`00000000 fffff8a0`00000200 : nt!HvWriteHive+0x4e1
  91. fffff880`098a0320 fffff800`02cfa12a : 00000000`00000000 00000000`00000002 fffff8a0`08990bb8 00000000`00000001 : nt! ?? ::NNGAKEGL::`string'+0x5b698
  92. fffff880`098a0380 fffff800`02cfacb9 : fffff880`098a0520 fffff880`098a05f0 ffffffff`8000166c fffff880`098a0a28 : nt!CmpInitializeHive+0x4a6
  93. fffff880`098a0470 fffff800`02cfdb9e : 00000000`00000000 00000000`00000000 fffff880`098a07d8 fffff880`098a07d1 : nt!CmpInitHiveFromFile+0x249
  94. fffff880`098a0590 fffff800`02d00517 : 00000000`00000000 00000000`00000000 00000000`00000000 0000007f`fffffff8 : nt!CmpCmdHiveOpen+0x8a
  95. fffff880`098a0780 fffff800`02cfc273 : 00000000`00000020 fffff880`098a0aa0 00000000`00000000 00000000`00000021 : nt!CmLoadKey+0x1a7
  96. fffff880`098a0970 fffff800`02cfe510 : 00000980`00000000 00000000`013be8f8 00000000`00000000 00000000`00000000 : nt!NtLoadKeyEx+0x4c5
  97. fffff880`098a0bd0 fffff800`02a79153 : 00000000`00000008 00000000`013be8c8 00000000`013be801 00000000`00000001 : nt!NtLoadKey+0x24
  98. fffff880`098a0c20 00000000`77ad0cba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
  99. 00000000`013be7f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ad0cba
  100.  
  101.  
  102. FOLLOWUP_IP:
  103. nt!HvWriteHive+4e1
  104. fffff800`02e3d001 403ac7 cmp al,dil
  105.  
  106. SYMBOL_STACK_INDEX: 1
  107.  
  108. SYMBOL_NAME: nt!HvWriteHive+4e1
  109.  
  110. FOLLOWUP_NAME: MachineOwner
  111.  
  112. MODULE_NAME: nt
  113.  
  114. IMAGE_NAME: ntkrnlmp.exe
  115.  
  116. DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
  117.  
  118. STACK_COMMAND: .cxr 0xfffff8800989f850 ; kb
  119.  
  120. FAILURE_BUCKET_ID: X64_0x3B_nt!HvWriteHive+4e1
  121.  
  122. BUCKET_ID: X64_0x3B_nt!HvWriteHive+4e1
  123.  
  124. Followup: MachineOwner
  125. ---------
  126.  
  127. 6: kd> .cxr 0xfffff8800989f850
  128. rax=fffff880098a0330 rbx=fffff8a008990010 rcx=fffff8a008990010
  129. rdx=0000000000000000 rsi=fffff8a000fd9000 rdi=0000000000000000
  130. rip=0000096000000008 rsp=fffff880098a0238 rbp=fffff880098a05f0
  131. r8=fffff880098a0298 r9=0000000000000001 r10=fffff80002bf37c0
  132. r11=fffffa8006515320 r12=fffff880098a0388 r13=fffff8a008e60180
  133. r14=0000000000000200 r15=000000000095e000
  134. iopl=0 nv up ei pl zr na po nc
  135. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
  136. 00000960`00000008 ?? ???



now trying with new sata cables as told by badge
m
0
l
April 19, 2010 2:12:15 PM

Hi everyone.
Problem not solved jet, even if with SATA new cables.

I tryed changing the video card, from my Sapphire HD3870X2 to my old Sapphire X800XL. It seems to work.
Does anybody knows if Rampage II Gene has some incompatibility issue with Sapphire graphic cards or with HD38XX series?

Thanks
m
0
l
!