BSOD help - this is driving me nuts please help me

By EV1L1NT3NT
Jul 20, 2009
Topic Status:
Not open for further replies.
  1. Hi guys, any chance you could give me some advice on what is causing these blue screens??

    they are happening very frequently (2-3 times in 3 hours)

    here are my logs / minidump.

    this is what windows reported when i restarted last crash....

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.0.6000.2.0.0.768.3
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 1e
    BCP1: FFFFFFFFC0000005
    BCP2: FFFFF80001C6F768
    BCP3: 0000000000000000
    BCP4: FFFFFFFFFFFFFFFF
    OS Version: 6_0_6000
    Service Pack: 0_0
    Product: 768_1

    then this is my saved mu saved debuglog after using kd on my minidump file.

    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * 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: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80001c6f768, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

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


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

    FAULTING_IP:
    nt!MiCheckVirtualAddress+c8
    fffff800`01c6f768 0fba612814 bt dword ptr [rcx+28h],14h

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001dfa0b0
    ffffffffffffffff

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x1E

    PROCESS_NAME: Dreamweaver.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80001cbad37 to fffff80001c4dd90

    STACK_TEXT:
    fffff980`1df7a178 fffff800`01cbad37 : 00000000`0000001e ffffffff`c0000005 fffff800`01c6f768 00000000`00000000 : nt!KeBugCheckEx
    fffff980`1df7a180 fffff800`01c4dbee : fffff980`1df7a8b8 fffffa80`0798d8a0 fffff980`1df7a960 fffff980`1df7ab78 : nt! ?? ::FNODOBFM::`string'+0x12767
    fffff980`1df7a780 fffff800`01c4c7cd : 0000000c`00000040 ffffffff`0000000c 00000000`00000004 00000400`00000400 : nt!KiExceptionDispatch+0xae
    fffff980`1df7a960 fffff800`01c6f768 : 00000000`00000f00 fffffa80`0406c000 00000002`042827b0 fffff800`01cc6ba9 : nt!KiGeneralProtectionFault+0xcd
    fffff980`1df7aaf0 fffff800`01c555c6 : 00000000`00000000 fffffa80`04ac9bb0 00000000`0007fd20 00000000`7efdb000 : nt!MiCheckVirtualAddress+0xc8
    fffff980`1df7ab20 fffff800`01c4c919 : 00000000`00000000 00000000`0f57e618 00000000`0f4b8d01 00000000`00000000 : nt!MmAccessFault+0x202a
    fffff980`1df7ac20 00000000`75cd904c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119
    00000000`00179068 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75cd904c


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiCheckVirtualAddress+c8
    fffff800`01c6f768 0fba612814 bt dword ptr [rcx+28h],14h

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: nt!MiCheckVirtualAddress+c8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 49ac932a

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: X64_0x1E_nt!MiCheckVirtualAddress+c8

    BUCKET_ID: X64_0x1E_nt!MiCheckVirtualAddress+c8

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

    will post part 2 in a sec
  2. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    Part two of debug

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

    rax=ffffffffffffffff rbx=fffff9801df7a8b8 rcx=000000000000001e
    rdx=ffffffffc0000005 rsi=fffff9801df7a960 rdi=0000000000075cd9
    rip=fffff80001c4dd90 rsp=fffff9801df7a178 rbp=fffff9801df7a9e0
    r8=fffff80001c6f768 r9=0000000000000000 r10=fffff9801df7ac20
    r11=fffff80001c00000 r12=0000000080000003 r13=fffff9801df7a780
    r14=0000000000000000 r15=fffff9801df7ac00
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00200246
    nt!KeBugCheckEx:
    fffff800`01c4dd90 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff980`1df7a180=000000000000001e
    Child-SP RetAddr : Args to Child : Call Site
    fffff980`1df7a178 fffff800`01cbad37 : 00000000`0000001e ffffffff`c0000005 fffff800`01c6f768 00000000`00000000 : nt!KeBugCheckEx
    fffff980`1df7a180 fffff800`01c4dbee : fffff980`1df7a8b8 fffffa80`0798d8a0 fffff980`1df7a960 fffff980`1df7ab78 : nt! ?? ::FNODOBFM::`string'+0x12767
    fffff980`1df7a780 fffff800`01c4c7cd : 0000000c`00000040 ffffffff`0000000c 00000000`00000004 00000400`00000400 : nt!KiExceptionDispatch+0xae
    fffff980`1df7a960 fffff800`01c6f768 : 00000000`00000f00 fffffa80`0406c000 00000002`042827b0 fffff800`01cc6ba9 : nt!KiGeneralProtectionFault+0xcd (TrapFrame @ fffff980`1df7a960)
    fffff980`1df7aaf0 fffff800`01c555c6 : 00000000`00000000 fffffa80`04ac9bb0 00000000`0007fd20 00000000`7efdb000 : nt!MiCheckVirtualAddress+0xc8
    fffff980`1df7ab20 fffff800`01c4c919 : 00000000`00000000 00000000`0f57e618 00000000`0f4b8d01 00000000`00000000 : nt!MmAccessFault+0x202a
    fffff980`1df7ac20 00000000`75cd904c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x119 (TrapFrame @ fffff980`1df7ac20)
    00000000`00179068 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75cd904c
    start end module name
    fffff800`01c00000 fffff800`020d5000 nt ntkrnlmp.exe Tue Mar 03 02:17:14 2009 (49AC932A)
    fffff800`020d5000 fffff800`02126000 hal hal.dll Sun Dec 24 07:50:33 2006 (458E3149)
    fffff960`00000000 fffff960`002b2000 win32k win32k.sys Tue Apr 21 13:20:10 2009 (49EDB9FA)
    fffff960`00400000 fffff960`0040a000 TSDDD TSDDD.dll unavailable (00000000)
    fffff960`00600000 fffff960`00611000 cdd cdd.dll Tue Jul 03 04:19:46 2007 (4689C052)
    fffff980`00000000 fffff980`00009000 WMILIB WMILIB.SYS Thu Nov 02 09:43:26 2006 (4549BDBE)
    fffff980`00009000 fffff980`00060000 CLFS CLFS.SYS Thu Dec 06 02:10:53 2007 (47575A2D)
    fffff980`00060000 fffff980`00069000 PSHED PSHED.dll Thu Nov 02 11:14:26 2006 (4549D312)
    fffff980`00069000 fffff980`00095000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Apr 24 05:49:44 2007 (462D8C68)
    fffff980`00095000 fffff980`0009e000 kdcom kdcom.dll Thu Nov 02 11:14:44 2006 (4549D324)
    fffff980`00205000 fffff980`0020c000 pciide pciide.sys Sat Jan 19 03:10:33 2008 (47916A29)
    fffff980`0020c000 fffff980`0021f000 mountmgr mountmgr.sys Thu Nov 02 09:37:17 2006 (4549BC4D)
    fffff980`0021f000 fffff980`00231000 volmgr volmgr.sys Thu Nov 02 09:38:28 2006 (4549BC94)
    fffff980`00231000 fffff980`0023b000 msisadrv msisadrv.sys Thu Nov 02 09:10:06 2006 (4549B5EE)
    fffff980`0023b000 fffff980`00269000 SCSIPORT SCSIPORT.SYS Thu Nov 02 09:38:12 2006 (4549BC84)
    fffff980`00269000 fffff980`00277000 WDFLDR WDFLDR.SYS Thu Dec 06 02:50:19 2007 (4757636B)
    fffff980`00277000 fffff980`0034d000 Wdf01000 Wdf01000.sys Thu Dec 06 02:51:28 2007 (475763B0)
    fffff980`0034d000 fffff980`00400000 CI CI.dll Tue Feb 19 04:51:41 2008 (47BA605D)
    fffff980`00401000 fffff980`00410000 nvstor nvstor.sys Wed Oct 04 01:24:56 2006 (4522FF58)
    fffff980`00410000 fffff980`00434000 ataport ataport.SYS Sat Jan 19 03:10:34 2008 (47916A2A)
    fffff980`00434000 fffff980`0043c000 atapi atapi.sys Sat Jan 19 03:10:31 2008 (47916A27)
    fffff980`0043c000 fffff980`0044c000 PCIIDEX PCIIDEX.SYS Sat Jan 19 03:10:32 2008 (47916A28)
    fffff980`0044c000 fffff980`00479000 pci pci.sys Thu Nov 02 09:10:11 2006 (4549B5F3)
    fffff980`00479000 fffff980`004cc000 acpi acpi.sys Fri Aug 31 02:18:22 2007 (46D76C5E)
    fffff980`004cc000 fffff980`00600000 sptd sptd.sys Sun Mar 22 12:35:35 2009 (49C63097)
    fffff980`00609000 fffff980`00613000 crcdisk crcdisk.sys Thu Nov 02 09:39:40 2006 (4549BCDC)
    fffff980`00613000 fffff980`00625000 mup mup.sys Thu Nov 02 09:01:24 2006 (4549B3E4)
    fffff980`00625000 fffff980`00637000 partmgr partmgr.sys Thu Nov 02 09:38:30 2006 (4549BC96)
    fffff980`00637000 fffff980`0063f000 spldr spldr.sys Thu Oct 26 00:10:19 2006 (453FEEDB)
    fffff980`0063f000 fffff980`00647000 wd wd.sys Thu Nov 02 09:42:07 2006 (4549BD6F)
    fffff980`00647000 fffff980`0069b000 NETIO NETIO.SYS Mon Jan 14 03:41:02 2008 (478AD9CE)
    fffff980`0069b000 fffff980`006eb000 msrpc msrpc.sys Thu Nov 02 09:36:03 2006 (4549BC03)
    fffff980`006eb000 fffff980`006ff000 fileinfo fileinfo.sys Thu Nov 02 09:12:51 2006 (4549B693)
    fffff980`006ff000 fffff980`00742000 fltmgr fltmgr.sys Thu Nov 02 09:01:19 2006 (4549B3DF)
    fffff980`00742000 fffff980`00751000 nvstor64 nvstor64.sys Sat Dec 23 16:07:42 2006 (458D544E)
    fffff980`00751000 fffff980`007a7000 storport storport.sys Thu Nov 02 09:38:25 2006 (4549BC91)
    fffff980`007a7000 fffff980`00800000 volmgrx volmgrx.sys Thu Nov 02 09:38:40 2006 (4549BCA0)
    fffff980`00806000 fffff980`0081a000 disk disk.sys Thu Nov 02 09:38:20 2006 (4549BC8C)
    fffff980`0081a000 fffff980`0085a000 volsnap volsnap.sys Fri Oct 26 03:38:04 2007 (4721530C)
    fffff980`0085a000 fffff980`00a00000 ndis ndis.sys Thu Nov 02 09:46:57 2006 (4549BE91)
    fffff980`00a0d000 fffff980`00a89000 ksecdd ksecdd.sys Thu Nov 02 09:25:31 2006 (4549B98B)
    fffff980`00a89000 fffff980`00c00000 Ntfs Ntfs.sys Sun Dec 16 09:48:02 2007 (4764F452)
    fffff980`00daf000 fffff980`00dd7000 CLASSPNP CLASSPNP.SYS Thu Nov 02 09:38:10 2006 (4549BC82)
    fffff980`00dd7000 fffff980`00e00000 ecache ecache.sys Thu Nov 02 09:40:11 2006 (4549BCFB)
    fffff980`01c30000 fffff980`01c40000 usbehci usbehci.sys Fri Aug 31 02:50:35 2007 (46D773EB)
    fffff980`01d70000 fffff980`01d7fe00 1394BUS 1394BUS.SYS Thu Nov 02 09:43:52 2006 (4549BDD8)
    fffff980`01dd0000 fffff980`01de0000 raspppoe raspppoe.sys Thu Nov 02 09:47:32 2006 (4549BEB4)
    fffff980`02140000 fffff980`02150000 umbus umbus.sys Thu Nov 02 09:44:03 2006 (4549BDE3)
    fffff980`03cbd000 fffff980`03cbe180 nvBridge nvBridge.kmd Wed Jun 10 14:24:21 2009 (4A2FB405)
    fffff980`03cbf000 fffff980`03cc0d80 USBD USBD.SYS Fri Aug 31 02:50:30 2007 (46D773E6)
    fffff980`03cd5000 fffff980`03cd6480 swenum swenum.sys Thu Nov 02 09:37:33 2006 (4549BC5D)
    fffff980`04c09000 fffff980`04c14000 usbohci usbohci.sys Fri Aug 31 02:50:35 2007 (46D773EB)
    fffff980`04c81000 fffff980`04c92000 Npfs Npfs.SYS Thu Nov 02 09:01:04 2006 (4549B3D0)
    fffff980`04da6000 fffff980`04db1000 mssmbios mssmbios.sys Thu Nov 02 09:10:10 2006 (4549B5F2)
    fffff980`04db1000 fffff980`04dc3000 intelppm intelppm.sys Thu Nov 02 09:00:15 2006 (4549B39F)
    fffff980`05600000 fffff980`05612000 termdd termdd.sys Thu Nov 02 09:52:08 2006 (4549BFC8)
    fffff980`05612000 fffff980`05623a00 ohci1394 ohci1394.sys Thu Nov 02 09:43:56 2006 (4549BDDC)
    fffff980`05624000 fffff980`05640000 cdrom cdrom.sys Thu Nov 02 09:38:24 2006 (4549BC90)
    fffff980`05652000 fffff980`05657100 ksthunk ksthunk.sys Thu Nov 02 09:37:32 2006 (4549BC5C)
    fffff980`0568d000 fffff980`056a0000 HDAudBus HDAudBus.sys Sat Mar 24 18:58:47 2007 (460574E7)
    fffff980`056f4000 fffff980`05702000 kbdclass kbdclass.sys Thu Dec 06 02:45:48 2007 (4757625C)
    fffff980`05702000 fffff980`05710000 vga vga.sys Thu Nov 02 09:41:53 2006 (4549BD61)
    fffff980`05710000 fffff980`0571e000 crashdmp crashdmp.sys Thu Nov 02 09:38:17 2006 (4549BC89)
    fffff980`05756000 fffff980`05764000 tcpipreg tcpipreg.sys Thu Nov 02 09:47:05 2006 (4549BE99)
    fffff980`05788000 fffff980`0578fb80 HIDPARSE HIDPARSE.SYS Thu Nov 02 09:43:35 2006 (4549BDC7)
    fffff980`05a50000 fffff980`05a5c000 tunnel tunnel.sys Thu Jun 07 03:46:08 2007 (46677170)
    fffff980`05a5c000 fffff980`05a68000 ndistapi ndistapi.sys Wed Jul 04 02:59:27 2007 (468AFEFF)
    fffff980`05a68000 fffff980`05a74000 mouclass mouclass.sys Thu Dec 06 02:45:48 2007 (4757625C)
    fffff980`05a74000 fffff980`05a80000 nsiproxy nsiproxy.sys Thu Nov 02 09:46:47 2006 (4549BE87)
    fffff980`05a80000 fffff980`05a8c000 Dxapi Dxapi.sys Thu Nov 02 09:16:03 2006 (4549B753)
    fffff980`05b10000 fffff980`05b1f000 nvflsh64 nvflsh64.sys Thu Jan 08 00:10:51 2009 (4965448B)
    fffff980`05b3d000 fffff980`05b4c000 watchdog watchdog.sys Thu Nov 02 09:15:27 2006 (4549B72F)
    fffff980`05b5b000 fffff980`05b6a000 netbios netbios.sys Thu Nov 02 09:46:38 2006 (4549BE7E)
    fffff980`05b6a000 fffff980`05b79000 dump_nvstor64 dump_nvstor64.sys Sat Dec 23 16:07:42 2006 (458D544E)
    fffff980`05be2000 fffff980`05bf1000 nvoclk64 nvoclk64.sys Tue Jan 06 23:47:08 2009 (4963ED7C)
    fffff980`05c09000 fffff980`05c12000 tunmp tunmp.sys Thu Jun 07 03:45:55 2007 (46677163)
  3. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    couldn't figure out how to delete sorry
  4. Route44

    Route44 TechSpot Ambassador Posts: 12,117   +23

    Marcus, attach to your next post the five most recent dumps. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip. Please do us a favor and don’t Zip each one individually.

    Also, go ahead and delete your second and third post.
  5. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    Here is the minidmp

    Here you go, hope this helps only have 3 because its a fresh install (3days old)

    Marcus.

    p.s sorry i'm a n00b, how do i delete messages?
  6. Route44

    Route44 TechSpot Ambassador Posts: 12,117   +23

    First I goofed on deleting a post because I believe only moderators can do this; ask them and they can do it for you.


    The error that stands out the most is your 0x1E: KMODE_EXCEPTION_NOT_HANDLED

    The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors.

    0xA errors are either caused by hardware or drivers attempting an IRQ Level that they shouldn't.

    Your minidump spefcifically cited memory corruption as the cause which would explain why you are getting so many system crashes. You need to run Memtest on your RAM.

    Read this link and follow the instructions: http://www.techspot.com/vb/topic62524.html

    Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better.. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    If you have errors you have corrupted memory and it needs to be replaced.

    Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


    * Get back to us with the results.
  7. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    Memtest

    thanks, very much for your quick responce, i will start running memtest with a miniumum of 7 passes per stic of ram and let you know my results. I have 4 gig so it may take a while :)

    Cheers
    Marcus.
  8. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    Memtest results

    Hi, I tested one stick for 8 passes and the other for 10.

    Not one error. Passed all tests.

    Dang. I like my ram so happy about it being ok - but what does this mean for my blue screens, what else could they be???

    thanks for all your help.
  9. Route44

    Route44 TechSpot Ambassador Posts: 12,117   +23

    Give us your system specs including motherboard make and model, the type, make, and amount of RAM installed, OS, and security software.
  10. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    Spec

    q6600
    4 gb Patriot ddr2 800
    xfx 680 lt sli
    Windows Vista home premium x64
    xfx 9600gt xxx alpha dog edition
    1tb samsung spinpoint f1
    zalman gs1000 case with all fans fitted running off a zalman fan controler
    500w Colours IT power supply (awaiting Cooler master real power 700w)
    Spybot search and destory
    Avira antiVIR
  11. Route44

    Route44 TechSpot Ambassador Posts: 12,117   +23

    How has your BIOS set the RAM voltage as per Patriot's specifications?
     
  12. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    patrioit ram

    yes as per the ram's SPD.

    I belive its 1.8v.
    Everything in the BIOS is at default settings.

    Marcus :)
  13. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    Hi, i just re-read your last post,

    i will check what my ram reports is the right voltage from the label stuck on my ram, against what it says in the bios at defaults to see if there is a difference.

    Do you think its possible the bios is misreading and under or overvolting my ram which in turn could be causing instabiltys? Will check in a few hours and report what i find.

    Thanks Route44,
    Marcus.
  14. Route44

    Route44 TechSpot Ambassador Posts: 12,117   +23

    We've seen a number of memory issues that are read as memory corruption only to find out the motherboard/BIOS automatically set them at a different voltage than what the RAM is spected for. Once set at the correct voltage things corrected themselves. Thus my reason for asking.

    Also, we'll be very interested to see what happens when you get rid of that power suppy with the Coolermaster. If that Colours psu came with the case know that 99% those psu's are garbage.
  15. Route44

    Route44 TechSpot Ambassador Posts: 12,117   +23

    Double Post
  16. EV1L1NT3NT

    EV1L1NT3NT Newcomer, in training Topic Starter

    Ram misread

    Hi, well as suspected, the bios was reporting my ram voltage (auto) as 1.850v
    The sticker on the side of my patriot ram is 2.0v.
    Have set it manually to 2.0v in the BIOS now so we will see how it goes :)
    I will keep you updated,
    Thanks for all your help

    Marcus.
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.