locked
windows 7 blue screen RRS feed

  • Question

  • Hi, having issues with windows 7 ultimate x64. Getting random blue screens.

    At some point i started using my ubuntu linux installation more and also had a kernel crash there. So did some memory testing with memtest86 and found some issues. I disassembled my computer, cleaned it up and put it back together again. Not a single problem in ubuntu or memtest86 error ever since, regardless of the many hours i have tested.

    So far i have reinstalled my windows and used occt to do some testing but i have found nothing in particular. There is no specific task that can make the crash happen. I can play hours of the most intense game with no problem, only to get a BSOD when i stop the game and just start browsing the net. Or simply get to the computer in the morning to find it in the login screen after a BSOD. I have concluded that there is probably something wrong with my hardware. But i need to determine what is the problem so i can replace it. But it looks like almost every error is different from the one before. Most of my minidumps are not related to a specific driver, but to the kernel itself. Here are the last two:


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

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff800035be28f, Address of the exception record for the exception that c
    aused the bugcheck
    Arg3: fffff8800baaf0b0, Address of the context record for the exception that cau
    sed the bugcheck
    Arg4: 0000000000000000, zero.

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced me
    mory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    nt!IoRemoveIoCompletion+9f
    fffff800`035be28f 8b4b10          mov     ecx,dword ptr [rbx+10h]

    CONTEXT:  fffff8800baaf0b0 -- (.cxr 0xfffff8800baaf0b0)
    rax=0000000000000000 rbx=ff00fa800a07a470 rcx=0000000000000000
    rdx=00000000000007ff rsi=0000000000000001 rdi=0000000000000000
    rip=fffff800035be28f rsp=fffff8800baafa90 rbp=fffff8800baafca0
     r8=fffff8000325b000  r9=0000000000000000 r10=fffffffffffffffe
    r11=00000000002f12d0 r12=0000000000000000 r13=fffff8800baafba8
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz ac po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010296
    nt!IoRemoveIoCompletion+0x9f:
    fffff800`035be28f 8b4b10          mov     ecx,dword ptr [rbx+10h] ds:002b:ff00fa
    80`0a07a480=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    PROCESS_NAME:  MsMpEng.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff800032c53d6 to fffff800035be28f

    STACK_TEXT:
    fffff880`0baafa90 fffff800`032c53d6 : 00000000`00000000 fffff880`0baafba8 fffff8
    80`0baafbc8 00000000`00000001 : nt!IoRemoveIoCompletion+0x9f
    fffff880`0baafb20 fffff800`032d9453 : fffffa80`06c73b50 00000000`776b45c0 000000
    00`00000000 fffffa80`08da9301 : nt!NtWaitForWorkViaWorkerFactory+0x285
    fffff880`0baafc20 00000000`77602c1a : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0157f858 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : 0x77602c1a


    FOLLOWUP_IP:
    nt!IoRemoveIoCompletion+9f
    fffff800`035be28f 8b4b10          mov     ecx,dword ptr [rbx+10h]

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!IoRemoveIoCompletion+9f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

    STACK_COMMAND:  .cxr 0xfffff8800baaf0b0 ; kb

    FAILURE_BUCKET_ID:  X64_0x3B_nt!IoRemoveIoCompletion+9f

    BUCKET_ID:  X64_0x3B_nt!IoRemoveIoCompletion+9f

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


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

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff800032d00c5, Address of the exception record for the exception that c
    aused the bugcheck
    Arg3: fffff8800ec5fde0, Address of the context record for the exception that cau
    sed the bugcheck
    Arg4: 0000000000000000, zero.

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced me
    mory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    nt!ExpInterlockedPopEntrySListFault16+0
    fffff800`032d00c5 498b08          mov     rcx,qword ptr [r8]

    CONTEXT:  fffff8800ec5fde0 -- (.cxr 0xfffff8800ec5fde0)
    rax=000000014c070004 rbx=0000000000000108 rcx=fffff880009eab20
    rdx=ff00fa8007af0441 rsi=0000000000000004 rdi=0000000000000108
    rip=fffff800032d00c5 rsp=fffff8800ec607c0 rbp=fffff880009eab20
     r8=ff00fa8007af0440  r9=fffff80003259000 r10=fffff880009eab20
    r11=fffff8800ec60968 r12=fffff8000345f580 r13=0000000000000000
    r14=0000000000000002 r15=000000007246704e
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    nt!ExpInterlockedPopEntrySListFault16:
    fffff800`032d00c5 498b08          mov     rcx,qword ptr [r8] ds:002b:ff00fa80`07
    af0440=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    PROCESS_NAME:  chrome.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800032d00c5

    STACK_TEXT:
    fffff880`0ec607c0 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16


    FOLLOWUP_IP:
    nt!ExpInterlockedPopEntrySListFault16+0
    fffff800`032d00c5 498b08          mov     rcx,qword ptr [r8]

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!ExpInterlockedPopEntrySListFault16+0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

    STACK_COMMAND:  .cxr 0xfffff8800ec5fde0 ; kb

    FAILURE_BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

    BUCKET_ID:  X64_0x3B_nt!ExpInterlockedPopEntrySListFault16+0

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


    Like i said i have not been able to find nothing in common on these errors so i'm lost here. Thanks in advanced for the help and let me know if there is anything else i can provide to help the diagnose.

    Monday, September 24, 2012 4:27 PM

All replies

  • The error is nonspecific and points to something corrupting the memory and the system crashing later, I'd enable driver verifier to see if you can get something more definitive,

    http://mikemstech.blogspot.com/2011/12/troubleshooting-0x3b.html

    http://mikemstech.blogspot.com/2011/12/enable-driver-verifier-to-help-identify.html

    Monday, September 24, 2012 4:46 PM
  • Hi Mike,

    Thanks for your reply, i enabled the driver verifier as shown in your blog. At first i was getting a BSOD at boot complaining about the driver dtsoftbus01.sys, looking around i found that this driver is used by daemon tools, so i booted to cmd safe mode and removed daemon tools from my pc. Now i'm back in business, will post back when i get my next BSOD.

    Monday, September 24, 2012 5:48 PM
  • Just for good messures and most likely not the problem but I always like to verify BIOS and chipset are up to date.
    Monday, September 24, 2012 8:26 PM
  • Yup, took care of that when the problem started a couple of weeks ago, everything is up to date now. BIOS, and every hardware driver is update to the latest version.

    Also updated directx which actually solved some BSOD i was getting with crysis 2, funny thing one would guess directx would be updated via windows updates automatically.

    Tuesday, September 25, 2012 12:51 AM
  • Ok, i feel like there is a little green creature inside my PC laughing at me. I had the verifier on for a couple of days with no problems, at which point i assumed everything was back to normal.
    Since the verifier obviously slow the system down quite a bit i disabled it just to get a blue screen. Back to the verifier now and waiting, but what if i never get a blue screen with the verifier ?. That would be really sad.
    • Edited by carragom Thursday, September 27, 2012 1:27 PM
    Thursday, September 27, 2012 1:27 PM
  • Please upload copies of your System and Application logs from your Event Viewer to your Sky Drive and post a link here.

    To access the System log select Start, Control Panel, Administrative Tools, Event Viewer, from the list in the left side of the window select Windows Logs and System. Place the cursor on System, select Action from the Menu and Save All Events as and give the file a name. Do the same for the Applications log.

    Type System Information in the Search Box above the start Button and press the ENTER key. Select File, Export and give the file a name noting where it is located. Please upload to your Sky Drive, share and post a link here.

    Run the Windows 7 Memory diagnostic Tool
    http://www.sevenforums.com/performance-maintenance/104698-memory-diagnostic-tool.html


    Hope this helps, Gerry

    Thursday, September 27, 2012 2:31 PM
  • Hi, here are the system and application logs along with the system information. Still with the verifier on, no blue screes at all. Overall slowness of the system is driving me crazy. Specially disk operations.

    Saturday, September 29, 2012 11:52 AM
  • Ok i finally got a blue screen with the verifier on. It happened while restarting my pc. Looking around, this IOMap64.sys belongs to ASUS Tek, the only thing i have from them is the Smart Doctor which gives me information of my video card. Since i never use it, i'm going to remove it, disable the verifier and see how it goes. Will post back when i get more info.

    Here is the dump info:

    C:\Program Files\Debugging Tools for Windows (x64)>kd -y srv*c:\symbols*http://m
    sdl.microsoft.com/download/symbols -z C:\Windows\Minidump\092912-59576-01.dmp

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


    Loading Dump File [C:\Windows\Minidump\092912-59576-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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`03453670
    Debug session time: Sat Sep 29 11:30:02.460 2012 (GMT-6)
    System Uptime: 2 days 17:41:45.052
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ....................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C9, {226, fffff880098fd734, fffff980f75caee0, 0}

    Unable to load image \??\C:\Windows\system32\drivers\IOMap64.sys, Win32 error 0n
    2
    *** WARNING: Unable to verify timestamp for IOMap64.sys
    *** ERROR: Module load completed but symbols could not be loaded for IOMap64.sys

    Probably caused by : IOMap64.sys ( IOMap64+1734 )

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

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

    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000226, An IRP dispatch handler has returned without passing dow
    n or completing this IRP,
            or someone forgot to return STATUS_PENDING.
    Arg2: fffff880098fd734, The address in the driver's code where the error was det
    ected.
    Arg3: fffff980f75caee0, IRP address.
    Arg4: 0000000000000000

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


    BUGCHECK_STR:  0xc9_226

    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  226

    FAULTING_IP:
    IOMap64+1734
    fffff880`098fd734 4883ec28        sub     rsp,28h

    FOLLOWUP_IP:
    IOMap64+1734
    fffff880`098fd734 4883ec28        sub     rsp,28h

    IRP_ADDRESS:  fffff980f75caee0

    DEVICE_OBJECT: fffffa8009d63da0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

    PROCESS_NAME:  SmartDoctor.ex

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff800037143dc to fffff8000328e1c0

    STACK_TEXT:
    fffff880`0544a418 fffff800`037143dc : 00000000`000000c9 00000000`00000226 fffff8
    80`098fd734 fffff980`f75caee0 : nt!KeBugCheckEx
    fffff880`0544a420 fffff800`0371e47a : fffff800`037129f0 fffff880`098fd734 fffff9
    80`f75caee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0544a460 fffff800`0371f483 : 00000000`00000226 fffffa80`09422238 fffff9
    80`f75caee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`0544a4b0 fffff800`0372a79c : 00000000`00000000 fffffa80`09422180 fffffa
    80`09422238 fffffa80`09d63da0 : nt!VfErrorReport1+0x63
    fffff880`0544a550 fffff800`0372ab63 : fffffa80`09422180 00000000`00000002 fffffa
    80`09d63da0 fffff800`0371d2a7 : nt!IovpCallDriver2+0x1bc
    fffff880`0544a5b0 fffff800`03730c2e : fffff980`f75caee0 fffff980`f75caee0 000000
    00`00000002 fffffa80`09d63da0 : nt!VfAfterCallDriver+0x353
    fffff880`0544a600 fffff800`0359169f : fffff980`f75caee0 fffffa80`0a21a7d0 000000
    00`00000000 fffffa80`09422180 : nt!IovCallDriver+0x57e
    fffff880`0544a660 fffff800`03580dc4 : 00000000`00000000 fffff8a0`02e5a8f0 000000
    00`00000000 00000000`00000000 : nt!IopCloseFile+0x11f
    fffff880`0544a6f0 fffff800`03580b81 : fffff8a0`02e5a8f0 fffff8a0`00000001 fffff8
    a0`02e5a8f0 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
    fffff880`0544a770 fffff800`03540e70 : 00000000`0000011c fffff8a0`02e5a8f0 fffff8
    a0`02f85470 00000000`0000011c : nt!ObpCloseHandleTableEntry+0xb1
    fffff880`0544a800 fffff800`03540d68 : 00000000`00000004 00000000`00000000 fffffa
    80`0a21a7d0 fffff800`0352e311 : nt!ObpCloseHandleProcedure+0x30
    fffff880`0544a840 fffff800`035413ea : fffff8a0`02f81601 fffff880`0544ac20 fffffa
    80`0a21a7d0 00000000`00010286 : nt!ExSweepHandleTable+0x74
    fffff880`0544a880 fffff800`0355f692 : fffff8a0`02f816b0 00000000`00000000 000000
    00`00000000 00000000`00000000 : nt!ObKillProcess+0x62
    fffff880`0544a8c0 fffff800`03542bdd : 00000000`40010004 00000000`00000001 000000
    00`7ef9b000 00000000`00000000 : nt!PspExitThread+0x522
    fffff880`0544a9c0 fffff800`03280cda : 00000000`00000010 00000000`00010286 fffff9
    80`26d10ee0 fffff800`035a4bfc : nt!PsExitSpecialApc+0x1d
    fffff880`0544a9f0 fffff800`03281020 : 00000000`00000000 fffff880`0544aa70 fffff8
    00`03542b50 00000000`00000001 : nt!KiDeliverApc+0x2ca
    fffff880`0544aa70 fffff800`0328d4f7 : fffff8a0`0308b000 fffff8a0`02987000 fffff8
    a0`0001f000 fffff980`29484000 : nt!KiInitiateUserApc+0x70
    fffff880`0544abb0 00000000`74952e09 : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`036af0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : 0x74952e09


    STACK_COMMAND:  .bugcheck ; kb

    SYMBOL_NAME:  IOMap64+1734

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: IOMap64

    IMAGE_NAME:  IOMap64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4b6b7a96

    FAILURE_BUCKET_ID:  X64_0xc9_226_VRF_IOMap64+1734

    BUCKET_ID:  X64_0xc9_226_VRF_IOMap64+1734

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

    Saturday, September 29, 2012 6:07 PM
  • Ok i got another blue screen with the verifier off, just another boring KMODE_EXCEPTION_NOT_HANDLED(1e), not much information when analyzed so i'm not going to post that one. Turned the verifier back on, this time i left the following two drivers out in order to avoid system slowness (amd_sata.sys and amd_xata.sys) and got another blue screen, this dump looks a bit more interesting, definitively looks like a memory problem to me but then i got a ask what should i do next:

    - Is it possible to get more specific information to correctly decide what hardware should i replace ?

    - Buy new RAM ?.

    - Buy new CPU ?.

    - Buy new motherboard ?.

    - Start buying thing until i stop getting blue screens :P.

    Here is the dump analysis:

    C:\Program Files\Debugging Tools for Windows (x64)>kd -y srv*c:\symbols*http://m
    sdl.microsoft.com/download/symbols -z C:\Windows\Minidump\093012-27222-01.dmp

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


    Loading Dump File [C:\Windows\Minidump\093012-27222-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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a7670
    Debug session time: Sun Sep 30 13:52:36.039 2012 (GMT-6)
    System Uptime: 0 days 0:08:36.647
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck C1, {fffff9808775aff0, fffff9808775a01e, 5d4010, 23}

    *** 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 ( nt!MiCheckSpecialPoolSlop+9a )

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

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

    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff9808775aff0, address trying to free
    Arg2: fffff9808775a01e, address where bits are corrupted
    Arg3: 00000000005d4010, (reserved)
    Arg4: 0000000000000023, caller is freeing an address where nearby bytes within t
    he same page have been corrupted

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


    BUGCHECK_STR:  0xC1_23

    SPECIAL_POOL_CORRUPTION_TYPE:  23

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff8000336834a to fffff800032e21c0

    STACK_TEXT:
    fffff880`03308ac8 fffff800`0336834a : 00000000`000000c1 fffff980`8775aff0 fffff9
    80`8775a01e 00000000`005d4010 : nt!KeBugCheckEx
    fffff880`03308ad0 fffff800`033e0fa3 : fffff6fc`c0510d90 00000000`00000000 fffff8
    80`02f68f40 00000000`00000000 : nt!MiCheckSpecialPoolSlop+0x9a
    fffff880`03308b10 fffff800`0340c93b : fffff800`03263000 00000000`4f494656 ffffff
    ff`ff725fd0 fffff800`03469140 : nt!MmFreeSpecialPool+0x1d3
    fffff880`03308c50 fffff800`037831f6 : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : nt!ExDeferredFreePool+0xf33
    fffff880`03308d00 fffff800`03578e6a : fffff980`00636b50 fffff980`0035eb30 000000
    00`00000000 00000000`00000000 : nt!ViPoolDelayFreeTrimThreadRoutine+0x46
    fffff880`03308d40 fffff800`032d2ec6 : fffff880`02f64180 fffff980`00636b50 fffff8
    80`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03308d80 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
    00`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!MiCheckSpecialPoolSlop+9a
    fffff800`0336834a cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!MiCheckSpecialPoolSlop+9a

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  X64_0xC1_23_VRFK_nt!MiCheckSpecialPoolSlop+9a

    BUCKET_ID:  X64_0xC1_23_VRFK_nt!MiCheckSpecialPoolSlop+9a

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

    Sunday, September 30, 2012 8:20 PM
  • This device is causing problems -SAMSUNG Mobile  USB Modem.

    Download and run HD Tune 2.55 (Free) -you need to scroll down the web page
    http://www.hdtune.com/download.html
    On the Info tab check the Supported and Active mode for each drive in the lower right of the page.

    You C and F partitions have limited free disk space and as a consequence will prone to excessive fragmentation.

    Please post copies of your dumpfiles as a shared file to your Sky Drive with a link here.
    What is your computer make and model? If not a branded computer what is your motherboard make and model?



    Hope this helps, Gerry

    Sunday, September 30, 2012 9:07 PM
  • Hi Gerry, thanks for your reply.

    But I'm confused, how did you reach the conclusion that the SAMSUNG Mobile USB Modem is the cause of the problem?. My phone was not even connected at the moment of the crash. Also, my F disk is a usb disk that is normally not connected to the system, and yes C has around 30GB free but how is this related to a blue screen?.

    I normally build my own computers so no brand here. My motherboard is an ASRock 890FX Deluxe4.

    Also more info to report, I have found a way to reproduce the blue screen. Every time I try to use handbreak to transcode a video to H.264 I get a blue screen. My computer also freezes if I do the same operation on Ubuntu. I'll upload the dump to my skydrive. I'll also leave memtest running the next couple of nights and see how it goes.

    Monday, October 1, 2012 1:51 AM
  • I agree with you, I doubt it's due to the modem. The corruption appeared to occur in the graphics driver, but the cause is unclear

    If memtest doesn't show any errors, I'd step the dumps up from minidumps to kernel/full memory dumps and see what they show.

    Monday, October 1, 2012 3:35 AM
  • "But I'm confused, how did you reach the conclusion that the SAMSUNG Mobile USB Modem is the cause of the problem?."

    You are misintreting what I said was. "This device is causing problems -SAMSUNG Mobile  USB Modem." It is according to the Windows Reporting system. That is not the same as saying it is the cause of your BSOD errors. It is just another problem you need to fix.

    Please post copies of your dumpfiles as a shared file to your Sky Drive with a link here.
    What is your computer make and model? If not a branded computer what is your motherboard make and model?



    Hope this helps, Gerry


    Monday, October 1, 2012 6:43 AM
  • Hi, first thanks for you time.

    Gerry, you are right, I misunderstood your previous post, sorry about that. Also my motherboard model is ASRock 890FX Deluxe4, this is a custom built computer.

    Mike, here is a screenshot of my dump configuration, I'm using 'Kernel memory dump' instead of 'Small memory dump', is this what you mean ?. Dump Config

    Now, been able to reproduce the problem at will (I hope it's only one problem). I had the chance of  some more testing, I have 4 memory sockets (A1, A2, B1 and B2) and I had a 2GB stick per socket, that's 8GB. After some testing I found out that, whenever I have memory on my A1 socket the problem happens. So I now have 4GB, 2GB on B1 and 2GB on B2. And the video transcode that had never successfully finished before now works like a charm. My conclusion here is that either socket A1 is broken, or the complete channel A (A1 and A2) is having problems. Since I can't have memory on A2 without having on A1 I'm not sure which might be the case. Of course, this is less than optimal since dual-channel is out of the question right now.

    I plan to take this to the motherboard manufacturer and see if there is any tool to diagnose this problem, otherwise I'll just buy a new one. Any other advice or testing you guys want to do is welcome.

    Thanks again.

    Monday, October 1, 2012 3:46 PM
  • Is the motherboard still under warranty?

    Type System information in the Search Box above the start Button and press the ENTER key. What is your BIOS version and date?


    Hope this helps, Gerry

    Monday, October 1, 2012 6:07 PM
  • BIOS Version is P1.70, this is the latest version available on the vendor site, date is feb 2 2012.
    And no, motherboard is out of warranty, bought it around 2 years ago. Time to get a new mobo, thanks for the help.

    Cheers.
    • Edited by carragom Tuesday, October 2, 2012 4:19 AM
    Tuesday, October 2, 2012 4:19 AM