I'm getting alot of BSOD errors.

Page 1 of 3 123 LastLast

  1. Posts : 12
    Windows 7
       #1

    I'm getting alot of BSOD errors.


    Hi,
    Dump files attached to thread, I wasn't able to upload health check wouldn't let me :s

    My specs:

    Is Windows 7 . . .
    - x86 (32-bit) or x64 ? x64
    - the original installed OS on the system? Yes
    - an OEM or full retail version? OEM

    - What is the age of system (hardware)? ~ 5 Months
    - What is the age of OS installation (have you re-installed the OS?) ~ 5 Months

    Thanks NexPB.
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2

    Hello nexpb,

    These crashes were caused by memory corruption/exception (probably a driver).
    Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


  3. Posts : 12
    Windows 7
    Thread Starter
       #3

    Thanks for the post. I already did the memtest and it did 100% without finding any errors now I'm doing the Driver verifier. Wich I wil post the results from later.

    edit: where can I find the memory dump?
    edit 2: I think I found it added to post
    Last edited by nexpb; 04 Feb 2012 at 09:12.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    nexpb said:
    Thanks for the post. I already did the memtest and it did 100% without finding any errors now I'm doing the Driver verifier. Wich I wil post the results from later.

    edit: where can I find the memory dump?
    edit 2: I think I found it added to post

    This one also appears to be caused by a memory exception (probably your directX) but since this one isnt driver verified we need to wait for the next one.
      My Computer


  5. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #5

    It is much easier to find patterns, etc, when there are more than one crash.

    We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.
      My Computer


  6. Posts : 12
    Windows 7
    Thread Starter
       #6

    zigzag3143 said:
    nexpb said:
    Thanks for the post. I already did the memtest and it did 100% without finding any errors now I'm doing the Driver verifier. Wich I wil post the results from later.

    edit: where can I find the memory dump?
    edit 2: I think I found it added to post

    This one also appears to be caused by a memory exception (probably your directX) but since this one isnt driver verified we need to wait for the next one.
    I didn't see DirectX in the list from verified.
      My Computer


  7. Posts : 12
    Windows 7
    Thread Starter
       #7

    Weird I didn't get for 2 days blue screen and today again.

    Info:


    On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    nexpb said:
    Weird I didn't get for 2 days blue screen and today again.

    Info:


    On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    Again we need the actual DMP file.

    Again memory management
      My Computer


  9. Posts : 12
    Windows 7
    Thread Starter
       #9

    zigzag3143 said:
    nexpb said:
    Weird I didn't get for 2 days blue screen and today again.

    Info:


    On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    Again we need the actual DMP file.

    Again memory management
    I couldn't zip it with winrar it said: Can't be accesed.
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    nexpb said:
    zigzag3143 said:
    nexpb said:
    Weird I didn't get for 2 days blue screen and today again.

    Info:


    On Wed 2/8/2012 6:17:42 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\020812-32261-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0x66, 0x68000000EC)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
    Again we need the actual DMP file.

    Again memory management
    I couldn't zip it with winrar it said: Can't be accesed.
    Did you follow the directions exactly? did you save it to somewhere like your desktop?
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:58.
Find Us