locked
windows 7 64bit professional 60-70 Blue screens and counting...really need some help please RRS feed

  • Question

  • I really am totally confused by all this as I am a total novice and don't know what to do. I have done a memtest on the ram and plenty on chkdsk and not a lot has come up.

    Windows problem solver came back with a Win32/Small.ca virus but I have read that this can be caused by false positives from running more than one antivirus software.

    I have done windbg on the minidump files and the main finger pointing is done at the following

    ntkrnlmp.exe (nt!CmpKcbCacheLookup+1de)

    fltmgr.sys (fltmgr!DoReleaseContext+7)

    Win32k.sys (win32k+829d)

    ntfs.sys (ntfs!NtfsPagingFileIo+155)

    I will not list them all as there are that many and I have not attached any minidumps as there are that many and really would like to post the most relevant one once somebody thinks they know the way forward.

    I have removed Kaspersky Internet Security 2010 and the system is working a little better but I am still getting BSOD's

    PC is self built and spec is as follows

    Motherboard - Gigabyte GA-890GPA-UD3H

    Ram - 16gb G skill ripsaw

    Processor - AMD Phenom II 1090t

    GPU - ATI Radeon HD-5770

    PSU - Novatech Powerstation 750w

    Any help would be greatly appreciated as I really am out of my comfort zone with this.

    Many thanks in advance of any replies

    Paul

    Sunday, December 4, 2011 8:21 PM

Answers

  • Hi Mike

    I was informed it was but that means nothing but I do think that I cracked the possible cause today. I have been informed by GSKILL that the do not reccomend the use of two set over 4 dimms and if I do my guarantee is void....thanks GSKILL. I looked at all the ram again by removing it from the dimms and looking at the barcodes and then reinstalling them in the dimms they way that looked suitable and I have a stable system at present.

    It could be that when I installed the ram that the sets somehow got mixed up and this caused the problem but I really can not say for certain as the ram has been moved about a bit over the last few days.

    Here's hoping it is done and dusted????

    all the best Mike, have a great Christmas and New Year!

    Thanks again for all your help.

    Regards

    Paul

    • Marked as answer by Niki Han Wednesday, December 28, 2011 5:41 AM
    Monday, December 19, 2011 7:46 PM

All replies

  • Is this a known problem with Windows 7 as there are a good number of these cases on the forum?

    Is it a problem that might be addressed in SP2 ?? The errors always seem to point a Vista_driver_fault

    Has nobody from Microsoft found a solution to all the blue screens that are happening?

    Thought I'd better put at least the last minidump file on so someone can have a look.....there are others....lots of them.

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          03/12/2011 23:15:47
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      Paul-PC
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
        <EventID>41</EventID>
        <Version>2</Version>
        <Level>1</Level>
        <Task>63</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000002</Keywords>
        <TimeCreated SystemTime="2011-12-03T23:15:47.190430800Z" />
        <EventRecordID>281859</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>Paul-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">59</Data>
        <Data Name="BugcheckParameter1">0xc0000005</Data>
        <Data Name="BugcheckParameter2">0xfffff8000375be6e</Data>
        <Data Name="BugcheckParameter3">0xfffff880081ea720</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>

    Windbg pointed to ntkrnlmp.exe as a possible cause for this BSOD


    • Edited by gillybrand Sunday, December 4, 2011 10:52 PM
    Sunday, December 4, 2011 8:44 PM
  • Running two antivirus programs simultaneously is likely the issue, but
    you should probably upload all of the dumps for analysis,
     
     

    -- Mike Burr
    Technology
    Monday, December 5, 2011 6:35 AM
  • Hi Mike

    I'm not sure that I was using two antivirus programs while getting the blue screens but since removing Kaspersky the PC has run a lot smoother and quite a few applications appear to be happier it's gone.

    I have plenty of ram as I use this PC for CAD work and I have tried doing folding for Stanford but I have had so many stop errors that I am always waiting for my PC to have a cough and a splutter and die on me again.

    My wife just thinks I've spent alot of money on something that does not work and I don't think I have built an unstable PC as it must be software related.

    Thanks for th SKYDIVE link and how to use information which I have posted below.

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="165px" height="128px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21213&authkey=AHU2w8Bqtw51Sgw"></iframe>

    Hope that is what you wanted.

    Thanks again for taking a look at this for me.

    Regards

    Paul

    Scotland, England

    Monday, December 5, 2011 6:50 PM
  • I suggest trying "SFC /ScanNow"...  Although it's not completely a magic pill, no mystery blue-screen diagnosis endeavor is complete without at least trying it.  Have your Windows DVD handy, and it generally finishes in less than a few hours.  Totally worth trying.

    For more, visit http://support.microsoft.com/kb/929833.
    • Edited by johnqflorida Monday, December 5, 2011 9:17 PM Added "blue screen"
    Monday, December 5, 2011 8:41 PM
  • Hi johnqflorida

    I am willing to try anything as I really don't want to wipe the drives and rebuild the system. I just can't understand why Windows & after a stop error comes back with a Win32k/Small.ca virus and then when I use security essentials it can't find it and neither can any other virus scanner.

    I will give sfc scan now a go and see if it points me in the right direction.

    Many thanks.

    Paul

    A wee bit snowy Scotland

    Monday, December 5, 2011 9:10 PM
  • Hi,
     
    I'm seeing a lot of the following in the dumps so far,
     
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff880010910f7, Address of the instruction which caused the bugcheck
    Arg3: fffff8800bf7f9c0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
     This indicates that there is some memory corruption occurring. To rule
    out a hardware issue, could you run a test with memtest86+ (see
     
    If memtest86+ doesn't report any errors, we may need to get a little
    more involved with the driver verifier to see if we can pin the
    corruption to a specific driver
     

    -- Mike Burr
    Technology
    Wednesday, December 7, 2011 11:03 PM
  • Hi Mike,

    I'll do this right away and get back to you, and thanks again for your help.

    Regards

    Paul

    Wednesday, December 7, 2011 11:12 PM
  • Hi,

     

    If the BSOD is caused by different factors, it is most likely a hardware problem. Except checking memory, please also open an elevated command prompt and run chkdsk /f /r.

     

    Meanwhile, please use Microsoft Safety Scanner to ensure the computer is clean.

    http://www.microsoft.com/security/scanner/en-us/default.aspx

     

    Also, test if the issue occurs in Safe Mode.

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Edited by Niki Han Thursday, December 8, 2011 7:49 AM
    Thursday, December 8, 2011 7:48 AM
  • Hi Mike

    Sorry for the delay getting back to you. I have done 3 passes with MEMTEST and it found nothing. I don't know if this information has anything to do with the problem but the last crash happened while I was doing Protein Folding and the computer was not being used for a good few hours.

    Since I removed Kaspersky Internet Security 2010 the crashes have also been less frequent.

    Hope this information gives some pointers.

    Kind regards

     

    Paul

     

     

    Thursday, December 8, 2011 1:15 PM
  • Hi Niki

    I will do the security scanner right now and the chkdsk/f/r. later today. I have also done 3 passes on MEMTEST and it found nothing. I feel reluctant to point the finger at any part of the hardware but I have a hunch/feeling that the GPU could be the problem???? could be so many things but I just get a funny feeling about the card even though the drivers are up to date.

    Time will tell.

    Kind regards

    Paul

    Thursday, December 8, 2011 1:21 PM
  • Hi Niki,

    I started the security scanner at 1.36 gmt today and it has crashed again....the unusal thing is that event manager has not recorded the event and the last recorded stop error happened on 03/12/11.

    I am going to try it again to see if it will run through the full scan.

    Regards

    Paul

    Thursday, December 8, 2011 6:03 PM
  • OK, Since we are still seeing crashes, can you do two things,
     
    Move/Delete the files in c:\Windows\minidump
     
    Enable Driver verifier,
     
     
    After the next system crash, can you re-upload the dump in
    c:\windows\Minidump to skydrive and post a link?
     

    -- Mike Burr
    Technology
    Thursday, December 8, 2011 7:32 PM
  • Hi Mike,

    I'm in a bit of a pickle now as I copied the dump file to another folder and deleted the other ones in the minidump folder as requested. I then enabled driver verifier and I am now in a cycle of blue screens and startup repair mode and no option for safe mode to break the cycle. I am on another Pc so I can get messages just fine.

    The first two crashes were during a security scan that Niki Han asked me to do and they happened at different times, coupled with two further blue screens which I think were developed by event viewer.

    I had event code on the two crashes of 7000 ANSinshelp service failed due to the following

    could not find file or something ...hard to remember what it said now but it was something along those lines.

    I have had 4 further blue screens generated a welcome screen stage...as soon as I put my password in it crashes.

    Sorry to be such a pain for you Mike.

    Regards

    Paul

    Thursday, December 8, 2011 8:32 PM
  • No worries, when the system first starts, can you tap F8 and see if you
    can get this screen,
     
     

    -- Mike Burr
    Technology
    Thursday, December 8, 2011 8:44 PM
  • Hi Mike

    Safe mode is about to start, what would you like me to do next....safe mode will not start Mike it Blue screened again.

    Normal program has now launched but it is really slow and the keyboard does not work but the mouse does. Internet security not working and will not launch.

    Paul

     

    Thursday, December 8, 2011 8:53 PM
  • By "Normal program has now launched but it is really slow and the
    keyboard does not work but the mouse does", can you try disabling the
    driver verifier? It is actually located in
    c:\windows\system32\verifier.exe. You should be able to get there with a
    mouse...
     

    -- Mike Burr
    Technology
    Thursday, December 8, 2011 8:57 PM
  • no problem, what do I do when I get there?

    It's not there? I wonder if startup repair removed it when I hit start in last safe setup???

    Keyboard and mouse working again but no internet security.

     

     


    • Edited by gillybrand Thursday, December 8, 2011 9:08 PM
    Thursday, December 8, 2011 9:03 PM
  • Open verifier.exe and select the radio button for "delete existing settings"
     

    -- Mike Burr
    Technology
    Thursday, December 8, 2011 9:09 PM
  • Sorry Mike it's not there. I think startup repair has removed it. Just putting some antivirus on and I'll feel a little happier.

    Windows says that I have a win32k/Small.ca virus but whenever I have scanned for this in the past it could not be not be found. and when I had Kaspersky on the pc it did not even list it as a known virus???

    Really am sorry about all the messing about, I was really hoping that driver verifier would get to the bottom of things.

    Paul

     

     


    • Edited by gillybrand Thursday, December 8, 2011 9:24 PM
    Thursday, December 8, 2011 9:17 PM
  • Hi Niki

    Just so you know what is going on I have tried to run the security scanner you recommended but it crashed the pc twice. Windows does say that I have win32/small.ca virus but I don't even know if that is a real virus.

    Regards

    Paul

     

    Thursday, December 8, 2011 9:28 PM
  • It may have, can you upload the latest minidumps and post a link. Also,
    do you have an antivirus already, MSE might be able to catch it:
     
     

    -- Mike Burr
    Technology
    Thursday, December 8, 2011 9:30 PM
  • Already in the process of loading it, I have had MSE on before and it didn't find this win32/Small.ca virus, I find it rather odd that Microsoft action center can find this potential virus but MSE can not...really could be down to false positive but I won't rule anything out at this stage....just want a healthy pc.

    Hope you can help me sort it out....if I had hair to pull out I would do.

    Paul

    Thursday, December 8, 2011 9:35 PM
  • Hi Mike

    Sorry for the delay, here is the last minidump...hope it helps.

    Paul

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21244&authkey=AEAXnphl7pQDf5g"></iframe>

    Thursday, December 8, 2011 10:21 PM
  • Hi Paul,
     
    You wrote in a previous post that your keyboard was acting up, the
    driver identified is the driver that handles human interface devices
    (such as keyboards, mice, etc). Do you have a spare keyboard to test, or
    can you move which USB port the keyboard is on (if it is a USB keyboard)?
     
    4: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
    Arg2: fffff880057de710, The address in the driver's code where the error was detected.
    Arg3: fffff980134b8dc0, IRP address.
    Arg4: fffffa800cafb060, ProviderId.
     
    Debugging Details:
    ------------------
     BUGCHECK_STR:  0xc9_220
     
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220
     
    FAULTING_IP:
    HIDCLASS!HidpMajorHandler+0
    fffff880`057de710 48895c2410      mov     qword ptr [rsp+10h],rbx
     
    FOLLOWUP_IP:
    HIDCLASS!HidpMajorHandler+0
    fffff880`057de710 48895c2410      mov     qword ptr [rsp+10h],rbx
     
    IRP_ADDRESS:  fffff980134b8dc0
     
    DEVICE_OBJECT: fffffa800fe96b80
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
     
    PROCESS_NAME:  System
     
    CURRENT_IRQL:  2
     
    LOCK_ADDRESS:  fffff800036c5b80 -- (!locks fffff800036c5b80)
     
    Resource @ nt!PiEngineLock (0xfffff800036c5b80)    Available
     
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
     WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
     
    1 total locks
     
    PNP_TRIAGE:
        Lock address  : 0xfffff800036c5b80
        Thread Count  : 0
        Thread address: 0x0000000000000000
        Thread wait   : 0x0
     
    LAST_CONTROL_TRANSFER:  from fffff800039503dc to fffff800034c6c40
     
    STACK_TEXT:
    fffff880`0318b0a8 fffff800`039503dc : 00000000`000000c9 00000000`00000220 fffff880`057de710 fffff980`134b8dc0 : nt!KeBugCheckEx
    fffff880`0318b0b0 fffff800`0395a47a : fffff800`0394e9f0 fffff880`057de710 fffff980`134b8dc0 fffffa80`0cafb060 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`0318b0f0 fffff800`0395b0ff : 00000000`00000220 fffffa80`0cafb060 fffff980`134b8dc0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`0318b140 fffff800`039606a7 : fffff980`134b8f20 fffff880`057de710 00000000`00000000 00000000`00000000 : nt!VfErrorReport10+0x6f
    fffff880`0318b220 fffff800`0395004e : fffffa80`0e70c788 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfWmiVerifyIrpStackUpward+0x67
    fffff880`0318b250 fffff800`0395cb2d : fffffa80`104fa670 fffffa80`0e70c5d0 fffff980`134b8dc0 fffff980`134b8dc0 : nt!VfMajorVerifyIrpStackUpward+0x6e
    fffff880`0318b290 fffff800`0396e50d : fffff980`134b8f20 fffff880`0318b480 00000000`c0000010 fffff980`134b8f20 : nt!IovpCompleteRequest2+0xad
    fffff880`0318b300 fffff800`034ca021 : fffff980`134b8f23 00000000`00000000 00000000`000000ff fffff800`03951eea : nt!IovpLocalCompletionRoutine+0x9d
    fffff880`0318b360 fffff800`0396619f : fffff980`134b8dc0 fffff880`057e8400 fffffa80`0fe96c00 00000000`00000000 : nt!IopfCompleteRequest+0x341
    fffff880`0318b450 fffff800`034ac876 : fffff880`00000013 fffff880`0318b578 fffff980`134b8f20 fffffa80`0fe96cd0 : nt!IovCompleteRequest+0x19f
    fffff880`0318b520 fffff880`057dea0f : 00000000`00000000 fffffa80`0fe96cd0 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
    fffff880`0318b550 fffff880`057de7fb : 00000000`00000000 fffffa80`0fe96cd0 fffff980`134b8dc0 fffff880`0318b600 : HIDCLASS!HidpIrpMajorDefault+0x8b
    fffff880`0318b590 fffff800`0396cc16 : fffff980`00000002 fffff980`134b8dc0 00000000`00000002 fffff800`0396837e : HIDCLASS!HidpMajorHandler+0xeb
    fffff880`0318b600 fffff800`0396bc42 : fffff980`134b8f68 00000000`00000002 fffffa80`0fe96a70 fffffa80`0e540db0 : nt!IovCallDriver+0x566
    fffff880`0318b660 fffff800`0396cc16 : fffff980`134b8dc0 00000000`00000002 fffffa80`0fe96920 00000000`00000000 : nt!ViFilterDispatchGeneric+0x62
    fffff880`0318b690 fffff800`0396bd58 : fffff980`134b8dc0 fffffa80`0fe96920 00000000`00000000 fffffa80`0e6ae920 : nt!IovCallDriver+0x566
    fffff880`0318b6f0 fffff800`0396be42 : fffffa80`0cafb060 00000000`00000001 fffffa80`0cafb060 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
    fffff880`0318b760 fffff800`03958faf : fffffa80`0cafbd90 00000000`000007ff fffff800`036005b8 fffff800`0385c899 : nt!VfWmiTestStartedPdoStack+0x72
    fffff880`0318b800 fffff800`035739d2 : fffffa80`0cafbd90 00000000`00000000 ffffffff`ffffffff 00000000`00000016 : nt!VfMajorTestStartedPdoStack+0x5f
    fffff880`0318b830 fffff800`038b0e5c : fffffa80`0cafbd90 00000000`00000001 00000000`00000000 00000000`00000002 : nt!PpvUtilTestStartedPdoStack+0x12
    fffff880`0318b860 fffff800`038b2a54 : fffffa80`0cafbd90 fffffa80`0cafbd90 fffffa80`0caf6d90 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
    fffff880`0318b950 fffff800`038b2f3c : fffff800`036c3500 00000000`00000000 00000000`00000001 fffff800`03730814 : nt!PipProcessDevNodeTree+0x264
    fffff880`0318bbc0 fffff800`035c38c2 : 00000001`00000003 fffff800`036672b8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
    fffff880`0318bc10 fffff800`034d1001 : fffff800`035c35c0 fffff800`037bd901 fffffa80`0cadab00 00000000`00000000 : nt!PnpDeviceActionWorker+0x302
    fffff880`0318bcb0 fffff800`03761fee : 00000000`00000000 fffffa80`0cadab60 00000000`00000080 fffffa80`0c9f3040 : nt!ExpWorkerThread+0x111
    fffff880`0318bd40 fffff800`034b85e6 : fffff880`030a4180 fffffa80`0cadab60 fffff880`030af040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0318bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
     STACK_COMMAND:  .bugcheck ; kb
     
    SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: HIDCLASS
     
    IMAGE_NAME:  HIDCLASS.SYS
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665
     
    FAILURE_BUCKET_ID:  X64_0xc9_220_VRF_HIDCLASS!HidpMajorHandler+0
     
    BUCKET_ID:  X64_0xc9_220_VRF_HIDCLASS!HidpMajorHandler+0
     
    Followup: MachineOwner
    ---------
     

    -- Mike Burr
    Technology
    Thursday, December 8, 2011 10:31 PM
  • Hi Mike

    I have the following on USB

    logitech lx710 wireless keyboard and mouse

    logitech trackman mouse (wired)

    epson stylus dx9400f printer

    logitech speakers m/n s-0264b

    and thats it other than a tablet by aiptek (14000u0 which is very rairly connected.

    I have no "wired keyboard" so I will go and buy one tomorrow but I know that the drivers for these items are up to date.

    The printer has however, given me a few problems as I do not think that it likes all the windows settings.

    Regards

    Paul

    Thursday, December 8, 2011 11:27 PM
  • Hi Mike,

    Got myself a wired keyboard this morning and I am about to remove all the drivers for any other all other plug in and play/USB related drivers. After I have done this the only usb connected items will be a Microsoft wired keyboard and Logitech wired Trackman wheel mouse.

    I will reboot the pc once the drivers are removed and leave the pc switched on all the time to see if it crashes again.

    Just as an added note I thought I would tell you that the other pc I was using crashed and Microsoft pointed the finger at the antivirus software causing the crash. I have already removed Kaspersky from the original pc and I am now running MSE but I am wondering if any lingering files for Kaspersky could be causing the crashes even though the bugcheck has pointed out a plug in and play driver.

    I really want to thank you for all your help, you really are a star. I hope this is the fianl push now to get the problem solved.

    Kind regards

     

    Paul

    Friday, December 9, 2011 2:20 PM
  • Hi Mike,

    I have just had another blue screen and I have attached the skydive link below...

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21245&authkey=AN53Ik5nGKTBrjo"></iframe>

    I will give you a little background as to what I was doing when the crash happened to see if this can give you any pointers. I deleted all software that related to any usb related hardware and bought a new keyboard which is a Microsoft Windows 7 compatible. I deleted all my printer, tablet, 3d mouse, and wireless keyboard and mouse software. The only item that I was using from the previous BSOD riddled setup was my Logitech trackman wheel mouse which is a wired version.

    I was in the pc performace index page and there was a button requesting to update the index as new hardware had been fitted (new keyboard) and it promptly crashed.

    I don't want to jump on the fact that the mouse was the only usb device used while all the other blue screens have happened as not all the blue screens have happened while I have been using the mouse. The blue screens have happened while I have been away from the pc and in some cases not used the pc or mouse for a number of hours.

    Maybe we have moved a little closer to an answer???

    All the best

    Paul

    Friday, December 9, 2011 6:34 PM
  • Just me again

    Just tried to replicate the same blue screen by by left clicking the review index button with the oldest most rubbish corded mouse I have and no bluse screen.

    I don't know if the culprit has been found and that it is too early to jump for joy but I have to say that I am really positive. I wonder if you still get the same pointer from the bugcheck highlighting to a faulty vista driver relating to a plug in and play device.

    I am just confused that if it is the mouse that is causing the problem why has it not happened on other pc's of mine when I've used the Trackman mouse. I thought that by buying Windows 7 Professional that it allowed me to use hardware and software that had previously worked withvista/xp.

    Regards

    Paul

    I take it that it would be unlikely to be the GPU in any way...just I thought it might be my ATI Radeon HD5770 card, I guess thats not plug in and play though.

    Friday, December 9, 2011 6:56 PM
  • This is back to being a general indicator of memory corruption by a
    driver, do you want to try re-enabling the driver verifier to see if we
    can catch anything else? Hopefully it will go smoother this time with
    the new keyboard/mouse...
     
    5: kd>  !analyze -v
     
    *******************************************************************************
     
    *                                                                             *
     
    *                        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: fffff800035ffdd3, Address of the instruction which caused the bugcheck
     
    Arg3: fffff88007b4eec0, Address of the context record for the exception that caused the bugcheck
     
    Arg4: 0000000000000000, zero.
     
     

    -- Mike Burr
    Technology
    Friday, December 9, 2011 7:23 PM
  • Hi Mike,

    I'm willing to try anything but before I go any further I just wanted to let you know that when I did the Resource and Performance Monitor the following came up as a problem....

    ConfigManagerError Code  Device not present,not working properly or does not have all its drivers installed

    ConfigManagerUserconfig   0

    Description                          ASInsHelp

    Name                                  ASInsHelp

    Service                                ASInsHelp

    Status                                 Error

    Win32_PnPEntity.DeviceID="ROOT\\LEGACY_ASINSHELP\\0000"

    Mike I really hope that means something to you as I can not make heand nor tail of it.

    I'll go ahead with verifier once tou have had a chance to look at this info.

    Regards

    Paul

     

    Friday, December 9, 2011 8:10 PM
  • That error is a new one for me, but based on what I can find it is
    complaining about an incorrect driver being installed
     
    Let's enable driver verifier, can you also post a screenshot of device
    manager (start -> search box, type devmgmt.msc) or let me know if any
    devices have a yellow exclamation point with them and what error they
    are reporting?
     

    -- Mike Burr
    Technology
    Friday, December 9, 2011 8:55 PM
  • I put that error into google and very little came out.

    I have done as you asked and there is nothing on device manager showing any warnings applied to any devices so it's a bit of a mystery.

    I will launch verifier after I have sent this message as I would love to get my old logitech keyboard back as my fingers are not wotking too well with this one.

    Honest I can spwell but the keys are different sizes and I'm make a right pigs ear of the messages I'm sending.

    Regards

    Paul

    Friday, December 9, 2011 9:27 PM
  • Hi mike

    On my other pc now. Pc with BSOD problem crashed while loading windows so I am hoping that the minidump will pinpoint something.

    That pc is now up and running but very slowly, I will get into the minidump and send it to skydive.

    Do you want me to disable verifier??

    Friday, December 9, 2011 9:42 PM
  • just blue screened again so I will have to disable verifier. Last blue screen mentioned memory management.
    Friday, December 9, 2011 9:46 PM
  • After you get a couple of dumps with verifier enabled, go ahead and
    disable it and we can see if anything turns up in the dumps.
     

    -- Mike Burr
    Technology
    Friday, December 9, 2011 10:02 PM
  • hi Mike

    I am in a cycle of blue screens here so I will send the link to skydive as soon as I can get it to stop crashing long enough to send it.

    Normal service will resume shortly. Can' start in safe mode at all, just keeps crashing.

    Happy days :-(    

     

    Friday, December 9, 2011 10:09 PM
  • Hi Mike

    Here is the skydive link, some of the crashes were not there but I am guessing that Windows did not not boot up far enough to record them.

    Hope you find something in this lot.

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="165px" height="128px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21213&authkey=AHU2w8Bqtw51Sgw"></iframe>

    Cheers Mike, and thanks again for your patience.

    Paul

    Friday, December 9, 2011 10:19 PM
  • did that last skydive link work ok?

     

    Friday, December 9, 2011 10:26 PM
  •  The other recent dumps were SYSTEM_SERVICE_EXCEPTION and
    MEMORY_MANAGEMENT, but we did get a possibly meaningful crash due to the
    Gigabyte motherboard driver. Is this the chipset driver that you
    installed when you last rebuilt your PC?
     
     0: 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: fffff9805740eff0, address trying to free
    Arg2: fffff9805740effc, address where bits are corrupted
    Arg3: 0000000000fd000c, (reserved)
    Arg4: 0000000000000024, caller is freeing an address where bytes after the end of the allocation have been overwritten
     
    Debugging Details:
    ------------------
     BUGCHECK_STR:  0xC1_24
     
    SPECIAL_POOL_CORRUPTION_TYPE:  24
     
    CUSTOMER_CRASH_COUNT:  1
     
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
     
    PROCESS_NAME:  essvr.exe
     
    CURRENT_IRQL:  1
     
    IRP_ADDRESS:  fffff9804f9a4f3b
     
    LAST_CONTROL_TRANSFER:  from fffff80003582b54 to fffff80003480c40
     
    STACK_TEXT:
    fffff880`0890a4d8 fffff800`03582b54 : 00000000`000000c1 fffff980`5740eff0 fffff980`5740effc 00000000`00fd000c : nt!KeBugCheckEx
    fffff880`0890a4e0 fffff800`035ae93b : fffff800`03404000 00000000`20206f49 00000000`0005daba fffffa80`0e206740 : nt!MmFreeSpecialPool+0x374
    fffff880`0890a620 fffff800`0349609e : 00000000`00000000 fffff980`4f9a4fb0 fffff980`001a4af0 fffffa80`0e7a4660 : nt!ExDeferredFreePool+0xf33
    fffff880`0890a6d0 fffff800`0348434a : fffff980`4f9a4fb3 00000000`00000001 00000000`00000001 fffff800`0353d803 : nt!IopCompleteRequest+0x5ce
    fffff880`0890a7a0 fffff800`0392019f : fffff980`4f9a4ee0 fffffa80`0d894400 fffff980`4f9a4f00 00000000`00000000 : nt!IopfCompleteRequest+0x66a
    fffff880`0890a890 fffff880`0916c0c7 : fffff880`0916ca50 00000000`00000008 00000000`00000000 fffff980`4f9a4fb0 : nt!IovCompleteRequest+0x19f
    fffff880`0890a960 fffff880`0916ca50 : 00000000`00000008 00000000`00000000 fffff980`4f9a4fb0 00000000`00000001 : gdrv+0x30c7
    fffff880`0890a968 00000000`00000008 : 00000000`00000000 fffff980`4f9a4fb0 00000000`00000001 00000000`00000000 : gdrv+0x3a50
    fffff880`0890a970 00000000`00000000 : fffff980`4f9a4fb0 00000000`00000001 00000000`00000000 00000000`00000001 : 0x8
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    gdrv+30c7
    fffff880`0916c0c7 ??              ???
     
    SYMBOL_STACK_INDEX:  6
     
    SYMBOL_NAME:  gdrv+30c7
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: gdrv
     
    IMAGE_NAME:  gdrv.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  49b9d175
     
    FAILURE_BUCKET_ID:  X64_0xC1_24_VRF_gdrv+30c7
     
    BUCKET_ID:  X64_0xC1_24_VRF_gdrv+30c7
     
    Followup: MachineOwner
    ---------
     
    0: kd>  lmvm gdrv
    start             end                 module name
    fffff880`09169000 fffff880`09172000   gdrv     T (no symbols)
        Loaded symbol image file: gdrv.sys
        Image path: \??\C:\Windows\gdrv.sys
        Image name: gdrv.sys
        Timestamp:        Thu Mar 12 21:22:29 2009 (49B9D175)
        CheckSum:         000105CE
        ImageSize:        00009000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd>  !sysinfo machineid
    Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=3000]
    BiosVendor = Award Software International, Inc.
    BiosVersion = FF
    BiosReleaseDate = 11/24/2010
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = GA-890GPA-UD3H
    SystemFamily =
    SystemVersion =
    SystemSKU =
    BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
    BaseBoardProduct = GA-890GPA-UD3H
    BaseBoardVersion =
     
     

    -- Mike Burr
    Technology
    Friday, December 9, 2011 10:52 PM
  • do you really think that motherboard driver is the key? Shall I download a new chipset driver and see where it goes?
    Friday, December 9, 2011 11:03 PM
  • Sorry mike I miss read your reply. I am not sure as I installed the drivers that were supplied with the motherboard but I think that an update request or recommendation came through when I first cinnected to the internet.

    Looking at the date I would say it looks about right, but, I wonder if I should just try and update the chipset driver and see if that does the trick.

    How can I verify which driver is in use for the motherboard/chipset

     

    Friday, December 9, 2011 11:19 PM
  • is memory classed as plug in and play???

     

    Friday, December 9, 2011 11:20 PM
  • That's what I'd recommend at this point, you may also want to see if
    Gigabyte has any recommendations for testing the motherboard and related
    components,
     
     

    -- Mike Burr
    Technology
    Saturday, December 10, 2011 5:33 AM
  • Hi Mike,

    Sorry for the delay getting back to you. I went on to the Gigabyte website and it recommended using using DRIVERAGENT and I decided to go for it, I know you are saying "stupid idiot" but I thought it may be worth a try.

    I have always stayed clear of driver management software as I thought that windows 7 would do a good enough job. I have downloaded the recommended driver and loaded them and the pc has been running since about 10pm yesterday and it has not fallen over....yet.

    The two Gigabyte drivers did not appear to have anything to do with the memory/chipset side of things but it did mention sata2.

    I ran the Resource and Performance Monitor and it is still showing the ASInsHelp error code but.

    I intend running the pc all the time and introduce each usb related hardware one at a time over the next week and leave each one a couple of days before loading another to see if this flushes out  the software that is causing the problem.

    I have left a message with Gigabyte service and I will see if there are any known issues with the board.

    I don't know if this should have anything to do with the memory corruption but I am running the maximum amount of ram the board can handle, maybe too much of a good thing??

    Hope you are well and thanks again for all you help, your a legend.

    Many thanks

    Paul

     

    Sunday, December 11, 2011 6:11 PM
  • If you are within the vendor specifications for the maximum amount of
    RAM, that should not be a problem, but it could be a problem if the
    memory is not compatible with the motherboard.
     
    Every now and again, the vendor's driver utility will help identify
    something missing, but I've had cases with Dell, HP, and a couple other
    vendors where the utility detects the wrong hardware (and thus installs
    the wrong driver). We were getting to the point where just about
    anything was in the realm to try, so I'm glad that it helped...
     

    -- Mike Burr
    Technology
    Sunday, December 11, 2011 10:07 PM
  • Hi Mike

    Thankfully I bought all of the hardware for the pc from one supplier so I am luck in some ways as I asked them to check over before I bought it that everything is compatible.

    As it stands the pc is still on and still working, I have run a number of antivirus and adaware and Microsoft security scanner which have previously crashed the pc at various different stages of scan.

    Since the crashes are fairly erratic I do not know how relevant the above information is. I hope you agree that it would be correct to go ahead with loading each usb hardware and related software a little bit at a time until it either falls over again or in fact does not.

    It may be that DRIVERAGENT has picked up on a driver that was required that Windows did not...which I find hard to believe.

    If you don't mind I will keep in touch and let you know of any further problems/developments.

    Thanks once again for all your valued help, I am just keeping my fingers crossed nowhoping that that is it.

    Kind regards

    Paul

    Sunday, December 11, 2011 10:37 PM
  • Thats the best way to identify a fault in this case, whatever causes it
    to break is probably the cause. Feel free to let me know how things go.
     

    -- Mike Burr
    Technology
    Monday, December 12, 2011 12:22 AM
  • I would like a little information regarding hard drives if you could help me out.

    on all the pc's I have ever had all noise....clicks and such likes have always been when the pc starts up but this one on a regular basis even if it is not being used, the screen might be switched off and no programs running but I get clicking noises like it's about to crash. Is this normal or am I due to the amount of crashes listening and looking for anything that may be a sign?

    Regards

    Paul

     

    Monday, December 12, 2011 12:58 AM
  • Hi Paul,

    After reviewing the above debug inforation, I noticed that the BSOD occurs randomly, the call stack information also seems untablely. Usually in this situation, we can suspect the hardware issue caused that. Please refer to the following items:

    1. Please try to reinsert the memory card, and disply card...

    2. Try to upgade the drivers/firmware/BIOS to the latest version.

    3. If possible, try to image this OS to a virtual Machine for further troubleshooting.

    4. If this BSOD occurs vey frequently, we can boot the server t clean boot mode to check if any 3th party sfteware caused that.

     

    Best Regards

    Kevin


    “Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.”
    Monday, December 12, 2011 3:16 AM
  • Hi Kevin,

    I seem to have the pc fairly stable at the moment, but I take on board what you are saying. I have run memtest86 and the ram is ok, I have also done checks on the hard drives also and no defrag was required as only 1% came through on the analysis as being suitable for defragging.

    This leaves the GPU, which I do not no how to test. I would like to have some sort of stress test done on the pc if you can recommend some software.

    Regards

    Paul

    Monday, December 12, 2011 1:22 PM
  • Hi Mike

    Now that the system appears stable I was just wondering if you think it maybe worth while using some sort of stress test to see if it highlights a problem.

    I have done one full scan using MSEssentials and it took forever as I think that as a default it uses 50% of the CPU while in progress, I just wonder if it is worth while increasing that figure to around 60-80% to see if it cracks.

    The pc has been on now since Sunday night and I would have expected a stop error by now so I am hoping that it is cured.

    I have had a comment from kevin that says that the debug information points to hardware problems but ram has been checked and hard drives are fine but driver faults came out of the debug information you looked at.

    What do you think?

    Regards

    Paul

    Monday, December 12, 2011 1:33 PM
  • It feels like the driver update utility that you used may have resolved
    the issue and other diagnostics haven't turned up any errors. If you
    want to perform a stress test, feel free... it may turn up any other issues
     
    As for the clicking hard drive, I just tested a utility
     
     
    After it installs, on the start menu there will be a
    smartmontools\smartctl folder and there will be a "SMART error log (-l
    error)" that will help identify any early warning signs hat have
    appeared. As for the noise, I wouldn't know without hearing it, but
    noises can occur during regular drive operations, but you may get an
    early warning by checking the SMART log.
     

    -- Mike Burr
    Technology
    Monday, December 12, 2011 5:58 PM
  • Hi Paul,
     
    I wrote a post on using smartctl to detect hard drive errors if you are
    interested,
     
     
     

    -- Mike Burr
    Technology
    • Proposed as answer by Niki Han Wednesday, December 28, 2011 5:40 AM
    Monday, December 12, 2011 9:44 PM
  • Cheers Mike,

    Can't thank you enough for all your efforts, I've got my pc back!!! read something about the ASInshelp service problem which shows up in Resourse and Performance Monitor and it has something to do with network drivers in relation to servers (Winsock)

    I hope this means something to you but it appears to be a common problem that does not cause a problem if you see what I mean. I have some more digging to do on it but I thought you may want to know about it as you said it was not a problem you are familiar with.

    Thanks for the post.

    Regards

    Paul

    Monday, December 12, 2011 10:02 PM
  • Hi Mike

    Well I guess my over confidence that the problem was solved has slapped me in the face as my pc crashed this morning. I have posted the skydive link below.

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21250&authkey=AOpEd0l8rE1cUNc"></iframe>

    I am not sure if this gives you the correctinfo as I had to do a soft crash as the blue screen was still on when I switched the screen on which is in itself a bit odd as it should reboot after a crash.

    A little history for you, lastnight I loaded my 3d mouse drivers from 3d connexion and I did an adaware run which I left running when I went to bed and as I said before the screen was blue when I switched it on.

    I hope th info in the minidump file has more information than just the soft crash.

    Regards

    Paul

    PS. did not run the hard drive software you recommended as I thought that I was jumping the gun. Two days without crashing was making me too headstrong, I guess one swallow doesn't make it summer.

     

    Tuesday, December 13, 2011 9:28 AM
  • Hi Mike

    Well I guess my over confidence that the problem was solved has slapped me in the face as my pc crashed this morning. I have posted the skydive link below.

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21250&authkey=AOpEd0l8rE1cUNc"></iframe>

    I am not sure if this gives you the correctinfo as I had to do a soft crash as the blue screen was still on when I switched the screen on which is in itself a bit odd as it should reboot after a crash.

    A little history for you, lastnight I loaded my 3d mouse drivers from 3d connexion and I did an adaware run which I left running when I went to bed and as I said before the screen was blue when I switched it on.

    I hope th info in the minidump file has more information than just the soft crash.

    Regards

    Paul

    PS. did not run the hard drive software you recommended as I thought that I was jumping the gun. Two days without crashing was making me too headstrong, I guess one swallow doesn't make it summer.

     

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    Debugging Details:
    ------------------
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    FAULTING_IP: 
    +3162613763613638
    00000000`00000000 ??              ???
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000000
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    BUGCHECK_STR:  0x1E_0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    EXCEPTION_RECORD:  fffff80000b9c328 -- (.exr 0xfffff80000b9c328)
    ExceptionAddress: fffff800034d1d1f (nt!KiDeferredReadyThread+0x000000000000005f)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    TRAP_FRAME:  fffff80000b9c3d0 -- (.trap 0xfffff80000b9c3d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffbbf53591a0e6 rbx=0000000000000000 rcx=fffffa800d6eeb60
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800034d1d1f rsp=fffff80000b9c560 rbp=fffffa8011401580
     r8=0000000000000001  r9=0000000000000000 r10=fffff8000344f000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KiDeferredReadyThread+0x5f:
    fffff800`034d1d1f 0f825c080000    jb      nt!KiDeferredReadyThread+0x8ca (fffff800`034d2581) [br=0]
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800034c35fe to fffff800034cbc10
    STACK_TEXT:  
    fffff800`00b9b408 fffff800`034c35fe : fffff800`034f79f0 fffff800`036138dc fffff800`00b9bb80 fffff800`034f7830 : nt!KeBugCheck
    fffff800`00b9b410 fffff800`034f74fd : fffff800`036d571c fffff800`03612c30 fffff800`0344f000 fffff800`00b9c328 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`00b9b440 fffff800`034f62d5 : fffff800`036160fc fffff800`00b9b4b8 fffff800`00b9c328 fffff800`0344f000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00b9b470 fffff800`03507361 : fffff800`00b9c328 fffff800`00b9bb80 fffff800`00000000 fffffa80`0d6eeb60 : nt!RtlDispatchException+0x415
    fffff800`00b9bb50 fffff800`034cb2c2 : fffff800`00b9c328 fffffa80`0d6eec00 fffff800`00b9c3d0 fffffa80`16943c00 : nt!KiDispatchException+0x135
    fffff800`00b9c1f0 fffff800`034c941f : fffff800`00b9c3d0 fffff880`04393d02 fffffa80`0d952e00 fffff880`00000000 : nt!KiExceptionDispatch+0xc2
    fffff800`00b9c3d0 fffff800`034d1d1f : fffffa80`10bc6ef8 fffffa80`10bc6ef8 00000000`00000000 fffffa80`10bc6ef0 : nt!KiInvalidOpcodeFault+0x11f
    fffff800`00b9c560 fffff800`034d7527 : fffffa80`0d6eec20 fffffa80`0d6eec68 fffffa80`0d6eec68 fffffa80`16943c00 : nt!KiDeferredReadyThread+0x5f
    fffff800`00b9c5e0 fffff800`034d737e : 000001d1`b58fcb6f fffff800`00b9cc58 00000000`00c3a4f6 fffff800`03646148 : nt!KiProcessExpiredTimerList+0x157
    fffff800`00b9cc30 fffff800`034d7167 : 00000092`52106cc3 00000092`00c3a4f6 00000092`52106c85 00000000`000000f6 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`034c396a : fffff800`03641e80 fffff800`0364fcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiKernelCalloutExceptionHandler+e
    fffff800`034c35fe 90              nop
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
    BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
    Followup: MachineOwner
    -----------------------------------------------------------------------------------------------------------------------------------------------------
    Regards,

    MCP ✦ MCTS ✦ MCITP
    Tuesday, December 13, 2011 10:18 AM
  • Just curious... did you ever wind up doing and completing the SFC /ScanNow step?  (Keep in mind, that's not a virus scan, it's a scan to make sure key system files are correct, and it's a worthwhile endeavor to try). 

    And I believe you said Microsoft Safety Scanner did complete eventually?  (that is a virus/malware scanner).  I think Safety Scanner is a very good program, but still, no single program catches every single piece of malware.  Consider exploring the malware removal forums at bleepingc0mputer or aumha.0rg and following the extremely specific prerequisite steps they recommend then posting your scan logs there.   On the chance all these issues are actually malware related, it is worth going through a process of elimination on that front too.

    Tuesday, December 13, 2011 3:52 PM
  • Hi John

    I know this is going to sound odd but I think I have but I can't be sure....I tried so many thinks over the past....ages. I will do it tonight after MSE full scan finishes, I run this because it trips windows up normally.

    I still want to test the GPU out but I will save that until tomorrow. I ran adaware lastnight and the pc had a blue screen when I switched it on so I don't know what to blame.

    I bought driveragent as much as I didn't want to and it picked up on smoe old drivers to be updated. Gigabyte have not bothered to return my email regarding chipsets for my board.

    I will run SFC scan/now but I don't think that it found anything...thats if my memory serves me well.

    Regards

    Paul

     

    Tuesday, December 13, 2011 5:33 PM
  • Ok. And one other reminder (which you probably know already, I'm just saying on the chance the similar names threw you, and also since you said "MSE"): Microsoft Safety Scanner (the moderator posted the link earlier in this thread) is NOT the same thing as Microsoft Security Essentials.. If you haven't already, make a point to install and run Safety Scanner. (I'd even be willing to say that if what you're waiting on now is the Security Essentials scan, you could abandon it in favor of Safety Scanner for the immediate moment). P.S. Run the "quick scan" first too. (Not that you shouldn't run the full scan too, but the quick scan could potentially find more obvious things in just an hour or two and clean them, making the system more stable for later steps).
    • Edited by johnqflorida Tuesday, December 13, 2011 5:56 PM Added Quick Scan comment
    Tuesday, December 13, 2011 5:49 PM
  • cheers john

    I've run that many different things and more than once but I will give that a go. What I plan to do tonight is the following.....

    1. Wait for the outcome of Microsoft Security Essential full scan ( which is not to find a virus but more to do with making the pc crash)

    2. run SFC /scannow to see what that kicks up

    3. Maybe remove the 3d connexion mouse driver and then run adaware again to see if the pc crashes.

    4. Maybe remove the GPU and then scan Hard drive for potential problems.

    5. not sure I'll think of something to do.

    Really want to get this sorted now the pc has been unstable for months now and I'm just a bit fed up.

    Regards

    Paul

    Tuesday, December 13, 2011 6:26 PM
  • hi John

    cancelled the MSE full scan and I am now running the security scanner as you recommended. I have started with the quick scan and will move on to full scan if it does not crash.

    I have disabled a file that keeps showing up on resource and performance monitor - ASInshelp service  from what I have read it is to do with ASUS cool and safe??? I don't have an ASUS board but it maybe some ort of cross over with AMD and I do have an AMD processor. Mike suggested that my crash problem maybe related to a plug and play driver/device but ASInshelp service is a hidden non plug in and play device/driver. I can see no use for it so I thought that it would be best to diable it and run resource and performance monitor after Security scanner has finished.

    Regards

    Paul

    Tuesday, December 13, 2011 11:25 PM
  • Quick scan finished and no problems to report, moving on to full scan. I will keep you informed.
    Tuesday, December 13, 2011 11:27 PM
  • Hi Mike

    Here is the latest crash which happened while I was running Microsoft Safety Scanner - Full Scan. The quick scan had worked and found no problem. I also disabled ASInshelp approx 10mins before hand as it appears to be a redundant item.

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21251&authkey=AKB3sGt0rGx4Zkc"></iframe>

    Hope this gets us closer to finding this error.

    Kind regards

    Paul

    Tuesday, December 13, 2011 11:48 PM
  • Hi John

    Pc crashed a short time after starting Safety Scanner ( sorry I kept calling it Security Scanner) I have posted the skydive link below in case you want a look.

    Regards

    Paul

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21251&authkey=AKB3sGt0rGx4Zkc"></iframe>

    Going to give full scan another go now.

    Tuesday, December 13, 2011 11:51 PM
  • Hi Mike

    At the request of John I have tried to run Microsoft Safety Scanner and it has now crashed twice while trying to run a full scan, while a quick scan does not trip the system up at all.

    Skydive link is below...

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21252&authkey=ALl6HAzPrz4i_GE"></iframe>

    I wonder if it is time to try verifier again.

    I will try to run Safety Scanner again but if it crashes again I guess the system is trying to tell me that it can not cope with a full scan.

    regards

    Paul

    Wednesday, December 14, 2011 7:23 AM
  • Hi John

    pc really does not like the full scan but I am going to try for a third time but if it crashes for a third time I will have to leave it and do some backtracking.

    Here is a skydive link if you are interested.

    Regards

    Paul

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21252&authkey=ALl6HAzPrz4i_GE"></iframe>

    Wednesday, December 14, 2011 7:25 AM
  • Hi Mike

    Just a quick one that may make no difference but the ast couple of blue screens  have not rebooted and the blue screen  is just there waiting for me when I switched the screen on.

    I have checked that I have reboot after system failure box checked so I do not understand why it is not doing it.

    I have deleted my 3d mouse software, and adaware and started safety scanner again.

    regards

    Paul

    Wednesday, December 14, 2011 7:49 AM
  • Hi Mike

    Another minidump for you while Microsoft Safety Scanner was running. I was also running google earth in street view and it crashed while I was scrolling and again the system would not reboot after system failure.

    I tried to start the pc in safe mode with networking and safe mode does not work on this pc at all, every time it tries to launch in safe mode it crashes again but does not record that event in event viewer.

    I plan to run Memtest86 again now and then run the failing hard drive test. After that I plan to the following...

    Remove GPU and all related software.

    move all but the main software I use to a different drive so that the c drive is running windows and as few other programs as possible.

    I will not run Safety Scanner again until you think the system is stable enough to try it.

    skydive link

    <iframe title ="Preview" scrolling="no" marginheight="0" marginwidth="0" frameborder="0" width="98px" height="120px" style="padding:0;background-color:#fcfcfc;" src="https://skydrive.live.com/embed?cid=C54CFE22DEAC8E2D&resid=C54CFE22DEAC8E2D%21253&authkey=AEG6IAFn0SQZ2mI"></iframe>

    I do not understand why safe mode will not launch?????

    Regards

    Paul

    Wednesday, December 14, 2011 12:59 PM
  • Hi Paul,
     
    Can we try something else,
     
    Please enable driver verifier and configure your system for kernel
    memory dumps (instead of small memory dumps),
     
     
    By default, the kernel memory dump will be in c:\windows\memory.dmp
    instead of c:\windows\minidump
     
    To upload the kernel memory dump, you may need to split the dump into
    smaller files,
     
     
    I'm also working on a set of instructions for performing an offline scan
    of system files that will hopefully help.
     

    -- Mike Burr
    Technology
    Wednesday, December 14, 2011 6:31 PM
  • Good job on the persistence. Eventually, all this will pay off and you or someone will identify the cause. Don't forget, give SFC /ScanNow a shot too.
    Wednesday, December 14, 2011 9:04 PM
  • Hi Mike

    I will do as you requested and move to kernel memory dump.

    I decided to test the ram again but one stick at a time to see if I can make each stick crash running Safety Scanner and loads of other applications at a time. Still on with the first stick of the 4 x 4gb Ripsaw ram, I thought it might be woth a try as MEMtest86 did not find anything wrong while they were all fitted and working together.

    My plan is to test each stick in a different slot and if the ram fails move it to a slot that I know works. I also plan to remove the GPU at some point as the last BSOD points at a graphics problem.

    Regards

    Paul

    Wednesday, December 14, 2011 9:21 PM
  • Hi John

    Will do, I want the pc that I paid for albeit as components. I built my own system because I wanted to know more about how they work and there is no better way to find out how something works than having a problem to fix.

    Thank god for all the people that have bothered to look at the post and help me out if I could hand out medals I would do.

    Thanks again

    Paul

    Wednesday, December 14, 2011 11:15 PM
  • Hi Mike

    Here's a little update for you with regard to the last test/operation I have done. I removed all of the ram all bar one stick and then ran everyhting that would normally produce a blue screen and it has not.

    I am going to run MEMTEST86 for 3 passes on the installed stick to prove that the ram and the ram slot/bay is ok.

    I will do the same for slot two and another stick of ram until something fails.

    I ran the full test on Microsoft Safety Scanner and no crash as well as running a trolley load of other stuff at the same time and nothing, yes it was slower but no blue screen.

    I am thinking that I maybe have a stick of ram that is faulty or a motherboard ram slot which is going to take me a while to slug it out as each full scan with Microsoft Safety Scanner takes 8 hours and 40 mins but it is my weapon of choice as it has crashed the system so many times before.

    I don't know how MEMTEST86 scans the ram but I am wondering if there has somehow been a "safety in numbers" thing going on and maybe the other ram supported the faulty ram in some way to make it look like there were no ram faults.

    Still a long way to go as I have a lot more testing to do as I plan to do everything you have recommended as well as what I am currently doing but I am sure that if the pc gets kicked hard enough something will fall out at some point.

    Thanks once again.

    Paul

    Thursday, December 15, 2011 1:05 AM
  • Hi Mike

    I am about 50% through the ram/memory slot check and so far the system is not crashing. I still have two sticks to check and two memory slots to check and I do not understand why it has not crashed yet as I am throwing everything at the system...

    Running to two online tv documentaries at the same time.

    Google earth running and I have the world spinning at a huge rate of knots to give the graphics card something to think about.

    Five large photographs open at the same time.

    Autocad 2012 and Autodesk Inventor - two large computer aided design programs.

    Safety scanner open and running a full scan.

    Ten web pages open in Firefox with youtube and video files running.

    No crashes yet and while I can tell that the system is slower I expect it to finish the scan with no crash.

    Testing each stick and memory slot is taking around 1-2 hours for the passes with MEMTEST86 v 4.2 and approx. 8-9 hours for Safety scanner/other applications test. I plan to then introduce extra stick after I have tested each individual stick and ultimately test all the sticks working together again.

    Really exected the system to have fallen over by now????

    Regards

    Paul

    Thursday, December 15, 2011 5:55 PM
  • I would think so too, maybe you will identify it with the other two
    sticks of RAM and the other 2 DIMM slots...
     

    -- Mike Burr
    Technology
    Thursday, December 15, 2011 7:10 PM
  • Hi Mike

    I think I may have solved this one????

    I have no problems with running 1 stick of ram and all ram has been MEMtested with v4.2 and I have now tested all of the dimms and I have thrown everything at the pc and there is no stop errors.

    I think the problem is the amount of ram. In an earlier post I wondered if the amount of ram I have could be causing  the problem "too much of a good thing" and I think that using two sticks of 4gb in the first two dimms will be fine but I do not think that the voltages will be sufficient if I install further ram into a third and fourth dimms.

    I have hunted high and low on the web for possible comparisons with my BSOD problem and this is the only that I think fits.

    This would account for the power failure as many posts similar to mine a recommendation is to change the PSU but I have 750W PSU and it is almost impossible to check the PSU I believe.

    I am going to go through all of the motherboard/CPU/ram documentation I have tonight to see how much I can safely kick up the voltages on the CPU and the memory to stop the instability.

    Before I go ahead with this one I just want to know what you think about this as I do not want to fry the CPU and ram.

    Kind regards

    Paul

    Thursday, December 15, 2011 10:28 PM
  • Hi Mike

    I am waiting to hear back from the supplier of the ram and the ram manufacturer [gskill] to see if the blue screens are caused by having 16gb of ram over over 4 dimms. My motherboard can handle 16gb but I don't think that the dual channel platfom works with 2 matched pairs of dual channel ram across 4 dimms.

    I don't know as yet if the setup with 16gb over 4 dimms causes some sort of dip or spike in voltage or maybe even a heat issue  but observation is showing that the amount ram is an issue as the use of 4 gb ram is making the system more stable than using 16gb.

    Maybe it is to do with the two matched pairs 'fighting' for bandwidth, time will tell as I hope hear back from the manufacturer today.

    Really hope this is it?

    Regards

    Paul

     

    Friday, December 16, 2011 9:22 AM
  • Hi John

    I have a stable system.... with 8gb, as soon as I populate all four dimms with the 16gb the system becomes unstable. My motherboard can handle 16gb but I don't think that the ram works well together as a team of four.

    Strange don't you think? Ever heard of this before???

    Regards

    Paul

    Saturday, December 17, 2011 11:31 PM
  • Anything is possible, is the RAM certified to work with that motherboard?
     

    -- Mike Burr
    Technology
    Monday, December 19, 2011 12:14 AM
  • I have a 16 GB Windows 7 system that's quite stable.  It's not a systemic problem with Windows using 16 GB.

    RAM *does* fail - more often than you'd think.  It's the downside of running everything at the fastest possible speeds while trying to keep costs down.

    We have had multiple workstations with ECC (error correcting) RAM in which the systems will immediately halt on uncorrectable RAM errors (and will report corrected RAM errors if queried).  Some of the systems required several RAM module replacements before they were finally stabilized.  After realizing how many errors these systems caught, I'll never have another system that has anything but ECC RAM, even though it costs more.

    -Noel

    Monday, December 19, 2011 3:33 AM
  • Hi Noel,

    I have got a very stable 16gb system at present as I think I have solved the original issue with 16gb. I have been informed by Gskill that they do not guarantee the use of 2 x 4gb sets over four dimms and that I may get an unstable system. I have ruled out the possiblity of faulty ram as every stick has been MEMTESTED over and over again and while I know MEMTEST can never find everything I think that the main reason for the fault is the fact that I am a novice with building PC's.

    Today I decided to take all the ram out and have a look at how I installed it and realized that in my rush of energy to get it built that I may have fitted the sets in an order that caused the instability. I have looked at the barcodes on the ram and fitted it in such a way that I feel will work right with the dimm layout.

    When I first assembled the pc I worked on two large tables, one table had all the unwraped components and I used the other table to assemble the pc....sounds fine but I think that the ram may have been somehow mixed up so that it was not in the dimms in the correct layout. This is the only thing that I can think of now and I cannot say for certain that this is what I did as the ram has been in and out over the last week or so to do testing on each stick and pairs of sticks.

    But here I am with things working fine at the moment running a trolley load of applications on a 16gb system that have tripped up by now based on past history.

    I'm keeping my fingers crossed as the news from Gskill did not fill me with confidence.

    Thanks for getting in touch and all the very best to you. Hope santa brings something nice... I'm hoping for a stable system and a nice new 28"monitor.

    Regards

    Paul

    Scotland

     

    Monday, December 19, 2011 7:37 PM
  • Hi Mike

    I was informed it was but that means nothing but I do think that I cracked the possible cause today. I have been informed by GSKILL that the do not reccomend the use of two set over 4 dimms and if I do my guarantee is void....thanks GSKILL. I looked at all the ram again by removing it from the dimms and looking at the barcodes and then reinstalling them in the dimms they way that looked suitable and I have a stable system at present.

    It could be that when I installed the ram that the sets somehow got mixed up and this caused the problem but I really can not say for certain as the ram has been moved about a bit over the last few days.

    Here's hoping it is done and dusted????

    all the best Mike, have a great Christmas and New Year!

    Thanks again for all your help.

    Regards

    Paul

    • Marked as answer by Niki Han Wednesday, December 28, 2011 5:41 AM
    Monday, December 19, 2011 7:46 PM