BSOD d1

Diagro · 5 May 2013 at 18:41

hey

getting a lot of BSOD today, all with code ending d1.

My Overclock seems to be stable as its been running prime 95 for an hour with no errors.
4.5ghz @ 1.232V

I thought it might be my GPU overclock so i removed it, yet the BSOD still happens after 10mins+ ingame

Last thing i think it could be is my memory, I'm currently backing up my only spare USB stick to use memtest on it so will update when that's done.

I am running a fresh install of windows 7 ultimate 64bit

Diagro · 5 May 2013 at 23:39

left memtest running, did an entire 5 hour run through, No errors at all.

So.. will leave Prime95 and Kombuster on over night... will see what happens.

Diagro · 6 May 2013 at 12:14

Update

Left Kombuster running and prime 95 running over night... 12 hours later its still running albeit warmer than i like but hey its stable.

Does anyone know what on earth is causing my system to crash in games?

Smit · 6 May 2013 at 12:47

Have you tried running something like WhoCrashed to analyze your crash dumps? It should give some more information about the crash and can tell you which driver (assuming it's a driver issue) which is causing it.

troops · 6 May 2013 at 12:57

0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

Also check event viewer for any WHEA-Logger Errors which will mean more vcore even tho your p95 stable.

Diagro · 6 May 2013 at 16:29

Thanks you two. I will get that program and have a look and post my findings.

Will also increase the volts on mem to 1.52 from 1.5 and add .010 to the cpu. Will see if that sorts it

Diagro · 6 May 2013 at 18:21

troops said:
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

Also check event viewer for any WHEA-Logger Errors which will mean more vcore even tho your p95 stable.

Checked the Event Viewer, and a lot of WHEA-Logger Errors :/

Diagro · 6 May 2013 at 18:54

This is what WhoCrashed Says:

On Sun 05/05/2013 17:26:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050513-27939-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF880051AC5CD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880051AC5CD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port 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.

Seems its a USB issue? o.O