BSOD - Infrequent, browsing mostly. IRQL_NOT_LESS_OR_EQUAL

[Yeoman]

Bluescreen Blues
BSOD Error Code: IRQL_NOT_LESS_OR_EQUAL

Updated with further BSOD results & Up to date Perfmon Report.


Hi,
I've been having trouble with BSOD's ever since I built my computer in November last year. I think I've installed all my components & drivers correctly. This is the first time I've asked for help online, cus I'm kinda getting a bit tired of them; they spoil the joy a new pc ought to bring.


I don't know if this helps, but, a little bit of background information.

Since I built it in November, I found that I started receiving blue screens on a weekly basis, they would only occur on SUNDAY or MONDAY, which seemed odd to me, and only one or two on those days. I put off going all out to find the problem due to having a lot of uni coursework and I didn't want to lose too much time or become distracted etc. But each week I would try a little fix I had read online, and wait till next week to see if there was any impact. (I usually used my pc in the exact same way and for the same amounts of time whether in the week or weekend).

After the new year, I tried a repair install, but to no avail, as I then received a BSOD on a WEDNESDAY of all days, (It probably seems nonsense for them to be on a 'schedule', but it did seem like that at times). I then did a fresh install of windows, and reformatted my Hard Drive, installed all the drivers I knew of, since then I had a month or so before receiving another BSOD, but clearly a reinstall didn't cure the problem.


So now I'm asking for help, because I would like to get this fixed, and put the worry to bed. I hope the above information is useful, if not, I apologise. Below is some further 'technical' information.

My windows installation is about 2 months old roughly, I have Windows 7 Home Premium x64. I think my windows copy is OEM, I bought it separately.

My system is as follows (the components are about 4 months old):
Intel i5-2500K at 3.3ghz
Asus P8P67
Corsair Vengeance 2x4GB 1600MHZ C8
MSI HD6850
1TB Western Digital Caviar Blue
Samsung BH-B123L (blue ray drive)
Antec HCG 620watt
Zalman Z9 plus (case)

My BSOD's have occurred mainly whilst browsing the internet, and occasionally whilst on the desktop, or after clicking 'shut down', only once have I had a BSOD whilst playing a demanding game.
One thing I think might be related to the problem, is something to do with a driver for my USB3 ports (they don't work, or aren't able to power my USB2 memory stick). However, I have installed the USB3 drivers for my ASUS motherboard, and the program and my pc flagged no issues with the install of the driver, so I'm not sure if the 2 USB controllers in the device manager refer to my USB3 ports or not (I did try searching for a solution to the two flagged devices, but windows found nothing).

I think that's everything, I'm sorry it's a lot to read, but it is better to be thorough than brief, I hope. I've attached a .zip of the app results and the perfmon report.

One last thing: I am a university student, I commute to university usually everyday, which means I can be busy from 7am till 9pm most days, I hope you'll bear with me in that I might not be able to try things out straight sway, but I can still log on to acknowledge any help & ask questions.

Thanks in advance,
Daniel.

 

[zigzag3143]

This single crash is inconclusive I am afraid.

It is much easier to find patterns, etc, when there are more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

 

[Yeoman]

Oh right , I see. Sorry about that. I'll wait till I have a second crash then, I've done plenty of waiting I can stand to wait a bit longer

When that happens, should I post in this thread again with the updated report & app result, or would you rather I made a new one?

Edit: I'll prob wait till i have 3, if that will be more helpful. I guess I could start leaving my computer on desktop all day to see if I can 'encourage' some more BSOD's, or would that be a bad idea, because they might not be 'genuine'?

 

[zigzag3143]

Oh right , I see. Sorry about that. I'll wait till I have a second crash then, I've done plenty of waiting I can stand to wait a bit longer

When that happens, should I post in this thread again with the updated report & app result, or would you rather I made a new one?

Edit: I'll prob wait till i have 3, if that will be more helpful. I guess I could start leaving my computer on desktop all day to see if I can 'encourage' some more BSOD's, or would that be a bad idea, because they might not be 'genuine'?

Im sorry you have to wait but sometimes it crashes so fast there isnt time to write the problem to the DMP.

When you get the next one post it here. All we really need is the new DMP file. The other things you collected will remain the same.

If you want to speed the process, do what you do when it crashes (ie if it crashes in a game, play that game)

 

[Yeoman]

Okidoke, that makes sense.
I'll try letting my pc stay on more, since there is no obvious specific task that causes the BSOD's.

Thanks for your prompt replies. See you in a week or less hopefully.


Dan,

 

[zigzag3143]

Okidoke, that makes sense.
I'll try letting my pc stay on more, since there is no obvious specific task that causes the BSOD's.

Thanks for your prompt replies. See you in a week or less hopefully.


Dan,

Good job and good luck Dan. Keep us in the loop

 

[Yeoman]

Sorry for the long gap between posts, I've been snowed under with uni stuff, and was waiting for a 'clear patch'.

I've had some more BSOD's since the last time i posted. Three to be precise. Two more IRQL_NOT_LESS_OR_EQUAL, and one Page_Fault_in_nonpaged_Area (that's the first time I had one of those, I had it whilst I was installing a computer game, but it installed fine on a second attempt.) I don't know if that is related to the problem that's been causing all the NOT_LESS_OR_EQUAL bluescreens, or not, but I thought I'd mention it.

I've attached a zip file containing the updated perfmon report and the other info gathering programme. I'll update the first post too, so there's no confusion.

All the information I placed in the first post is still relevant, and correct. My situation is still the same however, I travel to uni each week day, and occasionally at the week ends, I hope you'll bear with me, I'll be able to respond to any replies at uni, and to ask questions, but it might take me slightly longer to be able to follow any commands/ fixes.

 

[writhziden]

Problem Devices:

Universal Serial Bus (USB) Controller	PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&108ABD8A&0&00E4	The drivers for this device are not installed.
Universal Serial Bus (USB) Controller	PCI\VEN_1B21&DEV_1042&SUBSYS_84881043&REV_00\4&DDEC341&0&00E1	The drivers for this device are not installed.

Make sure you get the drivers from ASUS - Motherboards- ASUS P8P67 through OS: Windows 7 64bit under USB.


Also, it does not appear all Windows updates have been installed. Make sure you install all Windows updates including optional updates but excluding driver updates through Windows updates. Driver updates should be obtained from the manufacturer of the driver or from your motherboard support site.

[list=1][*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Yeoman\Yeoman BSOD seven forums (second zip)\Windows_NT6_BSOD_jcgriff2\032912-14289-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a8650
Debug session time: Thu Mar 29 04:44:46.289 2012 (UTC - 6:00)
System Uptime: 0 days 3:32:54.476
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88003310000, 0, fffff800033307f4, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PfpFlushBuffers+294 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88003310000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033307f4, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003112100
 fffff88003310000 

FAULTING_IP: 
nt!PfpFlushBuffers+294
fffff800`033307f4 488b4d00        mov     rcx,qword ptr [rbp]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880087988a0 -- (.trap 0xfffff880087988a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000006007
rdx=fffff8a0033db178 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033307f4 rsp=fffff88008798a30 rbp=fffff88003310000
 r8=0000000000000001  r9=0000000000000717 r10=fffff8a0033d4000
r11=fffff8a0033da578 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!PfpFlushBuffers+0x294:
fffff800`033307f4 488b4d00        mov     rcx,qword ptr [rbp] ss:0018:fffff880`03310000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8d25c to fffff80002ee0d40

STACK_TEXT:  
fffff880`08798738 fffff800`02e8d25c : 00000000`00000050 fffff880`03310000 00000000`00000000 fffff880`087988a0 : nt!KeBugCheckEx
fffff880`08798740 fffff800`02edee6e : 00000000`00000000 fffff880`03310000 00000000`00002900 fffffa80`07aef000 : nt! ?? ::FNODOBFM::`string'+0x456cf
fffff880`087988a0 fffff800`033307f4 : 00000000`00000656 fffffa80`00000716 00000000`00000000 fffffa80`08a8ae48 : nt!KiPageFault+0x16e
fffff880`08798a30 fffff800`03351e80 : fffffa80`0adcab01 00000000`00000080 fffffa80`06cef040 fffff800`03067da8 : nt!PfpFlushBuffers+0x294
fffff880`08798ad0 fffff800`0317af7a : ffffffff`ff676980 fffffa80`0adcab60 fffff880`08798c70 fffffa80`0adcab60 : nt!PfTLoggingWorker+0xe0
fffff880`08798c00 fffff800`02ed19c6 : fffff800`03055e80 fffffa80`0adcab60 fffff800`03063cc0 fffff880`01266384 : nt!PspSystemThreadStartup+0x5a
fffff880`08798c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PfpFlushBuffers+294
fffff800`033307f4 488b4d00        mov     rcx,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PfpFlushBuffers+294

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x50_nt!PfpFlushBuffers+294

BUCKET_ID:  X64_0x50_nt!PfpFlushBuffers+294

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\Yeoman\Yeoman BSOD seven forums (second zip)\Windows_NT6_BSOD_jcgriff2\032412-29484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e18000 PsLoadedModuleList = 0xfffff800`0305c650
Debug session time: Sat Mar 24 06:28:41.842 2012 (UTC - 6:00)
System Uptime: 0 days 2:41:44.028
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffffff, 2, 1, fffff80002ec5932}

Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffffff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ec5932, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c6100
 ffffffffffffffff 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`02ec5932 48890a          mov     qword ptr [rdx],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  fffff88003d1a3a0 -- (.trap 0xfffff88003d1a3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003d1a5e0
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec5932 rsp=fffff88003d1a530 rbp=fffff88003d1a5c0
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8006bfe4b0
r11=fffff800030c9ac0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02ec5932 48890a          mov     qword ptr [rdx],rcx ds:0202:ffffffff`ffffffff=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e942e9 to fffff80002e94d40

STACK_TEXT:  
fffff880`03d1a258 fffff800`02e942e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03d1a260 fffff800`02e92f60 : 00000000`00000000 fffffa80`0a0d6b60 ffffffff`fffffd80 fffffa80`0182cbe0 : nt!KiBugCheckDispatch+0x69
fffff880`03d1a3a0 fffff800`02ec5932 : 00000000`00000000 00000000`00000001 fffffa80`06cefc68 00000000`00000001 : nt!KiPageFault+0x260
fffff880`03d1a530 fffff800`02ea46cd : fffffa80`0182cbe0 00000000`00000000 fffff880`03d1a5c0 fffffa80`06cefb60 : nt!KxWaitForLockOwnerShip+0x12
fffff880`03d1a560 fffff800`02ec6ee7 : 00000000`00000000 fffff680`00038eb8 00000000`00000000 00000000`00000001 : nt!MiInsertPageInFreeOrZeroedList+0x55d
fffff880`03d1a670 fffff800`02ec6137 : 00000000`00000000 fffff680`00038fb0 fffffa80`09ee9b30 00000000`00000000 : nt!MiDeletePteRun+0x4ed
fffff880`03d1a820 fffff800`02e814bf : fffffa80`00000000 00000000`07370fff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`03d1a9e0 fffff800`02e93fd3 : ffffffff`ffffffff 00000000`027fe720 00000000`027fe6e8 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`03d1aae0 00000000`773514fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`027fe658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773514fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`02ec5932 48890a          mov     qword ptr [rdx],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KxWaitForLockOwnerShip+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12

BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12

Followup: MachineOwner
---------


[/list]

1. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Antivirus Software... Drivers...
2. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...

When you have a chance, test for Windows corruption (not likely given this is a fairly fresh install, but sometimes installation DVDs can be faulty) and hardware problems:

• If you are overclocking any hardware, please stop.
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

I realize these are a lot of steps to do in your limited time, so do the best you can. Report back as you proceed, and whatever pace works for you, I'll be checking on the thread as you go, even if it takes a few weeks or more.

 

[Yeoman]

Thank you very much for your reply. I'm heading off to university shortly, I'll start on some of these things when I get back tonight, (I'll most likely do the drivers tonight, and windows update).

One thing I will briefly mention; I have afaik, downloaded and ran all the drivers for my motherboard previously. I believe I ran the USB driver twice, although it doesn't seem to have worked, but perhaps I did something incorrect. I'll double check later tonight ofc, and if I have no luck with the ones from the asus website, I could always see if there is something on the motherboard driver disk I've been missing on the website (although I understand using the manufacturers website is always recommended over the disk).

Thank you again, I'll repost later tonight, detailing what I have done, and anything else of interest.


Dan,

 

[writhziden]

Alright, sounds good. There are two sets of drivers in the USB section of your motherboard support driver downloads. One is for the controllers, and the other is for the ports themselves. Is it possible you only installed one of these sets of drivers the first time?

Let us know if you need any help as you go. Best of luck!

 

[Yeoman]

Okay, I've installed the remaining optional windows updates, one was some definitions for Microsoft security essentials; the other, I think was something to do with WLAN, didn't strike me as anything major. I've updated them, and done a search for more, but its telling me I'm up to date.
I've also downloaded those stress test/monitoring programs you posted, although I haven't used them yet, just making sure I have them handy for a later date.


I think you're right about the USB drivers on the ASUS website, I can remember, that I thought they where both the same driver, and I just downloaded & installed the one with the later date, which is the host controller. (It was dated 2011, the other, 2010).
However, I've had some trouble installing the other driver. The 'non controller' driver, refuses to try and install, it claims that "a later version of Renesas Electronics USB 3.0 Host Controller Driver is already installed on this machine".
I'm a little stumped here, I uninstalled the host controller driver via device manager> right click> uninstall drivers,(I'm not sure if that's the correct way to do it, but I'm no expert on drivers), I restarted, tried the 'non-controller' driver again, but it gave the same response as before.

So, I reinstalled the other USB driver, the '2011, host-controller ( V2.0.4.0)', but, I'm not sure if it installed correctly, it sort of gave an error, and wanted me to browse and show it where the driver was, I wasn't really sure what to do here, I directed it to the setup.exe file I used to run the driver installer, and that seemed to satisfy it. It supposedly installed the driver, and the program didn't indicate any errors.
Yet, in device manager, the two warning symbols were present again for the USB Host controllers (these did disappear however, when I uninstalled the host-controller as I mentioned further up). Then after a little while, I noticed a little 'bubble' pop up from the task bar, informing me the driver didn't install correctly. If I run the install again after this, (for the host controller driver), it doesn't ask me to identify a location again, and when its done, it informs me that the program has finished maintenance operations.


So now I'm not quite sure what to do next, I'm thinking I'm at fault, perhaps when I mentioned that the driver installer program wanted me to show it where the driver file was, I was making a mess of a really simply task, (but I'd assume it knew where its own driver was). I hope the above is clear enough; reading back over it it seems like a jumble.


Thank you again for your help & patience,
Dan

 

[Yeoman]

Quick update. I'm probably not the best person to be doing this with; I seem to have a bad habit of doing things in random orders and flitting here and there.

I just put my ASUS mobo disk in, and then installed the driver listed on that. I wasn't able to catch much tech information about the driver on the disc, but the driver is 'called' ASMedia, and that's the way it displays in the device manager window "ASmedia XHCI controller", and the two warning symbols have disappeared, the two previous "unknown devices" have moved down to the "Universal serial bus controllers" section, so that has to be a positive I hope?

I just plugged my memory stick into each of the USB 3.0 sockets, and it powered up and appeared on my computer. Hazarr!
So, that's one battle won, if perhaps not the war itself.

It seems odd though, why would the presumably up to date driver(s) on the asus website behave so awkwardly?
If it weren't for all the bloody people saying how recommended it was to get the most up to date drivers from websites, I would've used the damn disk in the first instance.


Thanks again,
Dan.

 

[writhziden]

Not sure what the problem is with the drivers on the site. May be worth contacting ASUS about. That is not the norm. We almost always recommend getting drivers straight from the website since the CD/DVD has out of date drivers by the time the user gets the motherboard.

How is the system responding since you resolved the USB problem?

If you right click on the Controller devices and click Properties, what error message is given in the General tab?

 

[Yeoman]

Well, I've not really noticed any difference, I've not had the computer on overnight cus I was quite tired yesterday after being in uni most of the day, and I thought I'd give it a rest after that bit of positive news. But, its too soon to tell f it had cured any BSOD's, they typically tend to take a week to occur, and that seems independent of how much the computer is on (they're infrequent and random). But I'll leave my PC during the day, to see if I can increase the chance of getting a BSOD.

I don't use usb3 either, or have an usb3 cables/memory sticks, but, my system is working as fine as it always does that I can tell.

I shall contact Asus at some point, I'd be interested to know what they think caused the issue with their drivers; I don't know if they simply got the wrong driver uploaded? Seems like an impossible mistake to make?


As for the error messages, I'm not quite sure what you mean (sorry). I checked in the device manager, and right clicked> properties for the two Asmedia Host controllers, and there was no error messages there, and I clicked on the top of the 'universal serial bus controllers' tree, and clicked on properties, and there's nothing there either. Did you mean what error message were on the warning symbols I mentioned earlier were showing, they've disappeared now, but if I uninstalled the Asmedia controllers, they'd come back I'd expect.


Driver Provider: ASMedia Technology Inc
Driver Date: 08/12/2010
Driver Version : 1.4.5.0

Those are the details of the disc drivers btw, just a little more information, may or may not be helpful.


I'm heading off to uni soon, but I can check this page during the day, sorry for the vagueness of the reply,
Dan

 

[writhziden]

No problem.

You had said that the exclamation moved to the USB Controllers. The General tab should then say why the exclamation is there. If the exclamation is gone, it will just say that the device is working properly. Since it is gone, my question is now moot and we will have to see if the problems are now gone. Best wishes that fixed everything.

 

[Yeoman]

Ah sorry about that. I was trying to be clear, but I guess I failed miserably.

What I meant was, that the two unknown devices with the 'warning symbols' had disappeared, and two new host controller devices had appeared in the usb section of the device manager. Everything seems tickety-boo in the device manager now.

Do you really think that might have solved it? Also, would you like me to still do the system file checker & the stress tests, or do you think they're unnecessary now?

Thanks again for your help,
Dan.

 

[writhziden]

I would recommend just doing your normal routine for a while. See how the system is responding. You can move on to the other steps if necessary, but I am hoping the problem is already solved.

Having missing drivers for important hardware can cause crashes, so the devices working properly may very well have been the key to getting the system to run stable.

 

[Yeoman]

Okay, I guess if i start giving my pc a workout, I might end up finding another 'problem' and think it was to due with the BSOD's even if it isn't.

I'l just carry on with normal usage for now. If I have any problems I'll post again.

Thank you, I shall keep my fingers crossed.

 

[writhziden]

You're welcome. When you are sure the problem is solved, you may mark the thread solved.

 

[Yeoman]

Okay, just a quick update. I've been using my pc pretty extensively over the past few days; I would've certainly expected one, maybe two BSOD's, but I haven't had any, so its looking quite promising.

Due to their infrequent nature, I'd be reluctant to consider it solved until another weekend (or two) has gone past. I probably won't post again until im sure the issue has been solved (and then i won't post, ill just mark the thread, no need for this thread to keep coming to the top),

I'd like to thank you one last time for your help, fixing these frustrating BSOD's is one big weight of a university student's shoulders.

All the best,
Dan.