• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

At boot why would SSD or HDD run before reaching ASRock logo?

balloonshark

balloonshark

Diamond Member
Edit: Event viewer shows that it was probably creating a dump file. Is there a way for someone to look at my Admin events? I've had about 11 BSOD's but I though they were related to a security program. It looks like the issue is getting worse. I've got plenty of Warnings, Errors and Critical's in the Admin events.

How can I test my SSD?
______________________________________________________________

When I boot my Windows 8 64 bit machine it is normal to see the ASRock logo, then a flash of my username/pic and then the start screen. This all happens in 9 to 12 seconds.

When I booted today the monitor stayed black for about a minute with a solid SSD/HDD light. After that everything looked like a normal boot.

What would run right after pressing the power button and before seeing the BIOS/UEFI/MB logo? Should I be worried that it was something malicious?

Windows update is set to check for updates only and let me decide when to download and install them.
 
Last edited:
If you have dump file(s), then you want to say hello to our friend WhoCrashed. Should support Windows 8. Download the program and let us know what it finds in your dump(s).

BTW, love you "Old Rig." The Q660 is quite a chip.
 
Thanks ketchup79! The Q6600 is a great chip.

I originally thought the BSOD's might be an issue with Online Armor. They looked at a full memory dump from the 14th and said it could be Sandboxie's fault. http://support.emsisoft.com/topic/12119-windows-8-64-bit-bsod-that-may-be-related-to-oamon/

Sandboxie says it has something to do with a security token. http://www.sandboxie.com/phpbb/viewtopic.php?t=16309&sid=726ddeb0d121f5afc196fe2472acc380

This last dump has me puzzled because it didn't happen like the others. The others were triggered after boot when starting firefox or palemoon sandboxed. I also have bluescreenview if it would offer extra information.
______________________________________________________________
[FONT=Segoe UI, Arial] Welcome to WhoCrashed (HOME EDITION) v 4.02 [/FONT]
[FONT=Segoe UI, Arial]This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
[/FONT]
[FONT=Segoe UI, Arial]To obtain technical support visit www.resplendence.com/support

[/FONT][FONT=Segoe UI, Arial]Click here to check if you have the latest version or if an update is available.

[/FONT][FONT=Segoe UI, Arial]Just click the Analyze button for a comprehensible report ...


[/FONT][FONT=Segoe UI, Arial] Home Edition Notice [/FONT]
[FONT=Segoe UI, Arial]This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
[/FONT]
[FONT=Segoe UI, Arial] System Information (local) [/FONT]
[FONT=Segoe UI, Arial]computer name: WOPRII
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8516931584 total
VM: 2147352576, free: 1917825024


[/FONT]
[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 8/19/2013 4:17:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081913-13078-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF88003C061E0, 0xFFFFF88003C06138, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_SECURITY_CHECK_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 8/19/2013 4:17:22 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]oanet.sys[/FONT] (oanet+0x2463)
Bugcheck code: 0x139 (0x3, 0xFFFFF88003C061E0, 0xFFFFF88003C06138, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_SECURITY_CHECK_FAILURE[/FONT]
file path: C:\Windows\system32\drivers\oanet.sys
product: [FONT=Segoe UI, Arial]OA Helper Driver[/FONT]
company: [FONT=Segoe UI, Arial]Emsisoft[/FONT]
description: OA Helper Driver
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: oanet.sys (OA Helper Driver, Emsisoft).
Google query: [FONT=Segoe UI, Arial]Emsisoft KERNEL_SECURITY_CHECK_FAILURE[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Wed 8/14/2013 12:24:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-13109-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A010DD4000, 0x0, 0xFFFFF8008A2D92A0, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 8/14/2013 10:11:58 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-13203-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A00845000C, 0x0, 0xFFFFF8014C2CC49A, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 8/11/2013 8:40:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-13328-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A009E4200C, 0x0, 0xFFFFF802804DA49A, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 8/11/2013 4:21:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081113-13187-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A0095F2000, 0x0, 0xFFFFF801B8ED12A0, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 8/5/2013 10:15:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-13234-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF8800A1951E0, 0xFFFFF8800A195138, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_SECURITY_CHECK_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 8/5/2013 4:10:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-14031-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A0089F4000, 0x0, 0xFFFFF8020FA562A0, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 8/4/2013 2:23:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080413-14296-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A010260000, 0x0, 0xFFFFF802D5AC42A0, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 8/3/2013 10:26:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080313-13234-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A009E58000, 0x0, 0xFFFFF8039026B2A0, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 7/30/2013 3:08:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-13390-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x139 (0x3, 0xFFFFF88003D6C1E0, 0xFFFFF88003D6C138, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_SECURITY_CHECK_FAILURE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 7/29/2013 1:21:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-13406-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A008C45000, 0x0, 0xFFFFF800958692A0, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 7/27/2013 9:46:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-14203-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A008E6600C, 0x0, 0xFFFFF800948C149A, 0x0)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial] Conclusion [/FONT]
[FONT=Segoe UI, Arial]13 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

[FONT=Segoe UI, Arial]oanet.sys (OA Helper Driver, Emsisoft)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.



[/FONT]
 
I am a little short on time ATM, but it looks like these are coming from a driver Windows 8 doesn't like. I would start looking on the Asrock page for recent Windows 8 drivers (last few months) and for software updates for devices that aren't in your sig. Same for the video card.

Windows 8 has a good updater, but it usually takes them a while to put a driver that they are OK with on Automatic Updates.
 
denis280 said:
yes it is.(Tall Emu Online Armor Firewall helper file.)you should restore you system to (before)this was install.or delete it from your pc.
Click to expand...
Thanks! Wasn't it just the most recent crash that had something to do with Online Armor or am I missing something? I really hate to ditch OA as it served me well for 5 years on XP. On the other hand these BSODs are getting annoying

ketchup79 said:
I am a little short on time ATM, but it looks like these are coming from a driver Windows 8 doesn't like. I would start looking on the Asrock page for recent Windows 8 drivers (last few months) and for software updates for devices that aren't in your sig. Same for the video card.

Windows 8 has a good updater, but it usually takes them a while to put a driver that they are OK with on Automatic Updates.
Click to expand...
The only new driver on the ASRock site is the ASMedia Sata 3 driver. http://www.asrock.com/mb/Intel/Z87 Extreme6/?cat=Download&os=Win864

I got my non-beta gpu driver from here. http://support.amd.com/us/gpudownload/Pages/index.aspx From the drop down boxes I selected Desktop graphics - Radeon HD series - Radeon HD Series 7XXX PCIe - Windows 8 64 bit. I think that was right which shows CCC Revision 13.4 and that is what I have installed. If I was supposed to get the driver elsewhere please let me know.

I have disabled automatically installing drivers from Windows Update. Not sure if the lower section needs changed.


When I check for optional updates the only driver shown is for my monitor. It's a slightly different monitor though (2232GW Plus). I did not install a driver for it when I built this machine. It looks to have been released in 2007 but published at the end of 2012. When I check Samsung's site They show a driver from Jan. 2008 for Win 98/ME/2K/XP/X64/Vista. http://www.samsung.com/us/support/owners/product/2232BWPLUS#

I got my printer drivers from Canon.

Logitech mouse and keyboard with no drivers installed. I have a eSata external HDD plugged in but it hasn't been on since I built the machine. I did have a logitech gamepad plugged in (no driver installed) but I unplugged it yesterday or day before. I've only had 1 thumb drive plugged into the machine and it hasn't seen action for a couple of weeks. I did plug a new one in to scan with Shadow Defender on (virtual mode) so it shouldn't have an impact. I can't think of anything else.
 
balloonshark said:
...Thanks! Wasn't it just the most recent crash that had something to do with Online Armor or am I missing something? I really hate to ditch OA as it served me well for 5 years on XP. On the other hand these BSODs are getting annoying....
Click to expand...

Misbehaving antivirus software is far and away one of the most common causes of PAGE_FAULT_IN_NONPAGED_AREA and KERNEL_SECURITY_CHECK_FAILURE errors. If WhoCrashed is identifying oanet.sys to be the faulting driver (as denis280 already pointed out) you can either check with Emsisoft for updated program software and/or drivers, or you can uninstall the software.

WhoCrashed is a just a user friendly GUI frontend for Microsoft's WinDBG and DriverVerifier tools. So, depending on what data is collected for any given crash dump, the offending driver, program, or service may or may not be identified. When WhoCrashed analyzes consecutive dumps it is narrowing down the list of possible faulting modules each time. I'd put my money on Emsisoft being the problem.

.
 
Thanks for your input Bubbaleone.

They haven't updated the main component of Online Armor since Oct. 2012. If I don't hear from them soon I'll have no choice but to install the program as a troubleshooting step.

I'll keep an eye on this topic is case anyone has other ideas. I do have the last full dump and this most recent dump that I can 7zip. The last one was 370MB though.
 
balloonshark said:
...They haven't updated the main component of Online Armor since Oct. 2012...
Click to expand...

And it's quite likely that a recent Windows Security Update finally broke OA's compatibility, even though it had previously been operating without problem. Your plan to uninstall and test if the BSOD stops occuring is correct, but if Emsisoft hasn't updated that program in nearly a year I wouldn't hold my breath waiting for an update. Although if this is is something that's recently begun happening to all OA clients, then Emsisoft might do something about updating the code. You should checkout a 30-day trial of ESET Smart Security for a really excellent, lightweight firewall/antivirus.

.
 
Last edited:
Sorry for the late reply. I uninstalled OA last night, rebooted twice and used my computer for a while afterwards. When I booted up today I got the normal BSOD when starting up my sandboxed browser.

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 8/21/2013 4:39:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082113-7703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x50 (0xFFFFF8A003D4A00C, 0x0, 0xFFFFF800C28D449A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 8/21/2013 4:39:06 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: sbiedrv.sys (SbieDrv+0x1C945)
Bugcheck code: 0x50 (0xFFFFF8A003D4A00C, 0x0, 0xFFFFF800C28D449A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Program Files\Sandboxie\SbieDrv.sys
product: Sandboxie
company: Sandboxie Holdings, LLC
description: Sandboxie Kernel Mode Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sbiedrv.sys (Sandboxie Kernel Mode Driver, Sandboxie Holdings, LLC).
Google query: Sandboxie Holdings, LLC PAGE_FAULT_IN_NONPAGED_AREA
____________________________________________________________
____________________________________________________________

Sandboxie's developer wanted me to upload my ntoskrnl.exe file. Hopefully he can figure something out. If not I will reinstall Windows and hope for the best.
 
balloonshark said:
Sorry for the late reply. I uninstalled OA last night, rebooted twice and used my computer for a while afterwards. When I booted up today I got the normal BSOD when starting up my sandboxed browser.....
.....Sandboxie's developer wanted me to upload my ntoskrnl.exe file. Hopefully he can figure something out. If not I will reinstall Windows and hope for the best.
Click to expand...
It appears that you prefer a layered security approach (which is good) if you've been running both Emsisoft's OA and Sandboxie. As an alternative to Sandboxie you might be interested in trying out the 30-day trial of Shadow Defender.

.
 
Bubbaleone said:
It appears that you prefer a layered security approach (which is good) if you've been running both Emsisoft's OA and Sandboxie. As an alternative to Sandboxie you might be interested in trying out the 30-day trial of Shadow Defender.
Click to expand...
I do use Shadow Defender when I try new software or surf the dark side of the net :thumbsup:. I love my layers and have been using them for quite a while on XP. It is also nice to finally run in a standard user account.

I do admit I was temped when I saw ESET Smart Security 5 for around $10 and read the 5 user was $20. NewEgg's been trying to get rid of the old version so keep your eye out if you need extra keys.

I may just reinstall Windows soon and try to keep things simple this time.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top