Brand new PC, BSOD 2 days in a row. Please help!

So I just received this new gaming rig from ibuypower. It has been working great for the time being. Yesterday I had a BSOD and today while the computer was idle it had another BSOD. This is the latest information in the error window:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
Any ideas?

The attached is the W7F Diagnostic Zip that should help solve this I hope!

Thank you very much in advance.



Last edited:
All files in the How to ask for BSOD Help thread are in the compressed folder. Truly hope someone is able to assist!

Last edited:


Honorable Member
You have 110 updates installed for SP1 - normally there are about 130 - 140. Please go to Windows Update and download all the available updates.

You have a wireless USB Network Adapter: Win7 doesn't like those -

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
Please disable this device:

Name NETGEAR WNA3100 N300 Wireless USB Adapter
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems. Please uninstall it using these instructions here:

-install the program, then use the following free tool to ensure that the troublesome

sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL]

DuplexSecure - FAQ [/DEL]
Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install"

when you run it).
Alternate link:
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
The following is a list of drivers that could be causing problems. Drivers in red should be removed or updated (using the link provided).

Lycosa.sys Fri Jan 18 19:51:42 2008 (4790689E)
Razer Lycosa/Razer Tarantula Keyboard Driver. Older versions have BSOD issues with Win7
Driver Reference Table - Lycosa.sys

dtsoftbus01.sys Sat Jan 14 00:45:46 2012 (4F10358A)
Daemon Tools driver Possible BSOD issues in Win7
Driver Reference Table - dtsoftbus01.sys

scmndisp.sys Fri May 27 20:30:22 2011 (4DDF7D3E)
Netgear Neutral Wireless Solution
Driver Reference Table - scmndisp.sys

The reason why I highlighted the scmndisp.sys driver is because of this:

Debug session time: Fri Nov 23 10:46:58.047 2012 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\112212-25849-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 21:32:38.653
BugCheck A, {0, 2, 1, fffff800034ced2c}
[COLOR=#ff0000]Probably caused by : scmndisp.sys ( scmndisp+16d1 )[/COLOR]
[COLOR=#ff0000]FAILURE_BUCKET_ID:  X64_0xA_scmndisp+16d1[/COLOR]
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
Debug session time: Thu Nov 22 13:13:24.189 2012 (UTC + 11:00)
Loading Dump File [C:\Users\MZ\SysnativeBSODApps\112112-24726-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 4:34:41.001
BugCheck A, {80, 2, 1, fffff800034ec2ff}
Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f )
FAILURE_BUCKET_ID:  X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f
MaxSpeed:     3600
CurrentSpeed: 3600
BiosVersion = F12
BiosReleaseDate = 07/05/2012
The first minidump points to scmndisp.sys (which is also your Wireless USB Adapter driver, which I mentioned in my second opening paragraph).

The second one, ntkrnlmp.exe (NT Kernel Multi Processor), comes with the message:
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  [COLOR=#ff0000]This is usually[/COLOR]
[COLOR=#ff0000]caused by drivers using improper addresses.[/COLOR]
If a kernel debugger is available get the stack backtrace.
Both minidumps relate to driver problems, and one of them points to the exact driver - this leads me to believe that it IS the wireless USB network adapter that's causing the problem.

Thank you. Working on it now.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.