Windows 7 Help Bsod Help

[John Lauhoff]

Ok its crashing mostly during gaming but sometimes just on its own the error is service exemption new pc just built

 

[John Lauhoff]

here is dmp files

 

[John Lauhoff]

A problem has been detected and Windows has been shut down to prevent damage
to your computer.


The problem seems to be caused by the following file: ntoskrnl.exe


KMODE_EXCEPTION_NOT_HANDLED


If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:


Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.


If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.


Technical Information:


*** STOP: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000,
0x0000000000000000)


*** ntoskrnl.exe - Address 0xfffff8000369ac10 base at 0xfffff8000361e000 DateStamp
0x4e02aaa3

 

[Trouble]

Hello John and welcome to the forums. Your two latest dump files are reporting problems with

BugCheck 1E, {0, 0, 0, 0} Probably caused by : hardware ( usbehci!EHCI_InternalPollHsIsoEndpoint+4ee )

not likely that actual cause of the problem but may be related to

BugCheck A, {fffff80008aa1bc0, 2, 0, fffff800036e2e3b} Probably caused by : rdyboost.sys ( rdyboost!ST_STORE::StReleaseRegion+4e )

So if you have a USB device that has an implentation of Ready Boost you may want to start by disconnecting that to see if it helps with the Blue Screen Issues. Additionally you have or have had (and some remnants remain) AVG installed AVGIDSEH.Sys and avgtdia.sys Since AVG is not an all uncommon is these types of Blue Screen issues you should probably consider uninstalling it completely, at least for now. Use the programs own uninstaller if available in the programs directory or else use the programs and features applet in the control panel. Follow that up with the vendor specific proprietary removal tool from here Link Removed get the right one for your particular architecture. Consider replacing it with Link Removed due to 404 Error.
A few older drivers (pre-Windows 7 RTM) that could use your attention.
mcdbus.sys 2/24/2009 Driver for MagicISO SCSI Host Controller
xusb21.sys 4/8/2009 Windows Common Controller (maybe xbox)
ALSysIO64.sys 4/19/2009 Possibly an old version of Core Temp
lirsgt.sys 5/17/2009 Tages SA Software
atksgt.sys 5/17/2009 Tages SA Software
GEARAspiWDM.sys 5/18/2009 Driver updates - GEAR Software

Give Google a try and see if there is anything more recent for these products in the way of associated drivers. Or else consider uninstalling and or renaming.

 

[John Lauhoff]

[FONT=Segoe UI, Arial]On Sat 5/5/2012 1:34:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-31715-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x44A7E)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002E8EA7E, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a system thread 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.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 5/5/2012 1:34:24 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002E8EA7E, 0xFFFFF880009A99D8, 0xFFFFF880009A9230)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 5/4/2012 10:48:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-48656-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031851CA, 0xFFFFF8800A7D1F60, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 5/4/2012 5:04:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-33072-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF80002EE6B46)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 5/4/2012 3:07:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050412-27300-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFE9A, 0x8, 0xFFFFFFFFFFFFFE9A, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 5/3/2012 10:21:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-24320-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030042FE, 0xFFFFF8800A1BBAA0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 5/3/2012 6:43:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050312-23852-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xC7 (0x4, 0xFFFFF80000000000, 0x1, 0xFFFFFFFF)
Error: [FONT=Segoe UI, Arial]TIMER_OR_DPC_INVALID[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 5/2/2012 10:45:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050212-34725-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880049EEAC7)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 5/1/2012 9:42:56 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050112-34320-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xFC (0xFFFFF88003E93AB8, 0x80000000B24E1963, 0xFFFFF88003E938B0, 0x2)
Error: [FONT=Segoe UI, Arial]ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 5/1/2012 5:05:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050112-34913-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x70590)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 5/1/2012 1:16:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043012-28329-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002EC33BC)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Tue 5/1/2012 12:12:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043012-42759-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0xA (0x1E, 0x2, 0x1, 0xFFFFF80002CA50E0)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 4/23/2012 10:55:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-18408-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x1, 0xFFFFF80002CCF682, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 4/22/2012 12:54:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-16801-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0xA (0x60910A342, 0x2, 0x1, 0xFFFFF80002C6E2BE)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 4/22/2012 12:07:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-17690-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x705C0)
Bugcheck code: 0xA (0x48D8, 0x2, 0x0, 0xFFFFF80002D2F00E)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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.
[/FONT]