imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #1
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {31, fffffa8006fc5d70, fffff880132d3000, fffff8a0053a229c}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7171 )
Followup: MachineOwner
Bugcheck 1A is often associated with faulty RAM as the bugchecks actual meaning is a severe memory management...
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #121
Hopefully. I might just add 8 more to my system before I do send it out. Don't really need it but hell it won't hurt to have it just in case I do end up using it.
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #123
Well I was out working on my truck and came back to see my computer was at the login screen. Bluescreened again when I was on my desktop. The old ram is still in there but I'm not sure what caused it this time though. I juuust got the new ram to put in and I'll send the old one off shortly. Gonna upload the logs to see if it was the same crap.
Attachments
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {44, 2, 1, fffff8000343c47c}
*** WARNING: Unable to verify timestamp for CMUACWO.sys
*** ERROR: Module load completed but symbols could not be loaded for CMUACWO.sys
Probably caused by : CMUACWO.sys ( CMUACWO+437d4 )
Followup: MachineOwner
looks like that C-media driver still isn't happy. This is what I wrote about the same dump file you received before:
it looks like CMUACWO.sys was the cause of the bsod and this relates to a C-Media USB audio device driver. The one your carrying is dated 2013 and a little googling found this 2014 version although I'm not 100% sure it's compatible:
http://drivers.softpedia.com/get/SO...io-DAC-Device-Driver-7013-for-Windows-7.shtml
Why not try updating it if possible?
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #125
Yea I tried when you told me about it but for some reason I get a file and no exe. I tried updating it manually through the device manager and selecting the file but had no luck
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #127
Alright will try it when I'm home. Thanks
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #128
There's no INF file
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Actually there is. Download the file again, extract the contents using something like 7zip and you'll find the 'inf'. Use Device manager to update.There's no INF file
Last edited by a moderator:
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #130
Wow I feel like a idiot now.
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #131
Link Removed Wont let me select the file to use for the update.
Last edited:
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Try this:Link Removed Wont let me select the file to use for the update.
Go to Device manager right click on device you want to update, click properties then update driver, click 'Let me pick from a list of device drivers on my computer', on the next revealed box look over to the right for 'Have Disk' click that, you'll then see a browse box appear asking you to browse to the location of the disk. You need to actually browse to the location of the 'inf' file. This browse box will or should only see the inf so once you have the right folder it'll pick it up straight away. Good luck!
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #134
Wait, do I have to dorp it in the x86 folder first? When I do that it says the specified path is not found.
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #136
Yea that's what I did at first and it worked out. I don't really know if it actually updated the driver properly. I had to restart and what not but it was basically an instant update.
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #138
Says 7.0.1.3 so it looks current. Date is a little off though. Shouldn't matter though, hopefully.
imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
-
- #140
Thanks for the help
Similar threads
- Solved
- Replies
- 14
- Views
- 2K
- Solved
- Replies
- 5
- Views
- 2K
- Solved
- Replies
- 5
- Views
- 9K
- Solved
- Replies
- 17
- Views
- 8K
- Replies
- 20
- Views
- 13K