Sign in with
Sign up | Sign in
Your question

Keep getting BSOD, i'm desperate, please Help

Last response: in Windows 7
Share
February 9, 2013 3:39:11 PM

Hello,
keep etting BSOD, tried everything, scanned RAM, turned fine, scanned HDD, turnd fine, went to bio asn disabled IRDQ port, didn't help...here's WhoCrashed report:
System Information (local)
--------------------------------------------------------------------------------

computer name: CIGANIN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X3 435 Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 2146754560 total
VM: 2147352576, free: 1993699328




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 9.2.2013. 17:05:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020913-13338-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7A (0xFFFFF6FC8060DCE0, 0xFFFFFFFFC0000185, 0x3B963880, 0xFFFFF900C1B9C008)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 9.2.2013. 17:05:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCDBC2)
Bugcheck code: 0x7A (0xFFFFF6FC8060DCE0, 0xFFFFFFFFC0000185, 0x3B963880, 0xFFFFF900C1B9C008)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 Fri 8.2.2013. 23:26:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020913-13275-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7A (0xFFFFF6FC5001C0C0, 0xFFFFFFFFC0000185, 0x1D392880, 0xFFFFF8A003818018)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 6.2.2013. 17:02:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020613-13244-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800375FB30, 0xFFFFFA800375FE10, 0xFFFFF80002D8B240)
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. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 5.2.2013. 17:50:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020513-13228-01.dmp
This was probably caused by the following module: ????????????.sys (Unloaded_????????????+0x7A)
Bugcheck code: 0x7A (0xFFFFF6FC50038F78, 0xFFFFFFFFC0000185, 0x1F964820, 0xFFFFF8A0071EF0CE)
Error: KERNEL_DATA_INPAGE_ERROR
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ????????????.sys .
Google query: ????????????.sys KERNEL_DATA_INPAGE_ERROR



On Sat 2.2.2013. 11:24:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020213-12043-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7A (0xFFFFF6FB80008000, 0xFFFFFFFFC000000E, 0xEBC3880, 0xFFFFF70001000000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 31.1.2013. 12:11:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013113-12916-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7A (0xFFFFF6FC5001C078, 0xFFFFFFFFC0000185, 0x65411880, 0xFFFFF8A00380F000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 22.1.2013. 23:35:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012313-12558-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x7A (0xFFFFF6FC50033C30, 0xFFFFFFFFC0000185, 0x77FAE820, 0xFFFFF8A006786104)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 5.1.2013. 12:54:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010513-12027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002ACA090)
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.




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

9 crash dumps have been found and analyzed. 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:

????????????.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

More about : bsod desperate

a b \ Driver
a b $ Windows 7
February 9, 2013 4:14:56 PM

start with the simple stuff first. make sure your mb bios has the newest codes. a lot of mb vendors add new code for ram and cpus. check the mb vendor ram list see if the ram you have is on there list or see on the ram vendor web page your ram on there tested ram guild. use cpu-z check that the mb set your ram speed and voltage right. sometime mb set the ram voltage to low on older 1.6v ram. make sure you update the mb chipset drivers. most times amd will have the newest driver. if it not the mb or dram check your power supply. a lot of no named units if the power is dirty or cant hold your system up you get unkown bsof with ram that checks out good.
!