blue screen/black screen

Associate
Joined
24 Aug 2011
Posts
128
hey all. i've posted here before about a blue screen problem i was getting:
http://forums.overclockers.co.uk/showthread.php?t=18445350

I bought the system from overclockers.

the problem kinda fixed itself. a few updates came out for the games and it all went away.

Few weeks later and here i am again :/

I was on WoW and my monitor turned black. I could still hear the sound and speak on teamspeak but i could not see anything. I rebooted and this time i got error #132 while on WoW. So a 3rd time i login and i get a blue screen!

I used the program Whocrashed and this is what it reports:

On Mon 22/10/2012 19:09:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102212-3915-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x4, 0x2, 0x8, 0x4)
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 Mon 22/10/2012 19:09:32 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x15375)
Bugcheck code: 0xD1 (0x4, 0x2, 0x8, 0x4)
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 which cannot be identified at this time.


---

Going to point out that the 3times it crashed, i had my headset plugged in. I've removed the headset and WoW has not crashed yet.

Does anyone understand that info above? Would they care to shead some light on it for me :-)

Thanks in advance!
 
You know you could just have continued your previous thread right. That aside, what headset do you have? That info is very generic but it sounds like you have a bad driver installation for one of your components.
 
Is doing a bios update easy? im pretty much a *** when it comes to this kinda stuff. I've only installed a razer naga mouse driver. Everything else on here is how they sent it
 
What MOBO do you have? Updating the bios is straightforward either via USB or an alternative. If you are OCing I would stop. Have you put any new RAM into the MOBO?

SoC
 
Motherboard: Gigabyte Z77X-UD3H Intel Z77

Not added anything new, and the computer came with an overclock.
CPU: Intel Core i5 3570K 3.40GHz @ 4.50GHz Ivybridge CPU

All the temps seem fine, and i've been on WoW for 30mins now without a headset and no crashes :S
 
Yes, memory faults only come to light when other applications require resources. If you can reproduce the BSOD or crash then you seem to have a driver issue. Check you graphics card manufacturer website to see if they have a driver which post-dates your windows installed driver.

What I would do:
1). Remove overclockers (you can put it back after you sort things out)
2) bios update
3) graphics card driver update

Windows should push all the other drivers down for you. Check that it does.

Just install wow only and check if things are stable. If it is then slowly increase what applications you install. You will quickly figure out the issue.

SoC
 
Will have a look. Seems Dishonoured and Borderlands2 just crashes now at startup.

if i cant fix this, does anyone know if you can still return and get a refund before 30days is up?

.. :/
 
true, im just getting mega frustrated as im clueless with computers :|

Although! i did just install the new nvidia gfx drivers, did a fresh install and atleast dishonoured and borderlands work again

I'll play around with it more tomorrow after work

thanks for ya help !
 
Last edited:
No problem ... With new builds it can take some time for drivers to be perfected etc. all part of the process. But I would get rid of the overclock until things settle.

SoC
 
Just posting here to let you know how it went.

After everything returned to normal, i kinda left it alone. until tonight! plugged headset in, loaded up raidcall and started playing borderlands2 with some mates. After 30mins+ I got a hard crash, rebooted and most of my games wouldnt even load. Just crash right to desktop, then i started getting blue screens in gaming and just on desktop / using IE.

I went into the bios and restored the settings and everything seems fine again. managed to play borderlands for 3+ hours without any problems. I bought this system from overclockers, it came with an overclock that they set... :/

but! touch wood! everything stays fine and i really dont mind not having an overclock, i dont notice any difference anyways :o)
 
Back
Top Bottom