Sign in with
Sign up | Sign in
Your question

RANDOM BSOD in this week

Last response: in Windows 7
Share
November 18, 2011 12:29:26 AM

Guys, I really need help, since week ago, my computer begins to get bluescreen of death, while I'm gaming or just on desktop, don't know what happen. It often gets blue screen, and the computer is running but, no display, the processor fan doesn't work, it just won't boot. but after I swap the RAM to other DIMM slot, it works again, but it will get bluescreen again, I've chkdsk no bad sector, memtest about 11 tests passed without issues, sfc/scan now result clean, don't know which trigger the issues

here's the mini dump

http://www.mediafire.com/?hbwpzek07klp751

More about : random bsod week

a b $ Windows 7
November 18, 2011 12:51:56 AM

check graphic card
November 18, 2011 1:22:40 AM

Furmark, no issues
Related resources
a b $ Windows 7
November 18, 2011 1:25:51 AM

could not read minidump on mediafire post the details of it directly here
November 18, 2011 2:13:06 AM

On Fri 11/18/2011 3:13:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-27346-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Fri 11/18/2011 2:40:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-24991-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x31D0C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004231D0C, 0xFFFFF880035D2868, 0xFFFFF880035D20C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 11/18/2011 2:02:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-25958-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xFFFFCE80307DBE28, 0x2, 0x0, 0xFFFFF88000F517D4)
Error: DRIVER_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 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.


On Fri 11/18/2011 2:00:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-26972-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880031931E8, 0xFFFFF88003192A40, 0xFFFFF800038AAC51)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 11/18/2011 1:58:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-24414-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBF2DA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600016F2DA, 0xFFFFF8800633F7C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 11/18/2011 1:27:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-45489-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1 (0x76EE138A, 0x0, 0xFFFF0000, 0xFFFFF88008412CA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
a b $ Windows 7
November 18, 2011 3:36:55 AM

i search all nt code on microsoft technet it's related to graphic card driver that give you memory error, so uninstall all and reinstall the latest ones
November 18, 2011 2:16:44 PM

found new thing again


On Sat 11/19/2011 6:54:57 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008AE4C08, 0xFFFFF88008AE4460, 0xFFFFF880012663C7)
Error: NTFS_FILE_SYSTEM
Bug check description: This indicates a problem occurred in the NTFS file system.
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: Unknown .
Google query: Unknown NTFS_FILE_SYSTEM




On Sat 11/19/2011 4:57:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-24429-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800318C268, 0xFFFFF8800318BAC0, 0xFFFFF8800122F9BA)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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.

after I reinstalled the windows it's still coming back
a b $ Windows 7
November 18, 2011 2:38:13 PM

Quote:
Error: NTFS_FILE_SYSTEM


Points to a HD problem.

Quote:
One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.



Quote:
Error: APC_INDEX_MISMATCH


Points to a file system problem, which again points to the HD.


As I doubt the windows default HDD driver is buggy, either your HDD has a REALLY bad driver, or its about to die on you. At the very least, I'd run a chkdsk, ASAP. I'd also start backing up any important data.
a b $ Windows 7
November 18, 2011 2:48:49 PM

Delete and recreate your swap file in case it has become corrupt. What is the brand and model (not just wattage) of your PSU? Dicey PSUs can cause all kinds of random-looking glitches and crashes.
November 18, 2011 3:26:58 PM

I've a tagan piperock 800w... I bought it 3 months ago...

my processor is Phenom II 965BE
GTX 560 Ti
Corsair Dominator PC8500 2 x 2Gb DDR2
Mobo, Asus M4A79 Deluxe
HDD, Sea gate 7200rpm 160GB
WD Black Cavier 250GB
WD Green Cavier 500GB

I've run CHKDSK many times ~:( 


I think it's the motherboard... or maybe the case?

as long as I know.... It seems that my hands are devil hands... my brother... playing dota, and got nil of BSOD...

but me... only browsing with a chrome / mozilla... It caused BSOD and also playing BF3 caused BSOD I think this computer hates me

after the BSOD, sometimes my computer can't boot, it's on, everything is running, but no display, no beep sound... and after that, I have to swap the RAM or Remove it and put it back ~~
November 19, 2011 5:22:24 AM

On Sat 11/19/2011 9:57:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-18876-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C903A9, 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 11/19/2011 9:57:02 PM 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: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C903A9, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 11/19/2011 7:36:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-28657-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002F6D63A)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 Intel CPU generated a trap and the kernel failed to catch this trap.
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 11/19/2011 4:57:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-24429-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800318C268, 0xFFFFF8800318BAC0, 0xFFFFF8800122F9BA)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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.


The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\111911-29094-01.dmp

new dump file
!