I am glad to see that you have found the source of the problem. One of the hardware guys will have to answer the question as to the cause of the buggy dual channel. I wonder if it could be a BIOS seting? However the good news is your RAM is good and you can run in single channel without crashing.
So, I spoke too soon. I've once again had a couple BSODs, looking (to me, at least) exactly like the ones from before. I updated everything I could, and I tried forcebly removing the old .sys files, having that hardware fail due to lack of drivers. Didn't make a difference, so I put them back.
I've attached fresh reports and captures. As far as I can tell, my memory is totally stable now, so I have no idea what the problem could be. My last-ditch effort would be to reinstall Windows entirely, but as this all seems to point to a hardware issue rather than software, I'm worried that it would just be a waste of my time. I couldn't do it for two weeks, either, as I'm really busy with work and moving. In the meantime, I guess I'm just putting up with a crashy computer.
If anyone can find anything new in these files, I'd bake you nonliteral cookies. Otherwise... I don't know. Do I bring it somewhere? Would it be worth my money to hand it over to a computer repair place for a day to at least try to get a diagnosis? And if that's a reasonable, if desperate, move -- does anyone know anywhere in Vancouver I can trust?
Please enable driver verifier: Using Driver Verifier to identify issues with Drivers
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Windows crash reports (27-07-10).zip\Windows7_BSOD_jcgriff2\072710-28282-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c65000 PsLoadedModuleList = 0xfffff800`02ea2e50 Debug session time: Tue Jul 27 23:00:37.443 2010 (GMT-4) System Uptime: 1 days 0:13:57.004 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ...................... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff900c8bcd860, 0, fffff960001b9d32, 2} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!xxxInternalGetMessage+16 ) Followup: MachineOwner ---------
I enabled the driver verifier. 80% of the time this resulted in a BSOD while booting, though I could still occasionally get into Windows normally. I did this for two days, resulting in half a dozen BSODs at boot but only one BSOD while Windows was running. Attached are the new dumps. Hopefully they'll have something to go on. Let me know if there's anything else I can do.
Verifier causing a BSOD so early is a sign of a bad boot driver.
I would suspect your older jraid.sys drivers:Code:System Uptime: 0 days 0:00:15.398 System Uptime: 0 days 1:01:00.543 System Uptime: 0 days 0:00:17.177 System Uptime: 0 days 0:00:14.820Check on your computer manufacturer's site for updates: GA-P55A-UD3P (rev. 2.0) - GIGABYTECode:jraid.sys Thu Aug 13 04:10:27 2009
You can also try here: ftp://driver.jmicron.com.tw/
...Summary of the Dumps:Code:Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sun Aug 8 13:21:05.212 2010 (UTC - 4:00) System Uptime: 0 days 0:00:15.398 BugCheck A, {1a2e00520050, 2, 0, fffff80002cab183} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sun Aug 8 05:07:13.672 2010 (UTC - 4:00) System Uptime: 0 days 1:01:00.543 BugCheck 24, {1904fb, fffff88008647b98, fffff88008647400, fffff88001314535} Probably caused by : Ntfs.sys ( Ntfs!NtfsExpandHashTable+75 ) PROCESS_NAME: rundll32.exe BUGCHECK_STR: 0x24 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Mon Aug 9 23:07:44.975 2010 (UTC - 4:00) System Uptime: 0 days 0:00:17.177 BugCheck A, {0, 2, 0, fffff80002ced183} Probably caused by : pci.sys ( pci!PciDispatchPnpPower+146 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Debug session time: Sun Aug 8 22:02:39.243 2010 (UTC - 4:00) System Uptime: 0 days 0:00:14.820 BugCheck A, {1a2e00520050, 2, 0, fffff80002ca2183} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Updated my RAID drivers, which updated jraid.sys. Got another BSOD today.
As always, reports and dumps are attached. Is it time to me to just give up and reinstall Windows?
It was caused by usbhub.sys, probably your USB hub?? I suggest updating your USB drivers via Device Manager.
The latest drivers may be installed, but perhaps they are corrupted. Uninstall them and reboot; the new ones should be automatically installed.
Regard,Code:BugCheck FE, {8, 6, 6, fffffa80087e5de0} Probably caused by : usbhub.sys ( usbhub!UsbhWaitEventWithTimeoutEx+3aa ) Followup: MachineOwner ---------
Tuan
I have two printers (Epson and Brother), a generic Logitech mouse, and a PS3 Eye webcam connected via USB. The PS3 Eye is the only thing that isn't officially supported, so I disconnected it. BSODs are still happening, though they seem to happen less now that I've updated my RAID drivers.
Worth noting: crashes are really, truly random. Playing games for hours and pushing the computer to its limits has never resulted in a crash, but then I see a BSOD across the room at 8am when the computer hasn't been touched since the night before.
One change: Prefmon is reporting some errors. Possibly related to recently-updated video drivers?
Three recent BSODs, everything is, once again, attached.
Disconnect all USB devices for the time being.
Install these Realtek drivers: Realtek
If that doesn't help, please enable driver verifier: Driver Verifier - Enable and Disable
...Summary of the Dumps:Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Wed Sep 1 04:47:00.147 2010 (UTC - 4:00) System Uptime: 1 days 6:22:06.560 BugCheck A, {1f, d, 0, fffff8000320139a} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) BUGCHECK_STR: 0xA PROCESS_NAME: System ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 30 22:23:44.178 2010 (UTC - 4:00) System Uptime: 1 days 2:05:13.364 BugCheck A, {daa94c9985, 2, 1, fffff80002c86cd8} Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 ) BUGCHECK_STR: 0xA PROCESS_NAME: chrome.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Fri Aug 27 15:07:28.193 2010 (UTC - 4:00) System Uptime: 2 days 8:51:16.374 BugCheck 4E, {99, 26452, 0, 14dd2} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) BUGCHECK_STR: 0x4E_99 PROCESS_NAME: Steam.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Quote