New PC. Constant BSODS. Graphic Card issue??

Toggle sidebar Toggle sidebar
Y

YeIIow

Reputable
Aug 23, 2014
3
0
4,510
Hi,
I recently built this new computer almost a month ago. 2 Weeks in, It was working perfectly. Than all of sudden It just kept crashing every time I played a game for like 30 minutes. Than it really got worse. Everytime I attempted to play a game. I kept getting blue screens. I thought it was the RAM. Did the whole memtest thing. No errors. So I wanted to see if it was motherboard. So i changed out the motherboard and I still had the weird crashes and constant BSODS. I thought it was just bad ram, so I just replaced the new ram with my old ram I was using for my old PC. And it still kept crashing. Do I have a bad graphic card? All my drivers are updated. I have a 750w PSU. Didn't overclock anything.

Computer Specs
Windows 8.1
i5 4650K
ASUS Sabertooth Z97 Mark 2
Corsair Dominator Platinum 16 GB DDR3
Samsung EVO 250 GB
Corsair HX750
EVGA GTX 780 SC

These are my WhoCrashed analyze stats.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 8/22/2014 9:47:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082214-5109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0x4068, 0x2, 0x0, 0xFFFFF80340473F17)
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 Fri 8/22/2014 9:47:20 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 (0x4068, 0x2, 0x0, 0xFFFFF80340473F17)
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 Fri 8/22/2014 8:50:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082214-4859-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x11CF)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800929BD1CF, 0x1, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 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/22/2014 7:55:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082214-5250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
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 Fri 8/22/2014 6:29:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082214-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x4E (0x99, 0x1EC751, 0x3, 0x200000000151501)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 8/16/2014 10:36:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081614-4515-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF800D2A24BDB)
Bugcheck code: 0xD1 (0xFFFFE000D85AF46C, 0x2, 0x0, 0xFFFFF800D2A24BDB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 Sat 8/16/2014 9:04:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081614-5015-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x122A8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80037EF12A8, 0xFFFFD00143EAAA90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.



On Sat 8/16/2014 6:59:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081514-4593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x50 (0xFFFFF8016B48C87E, 0x8, 0xFFFFF8016B48C87E, 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 Sat 8/16/2014 6:08:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081514-4859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x18 (0xFFFFE00138AF3ED0, 0xFFFFE0013DFCC5D0, 0x1, 0x4000)
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.


 
Solution
Shaun o
Ok what you have there is an Irq problem.
Now an Irq is basically a range of numbers that each device connected to the motherboard uses to talk to the cpu.
Is own channel if you like.

Now each device has its own number, but in some cases the same Irq can be shared between two devices.
When a software driver is used in conjunction with the hardware it uses it to talk from the driver to the cpu to the hardware device. The cpu switches rapidly between the Irq numbers to send data to each of the devices back an forth.
But if two devices using the same Irq attempt to use the cpu at the same time.
You get the message you are seeing.

Ok there are a few things you can do to resolve the problem.
1.Make sure all the drivers for all the devices...
Sort by date Sort by votes
Shaun o

Shaun o

Illustrious
Oct 7, 2007
6,113
1
41,960
Ok what you have there is an Irq problem.
Now an Irq is basically a range of numbers that each device connected to the motherboard uses to talk to the cpu.
Is own channel if you like.

Now each device has its own number, but in some cases the same Irq can be shared between two devices.
When a software driver is used in conjunction with the hardware it uses it to talk from the driver to the cpu to the hardware device. The cpu switches rapidly between the Irq numbers to send data to each of the devices back an forth.
But if two devices using the same Irq attempt to use the cpu at the same time.
You get the message you are seeing.

Ok there are a few things you can do to resolve the problem.
1.Make sure all the drivers for all the devices were installed off the provided disks after windows was installed.
2. In the bios you have an option for Irqs to be set up by auto or manual. you try changing this setting in the bios.
3. In the bios turn off any interfaces you do not use, examples of it can be Serial or parallel or com ports.
Game ports, or midi ports.

If none of it works then it may suggest that when the cpu was fitted in it`s socket that one of the pins is not contacting from the cpu to the socket.
You should check the socket, or the cpu depending on the make that there are no bent contacts or pins.
The last one is, double check the memory in the system is running at the correct rated speed on the sticker of the memory. also check that what the rated voltage stated on the sticker is set right in the bios.
If not manually amend in the bios to the right voltage.
If the memory is rated at 1600Mhz make sure it reports it in the bios as that.
If not make sure the XMP mode for memory is enabled.

If you run a system and put it under load but don`t have xmp mode enabled in the bios it can often cause an error in the kernal.
due to wrong voltage. Under volted or incorrect setting will cause a crash under load of the system or memory modules.

A bit of tinkering and one or the other should solve the problem.


 
Upvote 0 Downvote
Solution
Y

YeIIow

Reputable
Aug 23, 2014
3
0
4,510


I tried looking for a IRQ in the BIOS. Couldn't find it.
Do you think my H100i is the problem?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom