Jump to content

Recommended Posts

Posted

Are you imaging or installing Windows 7 from new?

 

When deploying Windows 7 previously (I rarely do this now), USB 3.0 drivers sometimes caused issues. One easy/temporary workaround is to disable the USB 3.0 Controller in the BIOS where possible, then image.

Posted

Thanks.

 

We got 32 of these machines and so far I've seen it on 3 machines.:eek:

 

They came with windows 8 and we downgraded them to Windows 7 Pro. We used the cd that they supplied to downgrade them.

 

Does the dmp file mention the USB 3 issue? we do have usb 3 but at the back of the machine and we don't use them.

 

Thanks

Posted

Zoostorm :( Why do people subject themselves to such rubbish!

They often use sub-par components so it'll be worth swapping RAM around to see if that helps. Also check the mainboard manufacturers websites for drivers and use them rather than anything provided by either Zoostorm or Windows Update.

Posted

Is that 3 out of 3 fails. I would say return them. It's obvious the downgrade facility that they provide is not working.

 

If you want them on 7 I would clean install them rather than downgrade them. Cleaner and you know that the drivers installed are not conflicting win 7 with windows 8 drivers that would be still present after the downgrade

Posted

Thanks guys.

 

I have just checked all the drivers for update and the display adaptors ( Intel graphics 4600 ) was in fact out of date.

 

Hopefully this will fix the issue. Time will tell.:)

 

I haven't choose these machines I'm only installing them;)

 

When I wrote downgrade I actually meant we wipe them and installed Win 7 Pro so I think its a clean install.

 

Cheers

 

 

 

 

 

Im only

Posted

I use BlueScreenView to open .dmp files.

 

The log doesn't tell me a great deal, other than referring to NTFS - You will need to disable UEFI in the BIOS and Secure Boot (most likely) for Windows 7 to boot/install correctly.

Posted

Hey Thanks for the program.

 

Will check it out.

 

I haven't been in school much, tonsilitis:(

 

Our guy did a manual clean install on each of these pcs.

 

Haven't got any program for image deployment, usually they come with Win 7, but I guess not anymore:)

 

Thanks for the posts

Posted
Out of curiosity, does Windows 10 install on it OK (as a test), despite wanting to use Windows 7? It could give you an excuse to start looking at it.
Posted
Possibly a numpty question but I'm going to ask it anyhow :) Are you sure this isn't a memory module issue. I had some memory delivered recently and several sticks were duff and they caused the machines to BSOD.
Posted
Possibly a numpty question but I'm going to ask it anyhow :) Are you sure this isn't a memory module issue. I had some memory delivered recently and several sticks were duff and they caused the machines to BSOD.

 

It's definitely a possibility, as you're absolutely right that installing/imaging does stress the computer's hardware, including the system memory. I suppose the only reservation I have is several devices all behaving the same, it reduces the odds of it being hardware related.

Posted
All 120 of ours are having BSOD problems. It seems to be when the PC boots it gets to the login screen then BSOD it doesnt happen every boot though and sometimes it does it a few times before people can log in. I have done a memory test on one of them and that passed 12 tests so that one at least is ruled out. We are having mainly Memory management 0x1a, NTFS file system 0x24 and Page fault in nonpaged area 0x50 BSODs.
Posted
I had a similar issues with a couple of brand new i5s and it turned out that the graphics driver was the problem. In my case I had to roll back to a previous version and the crashing stopped.
Posted
All 120 of ours are having BSOD problems. It seems to be when the PC boots it gets to the login screen then BSOD it doesnt happen every boot though and sometimes it does it a few times before people can log in. I have done a memory test on one of them and that passed 12 tests so that one at least is ruled out. We are having mainly Memory management 0x1a, NTFS file system 0x24 and Page fault in nonpaged area 0x50 BSODs.

 

I had a similar issues with a couple of brand new i5s and it turned out that the graphics driver was the problem. In my case I had to roll back to a previous version and the crashing stopped.

 

I guess graphics issues can rarely cause BSODs - what graphics chip are in these? Intel HD? I presume you also are using Windows 7 on these too Jessica?

 

Windows 10 does handle graphics chips/drivers - especially the likes of Intel HD much, much better, as Intel have made a right hash of what drivers support which generations when an all in one driver would be easier.

Posted
Thanks :) We updated some of the graphics drivers yesterday and couldn't get them to blue screen anymore but this morning we have had another load of blue screens on the updated PCs. Now trying the USB 3 drivers.
  • Thanks 1
Posted
What does the plain bsod say? When we had the issue with bsods with our zoostorm machines, it was a chipset driver issue (running the Intel driver update as a local admin) seemed to resolve the issue, and updated in the build disk stopped future issues). Have also seen batches where the ram was faulty. Zoostorm are cheap, and tend to use unbranded ram and power, and slightly older chipsets, but at Tha price you cant grumble really. If you give them a call, they may well look at the dmp file for you if you have a load of machines with the same error

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...