BSOD Help

[jako800]

Been having this problem with my PC for a while now and have tried many fixes.
Any help would be appreciated. Thank you in advance.


System Information (local)
--------------------------------------------------------------------------------

computer name: OBSIDIAN
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8457207808 total
VM: 2147352576, free: 1914720256




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 6/5/2013 4:18:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060513-35109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xA (0x7A800C6392B0, 0x2, 0x0, 0xFFFFF800718A65B5)
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.



On Wed 6/5/2013 4:18:30 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: 0xA (0x7A800C6392B0, 0x2, 0x0, 0xFFFFF800718A65B5)
Error: IRQL_NOT_LESS_OR_EQUAL
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.



On Wed 6/5/2013 4:24:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060413-35125-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40C90)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8801AA8B4D8, 0xFFFFF8801AA8AD10, 0xFFFFF802FF052168)
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 Tue 6/4/2013 9:17:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060413-36312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801BB50BCA4, 0xFFFFF8801AF3A4D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.



On Sun 6/2/2013 3:48:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060213-35671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x270E01)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800E8ADFE01, 0xFFFFF88003363628, 0xFFFFF88003362E60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 that cannot be identified at this time.



On Fri 5/31/2013 6:15:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053113-29031-01.dmp
This was probably caused by the following module: asupio.sys (AsUpIO+0x18C8)
Bugcheck code: 0xC4 (0xF6, 0x17C, 0xFFFFFA8008F52940, 0xFFFFF88003BD98C8)
Error: DRIVER_VERIFIER_DETECTED_VIOLATION
file path: C:\Windows\SysWow64\drivers\AsUpIO.sys
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. 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: asupio.sys .
Google query: asupio.sys DRIVER_VERIFIER_DETECTED_VIOLATION



On Thu 5/30/2013 5:34:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053013-25281-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001CFB5F8)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001CFB5F8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Wed 5/29/2013 8:57:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-40578-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001D1D5F8)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001D1D5F8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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 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 Wed 5/22/2013 2:58:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052213-32281-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40C90)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8801E8E2198, 0xFFFFF8801E8E19D0, 0xFFFFF8009BE57DB5)
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 Mon 5/20/2013 3:49:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051913-27062-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x40C90)
Bugcheck code: 0x24 (0xB50019060B, 0xFFFFF8800487A428, 0xFFFFF88004879C60, 0xFFFFF8800136C9F7)
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 Mon 5/20/2013 3:08:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051913-34562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF6FE50029598, 0x0, 0xFFFFF802317B61E8, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 that cannot be identified at this time.



On Tue 4/30/2013 4:27:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043013-29109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A240)
Bugcheck code: 0xA (0xA00FFFFD8, 0x2, 0x0, 0xFFFFF8039B17580F)
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.

[Geek-9pm]

This PC is not under warranty - Right?
You have a four core CPU, so I was thinking it might be new.
Important Question. Who installed the drivers? Was it you? Did you use the chip-set drivers first? The ones that are specifically for you rmotherboard.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.

Not a hardware issue, nut hardware related.
Which means that Windows can not fix this problem. You need to disable one or some hardware things by disabling its driver.

Start by disabling the sound driver. And then try to disable all  USB devices except your keyboard. (Just unplug  the devices and power up) Next, disable the graphics driver and fall back to the generic VGA driver for Windows 8.

Did the machine work fine when you first got it?
Have you adding any new hardware?

As the message says, it is not bad hardware, but the software driver for a hardware device is breaking software rules. The driver does not get the right memory address. Most likely it was not written or tested for Windows 8. So you have to either use the generic drivers or disable the hardware.

If you can ID the hardware device associated with the bum driver, contact the maker of the device to see if that have fixed the driver issue.

[patio]

What brand and wattage PSU is in this PC and what vid card are you running ? ?

[Allan]

Let's start with the basics. Have you run full scans with both your installed AV and with MalwareBytes? If not, please do so now.

[jako800]

Obsidian
Custom built computer

● OS: Windows 8 64bit
● Case: Corsair Carbide Series Black 400R Mid Tower Computer Case (CC-9011011-WW)
● Motherboard: ASUS P8Z77-V LGA 1155 Intel Z77 HDMI SATA 6Gb/s USB 3.0
● CPU: Intel Core i5-3570K Ivy Bridge 3.4GHz (3.8GHz Turbo) LGA 1155 77W Quad-Core Desktop Processor Intel HD Graphics 4000 BX80637I53570K
● Heat Sink: Cooler Master-Hyper 212 EVO
● Hard Drive: Seagate ST2000DM001 Barracuda 7200RPM 2 TB SATA 6 GB/s NCQ 64 MB Cache
● GPU: GIGABYTE GV-N66TOC-2GD GeForce GTX 660 Ti 2GB 192-bit GDDR5 PCI Express 3.0 x16 HDCP Ready SLI Support Video Card
● RAM: Corsair Vengeance 4x2GB = 8GB CMZ4GX3M2A1600C9
● Power Supply: Corsair CX Series 600 Watt ATX/EPS Modular 80 PLUS Bronze ATX12V/EPS12V 552 Power Supply CX600M
● Monitor: ASUS VS228H-P 21.5"

[jako800]

I have run full scans with AVG, Norton and MalwareBytes.

[jako800]

Using drivers from the manufacturer, all say they are compatible with Windows 8 64 Bit.

[Allan]

Multiple and varied bsod's can be caused by malware (you say you've run multiple scans so for now let's rule that out), faulty psu, faulty motherboard, hd, ram or other hardware. Let's check the hd and ram:

To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

To run checkdisk, right-click on a command prompt icon and open as administrator. In the command prompt window type: chkdsk /r  (then press ENTER). You'll be told the disk is in use and asked if you want to run checkdisk on the next boot. Say yes, exit the command prompt window, and reboot.

[jako800]

I will run both of those and get back to you.

[Calum]

IRQL_NOTE_LESS_OR_EQUAL is often a memory, video card or video driver related issue.
Running Memtest as suggested by Allan is a good first step, I would also suggest performing a clean install of your graphics drivers.
Your graphics card is an Nvidia - click here to download the driver package, and save it - don't run it yet.  Go to Computer, Uninstall or change a program, then remove anything that says Nvidia by it, and reboot the PC.  Now open the driver package you downloaded, select Custom install rather than Express or default, and check the box that says clean install.  Let the drivers finish installing, then reboot the PC again.

[jako800]

Both tests finished without any problems. And I have performed a clean install of my graphics drivers, many times recently, but that was not the problem. I did a little bit of looking myself and it seams most if not all of my problems are coming from the driver asupio.sys. I have uninstalled all Asus programs on my computer. I will let you know if anything else comes up. Thank you.

[patio]

You're replying to a 6 month old thread...