1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Blue Screen error

Discussion in 'Windows 7' started by TXCookiemonster, 2010/05/30.

  1. 2010/05/30
    TXCookiemonster

    TXCookiemonster Inactive Thread Starter

    Joined:
    2010/05/30
    Messages:
    4
    Likes Received:
    0
    I'm new to this site but I've gotten this blue screen error here. The info that I got are as follows:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 7f
    BCP1: 0000000000000008
    BCP2: 0000000080050031
    BCP3: 00000000000406F8
    BCP4: FFFFF80002CEF1ED
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\053010-30310-01.dmp
    C:\Users\Owner\AppData\Local\Temp\WER-52915-0.sysdata.xml

    Now a few months ago I was getting 8e errors or something like that and I got drivefinder and updated all drivers that were out of date and that seemed to fix the problem. Now I'm at a lost of what to do with this one. I'm not sure where this error is so If yall can help I would appreciate it. My system info is:

    OS Name: Microsoft Windows 7 Home Premium
    OS version: 6.1.7600 N/A Build 7600
    OS Config: Standalone Workstation
    OS Build Type: Multiprocessor Free
    System Type: x64-based PC
    Processor: Pentuim Dual-Core CPU E5300 @ 2.60GHz 2.60 GHz
    RAM: 8.00GB
    Memory: 1TB
    If yall need any more info, please let me know.

    Thanks,
    Dave
    Semper Fi
     
    TXCookiemonster,
    #1
  2. 2010/05/30
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    An explanation of of the stop error ....
    Probably the best move is to run the dump file - C:\Windows\Minidump\053010-30310-01.dmp through BlueScreenView and look for the files highlightesd in pink in the results window - as shown on their site and post them here.

    Note that one possible cause is memory so it would be worth checking that out .....

    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.

    Note ....
     
    PeteC,
    #2


  3. to hide this advert.

  4. 2010/06/02
    TXCookiemonster

    TXCookiemonster Inactive Thread Starter

    Joined:
    2010/05/30
    Messages:
    4
    Likes Received:
    0
    Hello,
    Hey thanks a million for the bluescreenview info. The main problem I'm having now is that my minidump folder is empty. I can right click on the folder and select previous versions and it will show the earlier minidump files but it won't let me put them in a place where I can actually access them with bluescreenview. I can't restore those files and when I try, it says that I don't have access. Now I got another blue screen error and it did come up on bluescreenview and I did copy the things that came up during the latest blue screen view. The things that were highligted in pink were the "caused by driver ". Now if you have any ideas on how to access the things in my minidump folder under the previous versions area, please let me know. The one thing I did was on one of the files that did come up, I selected the bluescreenview to open the .dmp file but the file still won't show up on the application of bluescreenview. So I would appreciate any help that could be given my way. Thank you.

    Semper Fi,
    Dave

    Dump File : 053110-93038-01.dmp
    Crash Time : 5/31/2010 12:11:18 AM
    Bug Check String : APC_INDEX_MISMATCH
    Bug Check Code : 0x00000001
    Parameter 1 : 00000000`77ae040a
    Parameter 2 : 00000000`00000000
    Parameter 3 : 00000000`0000ffff
    Parameter 4 : fffff880`091454a0
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+70600
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
    Processor : x64
    Computer Name :
    Full Path : C:\Windows\Minidump\053110-93038-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7600
    ==================================================

    This is the other type of copy and paste that I did. This was on the bottom part.

    Filename : ntoskrnl.exe
    Address In Stack : ntoskrnl.exe+6fb69
    From Address : fffff800`02c5e000
    To Address : fffff800`0323a000
    Size : 0x005dc000
    Time Stamp : 0x4b88cfeb
    Time String : 2/27/2010 2:55:23 AM
    Product Name : Microsoft® Windows® Operating System
    File Description : NT Kernel & System
    File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
    Company : Microsoft Corporation
    Full Path : C:\Windows\system32\ntoskrnl.exe
    ==================================================
     
    TXCookiemonster,
    #3
  5. 2010/06/02
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    My only thought re. previous versions of the .dmp files being inaccessible is that the default setting is for an existing file to be overwritten. This can be changed .....

    Right click My Computer icon > Properties > Advanced System Settings (left column) > Start up & Recovery > Settings and uncheck 'overwrite' and OK out.
    BlueScreenView should list the .dmp files available for analysis as shown in the upper illustration on their home page.

    Some more info on generating a BlueScreenView report ....

    I have no .dmp files on this box - has been perfectly stable since Win 7 was installed last August so cannot investigate further.

    The dump analysis you posted - APC_INDEX_MISMATCH is specific to Vista & 7 which run on a different core to XP - hence my list of STOP errors does not cover it. However there is an exolanation here .....

    http://www.geekswhoknow.com/articles/stop-0x00000001-0x0000001-apc_index_mismatch.htm

    and a couple of relevant threads here - they may say Vista, but will apply to 7 as well ....

    http://social.answers.microsoft.com...s/thread/dd45d22b-e92f-4669-88e2-f4a0871bb60d

    http://social.technet.microsoft.com...l/thread/c3b0999c-dbdb-4813-97ce-6e128e1a3e0f

    Various suggestions put forward including memory issues, as I posted earlier, and the health of the drive. On that basis I would test out the drive with the manufacturer's disk diagnostic software - DOS version - create boot CD ....

    Disk Diagnostic Software ....

    ExcelStore

    Hitachi/IBM

    Samsung

    Seagate, Maxtor, Quantum

    Western Digital

    You might also consider updating the chipset drivers for the mobo.

    BTW - We encourage all members to complete their System Specifications which help us to help you :)
     
    PeteC,
    #4
  6. 2010/06/14
    TXCookiemonster

    TXCookiemonster Inactive Thread Starter

    Joined:
    2010/05/30
    Messages:
    4
    Likes Received:
    0
    Ok..well I just got another blue screen that's similiar to the previous one and I'm having another major issue. I'll give the blue screen information first. Below is the given info:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1
    BCP1: 0000000076D5040A
    BCP2: 0000000000000000
    BCP3: 000000000000FFFF
    BCP4: FFFFF88007AAEC60
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\061310-67252-01.dmp
    C:\Windows\Temp\WER-88452-0.sysdata.xml

    Now here is the minidump report from BlueScreenView:



    ntoskrnl.exe ntoskrnl.exe+6fb69 fffff800`02e60000 fffff800`0343c000 0x005dc000 0x4b88cfeb Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16539 (win7_gdr.100226-1909) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
    hal.dll fffff800`02e17000 fffff800`02e60000 0x00049000 0x4a5bdf08
    kdcom.dll fffff800`00bcb000 fffff800`00bd5000 0x0000a000 0x4a5bdfdb
    mcupdate_GenuineIntel.dll fffff880`00c31000 fffff880`00c75000 0x00044000 0x4a5bdf66
    PSHED.dll fffff880`00c75000 fffff880`00c89000 0x00014000 0x4a5be027 Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll
    CLFS.SYS fffff880`00c89000 fffff880`00ce7000 0x0005e000 0x4a5bc11d
    CI.dll fffff880`00ce7000 fffff880`00da7000 0x000c0000 0x4a5be01d
    Wdf01000.sys fffff880`00ed3000 fffff880`00f77000 0x000a4000 0x4a5bc19f
    WDFLDR.SYS fffff880`00f77000 fffff880`00f86000 0x0000f000 0x4a5bc11a
    ACPI.sys fffff880`00f86000 fffff880`00fdd000 0x00057000 0x4a5bc106
    WMILIB.SYS fffff880`00fdd000 fffff880`00fe6000 0x00009000 0x4a5bc117
    fltmgr.sys fffff880`00e00000 fffff880`00e4c000 0x0004c000 0x4a5bc11f
    msisadrv.sys fffff880`00e4c000 fffff880`00e56000 0x0000a000 0x4a5bc0fe
    pci.sys fffff880`00e56000 fffff880`00e89000 0x00033000 0x4a5bc117
    vdrvroot.sys fffff880`00e89000 fffff880`00e96000 0x0000d000 0x4a5bcadb
    partmgr.sys fffff880`00e96000 fffff880`00eab000 0x00015000 0x4a5bc11e
    volmgr.sys fffff880`00eab000 fffff880`00ec0000 0x00015000 0x4a5bc11d
    volmgrx.sys fffff880`010aa000 fffff880`01106000 0x0005c000 0x4a5bc141
    mountmgr.sys fffff880`01106000 fffff880`01120000 0x0001a000 0x4a5bc11a
    iaStor.sys fffff880`0126f000 fffff880`0138b000 0x0011c000 0x4a287aa4
    amdxata.sys fffff880`0138b000 fffff880`01396000 0x0000b000 0x4a12f2eb
    fileinfo.sys fffff880`01396000 fffff880`013aa000 0x00014000 0x4a5bc481
    PCTCore64.sys fffff880`013aa000 fffff880`013e5000 0x0003b000 0x4bafde56
    Ntfs.sys fffff880`01441000 fffff880`015e4000 0x001a3000 0x4a5bc14f
    msrpc.sys fffff880`01200000 fffff880`0125e000 0x0005e000 0x4a5bc17c
    ksecdd.sys fffff880`015e4000 fffff880`015fe000 0x0001a000 0x4a5bc156
    cng.sys fffff880`01120000 fffff880`01193000 0x00073000 0x4a5bc814
    pcw.sys fffff880`01400000 fffff880`01411000 0x00011000 0x4a5bc0ff
    Fs_Rec.sys fffff880`01411000 fffff880`0141b000 0x0000a000 0x4a5bc111
    ndis.sys fffff880`01603000 fffff880`016f5000 0x000f2000 0x4a5bc184
    NETIO.SYS fffff880`016f5000 fffff880`01755000 0x00060000 0x4a5bc18a
    ksecpkg.sys fffff880`01755000 fffff880`01780000 0x0002b000 0x4b21e0b4
    tcpip.sys fffff880`01803000 fffff880`01a00000 0x001fd000 0x4a5bc26e
    fwpkclnt.sys fffff880`01780000 fffff880`017ca000 0x0004a000 0x4a5bc164
    volsnap.sys fffff880`01193000 fffff880`011df000 0x0004c000 0x4a5bc128
    spldr.sys fffff880`017ca000 fffff880`017d2000 0x00008000 0x4a0858bb
    rdyboost.sys fffff880`01000000 fffff880`0103a000 0x0003a000 0x4a5bc48a
    mup.sys fffff880`017d2000 fffff880`017e4000 0x00012000 0x4a5bc201
    hwpolicy.sys fffff880`017e4000 fffff880`017ed000 0x00009000 0x4a5bc0fa
    fvevol.sys fffff880`0103a000 fffff880`01074000 0x0003a000 0x4abd7db2
    disk.sys fffff880`0141b000 fffff880`01431000 0x00016000 0x4a5bc11d
    CLASSPNP.SYS fffff880`01074000 fffff880`010a4000 0x00030000 0x4a5bc11e
    cdrom.sys fffff880`02d5a000 fffff880`02d84000 0x0002a000 0x4a5bc11a
    Null.SYS fffff880`02d84000 fffff880`02d8d000 0x00009000 0x4a5bc109
    Beep.SYS fffff880`02d8d000 fffff880`02d94000 0x00007000 0x4a5bca8d
    vga.sys fffff880`02d94000 fffff880`02da2000 0x0000e000 0x4a5bc587
    VIDEOPRT.SYS fffff880`02da2000 fffff880`02dc7000 0x00025000 0x4a5bc58b
    watchdog.sys fffff880`02dc7000 fffff880`02dd7000 0x00010000 0x4a5bc53f
    RDPCDD.sys fffff880`02dd7000 fffff880`02de0000 0x00009000 0x4a5bce62
    rdpencdd.sys fffff880`02de0000 fffff880`02de9000 0x00009000 0x4a5bce62
    rdprefmp.sys fffff880`02de9000 fffff880`02df2000 0x00009000 0x4a5bce63
    Msfs.SYS fffff880`02df2000 fffff880`02dfd000 0x0000b000 0x4a5bc113
    Npfs.SYS fffff880`02c00000 fffff880`02c11000 0x00011000 0x4a5bc114
    tdx.sys fffff880`011df000 fffff880`011fd000 0x0001e000 0x4a5bc16b
    TDI.SYS fffff880`02c11000 fffff880`02c1e000 0x0000d000 0x4a5bc16e
    pctgntdi64.sys fffff880`00da7000 fffff880`00df7000 0x00050000 0x4b6b15f0
    PctWfpFilter64.sys fffff880`00c00000 fffff880`00c24000 0x00024000 0x4b6b176c
    afd.sys fffff880`03a3f000 fffff880`03ac9000 0x0008a000 0x4a5bc184
    netbt.sys fffff880`03ac9000 fffff880`03b0e000 0x00045000 0x4a5bc178
    ws2ifsl.sys fffff880`03b0e000 fffff880`03b19000 0x0000b000 0x4a5bccf9
    wfplwf.sys fffff880`03b19000 fffff880`03b22000 0x00009000 0x4a5bccb6
    pacer.sys fffff880`03b22000 fffff880`03b48000 0x00026000 0x4a5bccc5
    netbios.sys fffff880`03b48000 fffff880`03b57000 0x0000f000 0x4a5bccb6
    wanarp.sys fffff880`03b57000 fffff880`03b72000 0x0001b000 0x4a5bcced
    termdd.sys fffff880`03b72000 fffff880`03b86000 0x00014000 0x4a5bce64
    rdbss.sys fffff880`03b86000 fffff880`03bd7000 0x00051000 0x4a5bc219
    nsiproxy.sys fffff880`03bd7000 fffff880`03be3000 0x0000c000 0x4a5bc15e
    mssmbios.sys fffff880`03be3000 fffff880`03bee000 0x0000b000 0x4a5bc3be
    ElRawDsk.sys fffff880`03bee000 fffff880`03bf8000 0x0000a000 0x488b65ed
    discache.sys fffff880`03a00000 fffff880`03a0f000 0x0000f000 0x4a5bc52e
    dfsc.sys fffff880`03a0f000 fffff880`03a2d000 0x0001e000 0x4a5bc200
    blbdrive.sys fffff880`03a2d000 fffff880`03a3e000 0x00011000 0x4a5bc4df
    tunnel.sys fffff880`03c83000 fffff880`03ca9000 0x00026000 0x4a5bccc1
    intelppm.sys fffff880`03ca9000 fffff880`03cbf000 0x00016000 0x4a5bc0fd
    nvlddmkm.sys fffff880`0fe95000 fffff880`10bbe700 0x00d29700 0x4bb7d7fd
    nvBridge.kmd fffff880`10bbf000 fffff880`10bc0180 0x00001180 0x4bb7d45c
    dxgkrnl.sys fffff880`03cbf000 fffff880`03db3000 0x000f4000 0x4ac5509e
    dxgmms1.sys fffff880`0fe00000 fffff880`0fe46000 0x00046000 0x4a5bc578
    usbuhci.sys fffff880`0fe46000 fffff880`0fe53000 0x0000d000 0x4a5bcc03
    USBPORT.SYS fffff880`03c00000 fffff880`03c56000 0x00056000 0x4a5bcc07
    usbehci.sys fffff880`0fe53000 fffff880`0fe64000 0x00011000 0x4a5bcc06
    HDAudBus.sys fffff880`0fe64000 fffff880`0fe88000 0x00024000 0x4a5bcbf5
    Rt64win7.sys fffff880`03ee6000 fffff880`03f3d000 0x00057000 0x4b8fb8dc
    1394ohci.sys fffff880`03f3d000 fffff880`03f7b000 0x0003e000 0x4a5bcc30
    CompositeBus.sys fffff880`03f7b000 fffff880`03f8b000 0x00010000 0x4a5bcaa1
    msiscsi.sys fffff880`03f8b000 fffff880`03fc6000 0x0003b000 0x4a5bcad7
    storport.sys fffff880`03e00000 fffff880`03e62000 0x00062000 0x4a5bcace
    RootMdm.sys fffff880`03e62000 fffff880`03e6a000 0x00008000 0x4a5bcd07
    modem.sys fffff880`03e6a000 fffff880`03e79000 0x0000f000 0x4a5bcd08
    AgileVpn.sys fffff880`03e79000 fffff880`03e8f000 0x00016000 0x4a5bccf0
    rasl2tp.sys fffff880`03e8f000 fffff880`03eb3000 0x00024000 0x4a5bcce3
    ndistapi.sys fffff880`03eb3000 fffff880`03ebf000 0x0000c000 0x4a5bccd8
    ndiswan.sys fffff880`03fc6000 fffff880`03ff5000 0x0002f000 0x4a5bcce3
    raspppoe.sys fffff880`03ebf000 fffff880`03eda000 0x0001b000 0x4a5bcce9
    raspptp.sys fffff880`10bc1000 fffff880`10be2000 0x00021000 0x4a5bccea
    rassstp.sys fffff880`10be2000 fffff880`10bfc000 0x0001a000 0x4a5bccf1
    RimSerial_AMD64.sys fffff880`03eda000 fffff880`03ee1c00 0x00007c00 0x492addcd
    kbdclass.sys fffff880`03c56000 fffff880`03c65000 0x0000f000 0x4a5bc116
    mouclass.sys fffff880`03c65000 fffff880`03c74000 0x0000f000 0x4a5bc116
    pctNdis64.sys fffff880`03db3000 fffff880`03dca000 0x00017000 0x4b452912
    swenum.sys fffff880`03ee2000 fffff880`03ee3480 0x00001480 0x4a5bca92
    ks.sys fffff880`042dc000 fffff880`0431f000 0x00043000 0x4a5bca9f
    umbus.sys fffff880`0431f000 fffff880`04331000 0x00012000 0x4a5bcc20
    usbhub.sys fffff880`04331000 fffff880`0438b000 0x0005a000 0x4a5bcc2d
    NDProxy.SYS fffff880`0438b000 fffff880`043a0000 0x00015000 0x4a5bccdd
    RTKVHD64.sys fffff880`05e04000 fffff880`05fe4400 0x001e0400 0x4a78047c
    portcls.sys fffff880`043a0000 fffff880`043dd000 0x0003d000 0x4a5bcc03
    drmk.sys fffff880`043dd000 fffff880`043ff000 0x00022000 0x4a5bd8e5
    ksthunk.sys fffff880`05fe5000 fffff880`05fea200 0x00005200 0x4a5bca93
    win32k.sys fffff960`000b0000 fffff960`003bf000 0x0030f000 0x4bdc4376
    Dxapi.sys fffff880`05feb000 fffff880`05ff7000 0x0000c000 0x4a5bc574
    monitor.sys fffff880`04200000 fffff880`0420e000 0x0000e000 0x4a5bc58c
    RtsUStor.sys fffff880`0420e000 fffff880`0424d000 0x0003f000 0x4ba9e1e5
    USBD.SYS fffff880`05ff7000 fffff880`05ff8f00 0x00001f00 0x4a5bcbff
    cdfs.sys fffff880`0424d000 fffff880`0426a000 0x0001d000 0x4a5bc112
    usbccgp.sys fffff880`0426a000 fffff880`04287000 0x0001d000 0x4a5bcc15
    hidusb.sys fffff880`04287000 fffff880`04295000 0x0000e000 0x4a5bcbfe
    HIDCLASS.SYS fffff880`04295000 fffff880`042ae000 0x00019000 0x4a5bcbfd
    HIDPARSE.SYS fffff880`042ae000 fffff880`042b6080 0x00008080 0x4a5bcbf9
    mouhid.sys fffff880`042b7000 fffff880`042c4000 0x0000d000 0x4a5bca94
    kbdhid.sys fffff880`042c4000 fffff880`042d2000 0x0000e000 0x4a5bca94
    TSDDD.dll fffff960`004c0000 fffff960`004ca000 0x0000a000 0x00000000
    usbprint.sys fffff880`0fe88000 fffff880`0fe94000 0x0000c000 0x4a5bd37a
    dot4usb.sys fffff880`03dca000 fffff880`03dda000 0x00010000 0x4a5bca94
    Dot4.sys fffff880`02c1e000 fffff880`02c46000 0x00028000 0x4a5bca90
    USBSTOR.SYS fffff880`03dda000 fffff880`03df5000 0x0001b000 0x4a5bcc0a
    Dot4Prt.sys fffff880`042d2000 fffff880`042dc000 0x0000a000 0x4a5bca8d
    cdd.dll fffff960`007c0000 fffff960`007e7000 0x00027000 0x4a5bde94
    ATMFD.DLL fffff960`008c0000 fffff960`00921000 0x00061000 0x4bfdf0f3 Adobe Type Manager Windows NT OpenType/Type 1 Font Driver 5.1 Build 228 Adobe Systems Incorporated C:\Windows\system32\ATMFD.DLL
    usbscan.sys fffff880`02c46000 fffff880`02c57000 0x00011000 0x4a5bd2d4
    luafv.sys fffff880`02c57000 fffff880`02c7a000 0x00023000 0x4a5bc295
    crashdmp.sys fffff880`03c74000 fffff880`03c82000 0x0000e000 0x4a5bcabd
    dump_iaStor.sys fffff880`026de000 fffff880`027fa000 0x0011c000 0x4a287aa4
    dump_dumpfve.sys fffff880`02600000 fffff880`02613000 0x00013000 0x4a5bc18f
    amp.sys fffff880`02613000 fffff880`0263d000 0x0002a000 0x4ae8cab6
    lltdio.sys fffff880`0263d000 fffff880`02652000 0x00015000 0x4a5bcc92
    rspndr.sys fffff880`02652000 fffff880`0266a000 0x00018000 0x4a5bcc92
    HTTP.sys fffff880`02c7a000 fffff880`02d42000 0x000c8000 0x4a5bc1a8
    fastfat.SYS fffff880`0266a000 fffff880`026a0000 0x00036000 0x4a5bc1f0
    peauth.sys fffff880`06292000 fffff880`06338000 0x000a6000 0x4a5bd8df
    secdrv.SYS fffff880`06338000 fffff880`06343000 0x0000b000 0x4508052e
    srvnet.sys fffff880`063b4000 fffff880`063e1000 0x0002d000 0x4b1e0f1a
    tcpipreg.sys fffff880`063e1000 fffff880`063f3000 0x00012000 0x4a5bcccd
    srv2.sys fffff880`06200000 fffff880`06269000 0x00069000 0x4a5bc24e
    srv.sys fffff880`03966000 fffff880`039fe000 0x00098000 0x4b1e0f37
    pctNdis-PacketFilter64.sys fffff880`06269000 fffff880`06284000 0x0001b000 0x4b4ba091
    pctplfw64.sys fffff880`026a0000 fffff880`026cb000 0x0002b000 0x4b4ce98c
    asyncmac.sys fffff880`06284000 fffff880`0628f000 0x0000b000 0x4a5bcce5
    PCTSDInj64.sys fffff880`063f3000 fffff880`063fc220 0x00009220 0x49d47f8b
    bowser.sys fffff880`07435000 fffff880`07453000 0x0001e000 0x4a5bc206
    mrxsmb.sys fffff880`07453000 fffff880`07480000 0x0002d000 0x4b88cf33
    mrxsmb10.sys fffff880`07480000 fffff880`074ce000 0x0004e000 0x4b88cf3c
    mrxsmb20.sys fffff880`074ce000 fffff880`074f1000 0x00023000 0x4b88cf3a
    ampse.sys fffff880`03800000 fffff880`03959000 0x00159000 0x4ae8caa9
    WudfPf.sys fffff880`07522000 fffff880`07543000 0x00021000 0x4a5bcbd1
    WUDFRd.sys fffff880`07543000 fffff880`07574000 0x00031000 0x4a5bcbee

    **ntoskrnl.exe ntoskrnl.exe+6fb69 is what is highlighted in pink and it's what's causing the problem. Now I don't know how in the hell to fix it or anything. I do know that ntoskrnl.exe is located in C:/Windows/system32/ntoskrnl.exe but I don't know how to fix it now.

    The other problem I'm having is that I can't download anything off of internet explorer. I can't download Firefox, casinos, or anything. I keep getting windows internet explorer box and it says , internet explorer can't download <filename> from <website>. Something about either the internet settings are off or that the web site doesn't exist. Try again later. Now I just figured out tonight that I CAN download sites if I'm on safe mode using networking so I don't know if the ntsokrnl.exe has anything to do with it. It seems like it started when I got the blue screens.

    Computer type: HP 6110y
    My PC information is:
    Processor: Pentium Dual core CPU 2.60Ghz 2.60Ghz
    RAM: 8GB
    System Type: 64bit
    OS: Windows 7

    If there is anything else you need to know please email me or let me know otherwise.

    I'm using PCtools firewall and Iolo System Mechanic antivirus (if that helps at all).

    Take care and have a great day. Sorry about England and the USA the other day during soccer since we did tie England...lol...

    Semper Fi,

    Dave
     
    TXCookiemonster,
    #5
  7. 2010/06/14
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    So it's a rather important part of the Windows core.

    This dump looks to be the same or very similar to the first one you posted. Did you follow up any of the suggestions I made above?

    I would also eliminate malware as the root of the problem by downloading Malwarebytes, updating it and running a full scan.

    In Safe Mode only basic drivers are loaded so the fact that you can download in Safe Mode, but not in normal mode suggests a driver problem.

    Have you tried a Reset of Internet Explorer - Tools > Internet Options > Advanced - Reset?

    Appreciate your comment re. the World Cup - I'm not a follower of football and have very little faith in our National team anyway :)
     
    PeteC,
    #6
  8. 2010/06/14
    Christer

    Christer Geek Member Staff

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Christer,
    #7
  9. 2010/06/15
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    It is true that the Windows Memory Diagnostic Tool is now included in Windows 7 and its always worth a run, bearing in mind ......
    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.
     
    PeteC,
    #8
  10. 2010/06/15
    Christer

    Christer Geek Member Staff

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    My mistake ... :eek: ... I thought that this was not "some memory checking program" but their own would do it the right way!

    I've always believed that these procedures are to single out which module is faulty or if the modules are working fine but the motherboard is faulty.
     
    Christer,
    #9
  11. 2010/06/15
    alienboy

    alienboy Inactive

    Joined:
    2009/06/11
    Messages:
    1
    Likes Received:
    0
    I had a blue screen the other day on vista home premium 64 bit, i think it was because one of my memory modules came loose so maybe try shutting everything down and reseating the modules.

    Hope that helps anyone with a simialr problem =)
     
    alienboy,
    #10

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...