Random BSOD'S


  1. Adammm
    Posts : 7
    Windows 7 Enterprise x64
       New #1

    Random BSOD'S


    Built this PC about a month ago everything was going fine until i turned it on 2 days ago and randomly started blue screening. I've got no internet access now and if i try and install drivers for my wireless USB it will Blue screen, it will also blue screen after a while if i listen to music or watch videos i have saved on the HDD. Almost everytime i get a different BSOD message as well.


    This is what i got from WhoCrashed



    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 1/6/2013 5:31:51 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010613-13696-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032C1383, 0xFFFFF8800652D8E0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/6/2013 5:31:51 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x9CCA8)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032C1383, 0xFFFFF8800652D8E0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sun 1/6/2013 5:00:02 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010613-12573-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xA (0xFFFFBA800675AD38, 0x2, 0x0, 0xFFFFF800032B6DEB)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/6/2013 4:31:02 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010613-24008-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x50 (0xFFFFB70001082B18, 0x0, 0xFFFFF800032F6472, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 1/6/2013 4:21:31 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010613-11606-01.dmp
    This was probably caused by the following module: ntfs.sys (0xFFFFF880012CBC8E)
    Bugcheck code: 0x50 (0xFFFFB8A008F4D2F0, 0x0, 0xFFFFF880012CBC8E, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sun 1/6/2013 1:27:36 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010613-12511-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8002177580, 0xFFFF, 0x0)
    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 that cannot be identified at this time.



    On Sun 1/6/2013 1:25:07 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010513-12667-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xE86, 0xEB900001D74)
    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 that cannot be identified at this time.



    On Sat 1/5/2013 11:47:23 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010513-15974-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xFF8C, 0x1E045009)
    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 that cannot be identified at this time.



    On Sat 1/5/2013 10:37:00 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010513-10108-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x50 (0xFFFFBA80074AB208, 0x0, 0xFFFFF80003582A5E, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 1/5/2013 8:13:25 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010513-13384-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x50 (0xFFFFB8A00AB1C8A0, 0x0, 0xFFFFF8000355998D, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 1/5/2013 6:36:15 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010513-17284-01.dmp
    This was probably caused by the following module: ntfs.sys (0xFFFFF8800126D36D)
    Bugcheck code: 0x50 (0xFFFFB8A0020FB810, 0x0, 0xFFFFF8800126D36D, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sat 1/5/2013 5:46:20 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010513-15865-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0xD8A, 0x98800001314)
    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 that cannot be identified at this time.



    On Sat 1/5/2013 2:03:05 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010413-20311-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x1A (0x41790, 0xFFFFFA8005AA75E0, 0xFFFF, 0x0)
    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 that cannot be identified at this time.



    On Sat 1/5/2013 1:15:37 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010413-23197-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x50 (0xFFFFE8A00E504010, 0x0, 0xFFFFF800037BE9BC, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 1/5/2013 12:32:35 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010413-20888-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x50 (0xFFFFB8A00D3378E8, 0x1, 0xFFFFF80003402617, 0x7)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    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 invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    21 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    symnets.sys
      My Computer
    Quote Quote

  3. Adammm
    Posts : 7
    Windows 7 Enterprise x64
    Thread Starter
       New #2

    Bump,please help
      My Computer
    Quote Quote

  4. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #3

    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Do this test overnight, before going to bed.
      My Computer
    Quote Quote

  6. Adammm
    Posts : 7
    Windows 7 Enterprise x64
    Thread Starter
       New #4

    I ran Memtest for each stick of RAM in all RAM slots, it turns out one of the sticks was getting errors so I removed it. But I am still experiencing some problems. I am getting random black screens sometimes when windows is booting but mostly when I've been logged in for a while. I booted in safe mode and never got the black screen so I belive it is my video card drivers correct? I've tried installing an reinstalling the drivers but still no luck(GeForce GTX 560SE) I've noticed in Device manager in the Other devices category I have an exclamation mark next to PCI device
      My Computer
    Quote Quote

  7. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #5

    Upload a screenshot of your hard disk using CrystalDiskInfo and Summary tab using Speccy:
      My Computer
    Quote Quote

 

  Related Discussions
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now. It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem. Four days ago it started blue...
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
I have finally had it up to here with the BSODs, so I really need help. I ran a windows memtest and it detected no errors. I just finished updating to SP1 with pretty much most updates too. The BSODs I get the most are: Driver IRQL not less or Equal System Service Exception and these two I...
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 17:54.
Find Us