BSOD during any system intensive programs.


  1. Bojazz
    Posts : 24
    Windows 7 Ultimate
       New #1

    BSOD during any system intensive programs.


    My computer will give me various BSODs whenever I run anything intensive. Sometimes programs will begin crashing left and right just before the BSOD. Running a screen recording program (XSplit) for anywhere around 5-20 minutes will result in a BSOD, especially while playing a game at the same time. For a while I could play smaller games like League of Legends and Minecraft just fine, but recently it started BSODing during those as well. I am now running on a fresh install of windows with only a few programs installed to recreate the BSODs.

    Fixes I have attempted:
    - uninstalled and reinstalled three different versions of Nvidia WHQL Drivers
    - uninstalled and reinstalled Realtek HD audio driver (BSOD with and without it)
    - uninstalled Lachesis Mouse Driver (Driver verifier claimed it was causing BSOD)
    - uninstalled Avast Anti-virus
    - ran Ccleaner to clean up registry

    - ran Chkdsk /f
    - ran SFC /scannow
    - ran Driver Verifier
    - attempted windows repair from boot CD (said there was nothing to repair)
    - ran the windows memory test ( 4 advanced passes overnight)
    - updated motherboard BIOS to most recent version (1.14)
    - changed BIOS timings and settings listed by manufacturer for RAM
    - changed BIOS timings and settings to DEFAULT
    - reformatted hard drive, fresh install of Windows 7
    - installed newest versions of motherboard drivers from manufacturer website

    - replaced EVGA 560Ti video card with with a Galaxy 8800GT from a stable computer, still got BSODs
    - replaced both memory DIMMS with others from a stable computer, still got BSODs

    It may also be worth mentioning that CPU-Z reports my video card's link width running at 8x rather than 16x. Adjusting the voltage to NB_PCI-E in the BIOS had no effect on this and I haven't been able to figure out how to get it up to 16x.


    System:
    MSI 890FXA-GD70 motherboard
    AMD Phenom II 1100T Black Edition 6-core CPU
    EVGA Nvidia 560Ti (free performance boost 1GB edition)
    Patriot PGV38G1333ELK RAM (2x4gb, 1333mhz, 9-9-9-24)
    Ultra X4 850 watt power supply
    Seagate 2TB 5900 RPM SATA 6gb/s hard drive
    Last edited by Bojazz; 18 Aug 2012 at 13:38.
      My Computer
    Quote Quote

  3. Bojazz
    Posts : 24
    Windows 7 Ultimate
    Thread Starter
       New #2

    Whocrashed reports

    On Sat 8/18/2012 3:26:01 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081712-27939-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000308D185, 0xFFFFF8800AF50C70, 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 which cannot be identified at this time.


    On Sat 8/18/2012 3:26:01 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000308D185, 0xFFFFF8800AF50C70, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    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 which cannot be identified at this time.


    On Fri 8/17/2012 9:20:55 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081712-30108-01.dmp
    This was probably caused by the following module: cdd.dll (cdd+0x12446)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960007A2446, 0xFFFFF880091A1500, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\cdd.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Canonical Display 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 which cannot be identified at this time.


    On Fri 8/17/2012 1:50:21 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081612-42915-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
    Bugcheck code: 0x1A (0x41287, 0x1, 0x0, 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 which cannot be identified at this time.


    On Thu 8/16/2012 6:30:39 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081612-33197-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA8009D5B970, 0xFFFFFA8009D5BC50, 0xFFFFF80003184720)
    Error: CRITICAL_OBJECT_TERMINATION
    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 process or thread crucial to system operation has unexpectedly exited or been terminated.
    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 which cannot be identified at this time.


    On Thu 8/16/2012 4:53:49 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081612-30201-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x96108)
    Bugcheck code: 0x50 (0xFFFFF9604C3CF2A0, 0x1, 0xFFFFF960001B2C0B, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 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 which cannot be identified at this time.
      My Computer
    Quote Quote

  4. Bojazz
    Posts : 24
    Windows 7 Ultimate
    Thread Starter
       New #3

    more crashes from today. dmps attatched. Here's the whocrashed reports. First one was while Xsplit was running, second was while minecraft server was running and I was watching a movie with VLC. Also, possibly worth noting that the dmp files are all incorrectly timed. They are 4 hours in the future, but their "date modified" stamps are correct. Not sure what that means.

    On Sat 8/18/2012 9:14:51 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081812-31793-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030C24C2, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    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 kernel-mode program generated an exception which the error handler did not catch.
    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 which cannot be identified at this time.


    On Sat 8/18/2012 9:14:51 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: win32k.sys (win32k!memset+0x16D8)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030C24C2, 0x0, 0xFFFFFFFFFFFFFFFF)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    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 which cannot be identified at this time.


    On Sat 8/18/2012 8:16:32 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081812-31590-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70040)
    Bugcheck code: 0xA (0xFFFFFA7FFFFFFFD0, 0x2, 0x1, 0xFFFFF800030EEA33)
    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 which cannot be identified at this time.
      My Computer
    Quote Quote

  6. Bojazz
    Posts : 24
    Windows 7 Ultimate
    Thread Starter
       New #4

    BSODing continues. Most recently while watching a movie on VLC and while playing Prototype 2. Recorded highest temps using Speed Fan. CPU/NB peaked at 67C about 5 minutes before BSOD (down to 51 at the time of BSOD). GPU peaked at 65C. These seem like acceptable temps, correct? Still at a complete loss for a solution.
      My Computer
    Quote Quote

 

  Related Discussions
Hello there , this is a my last resort at figuring out what is actually wrong with my PC. I had numerous problems and I think I recently had solved the problem , but it just happened again when I existed CS:GO, out of nowhere and that is why I am here Although I suspect my graphics card for this...
Hello, I have been experience multiple BSODs, especially when using more memory-intensive programs, and have yet to determine the cause. I have run Windows Memory Diagnostic Tool after the last one, and it reported no errors. I have downloaded the Windbg Toolkit, and have followed the...
I have been getting random bsod error ranging from System Service exception to IRQ Less than Equal. Attached are my bsod dumps. I've also tested my memory for about 24 hours, and no errors to report. Any help is greatly appreciated.
This has begun happening roughly 1-2 weeks ago, prior to this the system ran flawlessly (never had a BSOD) The strangest thing is that the BSOD started happening right after a windows update, and an install of MSE (never had it before this) I have tried many different tests and fixes to try...
Hello all, I went through my first attempt at building my own computer about 2 months ago and the process went fine. But about a week after I began using it, I started getting BSOD that seemed happen whenever I would run a CPU intensive program (Handbrake, VMWare Player, etc). It won't always ...
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 09:35.
Find Us