New
#1
PC Constant BSOD when generally using.
So ever since i have built the pc ive been having constant BSOD. At first it used to be when gaming, and playing graphic intensive games but not its BSOD when I watch youtube and generally just using the PC. Also I had this really weird patch of time where I could not shut the PC down. If I shut the PC down and then started it up 100% of the time right after starting it up after about 1 minute of usuage it would BSOD. The second forced shutdown didnt yield an instant BSOD. I've changed the slots of the RAM and added new ram, new PSU and a new GFX card which "seemed" to have stopped the BSOD... but now theyre back again and this time I had like 5 BSOD in a row within 5 minutes.... Anyways heres all the stuff:
WHO Crashed:
Minidumps: (ive attached them)Code:On Thu 06/06/2013 18:22:53 GMT your computer crashed crash dump file: C:\Windows\Minidump\060613-17222-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x18 (0xFFFFFA800CDEB8F0, 0xFFFFFA800D93E1F0, 0x1, 0x800000000000000) Error: REFERENCE_BY_POINTER 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 the reference count of an object is illegal for the current state of the object. 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 that cannot be identified at this time. On Sat 25/05/2013 02:47:30 GMT your computer crashed crash dump file: C:\Windows\Minidump\052513-7987-01.dmp This was probably caused by the following module: asio.sys (AsIO+0x100E) Bugcheck code: 0x3B (0xC0000096, 0xFFFFF88004BAF00E, 0xFFFFF88004193E70, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\SysWow64\drivers\AsIO.sys 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. 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: asio.sys . Google query: asio.sys SYSTEM_SERVICE_EXCEPTION On Sat 11/05/2013 13:19:10 GMT your computer crashed crash dump file: C:\Windows\Minidump\051113-7800-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x44 (0xFFFFFA8010449260, 0x1D7B, 0x0, 0x0) Error: MULTIPLE_IRP_COMPLETE_REQUESTS 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 driver has tried to requested an IRP be completed that is already complete. 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. On Fri 03/05/2013 11:34:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\050313-7503-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x4688) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009E8C478, 0xFFFFF88009E8BCD0, 0xFFFFF80002EEEADE) 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 that cannot be identified at this time. On Thu 02/05/2013 10:12:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\050213-6489-01.dmp This was probably caused by the following module: netio.sys (NETIO+0x36E0) Bugcheck code: 0xBE (0xFFFFF88001F0B6E0, 0x48B0121, 0xFFFFF8800852BB40, 0xA) Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY file path: C:\Windows\system32\drivers\netio.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Network I/O Subsystem Bug check description: This is issued if a driver attempts to write to a read-only memory segment. 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 that cannot be identified at this time.
060613-17222-01.dmp is the 6/6/2013 one
The z4roc.zip contains everything from the SF diagnostic tool.
Thank you for your time, constant bsod are really aggrovating. And the one which keeps popping up the most is the ntfs.sys and ntoskrnl.exe.
Additional Notes:
I have carried out memtest for a whole day when I just had the x2 ripjaws alone and it went to completion with all passes and no errors.
IMO I think the problem lies with the mobo, I dont think its a good one or maybe the psu being inadequate or the fact that I had so many BSOD it may have corrupted the windows 7 files so I may need to completely reinstall my OS... helps if I still had the disc.