NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #1
Afternoon all , I get BSOD when trying to burn blu-ray disks , It,s Nero 2018 or 2017 I use when burning blu--rays . Thank you .
Solution
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {18, 0, ffffc70086fa3180, 4}
Probably caused by : memory_corruption
Followup: memory_corruption
I can see the process causing the issue is nerovision.exe which as your aware part of Nero itself.
Now as you can use a different app to burn the disks without...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
eh?if anyones interested
I'm not sure if understand the above remark but in any case can you post the dump files?
Did you miss this post?:
If you have a system restore point for around the time it worked you could try that.
Did you see my other questions regarding Nero support?
Your page file?
Did you also forget about this?
Try running the driver verifier, this will stress each driver in turn and if they bsod then the culprit will be named on the dump file.
If the driver verifier causes a bsod boot loop, you'll need to boot into safe mode and turn the verifier off. The resulting dump files should have the culprit named.
Link Removed
Is your version patched and please post the full version number. (your not sure if it's Nero 17 or 18)
I've asked you to do several things which could possibly help your situation but your either ignoring my advice or simply forgetting?
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #62
Yes Nero is Patched its 2018 , but still got BSOD on 2017 version as well .
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Try running the driver verifier, this will stress each driver in turn and if they bsod then the culprit will be named on the dump file.
If the driver verifier causes a bsod boot loop, you'll need to boot into safe mode and turn the verifier off. The resulting dump files should have the culprit named.
Link Removed
If the driver verifier causes a bsod boot loop, you'll need to boot into safe mode and turn the verifier off. The resulting dump files should have the culprit named.
Link Removed
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #64
it says ,.file not found or no read position , I still get that when I try to sent to a compressed zip folder .
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #65
kemical on Driver Verifier page wheres the download
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #66
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
There isn't one.kemical on Driver Verifier page wheres the download
The guide tells you how to use it. Just look down the list for your version of windows and follow the guide.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffb0824f4dc028, be000000, 800400}
Probably caused by : GenuineIntel
Followup: MachineOwner
Overheating can often cause bugcheck 124, when did you last clean the system free of dust?
If you have never done it then your system might be overheating. Check your system temps at stress and at idle.
HWiNFO64 is good for checking temps
Make sure everything you use is updated including things like browsers as i've known bugcheck 124 to be caused by an out of date flash module.
Also try contacting Nero support, they provide an application which you can use. This collects the relevant data associated with the crash and you can then send it in along with your post.
Tools and Utilities - Get Support Files
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #69
It is clean , had the side off the other day to check the memory . Also there are 4 fans so I don't think it will be the temperature .
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #70
In Windows 7 you did a Windows Memory Diagnostic test where you restarted and checked for errors . Is there nothing like that in Windows 10 .
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Can you check anyway?Also there are 4 fans so I don't think it will be the temperature .
Maybe the cooler isn't working properly or similar? But anyway it's up to you.
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
How to Test Your Computer’s RAM for ProblemsIn Windows 7 you did a Windows Memory Diagnostic test where you restarted and checked for errors . Is there nothing like that in Windows 10 .
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Overheating can often cause bugcheck 124 although software can cause it too.
Check your system temps at stress and at idle.
HWiNFO64 is good for checking temps
Make sure everything you use is updated including things like browsers as i've known bugcheck 124 to be caused by an out of date flash module.
Also try contacting Nero support, they provide an application which you can use. This collects the relevant data associated with the crash and you can then send it in along with your post.
Tools and Utilities - Get Support Files
Try running the driver verifier, this will stress each driver in turn and if they bsod then the culprit will be named on the dump file.
If the driver verifier causes a bsod boot loop, you'll need to boot into safe mode and turn the verifier off. The resulting dump files should have the culprit named.
Link Removed
To boot into safe mode with windows 10 you'll need a recovery disk/usb. Simply boot from the recovery, enter the recovery console, choose safe mode and then turn off the verifier (for boot loops)
Check your system temps at stress and at idle.
HWiNFO64 is good for checking temps
Make sure everything you use is updated including things like browsers as i've known bugcheck 124 to be caused by an out of date flash module.
Also try contacting Nero support, they provide an application which you can use. This collects the relevant data associated with the crash and you can then send it in along with your post.
Tools and Utilities - Get Support Files
Try running the driver verifier, this will stress each driver in turn and if they bsod then the culprit will be named on the dump file.
If the driver verifier causes a bsod boot loop, you'll need to boot into safe mode and turn the verifier off. The resulting dump files should have the culprit named.
Link Removed
To boot into safe mode with windows 10 you'll need a recovery disk/usb. Simply boot from the recovery, enter the recovery console, choose safe mode and then turn off the verifier (for boot loops)
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #74
kemical , I ran Driver Verifier this morning .
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #76
BSOD that's all it does about every minute , when I tried it yesterday morning . I got a new hard drive yesterday when I was out , I installed windows10 , that's how I;m talking to you now . Before it restarted it said BSOD code Bad-Pool-Caller or something like that .
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #77
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {62, ffff968040740000, ffff96804074000c, b7}
*** WARNING: Unable to verify timestamp for iocbios2.sys
*** ERROR: Module load completed but symbols could not be loaded for iocbios2.sys
Probably caused by : memory_corruption
Followup: memory_corruption
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #79
Can you give me some advice how to remove it please
NettleWarbler
Banned
- Joined
- Mar 25, 2016
- Messages
- 636
- Thread Author
-
- #80
Also can I remove it from this drive .
Similar threads
- Featured
- Article
- Replies
- 0
- Views
- 33
- Featured
- Article
- Replies
- 0
- Views
- 38
- Featured
- Article
- Replies
- 0
- Views
- 29
- Featured
- Article
- Replies
- 0
- Views
- 94
- Solved
- Replies
- 4
- Views
- 1K