help pleeeaassee blsod my poor pc needs your help

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by John Lauhoff, May 4, 2012.

  1. John Lauhoff

    John Lauhoff New Member

    Joined:
    Dec 2, 2011
    Messages:
    12
    Likes Received:
    0
    [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]
     

Share This Page

Loading...