Multiple BSOD's on new build

Spoonerz

New member
Local time
7:07 AM
Messages
13
System Info:

Windows 7 Ultimate 64-bit SP1
AMD Phenom II X4 955 Black Edition
Gigabyte GA-970A-UD3
Corsair 2x2GB DDR3 1333MHz
XFX HD 6870 1GB GDDR5
Samsung SpinPoint F3 500GB

Sometimes it's happened randomly, two or 3 times it's when im shutting down.

The other day my system crashed whilst watching a youtube video, but i think that was something to do with the flash video options. - Though come to think of it, it has messed up whilst i was watching something in vlc before...

Could really do with some proper help, only just built this system for my birthday(mid august) :(.
 
Last edited:

My Computer

OS
Windows 7 Ultimate x64
Spoonerz, Welcome to SF and now worries the BSOD team here is top flight and just be patient. I would like to suggest something to try till your zip is reviewed by the team. I was having issues with a new build and what I found was that a card reader attached via usb mobo port had gone bad. I would remove all none essential items from the mobo after first making sure that all of your drivers are up to date. Then have just your boot drive attached, all other drives and accessories cables removed from their mobo posts temporarily and then see how things go. Add items back one at a time and see which one creates the issue again and that could well be the culprit. Just something to try as this was the process I had to use when all my BSOD went on without reasonable cause.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
A blend of brains, brawn and dumb luck.
OS
Windows 7 Ultimate 64
CPU
i7 3770k OC'd 4.6 @ 1.17v, also FX 8120 & i5 miniITX
Motherboard
MSI P67A-GD80 b3
Memory
32 gb G.Skill Sniper DDR3 10-12-12-31 @ 2133
Graphics Card(s)
XFX Radeon 7870 2GB DDR5
Sound Card
Sound Blaster Z Series Card
Monitor(s) Displays
(2) LG LED 23" 1920 x 1080 2ms Monitors via mini d-port
Screen Resolution
1680 X 1050 p
Hard Drives
Samsung 256 gb 830 SSD sata III
(1) 1 tb WD Black
(2) 1 tb Hitachi deskmates/sata II
(2) 1 tb WD green/sata II
(2) 3 tb Seagate Barracuda
(1) 120 gb OCZ Vertex SS
(1) Drobo 5N w/5 Seagate 3tb
PSU
EVGA modular 1000G2 80% gold rating & APC 1200 RS
Case
CoolerMaster Storm Styker
Cooling
7 case fans 140mm & 120mm, NZXT Kraken X60
Keyboard
(2) Logitech Illuminated Keyboards (1) usb (1) wireless
Mouse
Logitech G700 & T-BC21 - nano nx for the laptop
Internet Speed
Basic 120mbps down
Antivirus
Trend Micro Titanium Max Security & Malwarebytes Premium
Browser
Chrome and IE 10
Other Info
5 Noctua case fans + 3 Noctua in p/p on NZXT cooler
Integrated hot swap drive bays for 2.5" Drives
(2) Lite-on dvd/cd/Blu Ray optical 22X
Integrated fan controller and led on/off
HP Officejet Pro 8630 all-n-one
Hot-swappable 3.5" hard drive bay
Netgear Nighthawk router
Asus USB 3 & sata 6 PCIe card
Vantec IDE to sata adptr./Ultra sata adptr
Lenovo L420 i5 lappy with m sata
Drobo 5N advanced NAS
Thanks for the welcome and yea i know, i just want to get it fixed as soon as possible lol.

I'm not sure how i could go about doing what you suggested as my BSOD's occur randomly, and all but one of the things connected to my mobo are necessary.

I think it might be to do with my drivers, but im not sure which ones :/
 

My Computer

OS
Windows 7 Ultimate x64
Sponnerz,
Open up device manager and look in each section for any yellow triangles. Once found then update those drivers and restart the system for testing. Gigabyte's site will be the best place to look for updates. Does Gigabyte have any add on that will monitor your system for important bios and driver updates? MSI has a program for this and it's a huge help.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
A blend of brains, brawn and dumb luck.
OS
Windows 7 Ultimate 64
CPU
i7 3770k OC'd 4.6 @ 1.17v, also FX 8120 & i5 miniITX
Motherboard
MSI P67A-GD80 b3
Memory
32 gb G.Skill Sniper DDR3 10-12-12-31 @ 2133
Graphics Card(s)
XFX Radeon 7870 2GB DDR5
Sound Card
Sound Blaster Z Series Card
Monitor(s) Displays
(2) LG LED 23" 1920 x 1080 2ms Monitors via mini d-port
Screen Resolution
1680 X 1050 p
Hard Drives
Samsung 256 gb 830 SSD sata III
(1) 1 tb WD Black
(2) 1 tb Hitachi deskmates/sata II
(2) 1 tb WD green/sata II
(2) 3 tb Seagate Barracuda
(1) 120 gb OCZ Vertex SS
(1) Drobo 5N w/5 Seagate 3tb
PSU
EVGA modular 1000G2 80% gold rating & APC 1200 RS
Case
CoolerMaster Storm Styker
Cooling
7 case fans 140mm & 120mm, NZXT Kraken X60
Keyboard
(2) Logitech Illuminated Keyboards (1) usb (1) wireless
Mouse
Logitech G700 & T-BC21 - nano nx for the laptop
Internet Speed
Basic 120mbps down
Antivirus
Trend Micro Titanium Max Security & Malwarebytes Premium
Browser
Chrome and IE 10
Other Info
5 Noctua case fans + 3 Noctua in p/p on NZXT cooler
Integrated hot swap drive bays for 2.5" Drives
(2) Lite-on dvd/cd/Blu Ray optical 22X
Integrated fan controller and led on/off
HP Officejet Pro 8630 all-n-one
Hot-swappable 3.5" hard drive bay
Netgear Nighthawk router
Asus USB 3 & sata 6 PCIe card
Vantec IDE to sata adptr./Ultra sata adptr
Lenovo L420 i5 lappy with m sata
Drobo 5N advanced NAS
Yea, there's no errors on any of them :/ and i'll look into that update add on thingy.
 

My Computer

OS
Windows 7 Ultimate x64
System Info:

Windows 7 Ultimate 64-bit SP1
AMD Phenom II X4 955 Black Edition
Gigabyte GA-970A-UD3
Corsair 2x2GB DDR3 1333MHz
XFX HD 6870 1GB GDDR5
Samsung SpinPoint F3 500GB

Sometimes it's happened randomly, two or 3 times it's when im shutting down.

The other day my system crashed whilst watching a youtube video, but i think that was something to do with the flash video options. - Though come to think of it, it has messed up whilst i was watching something in vlc before...

Could really do with some proper help, only just built this system for my birthday(mid august) :(.


These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
 

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
A blend of brains, brawn and dumb luck.
OS
Windows 7 Ultimate 64
CPU
i7 3770k OC'd 4.6 @ 1.17v, also FX 8120 & i5 miniITX
Motherboard
MSI P67A-GD80 b3
Memory
32 gb G.Skill Sniper DDR3 10-12-12-31 @ 2133
Graphics Card(s)
XFX Radeon 7870 2GB DDR5
Sound Card
Sound Blaster Z Series Card
Monitor(s) Displays
(2) LG LED 23" 1920 x 1080 2ms Monitors via mini d-port
Screen Resolution
1680 X 1050 p
Hard Drives
Samsung 256 gb 830 SSD sata III
(1) 1 tb WD Black
(2) 1 tb Hitachi deskmates/sata II
(2) 1 tb WD green/sata II
(2) 3 tb Seagate Barracuda
(1) 120 gb OCZ Vertex SS
(1) Drobo 5N w/5 Seagate 3tb
PSU
EVGA modular 1000G2 80% gold rating & APC 1200 RS
Case
CoolerMaster Storm Styker
Cooling
7 case fans 140mm & 120mm, NZXT Kraken X60
Keyboard
(2) Logitech Illuminated Keyboards (1) usb (1) wireless
Mouse
Logitech G700 & T-BC21 - nano nx for the laptop
Internet Speed
Basic 120mbps down
Antivirus
Trend Micro Titanium Max Security & Malwarebytes Premium
Browser
Chrome and IE 10
Other Info
5 Noctua case fans + 3 Noctua in p/p on NZXT cooler
Integrated hot swap drive bays for 2.5" Drives
(2) Lite-on dvd/cd/Blu Ray optical 22X
Integrated fan controller and led on/off
HP Officejet Pro 8630 all-n-one
Hot-swappable 3.5" hard drive bay
Netgear Nighthawk router
Asus USB 3 & sata 6 PCIe card
Vantec IDE to sata adptr./Ultra sata adptr
Lenovo L420 i5 lappy with m sata
Drobo 5N advanced NAS
You have some coming from you network so I would fix those drivers but the main ones are ntkrnlmp.exe which is linked mainly to hardware and hard to pinpoint without testing. I suggest running memtest86 via this guide:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\Windows_NT6_BSOD_jcgriff2\081111-29530-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032ac650
Debug session time: Wed Aug 10 12:49:23.771 2011 (UTC - 6:00)
System Uptime: 0 days 2:06:16.316
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff880015176a0, 2, 8, fffff880015176a0}

Unable to load image \SystemRoot\system32\DRIVERS\jswscimdx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for jswscimdx.sys
*** ERROR: Module load completed but symbols could not be loaded for jswscimdx.sys
Probably caused by : jswscimdx.sys ( jswscimdx+7869 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880015176a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880015176a0, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003316100
 fffff880015176a0 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisIMNotifyPnPEvent+0
fffff880`015176a0 48895c2408      mov     qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800a55e640 -- (.trap 0xfffff8800a55e640)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80050aa1a0
rdx=fffff8800a55e968 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015176a0 rsp=fffff8800a55e7d8 rbp=fffff8800a55e968
 r8=0000000000000000  r9=0000000000000000 r10=fffff880014f7ec0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ndis!NdisIMNotifyPnPEvent:
fffff880`015176a0 48895c2408      mov     qword ptr [rsp+8],rbx ss:0018:fffff880`0a55e7e0=fffff8800a55ebd4
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030e62a9 to fffff800030e6d00

FAILED_INSTRUCTION_ADDRESS: 
ndis!NdisIMNotifyPnPEvent+0
fffff880`015176a0 48895c2408      mov     qword ptr [rsp+8],rbx

STACK_TEXT:  
fffff880`0a55e4f8 fffff800`030e62a9 : 00000000`0000000a fffff880`015176a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0a55e500 fffff800`030e4f20 : fffff880`0150a010 00000000`0000005f 00000000`fd010109 fffffa80`05517270 : nt!KiBugCheckDispatch+0x69
fffff880`0a55e640 fffff880`015176a0 : fffff880`03f91869 fffff880`0a55ebd4 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0a55e7d8 fffff880`03f91869 : fffff880`0a55ebd4 00000000`00000000 00000000`00000001 fffffa80`05517270 : ndis!NdisIMNotifyPnPEvent
fffff880`0a55e7e0 fffff880`0a55ebd4 : 00000000`00000000 00000000`00000001 fffffa80`05517270 00000000`00000000 : jswscimdx+0x7869
fffff880`0a55e7e8 00000000`00000000 : 00000000`00000001 fffffa80`05517270 00000000`00000000 fffff880`0a55ea40 : 0xfffff880`0a55ebd4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
jswscimdx+7869
fffff880`03f91869 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  jswscimdx+7869

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: jswscimdx

IMAGE_NAME:  jswscimdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46d50821

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_jswscimdx+7869

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_jswscimdx+7869

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880015176a0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880015176a0, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS:  fffff880015176a0 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisIMNotifyPnPEvent+0
fffff880`015176a0 48895c2408      mov     qword ptr [rsp+8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800a55e640 -- (.trap 0xfffff8800a55e640)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80050aa1a0
rdx=fffff8800a55e968 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015176a0 rsp=fffff8800a55e7d8 rbp=fffff8800a55e968
 r8=0000000000000000  r9=0000000000000000 r10=fffff880014f7ec0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
ndis!NdisIMNotifyPnPEvent:
fffff880`015176a0 48895c2408      mov     qword ptr [rsp+8],rbx ss:0018:fffff880`0a55e7e0=fffff8800a55ebd4
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030e62a9 to fffff800030e6d00

FAILED_INSTRUCTION_ADDRESS: 
ndis!NdisIMNotifyPnPEvent+0
fffff880`015176a0 48895c2408      mov     qword ptr [rsp+8],rbx

STACK_TEXT:  
fffff880`0a55e4f8 fffff800`030e62a9 : 00000000`0000000a fffff880`015176a0 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0a55e500 fffff800`030e4f20 : fffff880`0150a010 00000000`0000005f 00000000`fd010109 fffffa80`05517270 : nt!KiBugCheckDispatch+0x69
fffff880`0a55e640 fffff880`015176a0 : fffff880`03f91869 fffff880`0a55ebd4 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x260
fffff880`0a55e7d8 fffff880`03f91869 : fffff880`0a55ebd4 00000000`00000000 00000000`00000001 fffffa80`05517270 : ndis!NdisIMNotifyPnPEvent
fffff880`0a55e7e0 fffff880`0a55ebd4 : 00000000`00000000 00000000`00000001 fffffa80`05517270 00000000`00000000 : jswscimdx+0x7869
fffff880`0a55e7e8 00000000`00000000 : 00000000`00000001 fffffa80`05517270 00000000`00000000 fffff880`0a55ea40 : 0xfffff880`0a55ebd4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
jswscimdx+7869
fffff880`03f91869 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  jswscimdx+7869

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: jswscimdx

IMAGE_NAME:  jswscimdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  46d50821

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_jswscimdx+7869

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_jswscimdx+7869

Followup: MachineOwner
---------
 

My Computer

Computer Manufacturer/Model Number
Alienware
OS
Windows 7 Ultimate x64
CPU
I7
Motherboard
GA-X58-USB3
Memory
6 x 1.5V DDR3 DIMM sockets supporting up to 24 GB of system
Graphics Card(s)
GeForce GTX 580
Sound Card
Realtek ALC892 codec 2/4/5.1/7.1-channel
Monitor(s) Displays
NEC Display Solutions E321 Black 32"
Screen Resolution
1366 x 768
Hard Drives
OCZ Colossus LT Series OCZSSD2-1CLSLT1T 3.5" 1TB SATA II MLC Internal Solid State Drive
PSU
XFX Black Edition XPS-850W-BES 850W ATX12V
Case
Antec
Cooling
Zalman
Keyboard
Microsoft
Mouse
Microsoft
Performed a memtest last night, ran 7 passes, no errors.

How do i go about fixing the driver errors?

Just had a A window pop up asking to send errors to windows, it said 2 of them were Video hardware errors ... :/
 
Last edited:

My Computer

OS
Windows 7 Ultimate x64
Hi Spoonerz did you enable driver verifier like zigzag suggested in his post? What we need to do first is find the guilty driver that is causing your problem and by enabling that it will cause your system to blue screen (which we want to happen) then you can upload the new .dmp files so we can take a closer look at what is causing the problem.

Thanks

Seth
 

My Computer

Computer Manufacturer/Model Number
Alienware
OS
Windows 7 Ultimate x64
CPU
I7
Motherboard
GA-X58-USB3
Memory
6 x 1.5V DDR3 DIMM sockets supporting up to 24 GB of system
Graphics Card(s)
GeForce GTX 580
Sound Card
Realtek ALC892 codec 2/4/5.1/7.1-channel
Monitor(s) Displays
NEC Display Solutions E321 Black 32"
Screen Resolution
1366 x 768
Hard Drives
OCZ Colossus LT Series OCZSSD2-1CLSLT1T 3.5" 1TB SATA II MLC Internal Solid State Drive
PSU
XFX Black Edition XPS-850W-BES 850W ATX12V
Case
Antec
Cooling
Zalman
Keyboard
Microsoft
Mouse
Microsoft
Okay i did the drivers part and it blue screened on start-up, couldn't boot to safe mode so used a system repair disk to do so, what do you suggest i do now?

Have a feeling i should restore and upload the new dump file but rather that rushing forward i'll wait for the people with experience to mak me some recommendations lol.

Also, from the previous post, not sure if it was seen, A window popped up asking to send errors to windows, it said 2 of them were video hardware errors.
 

My Computer

OS
Windows 7 Ultimate x64
Back
Top