Woke up to BSOD

timeless · 13 Sep 2014

bugcheck 50 as said earlier still relates to ram correct? lve removed the older ram from my system and left the brand new stuff in going to swap it round if there is another bsod, seems to be the easiest way to rule out ram without running memtest (havent got a spare system to test it in), tho ld like to run out all possibilities before uninstalling BD, its just that if l uninstall now lve wasted money on a new subscription so ld hope to rule out ram first by getting rid of my older sticks and just having the new ones in there.

as for drivers.

USB 3.0 driver should be up to date, in fact its the one from gigabytes support section:

GIGABYTE - Motherboard - Socket 1150 - GA-Z87-D3HP (rev. 1.x)
(did a little searching and l cant find one higher than 3.0.0.16)

as for the wireless adapter its a W322U v2.0 its an oldish adapter went with the newest driver that was on their site as the one l had was somewhat messed up.. that said l had problems with stability up till l updated the usb driver.

===
Edit, l seem to of found an updated driver for my wireless adapter... or should l say l went to the Ralink website and downloaded RT2870 compatible ones.

however as l said about the USB 3.0 driver, l cant find one higher.. l did download one from the intel website that looked newer but windows determined the current driver was newest.

Golden · 13 Sep 2014

The only way to test RAM is to run MemTest86+ for 8 passes.

timeless · 14 Sep 2014

agreed, but if it was caused by me mixing my older ram with the newer stuff. (l had 2 matched pairs, lve removed one now) and it doesnt happen again (fingers crossed) then its likely the older ram was the culprit however if it happens again l'll swap the ram around to the older sticks.

lm just thinking if it happens with both sets it will rule out ram as l wouldnt have thought both sets were bad, granted it wouldnt be a definitive as running memtest but it would be too much coincidence for both sets to be bad. if both sets bsod l'll have to contemplate running memtest.

timeless · 14 Sep 2014

was going through my event viewer and came across two critical events which were around the time of the 2 bsods l received.

first one in event viewer has a bugcheck code of 80 the second crash has a bugcheck code of 30, as you can tell by the links lve looked up the information on the codes l found in my event viewer the code 80 l would assume would be down to my ram given it was a hardware code but lm not sure what to make of the bugcheck code 30 as the page doesnt give much information.

on another note, l also fan the sfc check, it did note there was some issues with files which have been repaired, so far (touch wood) lve not had another bsod that said lve had this system up and running a week before one happened. but lm hoping removing the older ram and leaving the new 8gb in there stops my issue (granted it was same brand and rated the same voltages but the memory was different in the respects that the older stuff was very low profile compared to the new modules).

Golden · 15 Sep 2014

I suggest:

1. Run MemTest86+ for a minimum of 8 passes
2. Uninstall BitDefender and test

There are no other suggestions anyone else can offer you.

timeless · 15 Sep 2014

no point running memtest, have a completely new set of ram in there, lve completely swapped for a completely different matched 4gb pair. will scan the other ram within the next few weeks once lve access to a board that can take it.

ideally l dont want to waste money, but if and when it happens again that will be what l do next.

however lm still curious what bugcheck 30 means (at least in more simple terms).

timeless · 19 Sep 2014

lve been looking through my logs and was curious of a few logs:

1 user registry handles leaked from \Registry\User\S-1-5-21-3294739943-1419706600-419503986-1000: Process 4744 (\Device\HarddiskVolume2\Windows\System32\msiexec.exe) has opened key \REGISTRY\USER\S-1-5-21-3294739943-1419706600-419503986-1000\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts

The driver \Driver\WUDFRd failed to load for the device WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_LEXAR&PROD_JUMPDRIVE&REV_1.00#216 4626984&0#.

The following boot-start or system-start driver(s) failed to load:
UsbCharger

and lve just noticed this starting to show up in my logs:

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0xC83A35C2A0D8. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.