Solved Random BSOD Doing Anything, PROCESS_NAME: wininit.exe

[Chaospudding]

Quick Story About What I Use A PC For:

- Hi, I just recently built a new PC (It's about 3 months old, as of August 29th), and It's been giving me infrequent -random- crashes. I could be playing a game, or browsing the web, or having it idle. Sometimes it crashes after 2 days, sometimes it crashes after a week, or a week and a half. I only play "Guild Wars", "Minecraft" and "Starcraft 2", and I'm a frequent user of Google Chrome. Since the PC is new and has been giving me trouble since I purchased it, I haven't installed anything else on it other than what I listed above, and the occasional Microsoft Update.

PC Specifications:

OS: Windows 7 Ultimate x64 (Full Retail)
Case: In-Win Dragon Rider
Processor: Intel® Core™ i7-2600K
Graphics: AMD Radeon™ HD 6950
Motherboard: ASUS P8Z68-V Pro
Power Supply: OCZ Z Series 850W Power Supply (Gold Certified / Modular)
Memory: Corsair Vengeance™ - 16GB Dual Channel DDR3
SSD (Main): OCZ Agility 3 SATA III 2.5"
HDD (Not Main): Barracuda 7200.10 SATA 3.0Gb/s 320-GB

Memory Dump File:

- Is Attached

A Little Bio About My PC:

- It runs comfortably at 35 degrees Celsius idle, can go up to 45 when I'm gaming. Incredibly fast, runs all my programs flawlessly. There's no real cause to why it crashes, I've attempted to re-create the scenario in which it crashes, but seems to be completely random.

Last But Not Least, Things I've Tried:

- Despite the fact I've already tried these, I am open minded and am willing to try any of them again if necessary. Keep in mind whenever I say "It still crashed then", it still means that it was a -random- crash, and that my PC ran fine for about a week before it crashed again.

a) I've taken out my SSD, and just ran the HDD. It still crashed then.
b) I've taken out my HDD, and just ran the SSD. It still crashed then.
c) I updated the firmware on my SSD. It still crashed then.
d) I reformatted my SSD and my HDD and tried them both separately/together again. It still crashed.
e) I updated my BIOS version to whatever the latest is on the ASUS website. It still crashed.
f) I ran MemTest86+ on each stick separately for at least 8 passes, and then ran it again on all of them together, flawless results.

And just recently, I changed a few settings in my BIOS related to "Turbo Mode" and "Power Saving" ... which I don't think I need ... so I turned them off. I know my PC has the ability to Overclock, but I don't want it to until I can find a stable setting for my PC to run comfortably at without crashing.

Any help is appreciated. Thanks.

 

[zigzag3143]

Quick Story About What I Use A PC For:

- Hi, I just recently built a new PC (It's about 3 months old, as of August 29th), and It's been giving me infrequent -random- crashes. I could be playing a game, or browsing the web, or having it idle. Sometimes it crashes after 2 days, sometimes it crashes after a week, or a week and a half. I only play "Guild Wars", "Minecraft" and "Starcraft 2", and I'm a frequent user of Google Chrome. Since the PC is new and has been giving me trouble since I purchased it, I haven't installed anything else on it other than what I listed above, and the occasional Microsoft Update.

PC Specifications:

OS: Windows 7 Ultimate x64 (Full Retail)
Case: In-Win Dragon Rider
Processor: Intel® Core™ i7-2600K
Graphics: AMD Radeon™ HD 6950
Motherboard: ASUS P8Z68-V Pro
Power Supply: OCZ Z Series 850W Power Supply (Gold Certified / Modular)
Memory: Corsair Vengeance™ - 16GB Dual Channel DDR3
SSD (Main): OCZ Agility 3 SATA III 2.5"
HDD (Not Main): Barracuda 7200.10 SATA 3.0Gb/s 320-GB

Memory Dump File:

- Is Attached

A Little Bio About My PC:

- It runs comfortably at 35 degrees Celsius idle, can go up to 45 when I'm gaming. Incredibly fast, runs all my programs flawlessly. There's no real cause to why it crashes, I've attempted to re-create the scenario in which it crashes, but seems to be completely random.

Last But Not Least, Things I've Tried:

- Despite the fact I've already tried these, I am open minded and am willing to try any of them again if necessary. Keep in mind whenever I say "It still crashed then", it still means that it was a -random- crash, and that my PC ran fine for about a week before it crashed again.

a) I've taken out my SSD, and just ran the HDD. It still crashed then.
b) I've taken out my HDD, and just ran the SSD. It still crashed then.
c) I updated the firmware on my SSD. It still crashed then.
d) I reformatted my SSD and my HDD and tried them both separately/together again. It still crashed.
e) I updated my BIOS version to whatever the latest is on the ASUS website. It still crashed.
f) I ran MemTest86+ on each stick separately for at least 8 passes, and then ran it again on all of them together, flawless results.

And just recently, I changed a few settings in my BIOS related to "Turbo Mode" and "Power Saving" ... which I don't think I need ... so I turned them off. I know my PC has the ability to Overclock, but I don't want it to until I can find a stable setting for my PC to run comfortably at without crashing.

Any help is appreciated. Thanks.

No definitive proof but I would do this:

Update this driver (yours 3 years old)
Related to LVUSBS64.sys USB Statistic Driver from Logitech Inc.


Run driver verifier to find what driver is causing the problem.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[Chaospudding]

Sorry to be a pain, just a few questions...

a) I am unsure how to update the driver "LVUSBS64.sys" you listed above, how do I go about doing that? I have a Logitech Communicate STX webcam, along with a Logitech G510 series gaming keyboard. I reinstalled the software for both of those, unplugged both and plugged both back in, so I know it isn't related to those...I think...

b) Also, When I go into my device manager, under "Other Devices" there is one device called "Unknown Device" ... I have no information on it, so I cannot explain any further than that, do you have any insight on how to check what it is and how I can update it? I tried right-clicking and updating it, but to no avail. When I click "Scan for hardware changes" it pops up with a window that says "Scanning Plug and Play compliant hardware..." ... but it never does find any driver to update.

c) Also, I ran the Driver Verifier, computer is still running as it usually does. Been about 2 hours now. I selected all the non-Microsoft drivers. I will let it run for 36 hours as stated below, but how do I stop it from running if I need to?




Alright, I just woke up after letting my PC run all night with the driver verifier on. My SSD seems to have crashed, but it did not generate a Minidump file this time. Am I supposed to check something now?

 

[Chaospudding]

Don't mean to double post, but I thought I'd mention one more thing too. When my computer does crash, it's a gradual process. By that I mean...every program I'm currently running will pop up with an error message one after the other, like for example:

- Windows Media Centre has detected an error and will be shut down
- Flash player has detected an error and will be shut down
- Internet explorer has detected an error...etc...
- ...etc...

and then I'll get a "Cannot reference memory at -some address-" then a whole bunch of numbers that resemble this (0x0000008 or something) ... and then I go to blue screen.

Also, there was one time my computer had that exact same thing (above) happen, except it didn't go to a blue screen, which was weird. Instead, every program just crashed, and when I tried to open a program, it told me it couldn't find the program specified (As if I had deleted it or something) ... then when I restarted everything was fine.

I hope this helps a little more. Thanks for the support, really hoping to get this resolved soon too.

 

[zigzag3143]

Sorry to be a pain, just a few questions...

a) I am unsure how to update the driver "LVUSBS64.sys" you listed above, how do I go about doing that? I have a Logitech Communicate STX webcam, along with a Logitech G510 series gaming keyboard. I reinstalled the software for both of those, unplugged both and plugged both back in, so I know it isn't related to those...I think...

b) Also, When I go into my device manager, under "Other Devices" there is one device called "Unknown Device" ... I have no information on it, so I cannot explain any further than that, do you have any insight on how to check what it is and how I can update it? I tried right-clicking and updating it, but to no avail. When I click "Scan for hardware changes" it pops up with a window that says "Scanning Plug and Play compliant hardware..." ... but it never does find any driver to update.

c) Also, I ran the Driver Verifier, computer is still running as it usually does. Been about 2 hours now. I selected all the non-Microsoft drivers. I will let it run for 36 hours as stated below, but how do I stop it from running if I need to?




Alright, I just woke up after letting my PC run all night with the driver verifier on. My SSD seems to have crashed, but it did not generate a Minidump file this time. Am I supposed to check something now?

CP

a-go to logitech for the newest version of your drivers. Download and install them.

b-go to the unknown device>properties>pull down the bar>look for hardware ID's copy the ID and google it

c-Upload the DMP created when verifier crashed your machine as usual.

 

[Chaospudding]

CP

a-go to logitech for the newest version of your drivers. Download and install them.

b-go to the unknown device>properties>pull down the bar>look for hardware ID's copy the ID and google it

c-Upload the DMP created when verifier crashed your machine as usual.

Alright, maybe this will simplify things:

- I just cleared my RTC RAM in CMOS, and reformatted my SSD.
- My SSD is currently my only drive in the computer.
- I installed Windows 7 Ultimate x64.
- I installed the drivers (and -only- the drivers, as in, -not- the utilities) for my motherboard.
- I installed the graphics card driver from it's CD as well.
- The only USB devices plugged into my PC are my mouse and keyboard. Both function just fine.

- After I finished all the above, I went into my BIOS and checked through everything, and since I do not want to overclock -at all-, I set everything related to overclocking to "auto" or "disable", such as setting Phase Control to "Optimized" and setting my RAM speed to 1600mHz, disabling "Intel Speedstep Technology" and "Turbo Mode" ... etc.

Now, the system was running fine for about an hour or 2, and downloading some cool HD backgrounds from a site was the only thing I did on the PC, until I decided to do some windows updates. So I click "Check for updates" and since it's a fresh install, there were 69 important updates. So I click "Install" and it begins to download them. I believe it only downloaded (not installed) about 10 of them or so, and then it just goes to a BSOD.

I was hoping it would generate a crash dump file, but it didn't. Apologies. I turned off the "auto restart" so next time it crashes I'm hoping that'll give it the time it needs to generate the file. Until then I will try to re-create the error...

If you have any insight on what it might be this time, I'll try to respond asap. Thanks for the help so far though



EDIT: Ok, it crashed again, I will upload the files needed momentarily. I also set my RAM to 1333mHz instead instead of 1600mHz to see if it made a difference. Anyhow, I'm glad that when it crashed this time it gave a different error than "wininit.exe" ... hopefully correcting this will fix it completely. I have a feeling that it is related to a setting in my BIOS ... if you have any thoughts on what my settings should be in the BIOS that would be a great help too xD, maybe I'm setting up something wrong there...

 

[zigzag3143]

CP

a-go to logitech for the newest version of your drivers. Download and install them.

b-go to the unknown device>properties>pull down the bar>look for hardware ID's copy the ID and google it

c-Upload the DMP created when verifier crashed your machine as usual.

Alright, maybe this will simplify things:

- I just cleared my RTC RAM in CMOS, and reformatted my SSD.
- My SSD is currently my only drive in the computer.
- I installed Windows 7 Ultimate x64.
- I installed the drivers (and -only- the drivers, as in, -not- the utilities) for my motherboard.
- I installed the graphics card driver from it's CD as well.
- The only USB devices plugged into my PC are my mouse and keyboard. Both function just fine.

- After I finished all the above, I went into my BIOS and checked through everything, and since I do not want to overclock -at all-, I set everything related to overclocking to "auto" or "disable", such as setting Phase Control to "Optimized" and setting my RAM speed to 1600mHz, disabling "Intel Speedstep Technology" and "Turbo Mode" ... etc.

Now, the system was running fine for about an hour or 2, and downloading some cool HD backgrounds from a site was the only thing I did on the PC, until I decided to do some windows updates. So I click "Check for updates" and since it's a fresh install, there were 69 important updates. So I click "Install" and it begins to download them. I believe it only downloaded (not installed) about 10 of them or so, and then it just goes to a BSOD.

I was hoping it would generate a crash dump file, but it didn't. Apologies. I turned off the "auto restart" so next time it crashes I'm hoping that'll give it the time it needs to generate the file. Until then I will try to re-create the error...

If you have any insight on what it might be this time, I'll try to respond asap. Thanks for the help so far though



EDIT: Ok, it crashed again, I will upload the files needed momentarily. I also set my RAM to 1333mHz instead instead of 1600mHz to see if it made a difference. Anyhow, I'm glad that when it crashed this time it gave a different error than "wininit.exe" ... hopefully correcting this will fix it completely. I have a feeling that it is related to a setting in my BIOS ... if you have any thoughts on what my settings should be in the BIOS that would be a great help too xD, maybe I'm setting up something wrong there...

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Chaospudding]

Gotcha, I just read the steps to take, and here is what I've done so far corresponding to the steps in the guide that you just linked me to (Anything bolded below is changes I've made since I first posted this):


1) Ensured none of the components are overclocked. My RAM is set to X.M.P, which I'm pretty sure is supposed to be stable (Correct me if I'm wrong though ^_^). It currently runs at it's listed speed and power of 3.4Ghz (Processor) and 1600mHz (RAM)

2) Today I took off the processor/heatsink, and re-applied the thermal gel, as I don't think the gel that came with my processor was very good, nor did it apply correctly ... so I watched a YouTube video on how to remove/re-apply thermal gel properly, and did so according to that. I also made sure my heatsink was properly attached. My system temperature is now a nice 35-40 degrees Celsius, and the thermal gel no longer looks like a scatterplot graph on my chip.

3) Updated my graphics driver to the current one. BIOS is still latest as well. I have also applied Windows updates up to the current date, and am now going to install some software such as "Visual Studio 2010" on my HDD. I will also be plugging in my HDD too, since its currently not ...

4) My BIOS is already the latest version (0606)

5a) I installed Windows 7 Ultimate x64 from an ISO file from MSDN burnt on a DVD (With a legit key, of course) though I thought that might be giving me a problem, so I downloaded and burned Windows 7 Ultimate x64 /w SP1 on a new DVD, to see if it will make a difference.

5b) I literally removed about 2 bugs from my system as well, a live earwig and a dead moth. So thats all clean again now. Don't like bugs in my system ... x_x

6) I haven't stressed the components with the new Windows 7 installation ... but I had ran a MemTest86+ before, and my RAM returned perfect. I ran scandisks and other Harddrive testers as well, and did the "sfc /scannow" command, everything returned excellent results.

7) Vanilla installation complete. Hasn't crashed yet ... been up for about 2 hours now (Will edit this every now and then to keep track of how long it takes to crash again, if it does). My SSD is still the only harddrive in my system currently. I will not put in my other HDD until I know it's good to go.

8) I re-seated my RAM, ensured every stick was locked in place. I re-seated my processor/heatsink, and re-applied thermal gel as well. I also swapped out my 6GB/s data cable for my SSD with the other that came with the motherboard, in case that was faulty.

9) I hope it never comes to step 9...



Crashed again, though...it couldn't generate a .dmp file, but I did manage to write down the stop code at least. Hope this helps:

STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF80002C9DBA0, 0xFFFFF8800357DDC8, 0xFFFFF8800357D620)

***What I was doing when it crashed: The system ran fine with just my SSD in it, then I needed to pull some data off my HDD, so I put that in as well, with my SSD (So now there are 2 drives, my SSD as my main, and my HDD as storage), and was copying a folder full of files to an external drive I had from my HDD to that. While copying, my system crashed. So, I restarted, and then proceeded to copy the same data over again. This time, it succeeded. Does this sound like I have a, or multiple faulty hard-drives? I doubt it's my RAM, though, I thought I read somewhere that a stop code of 0x0000007E was related to a bad driver. I have yet to upgrade my SSD's driver to a more recent version, I will try that next. If you have any insight on what else I can try now, I'm willing


...Also, I noticed that when I went to reformat my HDD (to make it clean for storage), all my drives were listed as "Primary" ... isn't only one (my SSD) supposed to be a primary drive? Or is this related to the partition?

 

[Chaospudding]

I'm pretty sure I've solved the problem. While I can't specify the "exact" cause to as why it was crashing, I can say that by updating all my drivers to their latest version (Except my SSD) + buying a new webcam = Microsoft Lifecam Studio 3.5 (as my old one was incompatible), everything has been working for about a week now with 0 crashes.

My old webcam, Logitech Communicate STX wasn't compatible with my OS, even though it said it was on the Windows site. Every time I plugged it in, or updated it's driver from the Logitech site, it still showed up as "Unknown Device", so that might have been causing a problem as well.

Anyhow, thanks for your support. I'm not going to mark this as truly "Solved" until another week or 2 passes. Then I will know for sure that this is completely fixed

 

[Chaospudding]

Turns out my OCZ Agility 3 SSD was faulty. As soon as I put in a regular 1TB Western Digital Drive, it worked fine and has been working fine ever since.

Thanks for the help up until now, cheers.